Where the test includes exploitation or vulnerability confirmation, the organisation ensures it is conducted only within the authorised scope and rules of engagement, planned as a precision activity against agreed high-value targets rather than an indiscriminate one, and mindful of business disruption (with any noisy or high-impact activity reserved for an agreed point, such as gauging incident response). This leaf governs authorisation, planning and disruption control, and records the outcome for the report; it does not describe how any exploitation is performed.
This control maps to 2 controls across 2 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 2 it maps to, and the evidence behind each claim, over MCP and REST.