R155-CSMS-COMP | Competence and training of personnel | 0 |
R155-CSMS-CONTRACTING | Outsourced processes and joint development | 0 |
R155-CSMS-GOV | Cyber Security Management System governance | 0 |
R155-CSMS-INCIDENT | Incident response and reporting to approval authority | 0 |
R155-CSMS-MONITOR | Monitoring of cyber threats, vulnerabilities, and attacks | 0 |
R155-CSMS-SUPPLIER | Management of supplier-related cybersecurity | 0 |
R155-VTA-ASSURANCE | Independent assurance and approval authority interaction | 0 |
R155-VTA-MITIGATIONS | Implementation of proportionate mitigations | 0 |
R155-VTA-POSTPROD | Post-production cybersecurity management | 0 |
R155-VTA-RISK | Vehicle type cybersecurity risk identification | 0 |
R155-VTA-TEST | Testing the cybersecurity of the vehicle type | 0 |
UNECER155-1 | Cyber Security Management System (CSMS) | 0 |
UNECER155-2 | Vehicle Type Approval and Cyber Security Demonstration | 0 |
UNECER155-3 | Threat Assessment (Annex 5) and Risk Mitigation | 0 |
UNECER155-4 | Software Updates Management System (alignment with R156) | 0 |
10 | 10 and 12 Penalties for non-conformity of production and authority contacts | 0 |
11.1 | 11.1 Inform the authority when production is definitively discontinued | 0 |
3 | 3 Application for approval | 0 |
3.2 | 3.2 Application documents: vehicle type description and the CSMS certificate | 0 |
3.2.2 | 3.2.2 Sufficient information despite intellectual property or know-how | 0 |
3.3 | 3.3 Documentation package and material open for inspection, kept ten years | 0 |
4.1 | 4.1 International approval mark on every conforming vehicle | 0 |
5 | 5 Approval | 0 |
5.1 | 5.1 to 5.2 How the authority verifies and when it must refuse | 0 |
5.3 | 5.3 Authority competence, uniform evaluation and the DETA exchange of methods and criteria | 0 |
5.4 | 5.4 Manufacturer ensures the cyber security aspects are implemented | 0 |
6 | 6 Certificate of Compliance for Cyber Security Management System | 0 |
6.10 | 6.10 Apply in due time for a new or extended CSMS certificate | 0 |
6.3 | 6.3 CSMS certificate application: CSMS documents and signed declaration | 0 |
6.4 | 6.4 Declare and demonstrate the necessary CSMS processes | 0 |
6.5 | 6.1 and 6.5 to 6.8 and 6.11 Authority grant, validity and withdrawal of the CSMS certificate | 0 |
6.9 | 6.9 Inform the authority of changes affecting the CSMS certificate | 0 |
7 | 7 Specifications | 0 |
7.2 | 7.2 Requirements for the Cyber Security Management System | 0 |
7.2.2.1 | 7.2.2.1 CSMS covers the development, production and post-production phases | 0 |
7.2.2.2 | 7.2.2.2 CSMS processes ensure security is adequately considered | 0 |
7.2.2.2(a) | 7.2.2.2(a) Processes within the organization to manage cyber security | 0 |
7.2.2.2(b) | 7.2.2.2(b) Processes to identify risks to vehicle types, considering Annex 5 Part A | 0 |
7.2.2.2(c) | 7.2.2.2(c) Processes to assess, categorize and treat identified risks | 0 |
7.2.2.2(d) | 7.2.2.2(d) Processes to verify that identified risks are appropriately managed | 0 |
7.2.2.2(e) | 7.2.2.2(e) Processes to test the cyber security of a vehicle type | 0 |
7.2.2.2(f) | 7.2.2.2(f) Processes to keep the risk assessment current | 0 |
7.2.2.2(g) | 7.2.2.2(g) Processes to monitor, detect and respond, and to re-check mitigation effectiveness | 0 |
7.2.2.2(h) | 7.2.2.2(h) Processes to provide data to support analysis of attacks | 0 |
7.2.2.3 | 7.2.2.3 Threats and vulnerabilities needing a response are mitigated within a reasonable timeframe | 0 |
7.2.2.4 | 7.2.2.4 Monitoring is continual, covers registered vehicles and uses vehicle data and logs | 0 |
7.2.2.5 | 7.2.2.5 CSMS manages dependencies on suppliers, service providers and sub-organizations | 0 |
7.3 | 7.3 Requirements for vehicle types | 0 |
7.3.1 | 7.3.1 Valid CSMS certificate relevant to the vehicle type, with the transitional allowance | 0 |
7.3.2 | 7.3.2 Identify and manage supplier-related risks for the vehicle type | 0 |
7.3.3 | 7.3.3 Identify critical elements and perform an exhaustive risk assessment for the type | 0 |
7.3.4 | 7.3.4 Protect the type with proportionate mitigations, including relevant Annex 5 Part B and C measures | 0 |
7.3.5 | 7.3.5 Secure dedicated environments for aftermarket software, services, applications or data | 0 |
7.3.6 | 7.3.6 Test before type approval that security measures are effective | 0 |
7.3.7 | 7.3.7 Measures to detect and prevent attacks, support monitoring and provide forensics | 0 |
7.3.8 | 7.3.8 Cryptographic modules in line with consensus standards or justified | 0 |
7.4 | 7.4 Reporting provisions | 0 |
7.4.1 | 7.4.1 Report monitoring outcomes at least once a year and confirm mitigations remain effective | 0 |
8.1 | 8.1 Notify modifications of the vehicle type affecting cyber security | 0 |
9.1.1 | 9.1.1 Conformity of production: record test results and keep the documents | 0 |
A5 | Annex 5 List of threats and corresponding mitigations | 0 |
A5-A.4.3.1 | 4.3.1 Threats regarding back-end servers related to vehicles in the field | 0 |
A5-A.4.3.2 | 4.3.2 Threats to vehicles regarding their communication channels | 0 |
A5-A.4.3.3 | 4.3.3 Threats to vehicles regarding their update procedures | 0 |
A5-A.4.3.4 | 4.3.4 Threats to vehicles regarding unintended human actions facilitating a cyber-attack | 0 |
A5-A.4.3.5 | 4.3.5 Threats to vehicles regarding their external connectivity and connections | 0 |
A5-A.4.3.6 | 4.3.6 Threats to vehicle data or code | 0 |
A5-A.4.3.7 | 4.3.7 Potential vulnerabilities that could be exploited if not sufficiently protected or hardened | 0 |
A5-B | Annex 5 Part B Mitigations to the threats intended for vehicles | 0 |
A5-B5-20.4 | Annex 5 B5-20.4 Correlate data from different sources against driving data or diagnostic data manipulation | 0 |
A5-C | Annex 5 Part C Mitigations to the threats outside of vehicles | 0 |
A5-M1 | Annex 5 M1 Security controls on back-end systems to minimise the risk of insider attack | 0 |
A5-M10 | Annex 5 M10 The vehicle verifies the authenticity and integrity of messages it receives | 0 |
A5-M11 | Annex 5 M11 Security controls for storing cryptographic keys | 0 |
A5-M12 | Annex 5 M12 Confidential data transmitted to or from the vehicle is protected | 0 |
A5-M13 | Annex 5 M13 Measures to detect and recover from denial of service attacks | 0 |
A5-M14 | Annex 5 M14 Measures to protect systems against embedded viruses or malware should be considered | 0 |
A5-M15 | Annex 5 M15 Measures to detect malicious internal messages or activity should be considered | 0 |
A5-M16 | Annex 5 M16 Secure software update procedures are employed | 0 |
A5-M18 | Annex 5 M18 User roles and access privileges defined and controlled on least privilege | 0 |
A5-M19 | Annex 5 M19 Security procedures defined and followed, with logging of security management actions | 0 |
A5-M2 | Annex 5 M2 Security controls on back-end systems to minimise unauthorised access | 0 |
A5-M20 | Annex 5 M20 Security controls on systems with remote access | 0 |
A5-M21 | Annex 5 M21 Software security assessed, authenticated and integrity protected; third-party software risk minimised | 0 |
A5-M22 | Annex 5 M22 Security controls on external interfaces | 0 |
A5-M23 | Annex 5 M23 Cyber security best practices for software, hardware, system design and integration, with adequate test coverage | 0 |
A5-M24 | Annex 5 M24 Best practices protect the integrity and confidentiality of stored personal data | 0 |
A5-M3 | Annex 5 M3 Back-end security controls with recovery measures for critical services | 0 |
A5-M4 | Annex 5 M4 Security controls to minimise cloud computing risks | 0 |
A5-M5 | Annex 5 M5 Security controls on back-end systems to prevent data breaches | 0 |
A5-M6 | Annex 5 M6 Systems implement security by design to minimise risks | 0 |
A5-M7 | Annex 5 M7 Access control techniques and designs protect system data and code | 0 |
A5-M8 | Annex 5 M8 System design and access control prevent unauthorised access to personal or system-critical data | 0 |
A5-M9 | Annex 5 M9 Measures to prevent and detect unauthorised access | 0 |
ANNEXES | Annexes 1 to 4: information document, communication, approval mark, CSMS certificate model | 0 |
INTERPRETATION | The Interpretation Document for UN Regulation No. 155 | 0 |
STANDARD | UN Regulation No. 155: the Regulation, its scope and definitions | 0 |
STATUS | Status: original version with Supplements 1 to 3; no 01 series; amendments in preparation | 0 |