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
- 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.
- 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.