UNECE WP.29 R155
Annex 5 Part B: Mitigations intended for vehicles – UNECE WP.29 R155

UNECE WP.29 R155 A5-M23: Annex 5 M23 Cyber security best practices for software, hardware, system design and integration, with adequate test coverage

What does A5-M23 require?

Cyber security best practices for software and hardware development are followed (Table B6: 26.1 to 26.3 weak, insufficient or deprecated cryptography, 27.1 parts engineered to enable attacks or failing design criteria, 28.1 software bugs, 28.2 development remainders such as debug and JTAG ports, development certificates and passwords, 29.1 superfluous open ports); for the 28.1 to 29.1 rows the table adds cybersecurity testing with adequate coverage, and for 29.2 circumventing network separation it includes best practices for system design and system integration.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

Other controls in Annex 5 Part B: Mitigations intended for vehicles – UNECE WP.29 R155

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.