A signed permission-to-test document is in place before testing starts: it states the scope, acknowledges awareness of the testers' activities, records that testing can cause instability and that due care will be taken, and allocates liability for any instability or crash. Where targets are hosted or operated by third parties (cloud providers, ISPs, web hosts, managed security service providers), the organisation ensures the third party's consent and any provider-specific request, notice or approval is obtained, because the client's permission does not speak for its providers. The legality of planned activities is checked for every jurisdiction (country, province or state) where systems are located or the work 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.