Contents

UN R155 and the Cyber Security Management System (CSMS)

The regulation that made cybersecurity a condition for selling vehicles in the EU, UK, Japan and other UNECE markets — what a CSMS is and what the vehicle type approval requires.

Why it exists

Connected vehicles can be attacked remotely and at scale. Regulators under the UN’s WP.29 forum decided that manufacturers must prove they manage cybersecurity systematically — across development, production and the years a vehicle is on the road.

What it requires

  1. CSMS certificate for the organisation: processes to identify and manage cyber risks, monitor and respond to attacks, and manage suppliers. Valid for a limited period and audited.
  2. Vehicle type approval: for each vehicle type, evidence that risks were assessed (TARA), mitigations implemented and tested, and that the vehicle can be monitored and updated.

R155 applies to all new vehicles in the EU since July 2024, in Japan and other UNECE contracting parties, and in Great Britain for new types since June 2026.

How organisations implement it

Most use ISO/SAE 21434 as the process framework: governance, risk management, TARA, cybersecurity requirements, verification and validation, production, and post-development operations (vulnerability management, incident response).

Best practices

  • Treat the CSMS as a living process with clear ownership, not a one-time document set.
  • Include suppliers through cybersecurity interface agreements.
  • Connect field monitoring (VSOC) to engineering so that findings lead to fixes and updates.

Common pitfalls

  • Producing documents for the audit without changing engineering practice.
  • Forgetting multi-stage vehicles (trucks with body builders) where several parties share responsibility.

What it means for your discipline

  • Cybersecurity Core

    Builds and runs the CSMS, prepares the evidence for the type approval and coordinates the whole organisation.

  • E/E architecture Partial

    Must show that the vehicle type's architecture addresses the risks identified — security by design.

  • Diagnostics & lifecycle Partial

    Post-production monitoring, incident response and updates are part of the CSMS obligations.

  • Base software Partial

    Provides security controls (SecOC, secure boot, secure diagnostics) whose existence and testing must be evidenced.

  • Software update & OTA Partial

    Connects update delivery and SUMS processes with CSMS vulnerability management and incident response, providing evidence that security fixes reach affected vehicles.

No direct stake: Functional safety · HPC & application software · Hardware & silicon · Networks & communication

Where it sits in the software stack

Generic layered software of a central HPC (application processor with hypervisor, plus a safety island) and of a classic MCU-based ECU (AUTOSAR Classic). Highlighted modules matter for this topic. Click any module to open its page.

HPC · application processor (MPU) and safety island (MCU)
  • Security services — Implements risk-driven security controls and collects intrusion events for field monitoring and incident response.
  • Secure boot chain · TEE — Verifies boot software authenticity as a security control whose effectiveness must be demonstrated.
  • OTA client · UCM — Delivers security fixes and reports installation status to support vulnerability management.
  • Diagnostics — Restricts diagnostic access and exposes evidence needed to investigate security incidents.
MCU-based ECU · AUTOSAR Classic
  • Communication — Applies communication protections such as SecOC where the vehicle risk assessment requires them.
  • Diagnostics — Enforces diagnostic access controls and provides relevant fault evidence for security investigations.
  • Flash bootloader · secure boot — Authenticates boot and update software to address identified tampering risks.
  • Memory · crypto · WdgM — Provides cryptographic operations and protected key handling for security controls derived from the risk assessment.