/// AUTOMOTIVE TESTING\\\


cyber arms race


Jonathan Newell talks to HORIBA MIRA about vehicle resilience and the battle for supremacy in the cyber-security arms race


(CAV) and while fully connected and fully autonomous cars are still a spot on the horizon, nonetheless every new car that comes on the market offers new levels of sophistication, connectivity and auton- omy at all levels.


T As this sophistication increases, so does


the potential threat to the security of the on-board computer systems. All computer and smartphone owners are aware of the threats that exist and mitigate against data loss with firewalls, security software and safe computing practices. But how does this trans- late to the vastly more complex computing environment of CAVs? To answer that question and put context


around the cyber-security of automotive products, UK automotive engineering consul- tancy, HORIBA MIRA, has just released a white paper “Why automotive security is different”. To discuss it in more detail, I spoke to An-


thony Martin, head of vehicle resilience tech- nologies and Paul Wooderson, chief engineer of the cyber security team at HORIBA MIRA.


Complexity at pace \\\ The white paper gives the reader some idea of


how vehicles are becoming more complex as a computing environment. Internal comput- ing power for engine management, vehicle control and external signal processing com- bine with advanced driver assist systems’ (ADAS) microprocessors and the sensor inputs that feed them. Vehicle-to-infrastructure (V2x) communications take the data workflow out- side the boundaries of the vehicle, connecting it to other sources of data (and threats). Regarding the quantity of data being pro- cessed, the report forecasts the vehicle’s sen- sor bandwidth alone will amount to 40Gbit/ second, equating to about 40TB of data pro- cessing every hour of operation. Low latency 5G communications for V2x will increase this flow potentially by orders of magnitude.


4 /// Test House Directory Extra \\\ 2021 In this environment, there is clear potential


for malicious activity that could compromise the operation of the vehicle. HORIBA MIRA recognised this threat early and has been working on vehicle resilience for a number of years.


Collaborative approach \\\ In 2019, the “ResiCAV” project was created in


partnership with other specialist organisa- tions including the Warwick Manufacturing Group and Thales. Backed by Innovate UK, the project created an actionable environment for tackling cyber-security threats to connected vehicles. The project is now in its second phase. According to Wooderson, the organisation


has in fact been working on vehicle cyber se- curity for 12 years. “It was initially started as a research project but its scope has increased as vehicles have become more connected.


There is more potential for things to go wrong as humans come further out of the loop,” he says.


More recently, regulatory frameworks have been put in place with both UNECE and ISO/SAE standards in place. However, as Mar- tin explains, regulations have been in devel- opment for about five years and are just a starting point. “Standards are the minimum requirements and individual manufacturers take different approaches based on risk. One of our tasks is to support them and offer a consultancy, test- ing and assessment service,” he says. He goes on to explain the approach HORIBA


MIRA takes: “Threats are analysed at a full sys- tem level. Vehicle manufacturing isn’t like a jigsaw where the whole is made up of the sum of the parts so the product must be analysed at the top level as there are often issues around system integration,” he says.


he automotive industry is bar- relling along the highway towards connected autonomous vehicles


Big guns join


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40