Where vulnerability analysis is performed, the organisation ensures it is scoped to the depth and breadth needed to meet the agreed goals (for example confirming a mitigation works, or exhaustively testing with authenticated access) and that identified issues are validated rather than reported on the say-so of a single tool. This leaf governs that the analysis is bounded, its depth agreed and its findings corroborated; it does not prescribe technique or tooling.
This control maps to 3 controls across 3 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 3 it maps to, and the evidence behind each claim, over MCP and REST.