CFTC System Safeguards (17 CFR 37, 38, 39, 49)
CFTC System Safeguards: Risk Analysis and Oversight Program

CFTC System Safeguards (17 CFR 37, 38, 39, 49) CFTC-SS-1: Program of Risk Analysis and Oversight

Establish and maintain a program of risk analysis and oversight covering operations and automated systems, to identify and minimise sources of operational risk through appropriate controls and procedures and through systems that are reliable, secure and have adequate scalable capacity.

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

What else in your programme already covers this

This control maps to 48 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.

HIPAA Security Rule · 5 controls

  • CPS230-11 Identification, Assessment and Management of Operational Risk
  • CPS230-24 Design and Embedding of Internal Controls
  • CPS230-9 Management of the Full Range of Operational Risks
  • CPS230-P12 Key Principles for Operational Risk, Resilience and Service Providers
  • NIST-CSF-GV.OV-01 Cybersecurity risk management strategy outcomes are reviewed to inform and adjust strategy and direction
  • NIST-CSF-GV.PO-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced
  • NIST-CSF-GV.RM-01 Risk management objectives are established and agreed to by organizational stakeholders
  • NIST-CSF-ID.RA-05 Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization

NIST SP 800-66 Rev 2 · 4 controls

C5 (Germany) · 3 controls

  • C5-OIS-01 Information Security Management System (ISMS)
  • C5-OIS-06 Risk Management Policy
  • C5-OIS-07 Application of the Risk Management Policy

FedRAMP High · 3 controls

  • CA-7 Continuous Monitoring
  • PL-2 System Security and Privacy Plans
  • RA-3 Risk Assessment

FedRAMP Moderate · 3 controls

  • CA-7 Continuous Monitoring
  • PL-2 System Security and Privacy Plans
  • RA-3 Risk Assessment

NIST SP 800-161 Rev 1 · 3 controls

DORA · 2 controls

ISO 22301:2019 · 2 controls

  • 5.2 Policy
  • 8.1 Operational planning and control

NIST SP 800-171 Rev 3 · 2 controls

NIST SP 800-53 Rev 5 · 2 controls

PCI DSS 4.0 · 2 controls

  • 12.1.1 12.1.1 Overall information security policy established and disseminated
  • 12.3.1 12.3.1 Targeted risk analysis for flexible-frequency requirements

SOC 2 · 2 controls

  • SOC2-CC3.1 CC3.1 Objectives specified clearly enough to assess risk (COSO principle 6)
  • SOC2-CC3.2 CC3.2 Identifying and analysing risks to objectives (COSO principle 7)
  • ASBv3-GS-5 Define and implement security posture management strategy

CMMC 2.0 · 1 control

ISO 27001:2022 · 1 control

  • 5.1 Policies for information security

ISO 27002:2022 · 1 control

  • 5.1 Policies for information security

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: Risk Analysis and Oversight Program

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

Query this from an agent

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