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-07: Vulnerability Identification

Scan organisationally managed assets for vulnerabilities at least monthly through a defined and evaluated process.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 49 controls across 28 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 · 6 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
  • 11.3.2.1 11.3.2.1 External scans after significant change
  • 6.3.1 6.3.1 Vulnerability identification and risk ranking

ACSC Essential Eight · 4 controls

  • E8-PATCHAPP-ML1 Patch Applications (ML1)
  • E8-PATCHAPP-ML2 Patch Applications (ML2)
  • E8-PATCHOS-ML1 Patch Operating Systems (ML1)
  • E8-PATCHOS-ML2 Patch Operating Systems (ML2)

CIS Controls v8 · 4 controls

  • CIS-16.2 Establish and Maintain a Process to Accept and Address Software Vulnerabilities
  • 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

FedRAMP High · 3 controls

  • RA-5 Vulnerability Monitoring and Scanning
  • RA-5(3) Vulnerability Monitoring and Scanning | Breadth and Depth of Coverage (RA-5(3))
  • SI-2 Flaw Remediation

FedRAMP Moderate · 3 controls

  • RA-5 Vulnerability Monitoring and Scanning
  • RA-5(3) Vulnerability Monitoring and Scanning | Breadth and Depth of Coverage (RA-5(3))
  • SI-2 Flaw Remediation
  • ASD37-02 Patch applications (Essential)
  • ASD37-19 Patch operating systems (Essential)

C5 (Germany) · 2 controls

  • C5-OPS-18 Managing Vulnerabilities, Malfunctions and Errors - Concept
  • C5-OPS-22 Testing and Documentation of known Vulnerabilities

CMMC 2.0 · 2 controls

ISO 27701:2019 · 2 controls

  • 6.15.2 Information security reviews
  • 6.9.6 Technical vulnerability management

NIST SP 800-53 Rev 5 · 2 controls

  • ANSSI-HYG-38 Carry Out Regular Security Checks and Audits and Apply the Corrective Actions
  • CBPR-PR-33 Testing the effectiveness of safeguards
  • AUCDR-IS-4 Formal vulnerability management program
  • PV-5 Perform vulnerability assessments

DORA · 1 control

EU AI Act · 1 control

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

NIST SP 800-172 · 1 control

  • 3.12.1e Penetration Testing by Independent Agents

NIST SP 800-218 · 1 control

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.

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-07 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 49 it maps to, and the evidence behind each claim, over MCP and REST.