In our overview of ISO 26262 and ISO 21434 we called the two standards siblings: one protects the vehicle against random failure, the other against deliberate attack. This article takes the cybersecurity sibling on its own, because since UN R155 made cybersecurity a type approval requirement, ISO 21434 has stopped being optional reading. If your vehicle has a connected function, and every modern electric vehicle does, this standard now sits on the critical path to the market.
Snelle antwoorden
- What is ISO 21434? ISO/SAE 21434 is the international standard for cybersecurity engineering of road vehicles, covering the whole lifecycle from concept to decommissioning
- Is it mandatory? The standard itself is voluntary, but UN R155 requires a certified Cybersecurity Management System for type approval, and ISO 21434 is the accepted way to demonstrate one
- What is a TARA? Threat Analysis and Risk Assessment: the structured exercise that identifies what an attacker could do to your vehicle and how much that matters
- Who must comply? OEMs seeking type approval in UNECE markets, and by contractual extension their suppliers, including battery, inverter and telematics suppliers
Why a cybersecurity standard for vehicles exists
A modern heavy vehicle is a rolling network: dozens of control units on CAN and Ethernet, a telematics unit with a SIM card, over-the-air update capability, and a charging port that speaks ISO 15118 with off-board infrastructure. Every one of those is an interface, and every interface is a potential entry point. The automotive industry learned this the public way, through demonstrated remote attacks on production vehicles, and the regulatory answer arrived in two layers: UN R155 for the legal requirement, ISO 21434 for the engineering method.
What the standard actually requires
ISO 21434 does not prescribe firewalls or encryption algorithms. It prescribes a process, organised around a simple demand: know your risks, treat them deliberately, and keep doing so for the life of the vehicle. In practice the work falls into four blocks.
Organisational: a cybersecurity policy, defined responsibilities, and competence management. Risicoanalyse: the TARA, where you enumerate assets (the brake-by-wire function, the battery management commands, the driver’s personal data), identify threat scenarios, rate feasibility and impact, and decide a treatment. Engineering: cybersecurity requirements flowing into design, implementation and verification, including penetration testing where the risk justifies it. Operations: monitoring for new vulnerabilities, an incident response process and secure update paths after the vehicle ships.
Readers familiar with functional safety will recognise the shape of this immediately: the TARA is the cybersecurity cousin of the HARA, and cybersecurity goals decompose into requirements exactly as safety goals do. Teams that already run an ISO 26262 process can extend it rather than build a parallel universe, which is the single biggest efficiency lever we know of.
ISO 21434 and UN R155: standard versus law
Aspect | ISO/SAE 21434 | UN R155 |
Nature | Engineering standard, voluntary | Regulation, condition for type approval |
Demands | Cybersecurity engineering process per project | Certified Cybersecurity Management System (CSMS) plus vehicle type assessment |
Audience | Engineering teams, OEMs and suppliers | Approval authorities and OEMs |
Relation | The accepted evidence that the CSMS is real | The reason the evidence is demanded |
The practical chain: the approval authority asks for R155, R155 asks for a working CSMS, and ISO 21434 is how you show one. For software updates the same pattern repeats with UN R156 and its update management system. A vehicle type approved today in the EU must satisfy both.
A realistic route for smaller teams
The standard was written with global OEMs in mind, but the principle scales down honestly. A converter or scale-up does not need a security operations centre; it needs a right-sized TARA, a supplier questionnaire that asks for cybersecurity evidence the same way it asks for EMC evidence, hardened defaults on every connected interface, and a named person who owns vulnerability monitoring. In our experience the TARA workshop for a typical heavy-duty platform is days of work, not months, provided the system architecture is documented. The expensive version of cybersecurity is the retrofitted one.
The supply chain dimension: nobody complies alone
A vehicle builder can write a flawless TARA and still fail the audit through its suppliers, because the standard explicitly spans the supply chain. The instrument for this is the cybersecurity interface agreement: a documented split, per component, of who performs which cybersecurity activity, who monitors which vulnerabilities, and how incident information flows in both directions. In practice this becomes a procurement artefact: the request for quotation for a telematics unit, an inverter or a charging stack should ask for ISO 21434 evidence and an interface agreement the same way it asks for EMC and safety evidence. Suppliers serious about the vehicle market have this paperwork ready; a supplier who cannot produce it is quoting you a future audit finding along with their hardware. For converters the same logic points upstream: the base vehicle manufacturer holds part of your evidence, and the moment to secure access to it is at purchase, not at approval.
What an assessment finds, typically
After enough ISO 21434 gap assessments a pattern emerges, and sharing it saves readers a consulting invoice. The most common gap is not technical but organisational: no named owner for cybersecurity, so evidence exists in pockets and nobody can present the whole. Second: a TARA that was done once, beautifully, and never updated when the architecture changed, which makes it worse than useless in an audit because it documents the wrong vehicle. Third: supplier blind spots, where the telematics unit or charging stack arrived with no cybersecurity evidence and no contractual right to demand any. Fourth: debug and diagnostic services still enabled in production software, the finding that penetration testers cherish most. None of these require exotic fixes; all of them require someone to look.
The audit itself, whether by an approval authority’s technical service or a customer, follows the standard’s own logic: show the policy, show the TARA, walk one risk from identification through requirement to verification evidence, and demonstrate the monitoring and response process with a real example. A team that can walk that path in an afternoon is compliant in every way that matters; the certificate then documents reality instead of aspiration.
Cybersecurity meets the test floor
Security requirements only become real when they are verified. On the campus we combine document-level assessment with hands-on interface testing, from charging communication to telematics, so the CSMS file describes a vehicle that was actually probed, not just modelled.
1. What is ISO 21434 in simple terms?
It is the standard that tells vehicle builders how to engineer cybersecurity: analyse what an attacker could do, design defences proportionate to the risk, verify them, and keep watching after the vehicle ships.
2. Is ISO 21434 certification mandatory?
The standard is voluntary, but UN R155 compliance is mandatory for type approval in UNECE markets, and authorities accept ISO 21434 conformity as the evidence for the required management system.
3. What is the difference between ISO 21434 and ISO 26262?
ISO 26262 protects against random hardware and systematic faults; ISO 21434 protects against deliberate attack. They share the same engineering culture and are usually run by the same team.
4. What is a TARA in automotive?
Threat Analysis and Risk Assessment: the structured identification of assets, threat scenarios, attack feasibility and impact, leading to risk treatment decisions. It is the heart of an ISO 21434 project.
5. Does ISO 21434 apply to off-road and heavy-duty vehicles?
UN R155 formally targets road vehicle categories, but connected off-road machines carry the same attack surfaces, and buyers increasingly demand the same evidence. Engineering-wise the standard applies without modification.
OVER DE AUTEUR
IntegratR Ingenieursteam
EMC & e-mobiliteit engineering, Innovatiecampus Nijmegen
IntegratR runt een zware EMC-testfaciliteit en engineeringsteam op de Innovation Campus in Nijmegen, Nederland. Het team brengt emissievrije voertuigen en machines van prototype naar gecertificeerd, en werkt samen met OEM's, Tier-1-leveranciers en scale-ups in heel Europa. Artikelen worden geschreven vanaf de testvloer, niet vanuit theorie.