<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>connected mobility - RiskInsight</title>
	<atom:link href="https://www.riskinsight-wavestone.com/en/tag/connected-mobility/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.riskinsight-wavestone.com/en/tag/connected-mobility/</link>
	<description>The cybersecurity &#38; digital trust blog by Wavestone&#039;s consultants</description>
	<lastBuildDate>Thu, 02 Jan 2020 14:05:26 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://www.riskinsight-wavestone.com/wp-content/uploads/2024/02/Blogs-2024_RI-39x39.png</url>
	<title>connected mobility - RiskInsight</title>
	<link>https://www.riskinsight-wavestone.com/en/tag/connected-mobility/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Saga 1/3: connected car: between cybersecurity and safety</title>
		<link>https://www.riskinsight-wavestone.com/en/2018/10/saga-13-connected-car/</link>
		
		<dc:creator><![CDATA[Qu3tinM4TYas]]></dc:creator>
		<pubDate>Thu, 25 Oct 2018 07:51:05 +0000</pubDate>
				<category><![CDATA[Cybersecurity & Digital Trust]]></category>
		<category><![CDATA[Manufacturing & Industry 4.0]]></category>
		<category><![CDATA[connected car]]></category>
		<category><![CDATA[connected mobility]]></category>
		<category><![CDATA[embbeded security]]></category>
		<category><![CDATA[IoT]]></category>
		<category><![CDATA[mobility]]></category>
		<category><![CDATA[regulation]]></category>
		<category><![CDATA[safety]]></category>
		<category><![CDATA[stakes]]></category>
		<guid isPermaLink="false">https://www.riskinsight-wavestone.com/?p=11369/</guid>

					<description><![CDATA[<p>The revolution is underway! The vehicles we drive will become ever-more connected and autonomous in the near future, something that will open the door to new uses. The user experience, in terms of mobility, will undoubtedly be better, but the...</p>
<p>Cet article <a href="https://www.riskinsight-wavestone.com/en/2018/10/saga-13-connected-car/">Saga 1/3: connected car: between cybersecurity and safety</a> est apparu en premier sur <a href="https://www.riskinsight-wavestone.com/en/">RiskInsight</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><em>The revolution is underway! The vehicles we drive will become ever-more connected and autonomous in the near future, something that will open the door to new uses. The user experience, in terms of mobility, will undoubtedly be better, but the services on offer will go hand -in-hand with new threats and new cybersecurity issues to be considered.</em></p>
<p><em>In this series, we’ll first present connected vehicles and their associated cybersecurity challenges; the main sources of threat and the risks will be addressed in a second installment. Lastly, a third article will present our views on the issue and the main lines of the response required to address it.</em></p>
<p>&nbsp;</p>
<h2>The connected car: a vehicle supporting a raft of interactions</h2>
<p>Entertainment, an extension of your smartphone, shared mobility, management of the car&#8217;s life cycle&#8230; users are demanding new experiences, and the services and applications they generate are resulting in a range of interactions. We can imagine a smart car being able to find a free parking space, automatically schedule an appointment for maintenance, or turn a traffic light green as it approaches. Since April 1, 2018, all new vehicle models must also have an emergency call system, as well as geolocalization to enable the authorities to be contacted in the case of an accident. In this respect, they are already &#8220;connected&#8221;.</p>
<p>Manufacturers and other players are already capitalizing on the opportunity to maintain a close relationship with customers throughout the vehicle life cycle. By doing this, they become &#8220;<strong>providers of services and mobility solutions</strong>,&#8221; drawing on, among other things, collected data. In particular, because such connectivity represents a step toward autonomy, the vehicle needs to be able to communicate with other vehicles and the surrounding environment. These changes are underway, and their pace will progressively increase.</p>
<p>However, the challenge of cybersecurity is scarcely taken into account, or ignored: yet it has to be a key plank of any connected solution—from the design phase to the end of the life cycle. Such thinking is essential to safeguarding the vehicle’s integrity, protecting passenger lives, and complying with current and future regulation.</p>
<p>The first prerequisite is to properly understand the connected vehicle&#8217;s technologies and ecosystem.</p>
<p>&nbsp;</p>
<h2>How connected vehicles interact with their environment</h2>
<p>A specific feature of a connected vehicle is that it interacts with its ecosystem, via mobile data streams, over both the short and long-ranges.</p>
<ul>
<li><strong>Short-range connections</strong>: Here, the vehicle interacts directly with an object (such as a smartphone, infrastructure, etc.), without any intermediary. It uses technologies with a limited range for local exchanges (WAVE, on-board Wi-Fi, Bluetooth, etc.).</li>
<li><strong>Long-range connections</strong>: Here, the vehicle uses remote access to interact with external components via a cloud platform. 4G, and soon 5G, connections are the technologies of choice for connecting vehicles to the internet.</li>
</ul>
<p>This connected-vehicle concept also covers exchanges with the vehicle’s direct environment under the umbrella term &#8220;Vehicle-to-Everything&#8221; (or V2X). Lastly, the standard, ISO 20077, covers &#8220;<strong>Extended Vehicles</strong>&#8221; (or ExVe) as a whole: which comprise the physical vehicle as well as all the platforms and infrastructures that the car manufacturer is responsible for.</p>
<p><img fetchpriority="high" decoding="async" class="aligncenter wp-image-10710" src="https://www.riskinsight-wavestone.com/wp-content/uploads/2018/05/image-1-395x191.png" alt="" width="600" height="290" srcset="https://www.riskinsight-wavestone.com/wp-content/uploads/2018/05/image-1-395x191.png 395w, https://www.riskinsight-wavestone.com/wp-content/uploads/2018/05/image-1-768x372.png 768w, https://www.riskinsight-wavestone.com/wp-content/uploads/2018/05/image-1-71x34.png 71w, https://www.riskinsight-wavestone.com/wp-content/uploads/2018/05/image-1.png 1405w" sizes="(max-width: 600px) 100vw, 600px" /></p>
<p>&nbsp;</p>
<h2>A range of ecosystems and players that need to work together</h2>
<p>The car was once a very closed system; with the exception of diagnostic connections for garages and some connectivity to be able to broadcast multimedia content; any connectivity risks were largely contained. Today, the proliferation of forms of connectivity and access to the internet have opened up new opportunities for manufacturers and service providers, but also for attackers.</p>
<p>The first ecosystem to consider is the . Electronic and communication systems must be able to communicate with each other without the transmitted data or stored secrets being altered or stolen. Among these systems are the ECUs, the mini &#8220;on-board computers&#8221; that control the vehicle’s key functions, such as the braking system, air conditioning, lighting, etc.</p>
<p>Beyond on-board security, there are the <strong>user and owner </strong>(the latter not necessarily an individual) who have the right to give orders to the vehicle according to pre-defined rules. In the future, their authentication will be essential when it comes to questions of responsibility, as well as for verifying the legitimacy of the orders they issue.</p>
<p>Another vitally important aspect concerns connected services that use centralized <strong>platforms</strong>, or even cloud-based ones, which have been developed by the manufacturers or their partners. These platforms represent a significant threat because they can trigger orders for entire fleets of vehicles, and therefore the impact of any problem is multiplied. Manufacturers will need to put in place sufficiently secure solutions to allow such services; they’ll need to combine their own platforms with those of partners and the APIs on the vehicle, as well as ensuring the required level of confidence in the environment.</p>
<p>Lastly, in the medium-term, <strong>external objects and the surrounding environment</strong> (other vehicles, garages, parking lots, road infrastructure, etc.) will need to communicate and share information. The challenges of ensuring security in real time (in terms of availability, integrity, etc.) will be complex ones.</p>
<p>&nbsp;</p>
<h2>Cybersecurity issues: from the virtual to the real world</h2>
<p>People’s safety, inside and outside vehicles, is a top priority for the automotive industry. We might imagine, then, that the cybersecurity issues raised by connected vehicles will be treated with the same degree of rigor—such that they can guarantee the car’s safety and integrity.</p>
<p>The first issue represents an <strong>organizational challenge</strong> for all stakeholders, especially manufacturers, because the emergence of this new model brings together two opposing worlds: <strong>services</strong> and <strong>engineering</strong>. The first is characterized by agility and speed, and large numbers of short-term projects. The second, with a much longer development cycle, must meet the safety and quality requirements associated with vehicle approval. This dichotomy has impacts on cybersecurity and, in particular, its integration into development projects, as well as the coverage of end-to-end risk. For example, as a result of its position, the backend becomes a nerve center that must be fully protected to avoid any risk of a systemic attack that could have repercussions for the entire fleet. Unfortunately, the true value of this need for security is not currently appreciated, mainly as a result of requirements for very short times to market.</p>
<p>Considering the other issues, it’s clear that the cybersecurity challenges for connected vehicles don’t differ greatly from those in the IS world: identity and access management, detection and response, the security of infrastructures, cryptography, third-party management, patch management, etc. A connected vehicle is a mobile IS, and numerous security standards (ISO2700x, NIST 800, etc.) have already been developed. These set out good practice in various guides and reference documents (SAE J3061, AUTOISAC, NHST, etc.) and the topic will shortly be covered to the ISO/SAE 21434 standard.<br />
However, a number of factors inherent to vehicles and their embedded systems mean that the topic needs to be considered from new and specific angles.</p>
<p>The vehicle’s <strong>mobility and connectivity</strong> make security more complex: security must be guaranteed where there is a limited connection, or no connection, and in the context of a changing environment. Regulatory aspects must not be ignored either, given that the vehicle may have to move between countries.</p>
<p>The world of <strong>on-board systems</strong> also places constraints on hardware—in terms of cost, computing power, and size.</p>
<p>Questions about updating components and services arise too, given that a system must be able to <strong>function at all times</strong> but may also be shut down for long periods.</p>
<p>Lastly, vehicles are designed for a <strong>long life cycle</strong>, which implies thinking about security from the start, especially when it comes to managing identities and accesses. This long life cycle also means considering evolving standards over time, as well as developing a model for updates that guarantees vehicle security in a way that is sustainable and manageable for constructors.</p>
<p>&nbsp;</p>
<p><em>The road ahead is long, and cybersecurity is approaching a crossroads that was not in view a decade ago. It’s vital that all players involved grasp the importance of what’s required and start to put in the effort now, before it’s too late.</em></p>
<p>Cet article <a href="https://www.riskinsight-wavestone.com/en/2018/10/saga-13-connected-car/">Saga 1/3: connected car: between cybersecurity and safety</a> est apparu en premier sur <a href="https://www.riskinsight-wavestone.com/en/">RiskInsight</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Saga 2/3: Connected cars… a path full of pitfalls (…and security holes)</title>
		<link>https://www.riskinsight-wavestone.com/en/2018/09/saga-23-connected-cars/</link>
		
		<dc:creator><![CDATA[Fl0r3ntD3LmoulY]]></dc:creator>
		<pubDate>Wed, 19 Sep 2018 08:20:23 +0000</pubDate>
				<category><![CDATA[Cybersecurity & Digital Trust]]></category>
		<category><![CDATA[Manufacturing & Industry 4.0]]></category>
		<category><![CDATA[connected car]]></category>
		<category><![CDATA[connected mobility]]></category>
		<category><![CDATA[cyberattack]]></category>
		<category><![CDATA[embedded security]]></category>
		<category><![CDATA[mobility]]></category>
		<guid isPermaLink="false">https://www.riskinsight-wavestone.com/?p=11261/</guid>

					<description><![CDATA[<p>The development of connected cars – and eventually autonomous cars – requires the presence of more and more software-driven electronic components in vehicles, as well as new interfaces allowing them to be connected to other devices and infrastructures. In a...</p>
<p>Cet article <a href="https://www.riskinsight-wavestone.com/en/2018/09/saga-23-connected-cars/">Saga 2/3: Connected cars… a path full of pitfalls (…and security holes)</a> est apparu en premier sur <a href="https://www.riskinsight-wavestone.com/en/">RiskInsight</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><em>The <a href="https://www.riskinsight-wavestone.com/en/2018/10/saga-13-connected-car/">development of connected cars – and eventually autonomous cars</a> – requires the presence of more and more software-driven electronic components in vehicles, as well as new interfaces allowing them to be connected to other devices and infrastructures. In a way, modern vehicles are becoming real computers on wheels.</em></p>
<p><em>Therefore, vehicles attack surface is becoming ever wider. They are then exposed to more and more risks which can jeopardize passengers’ safety but also the safety of people around vehicles under attack. Indeed, several researchers have already managed to perform different attacks on recent vehicles, and sometimes shown how to take full control of them. ​</em></p>
<p><em>What kinds of cyberattacks have been performed so far? What are the possible attack vectors? What could be the motives behind such cyberattacks?</em></p>
<p>&nbsp;</p>
<h2>A wide range of cyberattacks already performed on connected and autonomous cars…</h2>
<p>Over the last few years, several vulnerabilities have been discovered by researchers on connected vehicles. In particular two events gave rise to an important media response in 2015, bringing the topic to the forefront.</p>
<p>The first one was performed by American researchers Charlie Miller and Chris Valasek, who managed to <a href="https://www.wired.com/2015/07/hackers-remotely-kill-jeep-highway/">remotely hack a Fiat Chrysler car </a>and take control of many functionalities, from radio volume tuning to brakes activation. Their entry point was the Internet-connected feature Uconnect that was used in the car to control the vehicle&#8217;s entertainment and navigation system, enable phone calls and offer a Wi-Fi hot spot. By attacking this feature, they managed to reach an adjacent chip in the hardware used for the car&#8217;s entertainment system, and silently rewrite the chip&#8217;s firmware to plant their code. With this rewritten firmware, they were then able to send commands through the car&#8217;s internal network, known as CAN bus, to its physical components like the engine and wheels. Once this attack was presented by the researchers, Fiat Chrysler had to patch 1.4 million vehicles by sending USB sticks to all concerned customers so that they can manually fix the vulnerability in their vehicles.</p>
<p><a href="#_ftnref1" name="_ftn1"></a><img decoding="async" class="aligncenter wp-image-11254 size-full" src="https://www.riskinsight-wavestone.com/wp-content/uploads/2018/09/image1jpg.jpg" alt="" width="770" height="577" srcset="https://www.riskinsight-wavestone.com/wp-content/uploads/2018/09/image1jpg.jpg 770w, https://www.riskinsight-wavestone.com/wp-content/uploads/2018/09/image1jpg-255x191.jpg 255w, https://www.riskinsight-wavestone.com/wp-content/uploads/2018/09/image1jpg-768x576.jpg 768w, https://www.riskinsight-wavestone.com/wp-content/uploads/2018/09/image1jpg-52x39.jpg 52w" sizes="(max-width: 770px) 100vw, 770px" /></p>
<p style="text-align: center;"><em>© ANDY GREENBERG/WIRED</em></p>
<p>&nbsp;</p>
<p>Apart from cyberattacks that were made possible thanks to initial physical access or remote connection, others were <a href="https://www.wired.com/2016/08/hackers-fool-tesla-ss-autopilot-hide-spoof-obstacles/">also performed on sensors used in some cars to detect their surroundings</a>. For instance, in 2016, Chinese researchers showed how to attack the Tesla Model S through its different sensors: Millimeter Wave Radars (MMW Radars), LiDAR, cameras, ultrasonic sensors, etc. They presented different kinds of attacks such as:</p>
<ul>
<li>Jamming attack on MMW Radars: use of a transmitter tuned to the same frequency as the car’s receiving equipment, and with the same type of modulation, to override any signal at the car’s receiver. Thus, no signal is received by the car, meaning that if the sensor is used to detect obstacles for example, these ones can no longer be detected during the attack (“obstacle evaporation”).</li>
<li>Spoofing attack on ultrasonic sensors: use of a transmitter to create at a specific timing ultrasonic pulses with similar pattern as the ones of the car’s ultrasonic sensors to change the time of propagation. Thus, the distance between the car and the objects around it that is calculated by the sensors is no longer the real one during the attack.</li>
<li>Blinding attack on cameras: use of an LED spot or lasers to blind, or even cause permanent damage on cameras (permanent dead pixels).</li>
</ul>
<p>To sum up, researchers all around the world already managed to perform various cyberattacks on modern vehicles from different manufacturers, some of which are listed on the timeline below:</p>
<h2 id="post-11262 media-11262" class="align-none"><img decoding="async" class="aligncenter wp-image-11262 size-full" src="https://www.riskinsight-wavestone.com/wp-content/uploads/2018/09/image1.png" alt="" width="650" height="450" srcset="https://www.riskinsight-wavestone.com/wp-content/uploads/2018/09/image1.png 650w, https://www.riskinsight-wavestone.com/wp-content/uploads/2018/09/image1-276x191.png 276w, https://www.riskinsight-wavestone.com/wp-content/uploads/2018/09/image1-56x39.png 56w, https://www.riskinsight-wavestone.com/wp-content/uploads/2018/09/image1-245x170.png 245w" sizes="(max-width: 650px) 100vw, 650px" />6 main vectors to attack connected and autonomous vehicles…</h2>
<p><img loading="lazy" decoding="async" class="aligncenter wp-image-11252 size-full" src="https://www.riskinsight-wavestone.com/wp-content/uploads/2018/09/image2.png" alt="" width="974" height="639" srcset="https://www.riskinsight-wavestone.com/wp-content/uploads/2018/09/image2.png 974w, https://www.riskinsight-wavestone.com/wp-content/uploads/2018/09/image2-291x191.png 291w, https://www.riskinsight-wavestone.com/wp-content/uploads/2018/09/image2-768x504.png 768w, https://www.riskinsight-wavestone.com/wp-content/uploads/2018/09/image2-59x39.png 59w" sizes="auto, (max-width: 974px) 100vw, 974px" /></p>
<p>Today’s vehicles can connect to <strong>3G/4G</strong> networks and can provide <strong>Wi-Fi</strong> and <strong>Bluetooth</strong> access. These technologies are standard and present vulnerabilities: many different types of attacks on these networks are well known. One can easily imagine an opponent penetrating remotely the local network of the vehicle using these canals or performing a “Man-In-The-Middle” attack, in order to steal personal data, to alter some services or even to take control of the commands as shown previously.</p>
<p>In addition, it is possible to directly connect to the vehicle. All cars have <strong>ODB port</strong> for diagnostic purposes and most of the modern infotainment systems offer a <strong>USB port. </strong>It represents an open door for attackers to conduct malicious actions with serious consequences: blocking part or all the systems due to a ransomware, malicious frames sent to the CAN bus, alteration of ECUs due to malwares, etc.</p>
<p>With the advent of extended and autonomous vehicles, new types of attacks must also be considered. The automated drive relies on many kinds of sensors that are continuously <strong>interacting with the environment</strong> to collect information about roads, traffic, etc. Attacks affecting these <strong>sensors may have dramatic impacts</strong> and malicious people can deflect the primary functions of either the sensors or the road infrastructures to cause an accident. In the past, a fatal accident has occurred, showing that sensors are vulnerable and be a source of misinterpretationOne can say with certainty that the implementation of artificial intelligence within vehicles will result in more and more targeting this vulnerable part.</p>
<p>Finally, the vehicle is becoming a central point of connection with the <strong>internet of things</strong>. Services will be delivered from smartphones and external devices that will become new vectors to conduct an attack. For instance, authentication may fail or be compromised on the smartphone and can give an unlimited access to services on vehicles, allowing doors unlocking for instance.</p>
<p>According to the attack vector, attacks may be categorized and:</p>
<ul>
<li>Could affect a single vehicle or a whole fleet, which will increase the level of impact</li>
<li>Must be conducted close to the vehicle or can be realized remotely, which will change opponents’ capabilities and will contribute to increase the complexity of the attack because of the physical presence required or not.</li>
</ul>
<p>Sensors, IoT, public or private network, the extended vehicle is a concentrate of technologies. It represents a <strong>large playground </strong>for attacker ready to act! But why a person would attack a vehicle?</p>
<p>&nbsp;</p>
<figure id="post-11258 media-11258" class="align-none">
<figure id="post-11264 media-11264" class="align-none"><img loading="lazy" decoding="async" class="aligncenter wp-image-11264 size-full" src="https://www.riskinsight-wavestone.com/wp-content/uploads/2018/09/image5.png" alt="" width="706" height="564" srcset="https://www.riskinsight-wavestone.com/wp-content/uploads/2018/09/image5.png 706w, https://www.riskinsight-wavestone.com/wp-content/uploads/2018/09/image5-239x191.png 239w, https://www.riskinsight-wavestone.com/wp-content/uploads/2018/09/image5-49x39.png 49w, https://www.riskinsight-wavestone.com/wp-content/uploads/2018/09/image5-155x125.png 155w" sizes="auto, (max-width: 706px) 100vw, 706px" /></figure>
<p>&nbsp;</figure>
<h2>What would be the motives behind such cyberattacks?</h2>
<p>Motivations for the attackers could be diverse and varied. We have spotted 5 major categories:</p>
<ul>
<li>The first one is <strong>ideology</strong>: In the automotive context, several organization might intend to attack the vehicle. It could be an environmental group that wants to disclose a specific message (about air pollution for example), to cause a service outage, etc.</li>
</ul>
<ul>
<li>It could be simply<strong> financial</strong>: Some attacks could be very basic: to hack the infotainment system to gain access free of charge to musical streaming services for example.</li>
</ul>
<ul>
<li>Then, a third motivation could be <strong>destabilization</strong>: A state may want to destabilize another state by attacking a fleet of vehicle; a competitor may try to spoil the brand image of a car manufacturer, etc.</li>
<li>It could be also<strong> killing</strong>: The possibilities to take full control of the vehicle and to cause accidents with likely human fatalities could attract criminals or terrorists. It will have a dramatic impact on populations. In a near future, a fleet of vehicles could become a massive state weapon.</li>
<li>Then, the last one is<strong> attack capabilities procurement</strong>: Vehicles will become sophisticated systems with a great potential of computation. If a person finds a vulnerability, cars could become a way to spy citizens. Their performances could be also used for brute force attacks. They could be also turned into botnets to realize DDOS attacks.</li>
</ul>
<p>Current vehicles already offer many ways to connect with external systems which could present vulnerabilities: Bluetooth, Wi-Fi, USB, etc. With the development of autonomous cars, services platforms and connected road infrastructures, the attack surface is going to increase more and more, and impacts will become very serious. Therefore, car hacking will also appeal to many opponents.</p>
<p>It becomes urgent to adopt a granularity approach to secure vehicle vital functions and to guarantee the safety of passengers. Measures and organization are inspired from IT world, but they need to be adapted to the automotive context. For this purpose, start-ups can bring some answers to technical challenges and norms, such as the ISO21434 currently in development, intend to provide a worldwide framework to increase the resilience of connected vehicles. But what are concretely the solutions and how to protect vehicles from cyberattacks? Don’t put the car(t) before the horse, stay tuned, we will soon have a look on it!</p>
<p>Cet article <a href="https://www.riskinsight-wavestone.com/en/2018/09/saga-23-connected-cars/">Saga 2/3: Connected cars… a path full of pitfalls (…and security holes)</a> est apparu en premier sur <a href="https://www.riskinsight-wavestone.com/en/">RiskInsight</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
