Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

IoT/Embedded Security

6/13/2017
11:20 AM
Michael Lynch
Michael Lynch
News Analysis-Security Now
50%
50%

Autonomous Cars Must Be Secure to Be Safe

All of the airbags and crumple zones in the world won't help if hackers can take control of self-driving cars. What can manufacturers do to keep these next-generation vehicles secure and safe?

Once a concept that existed solely in the realm of science fiction, self-driving cars are fast becoming reality. A report by Goldman Sachs predicts that by 2030, computer-controlled vehicles will make up 60% of US auto sales.

The past decade has seen a tremendous push by both car manufacturers and technology firms to transform cars into Internet-connected computers on wheels. According to a report from Navigant Research, Ford leads the pack with GM and Renault-Nissan following behind. Daimler, Waymo (owned by Google), Volkswagen, Tesla and Uber are also all in the hunt.

But, given these computers are going to control the operations of multi-ton vehicles that travel at high rates of speed across tremendous distances, it's worth asking: Are they safe?

With a number of automakers ramping up testing in 2017 and into 2018, the hope is that securing these vehicles is as much a priority as innovation and competition. But some recent tests are troubling.

A test by Kaspersky Lab on nine different Internet-enabled cars, which can be located, unlocked and started by their downloadable Android apps, found the programs lacked even basic software defenses. Without this protection in place, users' devices can be hijacked by hackers to locate and steal the vehicle.

Another example was a test where a Wired Magazine correspondent in a moving Jeep Cherokee had the vehicle manipulated by two test "hackers" who intentionally took over the control of the vehicle's dashboard, steering, brakes and transmission using a laptop located miles away to demonstrate how this could be done.

While these are simply tests, it's imperative to get the security right on these vehicles before they achieve widespread adoption. To prevent someone with malicious intent from gaining operational control over a self-driving car via a mobile phone, laptop, iPad or other device, or even to prevent the theft of the actual car, authenticating that the person trying to access the vehicle is who they say they are is critical.

The good news is auto and technology companies are taking steps to enhance the security of self-driving cars. Both Toyota and Ford are reported to be incorporating biometric authentication into their respective fleet by developing fingerprint sensors to function in place of the ignition key in future vehicles. Other companies are exploring the use of iris scan authentication using the car's rear-view mirror.

Such systems could potentially provide some protection against car theft or system breach. However, security authentication best practices dictate the use of multiple authentication factors and "defense in depth."

It will be interesting to see how multi-factor authentication (MFA) evolves in the automobile industry, and whether before someone is authorized to operate a vehicle, they must present a combination of multiple attributes -- either something they know (for example, a password), something in their possession (a particular, uniquely identifiable device like a mobile phone) or something intrinsic to their person (such as a fingerprint or voice biometric). Once a combination of these attributes is presented and verified, the person is then cleared to operate vehicle.

Further, defenses are necessary to potentially block unauthorized access to the operating system of the car itself. To protect against security threats and malicious attacks mentioned previously, self-driving cars are going to need to evaluate the trustworthiness of any person or device requesting operational control of the vehicle's operating system, and employ standard defenses against hacking, malware and unauthorized access.

All best practices in cyberdefense and authentication should be considered, since Internet-connected vehicles have a large attack surface with numerous vulnerabilities. Given the potential consequences, it's crucial to get security right on self-driving vehicles before they can become a plausible reality.

Related posts:

— Michael Lynch is InAuth's Chief Strategy Officer and is responsible for developing and leading the company's new products strategy, as well as developing key US and international partnerships. He brings two decades of experience in key roles within financial services, consulting and Fortune 500 companies, specializing in security and technology leadership.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/21/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-25596
PUBLISHED: 2020-09-23
An issue was discovered in Xen through 4.14.x. x86 PV guest kernels can experience denial of service via SYSENTER. The SYSENTER instruction leaves various state sanitization activities to software. One of Xen's sanitization paths injects a #GP fault, and incorrectly delivers it twice to the guest. T...
CVE-2020-25597
PUBLISHED: 2020-09-23
An issue was discovered in Xen through 4.14.x. There is mishandling of the constraint that once-valid event channels may not turn invalid. Logic in the handling of event channel operations in Xen assumes that an event channel, once valid, will not become invalid over the life time of a guest. Howeve...
CVE-2020-25598
PUBLISHED: 2020-09-23
An issue was discovered in Xen 4.14.x. There is a missing unlock in the XENMEM_acquire_resource error path. The RCU (Read, Copy, Update) mechanism is a synchronisation primitive. A buggy error path in the XENMEM_acquire_resource exits without releasing an RCU reference, which is conceptually similar...
CVE-2020-25599
PUBLISHED: 2020-09-23
An issue was discovered in Xen through 4.14.x. There are evtchn_reset() race conditions. Uses of EVTCHNOP_reset (potentially by a guest on itself) or XEN_DOMCTL_soft_reset (by itself covered by XSA-77) can lead to the violation of various internal assumptions. This may lead to out of bounds memory a...
CVE-2020-25600
PUBLISHED: 2020-09-23
An issue was discovered in Xen through 4.14.x. Out of bounds event channels are available to 32-bit x86 domains. The so called 2-level event channel model imposes different limits on the number of usable event channels for 32-bit x86 domains vs 64-bit or Arm (either bitness) ones. 32-bit x86 domains...