Contents
StandardISO/SAE

ISO/SAE 21434

Road vehicles — Cybersecurity engineering

ISO/SAE 21434 defines how automotive teams manage cybersecurity risks throughout a vehicle’s lifecycle.

What it is

ISO/SAE 21434 is an automotive cybersecurity engineering standard. It establishes a framework for managing cybersecurity risks in vehicle electrical and electronic systems, their components and their interfaces, from concept through decommissioning. The full standard is paid; this page summarises its concepts. ISO’s standard overview

The central idea is to make protection decisions traceable: understand what could go wrong, decide which risks need treatment, define requirements and collect evidence that the resulting system meets them. Buying a security component alone does not establish that the vehicle’s risks have been addressed.

Who it applies to

Vehicle manufacturers and suppliers use the standard when developing and supporting automotive E/E systems. Work can span a complete vehicle, a controller, a software platform or a supplied component. Responsibilities and assumptions must remain clear across those boundaries.

Cybersecurity engineers coordinate the process, while system architects and implementation teams supply the technical detail. Production, purchasing, service and operational teams also contribute: a protection mechanism can fail if keys are provisioned incorrectly or field vulnerabilities have no responsible owner.

The standard is not itself a vehicle type-approval regulation. Its applicability to a supplier’s delivery should be established through the project scope, customer requirements and agreed responsibilities.

What it covers

The lifecycle approach connects organisational capability with project engineering and continuing support.

Activity Engineering purpose
Planning and supplier coordination Assign responsibilities, activities and expected evidence.
Threat Analysis and Risk Assessment (TARA) Identify potential damage, threats and attack paths; assess risk and decide its treatment.
Concept and development Derive cybersecurity goals and requirements, allocate controls and verify implementation.
Validation Evaluate whether the cybersecurity goals are achieved in the intended context.
Production and operations Preserve protections during manufacture, monitor vulnerabilities and respond to relevant findings.
End of support and decommissioning Address remaining cybersecurity responsibilities and affected assets.

It does not prescribe one universal technical solution. Secure boot, authenticated messages, protected diagnostic access and hardware-backed keys are possible controls whose suitability depends on the analysis.

How it fits with other documents

UN R155 establishes regulatory requirements concerning vehicle cybersecurity and the Cyber Security Management System (CSMS). ISO/SAE 21434 provides an engineering framework that can support the evidence needed for that work. Following the standard does not automatically establish regulatory approval.

ISO 26262 addresses functional safety. Teams should exchange relevant findings because an attack can affect safety-related functions, while safety mechanisms may rely on cybersecurity assumptions.

ISO 24089 addresses software update engineering. ISO/SAE 21434 contributes cybersecurity risk analysis and requirements for update activities and affected systems. Technical specifications such as AUTOSAR SecOC and Uptane address particular mechanisms; they do not replace lifecycle risk management.

In practice

For a zone controller, begin by describing its functions, external interfaces, assets and operating assumptions. Analyse scenarios such as unauthorised diagnostic commands or malicious traffic crossing a gateway.

Use the findings to derive justified requirements: which messages need authentication, who may invoke sensitive services, and which software must be verified before execution. Allocate each requirement to an owner and define how to verify it.

Keep the reasoning alongside the implementation evidence. Revisit it when interfaces, software, suppliers or threat information change. A useful project record explains why each protection exists, how its effectiveness was checked and who handles relevant vulnerabilities after release.

What it means for your discipline

  • CybersecurityCore

    Own the cybersecurity engineering process, TARA, risk-treatment decisions and supporting evidence. Coordinate vulnerability management throughout the supported lifecycle.

  • E/E architecturePartial

    Define system boundaries, interfaces and trust assumptions so risks can be analysed. Allocate cybersecurity requirements across vehicle systems and suppliers.

  • Functional safetyPartial

    Exchange information about attacks that could cause hazardous behaviour. Coordinate safety and cybersecurity analyses when assumptions or protective measures interact.

  • Base softwarePartial

    Implement allocated protections in platform services, such as secure boot, cryptographic services and access control. Provide evidence that configuration and integration satisfy cybersecurity requirements.

  • HPC & application softwarePartial

    Translate cybersecurity requirements into software design, implementation and verification. Assess vulnerabilities in applications, operating systems and dependencies.

  • Hardware & siliconPartial

    Provide hardware protection appropriate to the identified risks, including protection of keys and debug interfaces. Document hardware capabilities and limitations for system-level analysis.

  • Networks & communicationPartial

    Use risk analysis to justify communication protection, segmentation and gateway policies. Verify that network integration preserves the intended protection boundaries.

  • Diagnostics & lifecyclePartial

    Derive requirements for diagnostic authentication, authorisation and service access. Account for workshop, manufacturing and field-service use cases.

  • Software update & OTAPartial

    Assess threats to update activities and the cybersecurity effects of software changes. Support vulnerability remediation with verified updates and traceable release decisions.