Every vehicle manufacturer that ships software updates, over the air or in the workshop, must now prove to a type-approval authority that those updates are controlled, recorded and protected, and UN Regulation No. 156 is the rule that sets out how. UN R156 requires a certified Software Update Management System (SUMS) at organisation level and specific update protections on each approved vehicle type. It sits alongside UN R155 on cyber security management, and together they decide whether a vehicle type can be approved in the markets that apply them. This guide explains who R156 covers, what paragraphs 7.1 and 7.2 require, how certification and conformity of production work, how the OTA back end and its machine identities fit, and the practical steps to build and evidence a SUMS. It is written for vehicle and supplier security, homologation and OTA platform teams. For the wider automotive picture see the Automotive Cybersecurity Guide. Status checked against the official UNECE text on 27 October 2026.
Key takeaways
- Two layers of approval. R156 needs a Certificate of Compliance for the manufacturer's SUMS (valid for up to three years) and a vehicle type approval that shows each type meets the update requirements in paragraph 7.2.
- RXSWIN is the backbone. Every type-approval-relevant software configuration must carry a manufacturer-defined RXSWIN, be recorded before and after each update and be readable from the vehicle, at minimum through the OBD port.
- Updates must be assessed before release. The SUMS must check compatibility with the target vehicles and decide whether an update affects type-approved systems, which may mean going back to the approval authority.
- Security is explicit. Paragraph 7.1.3 requires protection against manipulation of updates and of the delivery process, and 7.2.1 requires the vehicle to protect update authenticity and integrity.
- The OTA back end is a set of powerful machine identities. Signing keys, campaign services and supplier pipelines can change thousands of vehicles at once; manage them as critical non-human identities.
Scope: who and what is covered
UN R156 is a regulation annexed to the UNECE 1958 Agreement on vehicle type approval. According to the official text (E/ECE/TRANS/505/Rev.3/Add.155), it entered into force on 22 January 2021.
| Element | What the regulation says |
|---|---|
| Vehicle categories (para 1.1) | Vehicles of categories M (passenger), N (goods), O (trailers), R (agricultural trailers), S (interchangeable towed machinery) and T (agricultural tractors) that permit software updates |
| Who must comply | The vehicle manufacturer applying for type approval; in practice suppliers that deliver ECUs, software or OTA services carry obligations through contracts and the manufacturer's SUMS |
| Software update (para 2.3) | A package used to upgrade software to a new version, including a change of configuration parameters |
| RXSWIN (para 2.2) | A dedicated identifier, defined by the manufacturer, for software of an electronic control system that is relevant to type approval |
| SUMS (para 2.5) | The systematic organisational processes and procedures for delivering software updates in line with the regulation |
| Delivery methods | All updates: over the air (OTA) and wired or workshop updates. Paragraphs 7.1.4 and 7.2.2 add requirements specific to OTA |
Where R156 applies depends on each contracting party's decision to apply it. In the European Union, the General Safety Regulation (EU) 2019/2144 applies from 6 July 2022, and its Annex II sets the dates from which cyber security and software update requirements are applied to new types and then to all new registrations (widely reported as 6 July 2022 and 7 July 2024; confirm them in Annex II). Check the consolidated EU text and your approval authority for how R156 itself is referenced for your vehicle categories, because annexes are amended by delegated acts. Other markets that apply UN regulations set their own dates.
Key obligations
SUMS requirements for the manufacturer (paragraph 7.1)
| Paragraph | Topic | What has to exist |
|---|---|---|
| 7.1.1 | Processes | Documented processes to record information about updates securely; to identify uniquely every initial and updated RXSWIN and the related software and hardware versions; to check software interdependencies and compatibility with target vehicles; to assess whether an update affects type-approved systems, safety, legally required parameters or functions defined at approval; to inform vehicle users about updates; and to make information available to the approval authority |
| 7.1.2 | Records | Documentation of the update processes; the configuration of relevant systems before and after each update; RXSWIN software registers; the target vehicles and confirmation of compatibility; and the purpose of each update and the systems or functions it affects |
| 7.1.3 | Security | Processes to protect software updates against manipulation before the update process starts, including the development of the update software; to protect the update delivery process against compromise; and to verify and validate software functionality and code |
| 7.1.4 | Over the air | Show that an OTA update performed during driving cannot affect safety, and that updates which need a skilled action (for example sensor recalibration) can only proceed when a qualified person is present or in control |
Vehicle type requirements (paragraph 7.2)
- Authenticity and integrity (7.2.1): the vehicle type must protect the authenticity and integrity of software updates and prevent invalid updates.
- RXSWIN (7.2.1): each RXSWIN must be uniquely identifiable and readable in a standardised way through an electronic interface, at minimum the OBD port (if RXSWINs are not held on the vehicle, the manufacturer declares software versions to the authority), and protected against unauthorised modification.
- OTA safety (7.2.2): a mechanism to restore the previous version or reach a safe state if an update fails; enough power to complete the update, including a possible rollback; safe execution of the update; informing the user before the update (purpose, changes to functions, expected time, functions unavailable during the update and instructions) and after it (success or failure, what changed); where running an update while driving may be unsafe, preventing the vehicle being driven and preventing the driver using functions that could affect safety or the update; and checking preconditions before execution.
Timeline and current status
| Date | Event | Source |
|---|---|---|
| 22 January 2021 | UN R156 enters into force as an annex to the 1958 Agreement | UNECE official text |
| 6 July 2022 | EU General Safety Regulation (EU) 2019/2144 applies; cyber security requirements reported to apply to new vehicle types (confirm in Annex II) | EUR-Lex |
| February 2023 | ISO 24089:2023 "Road vehicles: Software update engineering" published, an engineering standard widely used to implement R156 processes | ISO |
| 7 July 2024 | Reported date for EU refusal of registration of vehicles not meeting the cyber security requirements (confirm in Annex II) | EUR-Lex |
UN regulations are amended through supplements and series of amendments adopted by WP.29, the UNECE World Forum for Harmonization of Vehicle Regulations. Always confirm the current version and any transitional provisions on the UNECE WP.29 pages before an approval campaign. Interpretation documents and approval authority practice also change over time, so treat any summary, including this one, as a starting point rather than the final word.
Enforcement and penalties
- Certificate validity (para 6.6 to 6.10): the SUMS Certificate of Compliance is valid for a maximum of three years unless withdrawn. A new certificate or an extension of three years may be issued after a positive reassessment. Existing vehicle type approvals do not lose validity when a SUMS certificate expires, but new approvals and extensions need a valid one.
- Conformity of production (para 9): follows Schedule 1 of the 1958 Agreement, with record retention for up to 10 years after production of a vehicle type is permanently discontinued, verification of production control normally every three years, and periodic checks of manufacturer decisions not to notify an update to the authority.
- Withdrawal (para 10): an approval may be withdrawn if the requirements are not met or sample vehicles fail checks, and other contracting parties are notified using the Annex 2 form.
- National and EU penalties: financial penalties and market measures are set by the applying jurisdiction, not by R156. In the EU, Regulation (EU) 2019/2144 states that the administrative provisions of Regulation (EU) 2018/858, including corrective measures and penalties, apply. Take advice on the figures that apply to you.
What it means for AI agents and non-human identities
R156 does not mention AI or non-human identities by name, but its security and records requirements fall largely on machine credentials and automated systems.
- Signing keys are the regulation's trust root. Paragraph 7.2.1 authenticity protection is usually implemented with code signing; whoever holds the signing keys can push a valid update to an entire fleet. Keep them in HSMs, separate roles and keys (for example the Uptane split between director and image repositories), and log every signature. See the Uptane and Vehicle OTA Security Guide.
- Pipeline and campaign service identities: CI/CD service accounts, supplier upload credentials and the OTA campaign manager's API keys all touch the "development of the update software" and "delivery process" that 7.1.3 says must be protected. Inventory, scope and rotate them. See the CI/CD Pipeline Identity Security Guide.
- Back-end credential leaks are a real risk: the Toyota T-Connect Key Exposure 2022 shows how a single connected-vehicle back-end access key, pushed to public GitHub by a subcontractor, stayed exposed for nearly five years.
- Automated decision steps need evidence: if you use AI tools or agents to triage update impact, generate release notes or analyse compatibility, the 7.1.1 assessment and 7.1.2 records still have to be accurate and reviewable. Keep a human approver and an audit trail for any automated decision that sets whether an update affects type approval.
- Vehicle identity: per-vehicle and per-ECU identities authenticate update requests and let you target RXSWIN-specific campaigns. See the Connected and Autonomous Vehicle Security Guide.
Compliance steps
- Map scope. List vehicle types, markets and the categories they fall into, the ECUs that receive updates and which software is type-approval relevant (needs an RXSWIN).
- Gap-assess against 7.1 and 7.2. Use the paragraph list above as a checklist; ISO 24089 provides organisational and project-level processes that map onto it. Record which evidence already exists.
- Define the RXSWIN scheme and registers. Agree identifier format, ownership, how RXSWIN is read from the vehicle and how before and after configurations are stored.
- Build the update assessment gate. A documented decision for each update: target vehicles, compatibility check, impact on type-approved systems, need to notify the authority, user information content.
- Secure the chain. Threat-model the update pipeline (reuse your R155 and ISO/SAE 21434 TARA), protect signing keys, enforce signed builds and separate duties between developers, release approvers and campaign operators.
- Validate OTA behaviour. Test rollback or safe state, power management, driving inhibition and user messages on each vehicle type, including failure injection such as interrupted downloads and corrupted packages.
- Pilot and stage releases. Release new campaigns to internal fleets, then small customer rings, with criteria for halting and rolling back.
- Prepare for the audit. Assemble the Annex 1 information document and SUMS declaration, process descriptions and sample records; run an internal audit first.
- Operate and re-certify. Track certificate expiry (three years), conformity of production checks and changes that need an approval extension. Link R156 records with the R155 CSMS. See the UNECE R155 Cyber Security Management System Guide.
Measuring the SUMS
| Metric | Why it matters |
|---|---|
| Share of released updates with a complete 7.1.1 assessment record | Direct evidence for the auditor; target 100% |
| RXSWIN register accuracy (sampled vehicles read versus register) | Detects drift between fleet and records |
| OTA campaign failure and rollback rate per vehicle type | Shows 7.2.2 mechanisms work in the field |
| Signing operations outside approved release windows | Should be zero; any event is a security incident |
| Pipeline and campaign credentials older than rotation policy | Measures NHI hygiene in the delivery chain |
Decision points
- Who runs the OTA back end: an in-house platform gives direct control of signing keys and records; a supplier platform means the SUMS must reach into the supplier's processes, so contracts need evidence rights, key custody terms and incident notification. The manufacturer remains the applicant either way.
- Which software needs an RXSWIN: only type-approval-relevant software, but drawing that line too narrowly risks an update that changes an approved function without a record. Agree the boundary with the approval authority early.
- Workshop versus OTA: wired updates avoid the 7.1.4 and 7.2.2 OTA requirements but still need the full 7.1.1 to 7.1.3 processes and records. Dealer and workshop tools that flash ECUs hold credentials too, and belong in the same key and access management.
- Smaller manufacturers and low-volume types: the requirements do not scale down with volume, but evidence can. A small maker can run one integrated process covering R155 and R156 with a single change board, rather than separate teams.
Framework mapping
| R156 area | Related standard or control |
|---|---|
| SUMS processes (7.1.1, 7.1.2) | ISO 24089:2023 organisational and project requirements; NIST SP 800-53 CM-3 Configuration Change Control, CM-8 System Component Inventory |
| Update security (7.1.3, 7.2.1) | NIST SP 800-53 SI-7 Software, Firmware, and Information Integrity; CM-14 Signed Components; SR-4 Provenance |
| Cyber security management | UN R155 CSMS and ISO/SAE 21434. See the ISO/SAE 21434 Automotive Cybersecurity Engineering Guide |
| OTA framework design | Uptane specification (key separation, metadata roles) |
Practitioner checklist
- Confirm which vehicle types and markets require R156 and the dates that apply in each.
- Assign an owner for the SUMS and for the Certificate of Compliance renewal cycle.
- Define and publish the RXSWIN scheme and keep before and after configuration records.
- Run a documented impact assessment on every update before release.
- Hold update signing keys in HSMs with role separation and full logging.
- Inventory and rotate every pipeline, supplier and campaign service credential.
- Test rollback, safe state, power and driving inhibition for every vehicle type.
- Give users the pre- and post-update information the regulation lists.
- Retain records for the conformity of production period and rehearse an auditor request.
- Re-check the current UNECE text and any amendments before each approval campaign.
Standards and references
- UNECE: UN Regulation No. 156 Software update and software update management system
- EUR-Lex: Regulation (EU) 2019/2144 General Safety Regulation
- ISO: ISO 24089:2023 Road vehicles, Software update engineering
- Uptane: Uptane Standard for Design and Implementation
- NIST: SP 800-53 Rev. 5 Security and Privacy Controls
Related NHI Mgmt Group resources: UNECE R155 Cyber Security Management System Guide · Automotive Cybersecurity Guide · Uptane and Vehicle OTA Security Guide · Vehicle Security Operations Centre Guide. This guide summarises UN Regulation No. 156 and related EU type-approval rules as checked on 27 October 2026 and is not legal advice.