Once a security update is available, manufacturers must share and publicly disclose information on fixed vulnerabilities: a description, how users identify affected products, impact, severity and clear remediation help. In justified cases where publication risks outweigh benefits, they may delay publication until users have had the chance to patch.
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.