Before testing, the organisation and provider agree how and how often they will communicate and create an emergency contact list covering all parties in scope, with, for each contact, a name, role and operational responsibility, authorisation to discuss the test, and two forms of round-the-clock contact plus a secure bulk-data transfer method; a 24/7 staffed help desk or operations number may stand in for one contact. The list names the testers and their manager, technical and business contacts at the organisation and at any separate target, and a single responsible lead per party, and it is shared with everyone on it.
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.