UN Regulation 156: Vehicle Software Update Management

UNECE WP.29 UN Regulation No. 156 — Software Updates and Software Update Management System

International

RAI-IO-UNECE-R156-2021

Regulation No. 156

Effective: 22 Jan 2021
In Force(In Force)Checked 9 Sep 2026

UN Regulation 156: Vehicle Software Update Management is In Force in International as of 9 Sep 2026.

RegulationSafety, Testing, and EvaluationRisk Management
Export PDF

UN Regulation No. 156 mandates that vehicle manufacturers establish a Software Update Management System to ensure safe, secure, and traceable automotive software updates, as adopted by UNECE WP.29 in 2020. The international regulation entered into force on January 22, 2021, binding manufacturers under the 1958 Agreement.

Summary

UN Regulation No. 156, adopted by UNECE WP.29, establishes uniform provisions for managing software updates in vehicles. It mandates that manufacturers implement a robust Software Update Management System (SUMS) to ensure updates are secure, safe, and traceable throughout a vehicle's lifecycle. This regulation is crucial for maintaining vehicle integrity, cybersecurity, and compliance with safety standards in an era of increasingly software-dependent vehicles.

Full article

Read full text ↗

Overview

UN Regulation No. 156, developed by the UNECE World Forum for Harmonization of Vehicle Regulations (WP.29), establishes uniform provisions concerning the approval of vehicles with regard to software updates and software update management systems. This international regulation aims to ensure that software updates for vehicles are managed securely, safely, and in a traceable manner throughout the vehicle's lifecycle. It addresses the increasing complexity of modern vehicles, which rely heavily on software for various functions, including safety-critical systems, advanced driver-assistance systems (ADAS), and infotainment. The regulation mandates that vehicle manufacturers implement a robust Software Update Management System (SUMS) as a condition for type approval, thereby extending regulatory oversight beyond the initial production phase to cover the entire operational life of a vehicle. This proactive approach is vital in an era of software-defined vehicles, where vulnerabilities can emerge post-sale, impacting safety, security, and environmental performance. R156 seeks to build consumer trust by ensuring that vehicles remain secure and compliant even as their software evolves.

The scope of UN Regulation No. 156 encompasses all software updates, regardless of whether they are delivered over-the-air (OTA) or through traditional physical means at service centers. It applies to updates that affect type-approval-relevant systems or are delivered wirelessly, ensuring that the integrity, authenticity, and safety of the vehicle are maintained. This regulation is particularly crucial in the context of connected and automated vehicles, where software vulnerabilities could pose significant safety and security risks, potentially leading to unauthorized access, data breaches, or critical system failures. By requiring a structured approach to software update management, R156 seeks to mitigate these risks, protect vehicles from cyberattacks, and ensure continued compliance with safety and environmental standards even after initial sale, thereby safeguarding both vehicle occupants and other road users.

Definitions

Key definitions within UN Regulation No. 156 are fundamental to understanding its application and requirements. A central concept is the 'Software Update Management System (SUMS),' which refers to the organizational framework and processes established and maintained by a vehicle manufacturer to manage software updates safely, securely, and in compliance with the regulation. This system encompasses all stages from the development and approval of an update to its secure delivery, installation, and post-update validation, ensuring traceability and accountability throughout the entire process.

A 'Software Update' is defined as any change to the software within a vehicle's electronic control units (ECUs) that can affect its type approval relevant characteristics or functionality. This includes updates for telematics devices, GPS trackers, IoT sensors, engine control units, driver assistance systems, and infotainment units. The regulation differentiates between updates that affect type-approval-relevant systems and those that do not, though manufacturers must document the rationale for any exclusions. 'Vehicle Type' covers all vehicles of a manufacturer using the same technical solution for software updates, while 'Type Approval' refers to the certification process by which a vehicle type is approved by an authority, confirming its compliance with relevant regulations. An 'Electronic Control Unit (ECU)' is an embedded system that controls one or more electrical systems or subsystems in a vehicle, acting as the 'brain' for various functions. An 'Over-the-Air (OTA) Update' specifically refers to the wireless delivery of software updates to a vehicle's electronic systems, a method that requires stringent security measures under R156.

Governance and Institutional Framework

UN Regulation No. 156 was drafted and adopted by the United Nations Economic Commission for Europe (UNECE) World Forum for Harmonization of Vehicle Regulations (WP.29). This international body is responsible for developing and harmonizing technical regulations for wheeled vehicles, equipment, and parts, operating under the framework of the 1958 Agreement concerning the adoption of harmonized technical United Nations Regulations. This agreement facilitates reciprocal recognition of approvals among its Contracting Parties, ensuring a consistent global standard for vehicle safety and performance.

The governance structure places the primary responsibility for compliance squarely on vehicle manufacturers (OEMs). Manufacturers are required to establish, implement, and maintain a Software Update Management System (SUMS) that must be audited and certified by a neutral technical service or an approval authority. Without this certification, a vehicle type cannot receive type approval in adhering countries, effectively preventing its sale in those markets. The regulation sets out the detailed requirements for this management system, while national approval authorities and technical services are responsible for assessing and verifying the manufacturer's compliance through rigorous audits. The SUMS certificate is typically valid for three years, necessitating regular re-audits and continuous adherence to the established processes, thereby ensuring ongoing regulatory compliance and cybersecurity throughout the vehicle's operational life.

Key Focus Areas

UN Regulation No. 156 focuses on several critical areas to ensure the safe and secure management of vehicle software updates. A primary focus is the establishment of a robust Software Update Management System (SUMS) by vehicle manufacturers. This system must cover the entire lifecycle of software updates, from their initial secure development and build, through rigorous testing and approval, to their secure delivery, validation, and comprehensive recording. Manufacturers must demonstrate that every update is securely built, cryptographically signed, approved, delivered, validated, and recorded, ensuring full traceability and accountability for all software changes.

Another key area involves the processes for assessing and identifying the potential impact of a software update. This includes determining if an update will affect any other system required for the safe and continued operation of the vehicle, or if it will add or alter functionality compared to the vehicle's registered type-approved state. The regulation also mandates clear processes to inform vehicle users about updates, ensuring transparency regarding their purpose, potential impact, and any necessary user actions. Furthermore, it requires vehicles to have functionality that allows systems to be restored to a previous version in case of a failed or interrupted update, or to be placed into a safe state to prevent hazardous conditions. Updates can only be executed when the vehicle has sufficient power to complete the process, including any recovery procedures. The integrity and authenticity of software packages are paramount, requiring robust verification and protection against tampering or unauthorized installation, often through secure boot mechanisms and cryptographic checks.

Implementation Framework

The implementation framework for UN Regulation No. 156 is centered on vehicle type approval, making compliance a mandatory prerequisite for market entry in signatory countries. Specifically, the establishment and certification of a Software Update Management System (SUMS) is a condition for obtaining type approval for new vehicle types. This means that manufacturers must demonstrate to approval authorities that their SUMS meets all the stipulated requirements before their vehicles can be sold in countries adhering to the 1958 Agreement, such as the European Union, Japan, and South Korea.

The regulation has specific application dates to allow manufacturers time to adapt. It formally entered into force as an annex to the 1958 Agreement in January 2021. For the European Union, compliance became mandatory for new whole vehicle types seeking EU type approval from July 2022. This requirement will extend to all new vehicles sold in the EU, regardless of their initial type approval date, from July 2024. Similar phased timelines are being followed by other signatory countries, ensuring a harmonized global rollout. Manufacturers are also indirectly responsible for ensuring their supply chain complies, as they must prove they control risks introduced by suppliers of software components and services, thereby extending the regulatory reach throughout the automotive ecosystem.

Monitoring and Evaluation

Monitoring and evaluation of compliance with UN Regulation No. 156 primarily rely on an audit-based approach, shifting the focus from mere product testing to comprehensive process assessment. R156 requires manufacturers to submit their Software Update Management Systems (SUMS) for assessment by approval authorities or designated technical services. This involves rigorous audits that evaluate the organizational processes, responsibilities, documentation, and governance structures that manufacturers have in place to manage software updates throughout the vehicle's lifecycle.

During these assessments, auditors conduct in-depth reviews of documentation, process walkthroughs, and interviews with key stakeholders within the manufacturing organization to verify the practical implementation and effectiveness of the SUMS. The systematic and risk-based approach ensures that manufacturers can proactively identify, assess, and mitigate risks associated with software updates, including cybersecurity vulnerabilities, functional safety impacts, and data integrity issues. The goal is to ensure continuous regulatory compliance, robust cybersecurity, and overall vehicle safety. The SUMS certificate, once issued, typically has a validity period of three years, necessitating periodic re-audits and ongoing verification to ensure sustained adherence to the regulation's requirements and to promote a culture of continuous improvement in software update management.

Penalties, Liability, and Appeals

UN Regulation No. 156, as an international framework adopted by the UNECE, primarily sets out the technical and organizational requirements for vehicle manufacturers regarding software updates. While the regulation itself does not explicitly detail specific penalties, liability, or appeal mechanisms, these aspects are handled at the national or regional level by the individual Contracting Parties that have adopted the regulation. Each signatory country is responsible for implementing and enforcing R156 within its own domestic legal framework, which includes defining the consequences of non-compliance.

Manufacturers are directly liable for ensuring compliance with the regulation's provisions, particularly the establishment and operation of a certified Software Update Management System (SUMS). Failure to comply can result in severe consequences, such as a vehicle type not receiving or retaining its type approval, which would effectively prevent its sale or registration in adhering markets. National authorities would impose sanctions, which could range from administrative fines, mandatory recalls, to withdrawal of type approval, based on their domestic legislation. For instance, in the European Union, non-compliance could lead to significant financial penalties under national laws implementing EU type-approval regulations. The appeals process would similarly be governed by the administrative and legal procedures of the respective national jurisdiction where the non-compliance or penalty was issued, allowing manufacturers to challenge decisions through established legal channels.

Relationship to Other Instruments

UN Regulation No. 156 is closely interconnected with other international instruments, particularly within the UNECE regulatory framework, forming a comprehensive approach to modern vehicle challenges. It is considered a companion regulation to UN Regulation No. 155, which deals with uniform provisions concerning the approval of vehicles with regard to cybersecurity and cybersecurity management systems (CSMS). Together, R155 and R156 form a robust regulatory framework addressing the cybersecurity and software integrity of vehicles throughout their lifecycle. While R155 focuses on the overall cybersecurity of the vehicle and its systems, R156 specifically addresses the secure management of software updates, ensuring that the process of changing software does not introduce new vulnerabilities or compromise existing security measures.

Beyond the direct link to R155, UN R156 also references and aligns with international standards that provide detailed guidance for practical implementation. Notably, ISO/SAE 21434, 'Road Vehicles – Cybersecurity Engineering,' provides a comprehensive framework for managing cybersecurity risks in road vehicles, which is highly relevant to the secure development and execution of software updates. Furthermore, ISO 24089, 'Road Vehicles – Software Update Engineering,' specifies requirements for software updates, offering detailed implementation guidance for meeting R156's provisions regarding update processes, integrity, and traceability. These standards help manufacturers translate the high-level requirements of R156 into practical organizational processes and technical solutions, fostering a harmonized and effective approach to software update management across the global automotive industry.

International Alignment

UN Regulation No. 156 plays a crucial role in fostering international alignment and harmonization of vehicle regulations, a core objective of the UNECE WP.29. Developed under the auspices of the United Nations Economic Commission for Europe, it is part of a broader effort to create a common global framework for vehicle safety, environmental performance, and cybersecurity. The regulation is applicable to all UNECE countries that are members of the 1958 Agreement, which includes major automotive markets such as the European Union, the United Kingdom, Japan, South Korea, and many others.

By establishing uniform provisions for software updates and software update management systems, R156 aims to create a level playing field for vehicle manufacturers worldwide. This harmonization significantly reduces technical barriers to trade, simplifying the process for manufacturers to obtain type approval for their vehicles across multiple jurisdictions. For consumers, the widespread adoption of R156 ensures that vehicles sold in these diverse markets adhere to consistent, high standards for software update security and management, thereby enhancing consumer confidence in connected and automated vehicle technologies. This global alignment not only promotes safer and more secure vehicles but also encourages innovation by providing a clear, consistent regulatory landscape for the development and deployment of advanced automotive software features.

Implementation Timeline

MilestoneDateNotes
Formal Adoption by UN WP.292020-06-01The regulation was formally adopted by the UNECE World Forum for Harmonization of Vehicle Regulations.
Entry into Force (as annex to 1958 Agreement)2021-01-22The regulation officially entered into force, making it legally available for application in UN Member States.
Mandatory for new whole vehicle types (EU)2022-07-06From this date, compliance with R156 (and R155) became mandatory for manufacturers seeking EU type approval for new whole vehicle types.
Mandatory for all new vehicles (EU)2024-07-07From this date, compliance with R156 (and R155) will be extended to all new vehicles sold in the EU, regardless of when type approval was obtained.

Sources and References

SourceType
UN Regulation No. 156 - Software update and software update management system | UNECEofficial
UN Regulation No. 155 - Cybersecurity and cybersecurity management system | UNECEofficial
Agreement concerning the adoption of harmonized technical United Nations Regulations for wheeled vehicles, equipment and parts... (1958 Agreement)official
World Forum for Harmonization of Vehicle Regulations (WP.29) | UNECEofficial

Requirements for a company

What an organisation has to do under UN Regulation 156: Vehicle Software Update Management, at a glance. Not legal advice — the table below gives the provision and deadline for each item.

Must do

7
  • Establish and maintain a certified Software Update Management System to obtain vehicle type approval.Vehicle manufacturers seeking vehicle type approval
  • Ensure every software update is securely built, cryptographically signed, validated, and comprehensively recorded.Vehicle manufacturers
  • Equip vehicles with capabilities to restore previous software versions or enter a safe state upon update failure.Vehicle manufacturers
  • Evaluate whether a software update alters registered type-approved functionality or impacts safe vehicle operation.Vehicle manufacturers
  • Inform vehicle users about software updates, detailing their purpose, operational impact, and required actions.Vehicle manufacturers
  • Demonstrate control over software update and cybersecurity risks introduced by third-party suppliers.Vehicle manufacturers
  • +1 more in the table below

Must not do

1
  • Do not execute software updates unless the vehicle has adequate power to complete execution and potential recovery.Vehicle manufacturers

Should do

0

Nothing in this category.

Should not do

0

Nothing in this category.

Who must do what

The obligations under UN Regulation 156: Vehicle Software Update Management, most serious first. Not legal advice — verify against the official text before relying on it.

#WhoRequirementBy whenWhereSeverity
1Vehicle manufacturers seeking vehicle type approvalEstablish and maintain a certified Software Update Management System to obtain vehicle type approval.
“The regulation mandates that vehicle manufacturers implement a robust Software Update Management System (SUMS) as a condition for type approval”
Before obtaining vehicle type approval—Critical
2Vehicle manufacturersEnsure every software update is securely built, cryptographically signed, validated, and comprehensively recorded.
“Manufacturers must demonstrate that every update is securely built, cryptographically signed, approved, delivered, validated, and recorded”
Before deploying software updates—Critical
3Vehicle manufacturersEquip vehicles with capabilities to restore previous software versions or enter a safe state upon update failure.
“requires vehicles to have functionality that allows systems to be restored to a previous version in case of a failed or interrupted update, or to be placed into a safe state”
Before vehicle type approval—Critical
4Vehicle manufacturersDo not execute software updates unless the vehicle has adequate power to complete execution and potential recovery.
“Updates can only be executed when the vehicle has sufficient power to complete the process, including any recovery procedures.”
During update execution—Critical
5Vehicle manufacturersEvaluate whether a software update alters registered type-approved functionality or impacts safe vehicle operation.
“includes determining if an update will affect any other system required for the safe and continued operation of the vehicle, or if it will add or alter functionality”
Prior to software update release—Important
6Vehicle manufacturersInform vehicle users about software updates, detailing their purpose, operational impact, and required actions.
“mandates clear processes to inform vehicle users about updates, ensuring transparency regarding their purpose, potential impact, and any necessary user actions.”
Prior to executing software updates—Important
7Vehicle manufacturersDemonstrate control over software update and cybersecurity risks introduced by third-party suppliers.
“they must prove they control risks introduced by suppliers of software components and services, thereby extending the regulatory reach”
Before placing vehicles on the market—Important
8Vehicle manufacturersSubject the Software Update Management System to re-audits every three years to maintain certification.
“The SUMS certificate is typically valid for three years, necessitating regular re-audits and continuous adherence to the established processes”
Every 3 years—Important

© Regulations.AI — created on 20 May 2026 using Gemini 2.5 Flash · reviewed against official sources on 9 Sep 2026 using Gemini 3.6 Flash