CFTC System Safeguards: Business Continuity and Disaster Recovery
CFTC System Safeguards (17 CFR 37, 38, 39, 49) CFTC-SS-30: Outsourcing with Retention of Complete Responsibility
Where required resources are maintained through a contractual outsourcing arrangement, retain complete responsibility for any failure to meet the program and recovery requirements and employ personnel with the expertise necessary to supervise the provider delivery of the services.
Maintained by Gerard Blokdyk·Verified against the published standard ·Control text last updated
What else in your programme already covers this
This control maps to 45 controls across 19 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
NIST-CSF-DE.CM-06 External service provider activities and services are monitored to find potentially adverse events
NIST-CSF-GV.SC-01 A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders
NIST-CSF-GV.SC-02 Cybersecurity roles and responsibilities for suppliers, customers, and partners are established, communicated, and coordinated internally and externally
NIST-CSF-GV.SC-05 Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties
You are reading one control. How much of CFTC System Safeguards (17 CFR 37, 38, 39, 49) have you already done?
CFTC System Safeguards (17 CFR 37, 38, 39, 49) CFTC-SS-30 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.