Standards · Automotive cybersecurity

ISO/SAE 21434 — Road vehicles, cybersecurity engineering

Published in 2021 by ISO and SAE International, ISO/SAE 21434 governs the cybersecurity of the electrical and electronic systems of road vehicles, from concept to end of support. For IT security, it extends the approach of ISO 26262.

Autonomous driving — connected embedded systems
The stakes

More code, more attack surface

A recent vehicle carries around 100 million lines of code, and an autonomous vehicle up to 300 million. Connectivity, over-the-air updates, diagnostic interfaces: every function added widens the attack surface.

Cybersecurity is not added at the end of a project, nor “tested in” afterwards: it is designed in, and must be addressed at every step of the life cycle, at the vehicle manufacturer as at its suppliers.

UN Regulation No. 155 requires vehicle manufacturers to have a cybersecurity management system; ISO/SAE 21434 is commonly used as the reference to implement it.

Digital instrument cluster
Requirements

What the standard requires

ISO/SAE 21434 covers the whole life cycle: organization, project, concept, development, validation, production, operations and maintenance, end of support. Four areas directly concern software.

Threat analysis

TARA

Threat Analysis and Risk Assessment identifies the assets to protect, the attack scenarios, their impact and their feasibility, then decides how each risk is treated.

Clause 10

Product development

Cybersecurity specifications, design and verification. The standard cites static analysis among the verification methods (10.4.2) and requires coding guidelines, such as MISRA C or CERT C, for aspects not covered by the language itself (RQ-10-05).

Clause 11

Validation

Demonstrating, at vehicle level, that the cybersecurity goals are achieved and that no unreasonable risk remains.

Supply chain

Suppliers and reuse

Cybersecurity interface agreements with suppliers, assessment of their capabilities, control of reused and third-party components, made visible by the software bill of materials (SBOM).

Implementation

Securing the code, and demonstrating it

Part of the vulnerabilities lies in the source code: secure coding rules not followed, unchecked data flowing from an interface to a sensitive point, areas of complexity where defects hide. Static analysis detects them early, before testing, and at every change.

TiCS brings together the results of your analyzers — security static analysis, MISRA C or CERT C rule checking, compiler warnings, complexity — in a single dashboard, and tracks them over time.

  • Deviations from the coding rules by component, by rule and by severity.
  • Quality gates in the integration pipeline: no new violation enters the main branch.
  • Justified deviations, approved by a second person and kept.
  • History useful for the cybersecurity case and for audits.

Software composition analysis and the SBOM it produces complete this setup for third-party and open-source components.

TiCS orchestrates and aggregates the analyses: detection remains the job of the analyzers in your configuration. It replaces neither the threat analysis and risk assessment nor the validation required by the standard: it provides their continuous, dated measurement on the code side.

Discover TiCS → Evaluate TiCS on a pilot repository

Automotive powertrain
TiCS on video

Deviations, ready for the audit

ISO/SAE 21434 requires you to keep a record of cybersecurity decisions. The animation shows how a deviation from the coding rules is justified, approved by a second person and kept, ready for the audit.

The 14 TiCS animations →
Gearbox Dashboard instruments Truck on the highway
Functional safety

ISO 26262

The functional safety standard for road vehicles: ASIL levels and the structural coverage required, up to MC/DC.

See the ISO 26262 page →

Other standards

The standards landscape

DO-178C, EN 50716, IEC 60880, IEC 61508, IEC 62304, IEC 62443, ISO 26262: each standard sets its own requirements.

See all standards →