Keep a process for receiving and dealing with reports of software vulnerabilities, including a channel for outside parties. It should include a vulnerability handling policy naming the reporting route and the party responsible, and steps that take a report in, assign it, fix it and test the fix, using a tracking system with severity ratings and metrics on time to identify, analyse and fix. Review yearly or after significant change. Developers of third-party applications should treat this as an externally facing policy that sets expectations for outside stakeholders. Implementation Groups: IG2 and IG3 (not in the IG1 baseline; applies from IG2 upward). Asset type: Documentation. Security function: Govern.
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.