Crisam Logo
  • CRISAM®
    CRISAM®
    • What is CRISAM®?
    • Method
    • Content
    • Customers
    • Academy
    • Webinars
    • Events
  • Areas of application
    Areas of application
    • Information Security Management
    • Integrated Risk Management
    • ESG
    • CRISAM® AI
    • Data Protection Management
    • Audit Management
    • Compliance Management
    • Business Continuity Management
    • Tax Compliance Management System
    • Project Risk Management
    • Legal Register
    • Conflicts of Interest Software
    • CRISAM® Legal Hold Software
  • Industries
    Industries
    • Automotive
    • Energy
    • Manufacturing
    • Financial Services
    • Retail
    • Real Estate & Construction
    • Healthcare
    • Broadcasting & Telecommunications
    • Technology
    • Transport & Logistics
  • More
    More
    • Download Center
    • CRISAM® Academy
    • Webinars
    • News
    • Jobs
    • CRISAM® Partners
    • Trust Center
    • Contact
  • en
    • en-gb
    • de
Request
  • Language
    • en-gb
    • de
  • CRISAM®
    • What is CRISAM®?
    • Method
    • Content
    • Customers
    • Academy
    • Webinars
    • Events
  • Areas of application
    • Information Security Management
    • Integrated Risk Management
    • ESG
    • CRISAM® AI
    • Data Protection Management
    • Audit Management
    • Compliance Management
    • Business Continuity Management
    • Tax Compliance Management System
    • Project Risk Management
    • Legal Register
    • Conflicts of Interest Software
    • CRISAM® Legal Hold Software
  • Industries
    • Automotive
    • Energy
    • Manufacturing
    • Financial Services
    • Retail
    • Real Estate & Construction
    • Healthcare
    • Broadcasting & Telecommunications
    • Technology
    • Transport & Logistics
  • More
    • Download Center
    • CRISAM® Academy
    • Webinars
    • News
    • Jobs
    • CRISAM® Partners
    • Trust Center
    • Contact
  • Request
Short answer Dates Who it applies to Requirements Implementation Comparison Getting started FAQ
Regulations and frameworks

Implementing UN R 155 and R 156: from management system to type approval

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

Book a demo View requirements
CRISAM®Sample values
☰Manufacturer Inc./ CSMS and SUMS
DASHBOARDS, maturity level per topic area
Processes and responsibility
89 %
Risk treatment
76 %
Supply chain
62 %
Software updates
54 %
6Vehicle types
2Certificates valid
1Renewal due
24Measures open
Vehicle types and status
TypeCategoryCSMSSUMS
Model series 1M1coveredcovered
Model series 2M1coveredin progress
Model series 3N1in progressin progress
Model series 4L3eplannedplanned
Short answer

What do UN R 155 and R 156 require?

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.

UN R 155Cyber Security Management System
UN R 156Software Update Management System
CertificateValid for no more than three years
ConsequencePrerequisite for type approval
Dates

What already applies and for whom it does not yet

For passenger cars and commercial vehicles, the deadline has already passed. For motorcycles and light vehicles, it is still running.

22 January 2021

UN R 156 enters into force

The regulation on the Software Update Management System takes effect.

1 Jul 2024

Deadline for categories M, N and O

Transitional provision of UN Regulation No. 155 for passenger cars, commercial vehicles and trailers.

10 January 2025

Version in the EU Official Journal

The version of UN R 155 published in the Official Journal of the European Union enters into force.

1 Jul 2029

Deadline for category L

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.

Who it applies to

Which vehicles are affected

The two regulations have different scopes. If you fall under both regulations, you also need two certificates.

Typical triggers

  • Type approval is coming up for a new vehicle type
  • The certificate of compliance expires in the foreseeable future
  • A manufacturer requires evidence from its supplier for the supplier's management system
  • Software updates are rolled out without a documented procedure for them
  • Cybersecurity processes exist per project, but not as an overarching system
  • A category L vehicle type is in development and the deadline is approaching

The scopes as worded

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.

Why it affects suppliers

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.

What happens on expiry

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.

Requirements

What a management system has to show

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

CSMS and SUMS in CRISAM®, step by step

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.

CRISAM®Sample values
☰Manufacturer Inc./ CSMS and SUMS
6Vehicle types
2Certificates valid
1Renewal due
3in preparation
VEHICLE TYPES, status per type
TypeCategoryECUsCSMSSUMS
Model series 1M184coveredcovered
Model series 2M179coveredin progress
Model series 3N162in progressin progress
Model series 4L3e18plannedplanned
Model series 5O29in progressplanned
Model series 6N257plannedplanned
ECUs per vehicle category
M1N1N2L3eO2

The management system is defined as an approach that defines processes, responsibilities and governance. The wizard guides you through exactly these three elements.

CRISAM®Sample values
✕Manufacturer Inc./ CSMS and SUMS
TypesSystemRisksSuppliersGapsAssessment
←Map management system

System and assignment

SYSTEM
Cyber Security Management System
SCOPE
All vehicle types of categories M and N
PROCESSES
37
GOVERNANCE
described
LINKED TO
Existing ISMS, Automotive Knowledge Pack
FURTHER REFERENCES
Software Update Management System, TISAX
NOTE
The processes are assigned per vehicle type so that the certificate covers the right scope
RESPONSIBLE
Head of Product Security
NEXT ASSESSMENT
31 May 2027
Three things, not one

Processes, responsibilities and governance carry equal weight in the definition. If you only describe processes, you deliver two thirds.

The scope belongs to the type

The 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 scratch

An existing information security management system already covers part of the processes. The link makes this visible.

AssignmentNEXT

The approach is risk-based. Threats to the vehicle are assessed and treated, and the effect of the treatment remains visible.

CRISAM®Sample values
☰Manufacturer Inc./ CSMS and SUMS
118Threats assessed
96with effective measures
24Measures open
7above the acceptance threshold
RISKS, gross vs. net per threat
ThreatTypeGrossMeasuresNetReviewed
Access via the cellular connectionModel series 1very high5 effectivemedium4 Sep 2026
Unauthorized software updateModel series 2very high4 effectivemedium4 Sep 2026
Manipulation via the charging processModel series 1high3 effectivelow21 Aug 2026
Misuse of diagnostic accessModel series 3high2 effectivemedium21 Aug 2026
Readout of vehicle dataModel series 2medium3 effectivelow12 Jun 2026
Attack via a supplier serviceallhigh1 effectivemediumoverdue
Distribution of net risks
Very highHighMediumLowVery low

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.

CRISAM®Sample values
☰Manufacturer Inc./ CSMS and SUMS
Supply chain queries18 entries
AllOpenPartialCompleteOverdue
Evidence for the powertrain control ECUSupplier A
Component31 Jul 2026complete
Procedure for software packagesSupplier B
Process31 Oct 2026partial
Signing and key managementSupplier C
Process30 Nov 2026partial
Reporting channel for vulnerabilitiesSupplier D
Process31 Dec 2026open
Evidence for the telematics unitSupplier A
Component30 Jun 2026complete
Evidence for the charge controllerSupplier E
Component31 Jan 2027open
123›

What was open at the last assessment becomes the worklist for the next one. Every gap is assigned to the affected requirement.

CRISAM®Sample values
☰Manufacturer Inc./ CSMS and SUMS
GAPS, maturity level per topic area
Processes and responsibility
89 %
Risk treatment
76 %
Supply chain
62 %
Software updates
54 %
Open requirements
RequirementSystemTopic areaDeadlineStatus
Procedure for emergency updatesSUMSSoftware31 Dec 2026open
Evidence from two suppliersCSMSSupply chain31 Jan 2027open
Fallback in case of a failed updateSUMSSoftware31 Mar 2027in progress
Post-delivery monitoringCSMSRisk30 Jun 2027in progress
Roles for release describedBothGovernance30 Sep 2026done
Open items
ItemImpactResponsible
One supplier without a reporting channel for vulnerabilitiesGap in the evidence for the supply chainPurchasing
Category L not yet in scopeDeadline approaching, no lead timeProduct Security

Before the assessment by the approval authority, you compile the status per topic area together with the associated documents.

CRISAM®Sample values
☰Manufacturer Inc./ CSMS and SUMS
Assessment preparationAs of Q3 2026
Processes and responsibility
Risk treatment
Supply chain
Software updates
requiredachieved
DocumentContentAs ofResponsibleStatus
Description of the system37 processes, roles, governance4 Sep 2026Product Securitycomplete
ScopeVehicle types and ECUs4 Sep 2026Engineeringpartial
Risk treatment118 threats with assessment4 Sep 2026Product Securitycomplete
Supplier evidence18 queries, responses documentedongoingPurchasingpartial
Procedure for software updatesRelease, rollout, fallbackunder revisionSoftwareunder review
Measures register24 open items with deadlineongoingDepartmentspartial
Product Security

Management system, risk treatment, assessment preparation.

Engineering

Scope per vehicle type, requirements for components.

Software and aftersales

Procedures for updates, release, fallback.

Purchasing and homologation

Supplier evidence, coordination with the approval authority.

Multi-Compliance

Two certificates, one management system

Cyber security and software updates are regulated separately, but they concern the same vehicle types, the same suppliers and the same processes.

Four frameworks in one model

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.

The processes come from engineering

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 path to the TISAX label

The required Information Security Assessment can be generated, exported and imported directly from CRISAM®. Learn more on the TISAX page.

85 building blocks as a starting point

The integrated Automotive Knowledge Pack provides over 85 building blocks and more than 650 control objectives, structured for the automotive industry.

Comparison

UN R 155, UN R 156 and ISO/SAE 21434

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 in practice

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.

Getting started

How to get started with CRISAM®

The first step depends on where you stand today.

Starting point A

The processes are defined, but not assigned to the vehicle types

Then you start with the scope. Vehicle types, ECUs and processes are linked in one model so that the certificate covers the right scope.

Starting point B

The renewal is coming up

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.

Starting point C

The supplier evidence is missing

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.

Book a demo
Frequently asked questions

Frequently asked questions about UN R 155 and R 156

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

References

Sources and status

The information on the two UN regulations on this page is taken from the versions published in the Official Journal of the European Union.

  • UN Regulation No. 155 in the version published in the Official Journal of the European Union, scope, definition of the Cyber Security Management System, certificate of compliance and transitional provisionsUN R 155
  • UN Regulation No. 156 in the version published in the Official Journal of the European Union, scope, definition of the Software Update Management System, certificate and entry into force on 22 January 2021UN R 156
  • International Organization for Standardization, ISO/PAS 5112:2022, with the note that elements of the Cyber Security Management System are based on the processes of ISO/SAE 21434Comparison

The information reflects the status of the cited sources as of the review date stated above.

Next step

No certificate, no type approval.

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.

Book a demo

No risk - let's just stay in touch!

Green phone icon for getting in touch.
Phone

+43 732 601 216-0

Green envelope icon representing email.
E-Mail

office@crisam.net

Green paper plane icon representing sending an email.
Newsletter

Register now

CRISAM GRC Software
Darstellung eines Trends im Risikomanagement

CALPANA business consulting GmbH

Blumauerstr. 45-47

4020 Linz, Austria

+43 732 601 216-0 sales@crisam.net

CALPANA business consulting Deutschland GmbH

Paul-Dessau-Str. 1

22761 Hamburg, Germany

+49 (40) 35 98 29 21 sales@crisam.net

CALPANA business consulting GmbH

Blumauerstr. 45-47

4020 Linz, Austria

+43 732 601 216-0 sales@crisam.net

CALPANA business consulting Deutschland GmbH

Paul-Dessau-Str. 1

22761 Hamburg, Germany

+49 (40) 35 98 29 21 sales@crisam.net
CRISAM®
  • What is CRISAM?
  • CRISAM® Method
  • CRISAM® Content
  • Customers
  • Academy
  • Webinars
  • Events
  • CRISAM® Academy
Operational area
  • Integrated Risk Management
  • Information Security Management
  • CRISAM® AI
  • ESG
  • Data Protection Management
  • Audit Management
  • Compliance Management
  • Business Continuity Management
  • Tax Compliance Management System
  • Project Risk Management
  • Legal Register
  • Conflicts of Interest Software
  • CRISAM® Legal Hold Software
Industries
  • Automotive
  • Energy
  • Manufacturing
  • Financial Services
  • Healthcare
  • Retail
  • Real Estate & Construction
  • Broadcasting & Telecommunications
  • Technology
  • Transport & Logistics
More
  • Download Center
  • CRISAM® Academy
  • Webinars
  • CRISAM® Partners
  • Jobs
  • News
  • Trust Center
  • Contact

© 2026 CALPANA business consulting GmbH. All rights reserved.

  • Imprint
  • Privacy
  • Trustcenter
linkedin
xing
Chartis Research Category LeaderChartis RiskTech Quadrant® for GRC Analytics 2025

You complete your registration on the next page. Unsubscribe at any time.

Please enter a valid email address.

Solutions

  • Risk management
  • Information & Cyber Security (ISMS)
  • Internal control system
  • Compliance Management
  • All solutions

Platform

  • Platform overview
  • CRISAM® AI
  • Reporting
  • Standards and frameworks

Resources

  • Success Stories
  • News
  • Webinars
  • Events
  • Careers

Kontakt

  • Österreich+43 732 601 216-0
  • Deutschland+49 40 35 98 29 21
  • E-Mailoffice@crisam.net
Live-Demo buchen

© 2026 CALPANA business consulting GmbH. All rights reserved.

CALPANA business consulting GmbH, Blumauerstraße 45-47, 4020 Linz, Österreich

CALPANA business consulting Deutschland GmbH, Paul-Dessau-Straße 1, 22761 Hamburg, Deutschland

  • Legal notice
  • Privacy
  • Trust Center
  • Cookie settings
  • GGovernanceStrategy & objectives

    • Strategic Management
    • Lean Management Systems
    • GRC Twins
    • Decision Intelligence
    • Policy Management

    Overview

    All solutions on one platform

    View all solutions

    RRiskRisk & resilience

    • Integrated Risk Management (IRM)
    • Project Risk Management
    • Information & Cyber Security (ISMS)
    • Business Continuity Management (BCM)
    • Supply Chain Security

    New: AI governance

    AI Governed Autonomy

    Steer and evidence critical AI decisions without slowing AI down.

    Explore the framework

    CComplianceCompliance & regulation

    • Legal Register
    • Data Protection Management
    • AI Management System
    • ESG Management
    • Internal Control System (ICS)
    • Audit Management
    • Compliance Management
    • Tax Compliance (TCMS)
    • Legal Hold
    • Conflicts of Interest
  • Features

    • CRISAM® platform overview
    • Reporting
    • Integrations
    • CRISAM® Method
    • Content
    • Onboarding & implementation
    • Trust Center

    Regulations & frameworks

    • DORA
    • NIS2
    • ISO/IEC 27001
    • GDPR
    • EU AI Act
    • CSRD
    • TISAX
    • ISO 22301
    All standards and frameworks covered

    Featured

    CRISAM® AI

    AI Risk Intelligence and AI Risk Assistance detect risks early and suggest measures.

    Discover CRISAM® AI
  • Industries

    • Financial services
    • Healthcare
    • Energy & utilities
    • Public sector
    • Automotive
    • Manufacturing
    • Transport & logistics
    • Retail & consumer goods
    • Real estate & construction
    • Broadcasting & telecommunications
    • Technology

    Teams

    • Risk management
    • CFO & CRO
    • CISOs & ISMS owners
    • CIO
    • Compliance
    • Internal audit & ICS
    • Data protection officers
    • ESG & sustainability
    • AI officers

    Customers

    • Success Stories

    Success Story

    Vossloh

    Vossloh

    How Vossloh AG introduced CRISAM® GRC to meet the requirements of IDW PS 340 (revised).

    Read the story
  • About CRISAM®

    • About us
    • Careers
    • Contact

    Partners

    • CRISAM® partners
    • CALPANA consulting
    • Become a partner
  • Resources

    • News
    • Download center
    • Academy

    Events

    • Events
    • Webinars

    Next date

    Corporate Risk Minds Europe 2026

    23 to 24 November 2026, Hotel Okura, Amsterdam

    Book an appointment
EN DE Login
Book a live demo
  • DE
Book a live demo
#RISK Meet CRISAM® at #RISK Expo Europe, ExCeL London, 10 to 11 November, Stand 13. Learn more
Corporate Risk Minds Europe 2026 Meet CRISAM® at Corporate Risk Minds Europe, stand 4, Hotel Okura Amsterdam, 23 to 24 November. Learn more