Highlights from the recent Auto-ISAC Conference
At the eighth annual Auto-ISAC Cybersecurity Summit this month, NHTSA Deputy Administrator Sophie Shulman emphasized the importance of cybersecurity in the automotive industry, highlighting October as National Cybersecurity Awareness Month. She praised Auto-ISAC for fostering a collaborative environment where information sharing strengthens the industry’s defense against cyber threats and maximizing vehicle safety.
Proactive approach is needed
NHTSA’s robust research program underpins its policies and includes projects on vehicle electrical and electronics architecture, zero trust for in-vehicle networks, wireless battery management systems, and over-the-air updates. These projects aim to enhance cybersecurity and resilience in modern vehicles.
The speaker discussed the complexities of achieving cyber resiliency in modern vehicles, which incorporate diverse technologies and wireless connectivity that increase attack surfaces. A proactive approach to cybersecurity was stressed, guided by principles from NIST: anticipate, withstand, recover, and adapt. Collaboration across the federal government, including contributions from NHTSA, is crucial for securing the automotive supply chain and protecting against adversary threats.
In 2015, the first-ever cybersecurity safety recall, known as the “Jeep Hack,” led to the recall of 1.4 million vehicles after ethical security researchers discovered a system defect. Since then, NHTSA has monitored over 75 vehicle cybersecurity incidents.
Defect verified in NHTSA’s Lab
A recent case involved an aftermarket device leading to another recall. The case is an example of safety vulnerabilities that could arise from a non-safety related system. NHTSA’s Cybersecurity Lab verified a report by white-hat researchers, regarding an aftermarket device with wireless connections which uses telematics for electronic data logging.
The recalled device interfaces with the vehicle’s databus, such that a compromised device – such as leaking of keys used to authorize software updates – could ultimately be used as a proxy to stall the vehicle: An unauthorized third party could reprogram the unit and allow malicious actors to spoof communication packets.
Fortunately, the device was recalled (140,000 affected units) before the defect could be exploited.
Could this recall have been prevented?
Karamba’s XGuard is designed to prevent attackers from tampering with device firmware – including replacing the ECU’s firmware with a reprogrammed copy of the code. Such tampering becomes much harder to do with XGuard security controls in place.
The device configuration and program flow are recorded at build time to set up security controls at the binary level, without interfering with R&D, so that any deviation from intended behavior is detected and flagged as a potential threat. In Linux operating systems, allow lists of legal executables, as well as safeguarding of cryptographic keys, further minimize the attack surface. When needed, XGuard protection can be added – bolt-on – to legacy architectures.
Read the full NHTSA keynote address here.