CFTC System Safeguards (17 CFR 37, 38, 39, 49) CFTC-SS-19: Prompt Notification to the Commission

What else in your programme already covers this

This control maps to 29 controls across 20 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 Cybersecurity Framework 2.0 · 4 controls

NIST-CSF-GV.OC-03 Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed
NIST-CSF-RC.CO-03 Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders
NIST-CSF-RS.CO-02 Internal and external stakeholders are notified of incidents
NIST-CSF-RS.CO-03 Information is shared with designated internal and external stakeholders

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 3 controls

CCM-LOG-13 Failures and Anomalies Reporting
CCM-SEF-07 Security Breach Notification
CCM-SEF-08 Points of Contact Maintenance

APRA CPS 230 Operational Risk Management · 2 controls

CPS230-P33 APRA Notification of Operational Risk Incidents within 72 Hours
CPS230-P42 APRA Notification of Disruption Outside Tolerance within 24 Hours

ISO 22301:2019 · 2 controls

7.4 Communication
8.4.3 Warning and communication

NIST SP 800-161 Rev 1 · 2 controls

161R1-IR-5 Incident Monitoring
161R1-IR-6 Incident Reporting

SOC 2 · 2 controls

SOC2-CC2.3 CC2.3 Communication with external parties about internal control (COSO principle 15)
SOC2-CC7.4 CC7.4 Responding to security incidents

Azure Security Benchmark · 1 control

ASBv3-IR-2 Preparation - setup incident notification

C5 (Germany) · 1 control

C5-SIM-01 Policy for security incident management

CIS Controls v8 · 1 control

CIS-17.2 Establish and Maintain Contact Information for Reporting Security Incidents

CMMC 2.0 · 1 control

IR.L2-3.6.2 Incident Reporting

DORA · 1 control

DORA-Art.19 Reporting of major ICT-related incidents

FedRAMP High · 1 control

IR-6 Incident Reporting

HIPAA Security Rule · 1 control

164.308(a)(6)(ii) Response and Reporting (Required)

NIST SP 800-171 Rev 3 · 1 control

03.06.02 Incident Monitoring, Reporting, and Response Assistance

NIST SP 800-53 Rev 5 · 1 control

NIST800-IR-6 IR-6 Incident Reporting

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(6)(ii) Response and Reporting (Required)

PCI DSS 4.0 · 1 control

12.10.1 12.10.1 Incident response plan ready for activation

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.

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-19 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.

If you hold NIST Cybersecurity Framework 2.071.8% covered · 11 gaps If you hold FedRAMP Moderate69.2% covered · 12 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.161.5% covered · 15 gaps If you hold C5 (Germany)59% covered · 16 gaps If you hold DORA51.3% covered · 19 gaps If you hold NIST SP 800-161 Rev 148.7% covered · 20 gaps

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.

See the released pairs, $299 each Browse the graph free