CFTC System Safeguards (17 CFR 37, 38, 39, 49)
CFTC System Safeguards: Notification, Records and Remediation

CFTC System Safeguards (17 CFR 37, 38, 39, 49) CFTC-SS-21: Remediation of Vulnerabilities and Deficiencies

Identify and document the vulnerabilities and deficiencies revealed by the required testing and assessment, analyse and document the risks they present in order to decide and document whether to remediate or accept the risk, and remediate in a timely manner given the nature and magnitude of the risk.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 53 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 · 7 controls

  • NIST-CSF-GV.RM-02 Risk appetite and risk tolerance statements are established, communicated, and maintained
  • NIST-CSF-GV.RM-07 Strategic opportunities (i.e., positive risks) are characterized and are included in organizational cybersecurity risk discussions
  • NIST-CSF-ID.IM-01 Improvements are identified from evaluations
  • NIST-CSF-ID.IM-02 Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties
  • NIST-CSF-ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities
  • NIST-CSF-ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded
  • NIST-CSF-ID.RA-06 Risk responses are chosen, prioritized, planned, tracked, and communicated

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

PCI DSS 4.0 · 5 controls

  • 11.3.1.1 11.3.1.1 Lower-risk vulnerabilities handled per risk analysis
  • 11.4.4 11.4.4 Correct exploitable findings from penetration tests
  • 12.10.6 12.10.6 Plan evolved from lessons learned and industry developments
  • 6.3.1 6.3.1 Vulnerability identification and risk ranking
  • 6.3.3 6.3.3 Timely installation of security patches

CIS Controls v8 · 4 controls

  • CIS-16.2 Establish and Maintain a Process to Accept and Address Software Vulnerabilities
  • CIS-18.3 Remediate Penetration Test Findings
  • CIS-7.2 Establish and Maintain a Remediation Process
  • CIS-7.7 Remediate Detected Vulnerabilities

CMMC 2.0 · 3 controls

FedRAMP Moderate · 3 controls

  • CA-5 Plan of Action and Milestones
  • SI-2 Flaw Remediation
  • RA-7 Risk Response

NIST SP 800-161 Rev 1 · 3 controls

NIST SP 800-171 Rev 3 · 3 controls

NIST SP 800-53 Rev 5 · 3 controls

Azure Security Benchmark · 2 controls

  • ASBv3-IR-7 Post-incident activity - conduct lesson learned and retain evidence
  • ASBv3-PV-6 Rapidly and automatically remediate vulnerabilities

C5 (Germany) · 2 controls

  • C5-OPS-18 Managing Vulnerabilities, Malfunctions and Errors - Concept
  • C5-SP-03 Exceptions from Existing Policies and Instructions

FedRAMP High · 2 controls

  • CA-5 Plan of Action and Milestones
  • SI-2 Flaw Remediation

ISO 27001:2022 · 2 controls

  • 5.27 Learning from information security incidents
  • 8.8 Management of technical vulnerabilities

ISO 27002:2022 · 2 controls

  • 5.27 Learning from information security incidents
  • 8.8 Management of technical vulnerabilities

SOC 2 · 2 controls

  • SOC2-CC4.2 CC4.2 Evaluating and communicating control deficiencies (COSO principle 17)
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities

APRA CPS 230 Operational Risk Management · 1 control

  • CPS230-P31 Remediation of Material Operational Risk Weaknesses

DORA · 1 control

HIPAA Security Rule · 1 control

ISO 22301:2019 · 1 control

  • 10.1 Nonconformity and corrective action

NIST SP 800-66 Rev 2 · 1 control

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.

Other controls in CFTC System Safeguards: Notification, Records and Remediation

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-21 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 gapsIf you hold FedRAMP Moderate69.2% covered · 12 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.161.5% covered · 15 gapsIf you hold C5 (Germany)59% covered · 16 gapsIf you hold DORA51.3% covered · 19 gapsIf 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 eachBrowse the graph free

Query this from an agent

The graph holds this control, the 53 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll CFTC System Safeguards (17 CFR 37, 38, 39, 49) controls