Handling of an individual vulnerability starts when a new report arrives. Reports can concern vulnerabilities and potential vulnerabilities found internally, during development or after release; ones found by someone outside the vendor, whether a person or an organization (ISO/IEC 29147 governs that interface); and ones disclosed publicly without the vendor knowing or coordinating in advance. Vendors should keep a record of every vulnerability and potential vulnerability they receive and handle, whatever its source.
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.