Patch management procedures. Level 1 (a and b): patch management procedures, and a process for bringing up to date systems that were offline or left unused for a period. Level 2 (a to d): risk ratings assigned to identified vulnerabilities; prioritised patching within defined periods; testing of patches before deployment; and management of systems dormant or offline for more than 30 days. Level 3 adds a further patch management requirement.
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.
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.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.