OSPS-VM-02 Publish Contacts and Process for Reporting Vulnerabilities. (maturity level 1). Requirement: The project documentation MUST contain security contacts. Objective of the control: Enable external parties, such as researchers, to easily understand who they should contact in the event that a vulnerability is found, and what process they should follow. Recommendation: Create a security.md (or similarly-named) file that contains security contacts for the project.
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.