CIS Controls v8
CIS Control 7: Continuous Vulnerability Management

CIS Controls v8 CIS-7.2: Establish and Maintain a Remediation Process

Set up and keep a remediation process that records a risk-based strategy for fixing vulnerabilities, reviewed at least monthly.

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

What else in your programme already covers this

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

SOC 2 · 6 controls

  • SOC2-CC3.2 CC3.2 Identifying and analysing risks to objectives (COSO principle 7)
  • SOC2-CC4.2 CC4.2 Evaluating and communicating control deficiencies (COSO principle 17)
  • SOC2-CC5.1 CC5.1 Selecting control activities that mitigate risk (COSO principle 10)
  • SOC2-CC7.4 CC7.4 Responding to security incidents
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure
  • SOC2-CC9.1 CC9.1 Mitigating risks of business disruption
  • NIST-CSF-GV.OV-01 Cybersecurity risk management strategy outcomes are reviewed to inform and adjust strategy and direction
  • NIST-CSF-GV.RM-07 Strategic opportunities (i.e., positive risks) are characterized and are included in organizational cybersecurity risk discussions
  • NIST-CSF-ID.IM-02 Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties
  • NIST-CSF-ID.RA-06 Risk responses are chosen, prioritized, planned, tracked, and communicated
  • NIST-CSF-PR.PS-02 Software is maintained, replaced, and removed commensurate with risk

PCI DSS 4.0 · 5 controls

  • 11.3.1 11.3.1 Quarterly internal vulnerability scans
  • 11.3.1.1 11.3.1.1 Lower-risk vulnerabilities handled per risk analysis
  • 11.4.4 11.4.4 Correct exploitable findings from penetration tests
  • 6.3.1 6.3.1 Vulnerability identification and risk ranking
  • 6.3.3 6.3.3 Timely installation of security patches

ISO 22301:2019 · 4 controls

  • 10.2 Continual improvement
  • 6.1.2 Addressing risks and opportunities
  • 8.2.3 Risk assessment
  • 9.3 Management review

ISO 27001:2022 · 4 controls

  • 5.24 Information security incident management planning and preparation 
  • 5.35 Independent review of information security
  • 8.32 Change management
  • 8.8 Management of technical vulnerabilities

ISO 27701:2019 · 4 controls

  • 5.4.1 Actions to address risks and opportunities
  • 5.6.3 Information security risk treatment
  • 5.7.3 Management review
  • 5.8.1 Nonconformity and corrective action

NIST SP 800-53 Rev 5 · 4 controls

FedRAMP High · 3 controls

  • CA-5 Plan of Action and Milestones
  • SI-2 Flaw Remediation
  • SI-2(3) Flaw Remediation | Time to Remediate Flaws and Benchmarks for Corrective Actions (SI-2(3))

FedRAMP Moderate · 3 controls

  • CA-5 Plan of Action and Milestones
  • SI-2 Flaw Remediation
  • SI-2(3) Flaw Remediation | Time to Remediate Flaws and Benchmarks for Corrective Actions (SI-2(3))

ISO/IEC 42001:2023 · 3 controls

  • 10.2 Nonconformity and corrective action
  • 6.1.3 AI risk treatment
  • 9.3 Management review

NIST SP 800-171 Rev 3 · 3 controls

  • ANSSI-HYG-34 Define an Update Policy for Information System Components
  • ANSSI-HYG-38 Carry Out Regular Security Checks and Audits and Apply the Corrective Actions

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

NIS2 Directive · 2 controls

  • Art.21.2.e Security in acquisition, development and maintenance, including vulnerability handling and disclosure
  • Art.21.4 Take corrective measures without undue delay on finding that the measures are not met

NIST SP 800-161 Rev 1 · 2 controls

NIST SP 800-218 · 2 controls

  • E8-PATCHAPP-ML3 Patch Applications (ML3)
  • AUCDR-IS-4 Formal vulnerability management program
  • ISM-1143 Patch management processes and procedures
  • ASBv3-PV-6 Rapidly and automatically remediate vulnerabilities
  • CFTC-SS-21 Remediation of Vulnerabilities and Deficiencies

CIS Controls v8.1 · 1 control

  • 7.2 Establish and Maintain a Remediation Process

DORA · 1 control

  • DORA-Art.50 Administrative penalties and remedial measures

HIPAA Security Rule · 1 control

ISO 27002:2022 · 1 control

  • 8.8 Management of technical 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 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.2 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 70 it maps to, and the evidence behind each claim, over MCP and REST.