Compliance FrameworksInternational
UNECE WP.29
UN vehicle cybersecurity: software update management, risk assessment, ECU integrity.
UN vehicle cybersecurity: software update management, risk assessment, ECU integrity.
| Short name | WP.29 |
| Region | International |
| Country or scope | International |
| Sector | Automotive |
| In your workspace | On unless you switch it off in Compliance › Manage. |
How Safeguard covers WP.29
- Scan requirements: 7, all decided by a scan.
- Controls: the scan requirements below, plus 13 controls from Safeguard's control catalog for WP.29.
- Automated tests: none map to it directly. You can link any automated test to its controls yourself (how).
- Policy templates: 25: 3 written for WP.29 and 22 from the standard set.
How each kind of coverage works, and what the readiness score counts: Compliance frameworks.
What a scan checks
Each scan of a product checks these 7 requirements against what the scan found, including the product's software inventory (SBOM).
| Requirement | What Safeguard checks | Decided by |
|---|---|---|
WP29-R156-SWID Software Identification (RXSWIN) | Manufacturers must be able to identify the software relevant to type approval on each vehicle type, including component versions underlying the declared RXSWIN (UN R156 software identification requirements) | Scan |
WP29-R156-INV Software Composition Knowledge | A Software Update Management System must know what software is installed and updatable on vehicle systems, which requires a component inventory per software build (UN R156 SUMS requirements) | Scan |
WP29-R156-INT Update Integrity | Software updates must be protected so their integrity can be verified before installation on ECUs, requiring integrity hashes for delivered software components (UN R156 update integrity/authenticity requirements) | Scan |
WP29-R155-RISK CSMS Risk Assessment of Components | The CSMS must identify and assess cybersecurity risks across the vehicle lifecycle, including risks from third-party and open source software, requiring identifiable components for threat matching (UN R155 §7.2.2 CSMS process requirements) | Scan |
WP29-R155-SUPPLY Supply Chain Risk Management | Manufacturers must manage cybersecurity risks arising from their supply chain, including contracted suppliers, which requires supplier attribution for software components (UN R155 CSMS supplier-related requirements) | Scan |
WP29-R155-MON Post-Production Vulnerability Monitoring | Manufacturers must monitor for new threats and vulnerabilities affecting vehicles in the field and respond, requiring versioned components to determine affected fleets (UN R155 §7.2.2 monitoring and response obligations) | Scan |
WP29-DOC Type-Approval Documentation | Type approval requires documentation demonstrating CSMS/SUMS operation to the approval authority; dated, identifiable software composition records support this evidence (UN R155/R156 documentation requirements for approval authorities) | Scan |
More controls in the catalog
The framework's Controls tab lists its scan requirements and these controls from Safeguard's control catalog. Evidence them with automated tests, uploaded evidence, policies or an attestation.
| Control | Name |
|---|---|
4.3.1 | Cyber Security Management System (CSMS) |
4.3.2 | CSMS Risk-Based Approach |
4.3.3 | Organisational Roles and Responsibilities for CSMS |
4.3.4 | Supply Chain Management for Cybersecurity |
4.3.5 | Post-Production Cybersecurity Monitoring |
4.3.6 | Cybersecurity Incident Response |
4.3.7 | CSMS Audit and Improvement |
5.1.1 | Vehicle Type Cybersecurity Risk Assessment |
5.1.2 | Vehicle Type Cybersecurity Testing |
5.3.1 | Software Update Management System |
5.4.1 | Cryptographic Module Controls |
5.4.2 | External Connectivity Protection |
5.4.3 | Vehicle Data Integrity and Protection |
Policy templates
Written for WP.29:
- Vehicle Cyber Security Management System (CSMS) Policy
- Vehicle Software Supply Chain Security Policy
- Vehicle Cybersecurity Incident Response and SUMS Policy
And 22 from the standard set, adapted to WP.29.