What it is
UN R155 is a vehicle type-approval regulation with two linked requirements: a certified Cyber Security Management System (CSMS) and cybersecurity evidence for the vehicle type. The CSMS establishes organizational processes; vehicle approval examines their application to a particular design. A CSMS certificate alone does not approve every vehicle.
Who it applies to
The vehicle manufacturer holds responsibility for approval. Suppliers contribute information and evidence through the manufacturer’s supply chain. Approval authorities and technical services assess compliance.
The regulation’s scope includes vehicle categories L, M, N and O when fitted with an electronic control unit. These broadly cover powered two- and three-wheelers and quadricycles, passenger vehicles, goods vehicles and trailers. Local legislation determines which categories and approval routes are mandatory in a particular market; engineers should establish applicability for their project.
What it covers
The CSMS covers development, production and post-production. Vehicle evidence includes risk assessment, implemented mitigations and testing. Annex 5 identifies threats and corresponding mitigations to consider, including risks involving communications, software, external connections and supporting infrastructure. Detection, response and forensic information also form part of the requirements. These obligations are described in the published regulation.
For engineering work, translate those obligations into questions that have owners and reviewable answers:
| Engineering question | Useful project evidence |
|---|---|
| How could an attacker reach a sensitive function? | Interface inventory and attack-path analysis |
| Why is the chosen protection sufficient? | Risk rationale and security requirements |
| Does the protection work? | Verification results and resolved findings |
| Who acts when a weakness appears in service? | Response responsibilities and an exercised workflow |
How it fits with other documents
Use ISO/SAE 21434 as an engineering framework for organizing cybersecurity activities and evidence. Keep a mapping from its work products to the applicable UN R155 requirements; a standards-based process should not be treated as automatic regulatory approval.
Coordinate with UN R156 for software-update management. For example, an update campaign may need both evidence of secure delivery and evidence that the update process meets its separate approval obligations.
Implementation specifications sit below these management and approval requirements. AUTOSAR SecOC, secure boot, authenticated diagnostics, network filtering and Uptane can contribute to a security design. Select them against assessed attack paths and system constraints rather than treating a technology list as proof of compliance.
In practice
Start with a vehicle boundary diagram and an inventory of interfaces, connected services and supplier responsibilities. Build a traceable chain from each assessed risk to a requirement, implementation decision and verification result.
For example, consider a diagnostic operation that can change ECU software. Review who can invoke it, how authorization is established, how credentials are protected and what happens after repeated failed attempts. Test the complete access path, including gateways and service tools.
Agree early on what suppliers must deliver and who reviews it. Before release, walk through a realistic field vulnerability: identify affected vehicles, assign investigation ownership, evaluate corrective action and retain the decision evidence. This turns the approval dossier into a working engineering record.