According to Juniper Research, 206 million vehicles will have embedded connectivity by 2025 — with 30 million vehicles utilizing 5G connectivity. The connected car now contains units for communication, in-voice assistant, geolocation sensors and cloud-platforms that connect vehicles to mobility services.
To ensure that these hyper-connected vehicles remain secure, a standard known as ISO SAE 21434 was developed. This standard is designed to guide automotive product developers and OEMs in following effective cybersecurity strategies and measures for connected vehicles. The status of ISO/SAE 21434 is currently ‘under development’, but it’s trending towards acceptance, which means it will be a part of compliance requirements in the near future.
An overview of ISO/SAE 21434
ISO/SAE 21434 is a standard co-developed by the International Standard of Organization (ISO) and the Society of Automotive Engineers (SAE). ISO SAE 21434 “Road vehicles — Cybersecurity engineering” focuses on cybersecurity risks in the design and development of car electronics. The standard covers cybersecurity governance and structure, secure engineering throughout the life cycle of the vehicle and post-production security processes.
The precursor to ISO/SAE 21434 is ISO 26262 “Road vehicles – Functional safety”. This does not cover software development or car sub-systems, nor does it cover how to deal with cybersecurity incidents.
ISO/SAE 21434 covers every aspect of cybersecurity — from initial design to end-of-life decommissioning of a vehicle. The supply chain is also included to cover each step in automotive production.
All phases of a connected vehicle’s lifecycle covering electrical and electronic systems, including their components and interfaces, are covered in ISO/SAE 21434 including:
- Design and engineering
- Operation by customer
- Maintenance and service
This lifecycle approach to cybersecurity management makes ISO/SAE 21434 one of the most comprehensive approaches to connected vehicle cybersecurity.
The impact of ISO/SAE 21434 on automotive OEMs and developers
Although the standard is still in development, any manufacturer, developer, or OEM should consider proactively integrating ISO/SAE 21434 into their current production process. The primary concern with the new standard revolves around cybersecurity. The standards focus on providing better safety to automotive consumers by regulating the way manufacturers test their products.
ISO/SAE 21434 requires that manufacturers and developers perform a risk assessment. Before you can identify risk, you need to know what causes it. An assessment will identify any component, API, or software function that could be vulnerable to attack. With the assessment done, you then identify vulnerabilities. Blackbox fuzzing scans the system to find potential vulnerabilities in the same way an attacker would scan your system. Using the right fuzzing tools, you can ensure that development is done with security as a priority.
The impact to automotive developers and manufacturers is that they have the benefit of producing applications and components that are tested before being launched, which benefits drivers and their safety. Fuzzing applications and finding vulnerabilities before they cause harm to drivers safeguards them and your organization’s reputation.
Why is ISO/SAE 21434 necessary for the automotive industry?
The automotive industry saw a 605% increase in cybersecurity incidents in connected cars between 2016 to 2019. The increase is surprisingly high, but threat actors targeting automotive computers is relatively new. Not only have more exploits been introduced in recent years, but the consequences in some successful attacks threaten the lives of drivers. Now that the industry has a framework to base its cybersecurity, testing for vulnerabilities during the vehicle’s lifecycle will be normalized. Standards also work together with other frameworks: in the case of ISO/SAE 21434, NIST SP-800-30 and standard ISO/IEC 31010 can be used to establish a foundation of risk assessment using tried and tested methodologies.
Improving your cybersecurity with testing
Good cybersecurity practices involve being proactive, and automotive developers and manufacturers can be proactive by integrating testing into their development lifecycle. Fuzzing an automotive computer is somewhat similar to a standard computer. The fuzzers launch tests against the automotive computer’s functionality attempting to trigger a vulnerability and exploit it. It’s done in a similar way an attacker launches an exploit, only testing performed as the product is developed can be used to improve cybersecurity rather than reactively patching a system using recalls.
Imagine a driver with a connected car experiences an attacker fuzzing the system for a buffer overflow. Specially crafted data is sent to the engine that runs on feedback from various components on the car. A buffer overflow has potential to shut down the engine. It would be a frightening experience for a driver to experience an engine shutdown while on the freeway, and this type of scenario is exactly what ISO/SAE 21434 tries to stop. By fuzzing an automotive computer during the development lifecycle, the manufacturer can avoid putting drivers in dangerous situations from lack of cybersecurity testing.
The automotive industry is at an important juncture in its history. The connected car is offering drivers an exciting new era in car ownership. But this expanded capability introduces cybersecurity risks that could threaten the safety of drivers. The ISO/SAE 21434 standard was introduced by automotive stakeholders to address the security issues that connectivity brings. The standard provides a framework for hardened security to build safer vehicles using better fuzzing and testing methodologies.
Need to get ISO/SAE 21434 compliant? Contact us to schedule a free demo of our automotive security testing tools.