UN R155 compliance: CSMS, type approval, and ISO/SAE 21434 explained

What automakers and suppliers need for UN R155 type approval, and how ISO/SAE 21434 fits

Key takeaway

UN Regulation No. 155 (UN R155) requires vehicle manufacturers to operate a certified cyber security management system (CSMS) and to prove that each vehicle type is protected against cyber risks before it receives type approval. ISO/SAE 21434:2021 is the engineering standard widely used to meet it. R155 has applied to all new vehicles in the European Union (EU) since July 7, 2024, and to new vehicle types in Great Britain since June 1, 2026.

What is UN R155?

UN R155 is the first internationally harmonized, binding regulation on vehicle cybersecurity, according to the United Nations Economic Commission for Europe (UNECE). The UNECE World Forum for Harmonization of Vehicle Regulations (WP.29) adopted R155 on June 24, 2020, and the regulation entered into force on January 22, 2021.

The CSMS belongs to the manufacturer’s organization, not to the vehicle, and must cover development, production, and post-production. R155 requires two approvals:

  • A CSMS certificate of compliance for the manufacturer, valid for up to three years (R155 paragraph 6.7).
  • A cybersecurity type approval for each vehicle type, based on a risk assessment, proportionate mitigations, testing, and attack detection and response (R155 paragraph 7.3).

R155 covers passenger and goods vehicles (Categories M and N), trailers fitted with at least one electronic control unit (ECU) (Category O), and, under the amended text, Category L vehicles. VicOne’s products support both approval layers, as the map below shows.

UN R155 compliance: CSMS, type approval, and ISO/SAE 21434

How do UN R155 and ISO/SAE 21434 relate?

UN R155 is a regulation that sets legally binding conditions for vehicle type approval. ISO/SAE 21434:2021 (Road vehicles: Cybersecurity engineering) is a voluntary engineering standard, published on August 31, 2021, by the International Organization for Standardization (ISO) and SAE International, that specifies cybersecurity risk management across the vehicle lifecycle without prescribing technologies.

Most manufacturers and suppliers build their CSMS on ISO/SAE 21434 and use its work products, such as threat analysis and risk assessment (TARA), as audit evidence. Conforming to the standard supports R155 compliance but does not replace the CSMS certificate or type approval. VicOne’s own development processes are certified to ISO/SAE 21434 by DEKRA.

When does UN R155 apply? Key dates

RequirementDate
UNECE
R155 adopted by WP.29June 24, 2020
R155 enters into forceJanuary 22, 2021
European Union
R155 mandatory for new vehicle typesJuly 6, 2022
R155 mandatory for all new vehiclesJuly 7, 2024
Great Britain
R155 for new types of complete and base vehiclesJune 1, 2026
R155 for new completed vehiclesJune 1, 2028
China
New vehicle typesParallel national standard GB 44495-2024January 1, 2026
All vehiclesParallel national standard GB 44495-2024January 1, 2028

Vehicles already on the road are not retrofitted, but in the EU every new vehicle registered after July 7, 2024, must comply, including vehicles built to older type approvals. Japan also applies R155 through the UNECE 1958 Agreement. VicOne’s xAurient threat intelligence maps threats to UN R155 and ISO/SAE 21434 for teams tracking these markets.

How UD Trucks uses xNexus for UN R155

To meet UN R155, UD Trucks set up a product security incident response team (PSIRT). It selected VicOne's xNexus vehicle security operations center (VSOC) platform and integrated it into that process. xNexus gives the team real-time, actionable threat insights, and UD Trucks reports that they are reflected directly in its design process. UD Trucks expects this to shorten its software innovation cycle and help it meet the conditions for UN R155 certification.

VicOne's industry-leading AI and curated automotive threat intelligence deliver the insights we need: accurate and actionable.
Ryota Kawano, Manager of ERM Cybersecurity at UD Trucks

How do you comply with UN R155? A 6-step approach

The following six steps provide a practical implementation approach. They are not a substitute for the applicable UN R155 requirements or the approval authority's assessment.

  1. Map your markets and vehicle categories, and choose your approval authority or technical service.
  2. Build a CSMS on ISO/SAE 21434 that covers governance, risk management, supplier management, monitoring, and incident response.
  3. Run a TARA for each vehicle type that covers the threats listed in R155 Annex 5, and keep it current as new vulnerabilities emerge.
  4. Manage supplier risk through cybersecurity interface agreements, supplier evidence, and a software bill of materials (SBOM) for each ECU.
  5. Verify and test your mitigations, for example through penetration testing.
  6. Monitor, detect, and respond to attacks across the fleet after production, typically through a vehicle security operations center (VSOC).

VicOne supports steps 3 through 6 with live TARA, SBOM and vulnerability management, penetration testing, and fleet monitoring.

Why doesn’t compliance equal cybersecurity?

610automotive-related security incidents in 2025
1,384automotive-related vulnerabilities in 2025

A CSMS certificate shows that processes existed at the time of the audit, not that a vehicle can withstand attacks discovered later. New vulnerabilities keep emerging after approval: VicOne’s 2026 Automotive Cybersecurity Report, published February 2026, counted 610 automotive-related security incidents and 1,384 vulnerabilities in 2025. That is why R155 requires post-production monitoring and response, and why VicOne pairs continuous vulnerability intelligence with in-vehicle detection and fleet monitoring.

How does VicOne help OEMs and Tier 1 suppliers comply with UN R155?

VicOne, an automotive and Physical AI cybersecurity company and a Trend Micro subsidiary, helps OEMs and Tier 1 suppliers produce and maintain the evidence that R155 and ISO/SAE 21434 require. Beyond its DEKRA ISO/SAE 21434 certification, VicOne holds Automotive SPICE® (ASPICE) Capability Level 2 and a Trusted Information Security Assessment Exchange (TISAX®) Assessment Level 3 label.

R155 requirementVicOne capability
Requirement-to-solution map
Manage vulnerabilities in vehicle and supplier softwareR155 paragraph 7.2xZETAVulnerability and SBOM management covering known, undisclosed, and zero-day vulnerabilities
Keep risk assessment currentR155 paragraph 7.2Live TARAIntegrations with SystemWeaver and Saphira that feed xZETA intelligence into TARA tools
Verify and test mitigationsR155 paragraph 7.3xScopePenetration testing aligned with UN R155 and ISO/SAE 21434, backed by the Trend Zero Day Initiative (ZDI)
Detect attacks on the vehicleR155 paragraph 7.3xCarbonIn-vehicle intrusion detection and prevention system (IDPS)
Monitor and respond across the fleetR155 paragraphs 7.2 and 7.3xNexusVSOC platform for monitoring, detection, response, and forensics
Track the threat landscapeR155 Annex 5xAurientAutomotive threat intelligence mapped to UN R155 and ISO/SAE 21434

OEMs use VicOne to manage supplier software risk and monitor their fleets (OEM solutions), and Tier 1 suppliers use VicOne to deliver SBOMs, vulnerability status, and test evidence to their customers (Tier 1 solutions).

Frequently asked questions about UN R155

Do Tier 1 and Tier 2 suppliers need their own UN R155 approval?

No. Type approval and the CSMS certificate go to the vehicle manufacturer. Suppliers are usually required by contract to provide cybersecurity evidence such as TARA inputs, SBOMs, vulnerability status, and test results.

How do I comply with automotive cybersecurity regulations in 2026?

Build a CSMS on ISO/SAE 21434, keep a TARA for each vehicle type, manage supplier risk, test your mitigations, and monitor your fleet after production. The key new 2026 deadline is in Great Britain, where R155 has applied to new vehicle types since June 1, 2026.

Is ISO/SAE 21434 mandatory, and is it the same as UN R155?

No. ISO/SAE 21434 is a voluntary standard, while UN R155 is required for type approval in the markets that apply it. The standard helps manufacturers build the CSMS and evidence R155 requires but does not replace type approval.

What is the difference between ISO/SAE 21434 and IEC 62443?

ISO/SAE 21434 covers cybersecurity engineering for road-vehicle electrical and electronic (E/E) systems and applies to vehicle development. The International Electrotechnical Commission (IEC) 62443 series covers industrial automation and control systems, such as factories, not in-vehicle systems.

Sources: UN Regulation No. 155 (UNECE; EUR-Lex 2021/387; amended R155 text, OJ L 2025/5); UNECE press release of June 24, 2020; ISO/SAE 21434:2021 (iso.org/standard/70918); Great Britain SI 2025/1110.

Accelerate Your Automotive and Physical AI
Cybersecurity Journey Today

Request a Demo →