International (Contracting Parties to the UNECE 1958 Agreement that apply the Regulation)

UNECE WP.29 R155

98 controls. 0 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

98 controls 0 frameworks share controls with it International (Contracting Parties to the UNECE 1958 Agreement that apply the Regulation) verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

No measured overlap with another framework in the corpus.

Every control

CodeControlAlso in
R155-CSMS-COMPCompetence and training of personnel0
R155-CSMS-CONTRACTINGOutsourced processes and joint development0
R155-CSMS-GOVCyber Security Management System governance0
R155-CSMS-INCIDENTIncident response and reporting to approval authority0
R155-CSMS-MONITORMonitoring of cyber threats, vulnerabilities, and attacks0
R155-CSMS-SUPPLIERManagement of supplier-related cybersecurity0
R155-VTA-ASSURANCEIndependent assurance and approval authority interaction0
R155-VTA-MITIGATIONSImplementation of proportionate mitigations0
R155-VTA-POSTPRODPost-production cybersecurity management0
R155-VTA-RISKVehicle type cybersecurity risk identification0
R155-VTA-TESTTesting the cybersecurity of the vehicle type0
UNECER155-1Cyber Security Management System (CSMS)0
UNECER155-2Vehicle Type Approval and Cyber Security Demonstration0
UNECER155-3Threat Assessment (Annex 5) and Risk Mitigation0
UNECER155-4Software Updates Management System (alignment with R156)0
1010 and 12 Penalties for non-conformity of production and authority contacts0
11.111.1 Inform the authority when production is definitively discontinued0
33 Application for approval0
3.23.2 Application documents: vehicle type description and the CSMS certificate0
3.2.23.2.2 Sufficient information despite intellectual property or know-how0
3.33.3 Documentation package and material open for inspection, kept ten years0
4.14.1 International approval mark on every conforming vehicle0
55 Approval0
5.15.1 to 5.2 How the authority verifies and when it must refuse0
5.35.3 Authority competence, uniform evaluation and the DETA exchange of methods and criteria0
5.45.4 Manufacturer ensures the cyber security aspects are implemented0
66 Certificate of Compliance for Cyber Security Management System0
6.106.10 Apply in due time for a new or extended CSMS certificate0
6.36.3 CSMS certificate application: CSMS documents and signed declaration0
6.46.4 Declare and demonstrate the necessary CSMS processes0
6.56.1 and 6.5 to 6.8 and 6.11 Authority grant, validity and withdrawal of the CSMS certificate0
6.96.9 Inform the authority of changes affecting the CSMS certificate0
77 Specifications0
7.27.2 Requirements for the Cyber Security Management System0
7.2.2.17.2.2.1 CSMS covers the development, production and post-production phases0
7.2.2.27.2.2.2 CSMS processes ensure security is adequately considered0
7.2.2.2(a)7.2.2.2(a) Processes within the organization to manage cyber security0
7.2.2.2(b)7.2.2.2(b) Processes to identify risks to vehicle types, considering Annex 5 Part A0
7.2.2.2(c)7.2.2.2(c) Processes to assess, categorize and treat identified risks0
7.2.2.2(d)7.2.2.2(d) Processes to verify that identified risks are appropriately managed0
7.2.2.2(e)7.2.2.2(e) Processes to test the cyber security of a vehicle type0
7.2.2.2(f)7.2.2.2(f) Processes to keep the risk assessment current0
7.2.2.2(g)7.2.2.2(g) Processes to monitor, detect and respond, and to re-check mitigation effectiveness0
7.2.2.2(h)7.2.2.2(h) Processes to provide data to support analysis of attacks0
7.2.2.37.2.2.3 Threats and vulnerabilities needing a response are mitigated within a reasonable timeframe0
7.2.2.47.2.2.4 Monitoring is continual, covers registered vehicles and uses vehicle data and logs0
7.2.2.57.2.2.5 CSMS manages dependencies on suppliers, service providers and sub-organizations0
7.37.3 Requirements for vehicle types0
7.3.17.3.1 Valid CSMS certificate relevant to the vehicle type, with the transitional allowance0
7.3.27.3.2 Identify and manage supplier-related risks for the vehicle type0
7.3.37.3.3 Identify critical elements and perform an exhaustive risk assessment for the type0
7.3.47.3.4 Protect the type with proportionate mitigations, including relevant Annex 5 Part B and C measures0
7.3.57.3.5 Secure dedicated environments for aftermarket software, services, applications or data0
7.3.67.3.6 Test before type approval that security measures are effective0
7.3.77.3.7 Measures to detect and prevent attacks, support monitoring and provide forensics0
7.3.87.3.8 Cryptographic modules in line with consensus standards or justified0
7.47.4 Reporting provisions0
7.4.17.4.1 Report monitoring outcomes at least once a year and confirm mitigations remain effective0
8.18.1 Notify modifications of the vehicle type affecting cyber security0
9.1.19.1.1 Conformity of production: record test results and keep the documents0
A5Annex 5 List of threats and corresponding mitigations0
A5-A.4.3.14.3.1 Threats regarding back-end servers related to vehicles in the field0
A5-A.4.3.24.3.2 Threats to vehicles regarding their communication channels0
A5-A.4.3.34.3.3 Threats to vehicles regarding their update procedures0
A5-A.4.3.44.3.4 Threats to vehicles regarding unintended human actions facilitating a cyber-attack0
A5-A.4.3.54.3.5 Threats to vehicles regarding their external connectivity and connections0
A5-A.4.3.64.3.6 Threats to vehicle data or code0
A5-A.4.3.74.3.7 Potential vulnerabilities that could be exploited if not sufficiently protected or hardened0
A5-BAnnex 5 Part B Mitigations to the threats intended for vehicles0
A5-B5-20.4Annex 5 B5-20.4 Correlate data from different sources against driving data or diagnostic data manipulation0
A5-CAnnex 5 Part C Mitigations to the threats outside of vehicles0
A5-M1Annex 5 M1 Security controls on back-end systems to minimise the risk of insider attack0
A5-M10Annex 5 M10 The vehicle verifies the authenticity and integrity of messages it receives0
A5-M11Annex 5 M11 Security controls for storing cryptographic keys0
A5-M12Annex 5 M12 Confidential data transmitted to or from the vehicle is protected0
A5-M13Annex 5 M13 Measures to detect and recover from denial of service attacks0
A5-M14Annex 5 M14 Measures to protect systems against embedded viruses or malware should be considered0
A5-M15Annex 5 M15 Measures to detect malicious internal messages or activity should be considered0
A5-M16Annex 5 M16 Secure software update procedures are employed0
A5-M18Annex 5 M18 User roles and access privileges defined and controlled on least privilege0
A5-M19Annex 5 M19 Security procedures defined and followed, with logging of security management actions0
A5-M2Annex 5 M2 Security controls on back-end systems to minimise unauthorised access0
A5-M20Annex 5 M20 Security controls on systems with remote access0
A5-M21Annex 5 M21 Software security assessed, authenticated and integrity protected; third-party software risk minimised0
A5-M22Annex 5 M22 Security controls on external interfaces0
A5-M23Annex 5 M23 Cyber security best practices for software, hardware, system design and integration, with adequate test coverage0
A5-M24Annex 5 M24 Best practices protect the integrity and confidentiality of stored personal data0
A5-M3Annex 5 M3 Back-end security controls with recovery measures for critical services0
A5-M4Annex 5 M4 Security controls to minimise cloud computing risks0
A5-M5Annex 5 M5 Security controls on back-end systems to prevent data breaches0
A5-M6Annex 5 M6 Systems implement security by design to minimise risks0
A5-M7Annex 5 M7 Access control techniques and designs protect system data and code0
A5-M8Annex 5 M8 System design and access control prevent unauthorised access to personal or system-critical data0
A5-M9Annex 5 M9 Measures to prevent and detect unauthorised access0
ANNEXESAnnexes 1 to 4: information document, communication, approval mark, CSMS certificate model0
INTERPRETATIONThe Interpretation Document for UN Regulation No. 1550
STANDARDUN Regulation No. 155: the Regulation, its scope and definitions0
STATUSStatus: original version with Supplements 1 to 3; no 01 series; amendments in preparation0

Tell me when UNECE WP.29 R155 files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for UNECE WP.29 R155, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition