CIS Controls v8
CIS Control 7: Continuous Vulnerability Management

CIS Controls v8 CIS-7.6: Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets

Scan externally exposed enterprise assets for vulnerabilities automatically with a SCAP-compliant scanner, at least once a month.

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

What else in your programme already covers this

This control maps to 46 controls across 23 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 · 4 controls

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

FedRAMP Moderate · 4 controls

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

HIPAA Security Rule · 4 controls

NIST SP 800-66 Rev 2 · 4 controls

PCI DSS 4.0 · 4 controls

  • 11.3.1.1 11.3.1.1 Lower-risk vulnerabilities handled per risk analysis
  • 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.4.1 6.4.1 Public web application review or automated protection
  • ISM-1698 Daily vulnerability scanning of online services
  • ISM-1701 Daily scanning of internet-facing OS
  • ISM-1808 Up-to-date vulnerability database for scanning

C5 (Germany) · 3 controls

  • C5-OPS-19 Managing Vulnerabilities, Malfunctions and Errors - Penetration Tests
  • C5-OPS-22 Testing and Documentation of known Vulnerabilities
  • C5-PSS-02 Identification of Vulnerabilities of the Cloud Service

SOC 2 · 3 controls

  • SOC2-CC4.1 CC4.1 Ongoing and separate evaluations of control (COSO principle 16)
  • SOC2-CC6.6 CC6.6 Protection against threats from outside the system boundary
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • ASBv3-DS-5 Integrate dynamic application security testing into DevOps pipeline
  • PV-5 Perform vulnerability assessments
  • NIST-CSF-ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded
  • NIST-CSF-ID.RA-05 Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization
  • E8-PATCHOS-ML1 Patch Operating Systems (ML1)

APRA CPS 234 · 1 control

CMMC 2.0 · 1 control

DORA · 1 control

ISO 27001:2022 · 1 control

  • 8.8 Management of technical vulnerabilities

ISO 27002:2022 · 1 control

  • 8.8 Management of technical vulnerabilities

ISO 27701:2019 · 1 control

  • 6.9.6 Technical vulnerability management
  • 03.11.02 Vulnerability Monitoring and Scanning

NIST SP 800-172 · 1 control

  • 3.12.1e Penetration Testing by Independent Agents

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 CIS Control 7: Continuous Vulnerability Management

You are reading one control. How much of CIS Controls v8 have you already done?

CIS Controls v8 CIS-7.6 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CIS Controls v8 your existing evidence covers. Hold ISO 27001:2022 and 102 of 153 CIS Controls v8 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. 240 were rejected on the ISO 27001:2022 pair alone.

Query this from an agent

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