Security updates are delivered in a timely way, with timeliness judged by the issue, the fix, reachability of devices and resource constraints, and with priority for fixes to critical vulnerabilities with large-scale effects. Where several stakeholders (library vendors, device maker, platform operator) are involved they cooperate to achieve it, and users can be told through a bulletin once a fix exists. Status in Table B.1: M C (12) (mandatory, a shall provision; conditional on an update mechanism is implemented).
This control maps to 2 controls across 2 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 2 it maps to, and the evidence behind each claim, over MCP and REST.