To the extent practicable, coordinate the business continuity and disaster recovery plan with those of the members, clearing members and other market participants on whom the registrant depends, so that activity can effectively resume following a disruption.
This control maps to 14 controls across 11 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.
CFTC System Safeguards (17 CFR 37, 38, 39, 49) CFTC-SS-27 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CFTC System Safeguards (17 CFR 37, 38, 39, 49) your existing evidence covers. Hold NIST Cybersecurity Framework 2.0 and 28 of 39 CFTC System Safeguards (17 CFR 37, 38, 39, 49) controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 5 were rejected on the NIST Cybersecurity Framework 2.0 pair alone.
The graph holds this control, the 14 it maps to, and the evidence behind each claim, over MCP and REST.