Without a valid certificate, there is no type approval. The two regulations require not only secure vehicles, but also a management system that has to be confirmed again after no more than three years. The effort therefore arises not in the individual project, but in the organization.
As of: 23 September 2026
| Type | Category | CSMS | SUMS |
|---|---|---|---|
| Model series 1 | M1 | ||
| Model series 2 | M1 | ||
| Model series 3 | N1 | ||
| Model series 4 | L3e |
UN Regulation No. 155 governs the approval of vehicles with regard to cybersecurity and a Cyber Security Management System. It defines this system as a systematic, risk-based approach that defines organizational processes, responsibilities and governance to treat risks from cyber threats to vehicles and to protect vehicles from cyberattacks.
UN Regulation No. 156 requires the same for software updates: a Software Update Management System, meaning a systematic approach that defines organizational processes and procedures to meet the requirements for delivering software updates. For both systems, the approval authority issues a certificate of compliance that is valid for no more than three years.
For passenger cars and commercial vehicles, the deadline has already passed. For motorcycles and light vehicles, it is still running.
The regulation on the Software Update Management System takes effect.
Transitional provision of UN Regulation No. 155 for passenger cars, commercial vehicles and trailers.
The version of UN R 155 published in the Official Journal of the European Union enters into force.
Transitional provision for motorcycles and light vehicles. Manufacturers in this segment still have time, but should plan implementation early enough.
The dates are taken from the versions of the two regulations published in the Official Journal of the European Union. We do not state an earlier entry into force of UN R 155, because on EUR-Lex only the entry into force of the version published there could be verified.
The two regulations have different scopes. If you fall under both regulations, you also need two certificates.
UN Regulation No. 155 applies to vehicles of categories L, M, N and O that have at least one electronic control unit. UN Regulation No. 156 applies to vehicles of categories M, N, O, R, S and T that permit software updates.
Under UN Regulation No. 155, the vehicle manufacturer must hold a valid certificate of compliance for its Cyber Security Management System for the vehicle type to be approved. What it has to demonstrate for this, it passes on to its supply chain.
The certificate is valid for no more than three years and can be renewed or withdrawn. For UN Regulation No. 156, it is expressly stated that existing type approvals do not lose their validity solely because the manufacturer's certificate expires.
Eight points that matter in the assessment by the approval authority and again at every renewal.
| Requirement | System | What matters | How you map it in CRISAM® |
|---|---|---|---|
| Define processes | CSMS | The system is defined as an approach that defines organizational processes, responsibilities and governance. If these three elements are missing, there is nothing to assess | The integrated Automotive Knowledge Pack provides over 85 building blocks and more than 650 control objectives against which you can align your own processes. |
| Take a risk-based approach | CSMS | The approach is expressly risk-based. Measures without a recognizable link to risk are not convincing in the assessment | Risks can be identified and assessed in a structured way using wizards, qualitatively or quantitatively. The gross and net view shows what the measures achieve. |
| Treat threats | CSMS | What is treated are risks from cyber threats to vehicles, with the aim of protecting vehicles from cyberattacks | Threats are assigned to components and interfaces, measures to the threats. Compliance gaps and deviations are identified transparently. |
| Involve the supply chain | Both | A large share of the evidence lies with suppliers. The manufacturer must be able to obtain and assess it | Information can be collected from subject matter owners in a targeted, decentralized way. This reduces the effort for baseline audits, reviews and supplier inquiries. |
| Track software versions | SUMS | The system defines organizational processes and procedures to meet the requirements for delivering software updates | Requirements and evidence are assigned to the same objects as the components, each open item with an owner and a deadline. |
| Manage measures | Both | Every gap needs an owner and a deadline, otherwise it will still be open at the next assessment | Measures are planned, implemented and monitored with workflow support, including responsibilities and deadlines. |
| Renew the certificate | Both | The certificate is valid for no more than three years and can be withdrawn if the requirements are no longer met | The status per topic area is available at any time, instead of being collected again before every renewal. Dashboards show compliance status, deviations and measures. |
| Hand over documents to the authority | Both | What counts is which documents the approval authority receives, not what is stored in the system | Reports for audits and customer inquiries as well as export functions for assessments and audits are available. |
From the vehicle types to the documents for the approval authority.
At the start, you define which vehicle types the system has to cover. Certificates, deadlines and evidence are later tied to them.
| Type | Category | ECUs | CSMS | SUMS |
|---|---|---|---|---|
| Model series 1 | M1 | 84 | ||
| Model series 2 | M1 | 79 | ||
| Model series 3 | N1 | 62 | ||
| Model series 4 | L3e | 18 | ||
| Model series 5 | O2 | 9 | ||
| Model series 6 | N2 | 57 |
The management system is defined as an approach that defines processes, responsibilities and governance. The wizard guides you through exactly these three elements.
Processes, responsibilities and governance carry equal weight in the definition. If you only describe processes, you deliver two thirds.
The scope belongs to the typeThe certificate must apply to the vehicle type to be approved. That is why the scope is tied to the types and not to a department.
Do not start from scratchAn existing information security management system already covers part of the processes. The link makes this visible.
The approach is risk-based. Threats to the vehicle are assessed and treated, and the effect of the treatment remains visible.
| Threat | Type | Gross | Measures | Net | Reviewed |
|---|---|---|---|---|---|
| Access via the cellular connection | Model series 1 | 5 effective | 4 Sep 2026 | ||
| Unauthorized software update | Model series 2 | 4 effective | 4 Sep 2026 | ||
| Manipulation via the charging process | Model series 1 | 3 effective | 21 Aug 2026 | ||
| Misuse of diagnostic access | Model series 3 | 2 effective | 21 Aug 2026 | ||
| Readout of vehicle data | Model series 2 | 3 effective | 12 Jun 2026 | ||
| Attack via a supplier service | all | 1 effective | overdue |
The manufacturer must also be able to provide evidence for the supply chain. Queries are sent out decentrally and evaluated centrally, so responses do not get lost in email folders.
What was open at the last assessment becomes the worklist for the next one. Every gap is assigned to the affected requirement.
| Requirement | System | Topic area | Deadline | Status |
|---|---|---|---|---|
| Procedure for emergency updates | SUMS | Software | 31 Dec 2026 | |
| Evidence from two suppliers | CSMS | Supply chain | 31 Jan 2027 | |
| Fallback in case of a failed update | SUMS | Software | 31 Mar 2027 | |
| Post-delivery monitoring | CSMS | Risk | 30 Jun 2027 | |
| Roles for release described | Both | Governance | 30 Sep 2026 |
| Item | Impact | Responsible |
|---|---|---|
| One supplier without a reporting channel for vulnerabilities | Gap in the evidence for the supply chain | Purchasing |
| Category L not yet in scope | Deadline approaching, no lead time | Product Security |
Before the assessment by the approval authority, you compile the status per topic area together with the associated documents.
| Document | Content | As of | Responsible | Status |
|---|---|---|---|---|
| Description of the system | 37 processes, roles, governance | 4 Sep 2026 | Product Security | |
| Scope | Vehicle types and ECUs | 4 Sep 2026 | Engineering | |
| Risk treatment | 118 threats with assessment | 4 Sep 2026 | Product Security | |
| Supplier evidence | 18 queries, responses documented | ongoing | Purchasing | |
| Procedure for software updates | Release, rollout, fallback | under revision | Software | |
| Measures register | 24 open items with deadline | ongoing | Departments |
Management system, risk treatment, assessment preparation.
Scope per vehicle type, requirements for components.
Procedures for updates, release, fallback.
Supplier evidence, coordination with the approval authority.
Cyber security and software updates are regulated separately, but they concern the same vehicle types, the same suppliers and the same processes.
In addition to TISAX, requirements from UN R 155 and 156, ISO/SAE 21434 and IATF 16949 can be mapped and evaluated in a structured way.
According to ISO, elements of the management system are based on the processes of ISO/SAE 21434. If you document carefully there, you already have part of the evidence.
The required Information Security Assessment can be generated, exported and imported directly from CRISAM®. Learn more on the TISAX page.
The integrated Automotive Knowledge Pack provides over 85 building blocks and more than 650 control objectives, structured for the automotive industry.
The two UN regulations require management systems and lead to a certificate that is valid for no more than three years. ISO/SAE 21434 does not require a certificate, but provides the processes: according to ISO, elements of the Cyber Security Management System are based on the processes of this standard. If you have to meet all three, you can use the same objects for them.
| Criterion | UN R 155 | UN R 156 | ISO/SAE 21434 |
|---|---|---|---|
| Subject matter | Approval of vehicles with regard to cybersecurity and a Cyber Security Management System | Approval of vehicles with regard to software updates and a Software Update Management System | Cybersecurity engineering for electrical and electronic systems |
| Scope | Vehicles of categories L, M, N and O with at least one electronic control unit | Vehicles of categories M, N, O, R, S and T that permit software updates | Electrical and electronic systems in road vehicles |
| What is required | A systematic, risk-based approach with processes, responsibilities and governance | A systematic approach with processes and procedures for delivering updates | Terms, objectives, requirements and guidelines for engineering |
| Binding nature | Mandatory where the regulation is applied | Mandatory where the regulation is applied | Voluntary, but regularly required in the supply chain |
| What you end up with | A certificate of compliance, valid for no more than three years | A certificate of compliance, valid for no more than three years | Evidence of cybersecurity engineering |
| Link to type approval | The manufacturer must hold a valid certificate for the vehicle type to be approved | Existing type approvals do not lose their validity solely because the certificate expires | No direct link to type approval |
| Mapping in CRISAM® | As processes, risks and evidence per vehicle type | Using the same objects, supplemented by the procedures for updates | As requirements and risks for components and interfaces |
What matters is not which requirement is the strictest, but whether the scope is right. The certificate must apply to the vehicle type that is to be approved. If you align your management system with a department instead of the vehicle types, you often notice this only at the assessment. You can find an overview of all frameworks under Standards and frameworks.
The first step depends on where you stand today.
Then you start with the scope. Vehicle types, ECUs and processes are linked in one model so that the certificate covers the right scope.
Then what matters is that the status is available at any time. Dashboards show compliance status, deviations and measures, without having to collect the data again before every assessment.
Then the decentralized query is the next step. Information can be collected from subject matter owners in a targeted way, which reduces the effort for baseline audits, reviews and supplier inquiries.
For this you need the CRISAM® GRC Platform, the CRISAM® ISMS Module and the Automotive Knowledge Pack. In the demo, we discuss your starting point and show which of these you already have in place.
UN Regulation No. 155 governs the approval of vehicles with regard to cybersecurity and a Cyber Security Management System. It defines this system as a systematic, risk-based approach that defines organizational processes, responsibilities and governance to treat risks from cyber threats to vehicles and to protect vehicles from cyberattacks.
Under UN Regulation No. 156, it is a systematic approach that defines organizational processes and procedures to meet the requirements for delivering software updates under this regulation. The regulation applies to vehicles of categories M, N, O, R, S and T that permit software updates.
UN R 155 applies to vehicles of categories L, M, N and O that have at least one electronic control unit. The transitional provisions state 1 Jul 2024 for categories M, N and O and 1 Jul 2029 for category L.
The two UN regulations require management systems and lead to a certificate that is valid for no more than three years. ISO/SAE 21434 does not require a certificate, but provides the processes: according to ISO, elements of the Cyber Security Management System are based on the processes of this standard. If you have to meet all three, you can use the same objects for them.
No more than three years. It is issued by the approval authority and can be renewed. If the requirements are no longer met, it can be withdrawn. For UN Regulation No. 156, it is stated that existing type approvals do not lose their validity solely because the certificate expires.
Under UN Regulation No. 155, the vehicle manufacturer must hold a valid certificate of compliance for the vehicle type to be approved. What it has to demonstrate for this, it passes on to the supply chain through contracts and queries. For suppliers, the regulation is therefore felt in the form of evidence requirements.
In CRISAM®, information can be collected from subject matter owners in a targeted, decentralized way. This considerably reduces the effort for baseline audits, reviews and supplier inquiries, because every response is linked directly to the associated requirement.
What matters is whether vehicle type, process, risk and evidence are linked in one shared model. CRISAM® maps and evaluates the requirements from VDA TISAX as well as from UN R 155 and 156, ISO/SAE 21434 and IATF 16949 in a structured way, identifies compliance gaps and deviations, and provides more than 85 building blocks and over 650 control objectives through the integrated Automotive Knowledge Pack.
The information on the two UN regulations on this page is taken from the versions published in the Official Journal of the European Union.
The information reflects the status of the cited sources as of the review date stated above.
In the demo, we walk through your case: vehicle types and scope, processes and responsibilities, risk treatment, evidence from the supply chain and the documents for the assessment.
You are currently viewing a placeholder content from Facebook. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou need to load content from reCAPTCHA to submit the form. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Hubspot Embedded Content. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from HubSpot. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Hubspot Meetings. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Instagram. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from X. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More Information