CFTC System Safeguards (17 CFR 37, 38, 39, 49) CFTC-SS-13: Vulnerability Testing

What else in your programme already covers this

This control maps to 31 controls across 18 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

PCI DSS 4.0 · 5 controls

11.3.1 11.3.1 Quarterly internal vulnerability scans
11.3.1.2 11.3.1.2 Authenticated internal vulnerability scanning
11.3.1.3 11.3.1.3 Internal scans after significant change
11.3.2 11.3.2 Quarterly ASV external vulnerability scans
6.3.1 6.3.1 Vulnerability identification and risk ranking

CIS Controls v8 · 3 controls

CIS-7.1 Establish and Maintain a Vulnerability Management Process
CIS-7.5 Perform Automated Vulnerability Scans of Internal Enterprise Assets
CIS-7.6 Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets

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

CCM-A&A-03 Risk Based Planning Assessment
CCM-TVM-01 Threat and Vulnerability Management Policy and Procedures
CCM-TVM-07 Vulnerability Identification

NIST Cybersecurity Framework 2.0 · 3 controls

NIST-CSF-DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
NIST-CSF-ID.IM-01 Improvements are identified from evaluations
NIST-CSF-ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded

FedRAMP High · 2 controls

RA-5 Vulnerability Monitoring and Scanning
RA-5(2) Update Vulnerabilities to be Scanned

FedRAMP Moderate · 2 controls

RA-5 Vulnerability Monitoring and Scanning
RA-5(2) Update Vulnerabilities to be Scanned

NIST SP 800-161 Rev 1 · 2 controls

161R1-RA-5 Vulnerability Monitoring and Scanning
161R1-SI-5 Security Alerts, Advisories, and Directives

Azure Security Benchmark · 1 control

PV-5 Perform vulnerability assessments

C5 (Germany) · 1 control

C5-OPS-22 Testing and Documentation of known Vulnerabilities

CMMC 2.0 · 1 control

RA.L2-3.11.2 Vulnerability Scan

DORA · 1 control

DORA-Art.25 Testing of ICT tools and systems

HIPAA Security Rule · 1 control

164.308(a)(8) Evaluation (Standard)

ISO 27001:2022 · 1 control

8.8 Management of technical vulnerabilities

ISO 27002:2022 · 1 control

8.8 Management of technical vulnerabilities

NIST SP 800-171 Rev 3 · 1 control

03.11.02 Vulnerability Monitoring and Scanning

NIST SP 800-53 Rev 5 · 1 control

NIST800-RA-5 RA-5 Vulnerability Monitoring and Scanning

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(8) Evaluation (Standard)

SOC 2 · 1 control

SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities

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-13 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