UNECE WP.29 R155 A5-M19: Annex 5 M19 Security procedures defined and followed, with logging of security management actions

Organizations ensure security procedures are defined and followed, including logging of actions and access related to the management of security functions (Tables B3 and C2, 15.2: defined security procedures not followed).

Maintained by Gerard BlokdykVerified against the published standard 31 May 2026Control text last updated 21 May 2026

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

A5-B5-20.4 Annex 5 B5-20.4 Correlate data from different sources against driving data or diagnostic data manipulation
A5-M10 Annex 5 M10 The vehicle verifies the authenticity and integrity of messages it receives
A5-M11 Annex 5 M11 Security controls for storing cryptographic keys
A5-M12 Annex 5 M12 Confidential data transmitted to or from the vehicle is protected
A5-M13 Annex 5 M13 Measures to detect and recover from denial of service attacks
A5-M14 Annex 5 M14 Measures to protect systems against embedded viruses or malware should be considered
A5-M15 Annex 5 M15 Measures to detect malicious internal messages or activity should be considered
A5-M16 Annex 5 M16 Secure software update procedures are employed

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.

MCP endpoint All UNECE WP.29 R155 controls