ETSI EN 303 645
5.3 Keeping software updated – ETSI EN 303 645

ETSI EN 303 645 Provision 5.3-11: User told clearly when a security update is required and why

When a security update is needed, the user is told in a recognisable and apparent way, together with information on the risks it mitigates, for example through a UI notification or email. Status in Table B.1: R C (12) (recommendation, a should provision; conditional on an update mechanism is implemented).

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

What else in your programme already covers this

This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

  • Annex I Part II(8) Dissemination of security updates without delay and free of charge, with advisories

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in 5.3 Keeping software updated – ETSI EN 303 645

Query this from an agent

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