A process shall be employed to develop and maintain a threat model for the product covering its correct usage, trust boundaries, data flows, external interfaces, attack vectors, potential attackers and the security context, reviewed and updated with each significant change.
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.