Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-TVM-09: Vulnerability Management Reporting

What else in your programme already covers this

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

FedRAMP High · 3 controls

CA-5 Plan of Action and Milestones
RA-5 Vulnerability Monitoring and Scanning
SI-2(2) Automated Flaw Remediation Status

FedRAMP Moderate · 3 controls

CA-5 Plan of Action and Milestones
RA-5 Vulnerability Monitoring and Scanning
SI-2(2) Automated Flaw Remediation Status

NIST SP 800-218 · 3 controls

SP800-218-PW.8.2 Execute Security Testing
SP800-218-RV.1.3 Vulnerability Disclosure Policy
SP800-218-RV.2.2 Develop and Implement Remediation Plans

NIST Cybersecurity Framework 2.0 · 2 controls

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

NIST SP 800-171 Rev 3 · 2 controls

03.11.02 Vulnerability Monitoring and Scanning
03.12.02 Plan of Action and Milestones

APRA CPS 234 · 1 control

CPS234-28 Escalation of Unremediated Testing Deficiencies

AWS Well-Architected Security Pillar · 1 control

SEC04-BP02 Capture logs, findings, and metrics in standardized locations

Australia Consumer Data Right - Banking (CDR) · 1 control

AUCDR-IS-4 Formal vulnerability management program

Azure Security Benchmark · 1 control

PV-2 Audit and enforce secure configurations

C5 (Germany) · 1 control

C5-PSS-03 Online Register of Known Vulnerabilities

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

CFTC-SS-36 Internal Reporting and Review by Senior Management and the Board

CMMC 2.0 · 1 control

RA.L2-3.11.2 Vulnerability Scan

DORA · 1 control

DORA-Art.13 Learning and evolving

EU AI Act · 1 control

EUAI-Art.72 Post-market monitoring by providers and post-market monitoring plan for high-risk AI systems

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-161 Rev 1 · 1 control

161R1-CA-5 Plan of Action and Milestones

NIST SP 800-53 Rev 5 · 1 control

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

PCI DSS 4.0 · 1 control

11.4.4 11.4.4 Correct exploitable findings from penetration tests

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 Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 have you already done?

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-TVM-09 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 140 of 197 Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 controls already carry evidence.

If you hold NIST SP 800-53 Rev 571.1% covered · 57 gaps If you hold FedRAMP Moderate60.4% covered · 78 gaps If you hold PCI DSS 4.060.4% covered · 78 gaps If you hold C5 (Germany)58.4% covered · 82 gaps If you hold ISO 27001:202256.3% covered · 86 gaps If you hold ISO 27002:202256.3% covered · 86 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. 12 were rejected on the NIST SP 800-53 Rev 5 pair alone.

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