Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1
TVM - Threat & Vulnerability Management

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-TVM-08: Vulnerability Prioritization

Prioritise which vulnerabilities to fix first using a risk-based model built on an industry recognised framework rather than raw severity alone.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

CIS Controls v8 · 2 controls

  • CIS-16.6 Establish and Maintain a Severity Rating System and Process for Application Vulnerabilities
  • CIS-7.2 Establish and Maintain a Remediation Process

FedRAMP High · 2 controls

  • RA-5 Vulnerability Monitoring and Scanning
  • SI-2(3) Flaw Remediation | Time to Remediate Flaws and Benchmarks for Corrective Actions (SI-2(3))

FedRAMP Moderate · 2 controls

  • RA-5 Vulnerability Monitoring and Scanning
  • SI-2(3) Flaw Remediation | Time to Remediate Flaws and Benchmarks for Corrective Actions (SI-2(3))
  • NIST-CSF-ID.RA-05 Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization
  • NIST-CSF-ID.RA-06 Risk responses are chosen, prioritized, planned, tracked, and communicated

NIST SP 800-218 · 2 controls

PCI DSS 4.0 · 2 controls

  • 11.3.1.1 11.3.1.1 Lower-risk vulnerabilities handled per risk analysis
  • 6.3.1 6.3.1 Vulnerability identification and risk ranking
  • E8-PATCHAPP-ML1 Patch Applications (ML1)
  • ANSSI-HYG-34 Define an Update Policy for Information System Components
  • ASD37-19 Patch operating systems (Essential)
  • ASBv3-PV-6 Rapidly and automatically remediate vulnerabilities

C5 (Germany) · 1 control

  • C5-OPS-22 Testing and Documentation of known Vulnerabilities

CMMC 2.0 · 1 control

DORA · 1 control

  • DORA-Art.24 General requirements for the performance of digital operational resilience testing

HIPAA Security Rule · 1 control

ISO 27001:2022 · 1 control

  • 8.8 Management of technical vulnerabilities

ISO 27002:2022 · 1 control

  • 8.8 Management of technical vulnerabilities
  • 03.11.02 Vulnerability Monitoring and Scanning

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 TVM - Threat & Vulnerability Management

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

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.

Query this from an agent

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