CMMC 2.0
Risk Assessment

CMMC 2.0 RA.L2-3.11.3: Vulnerability Remediation

Remediate identified vulnerabilities in line with the priorities set by risk assessment.

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

What else in your programme already covers this

This control maps to 62 controls across 31 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-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.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure
  • SOC2-CC9.1 CC9.1 Mitigating risks of business disruption

CIS Controls v8 · 5 controls

  • CIS-16.2 Establish and Maintain a Process to Accept and Address Software Vulnerabilities
  • CIS-16.6 Establish and Maintain a Severity Rating System and Process for Application Vulnerabilities
  • CIS-7.2 Establish and Maintain a Remediation Process
  • CIS-7.3 Perform Automated Operating System Patch Management
  • CIS-7.7 Remediate Detected Vulnerabilities

NIST SP 800-218 · 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.1 11.3.2.1 External scans after significant change
  • 6.3.1 6.3.1 Vulnerability identification and risk ranking
  • 6.3.3 6.3.3 Timely installation of security patches

FedRAMP Moderate · 3 controls

  • RA-5 Vulnerability Monitoring and Scanning
  • SI-2 Flaw Remediation
  • RA-7 Risk Response

NIST SP 800-53 Rev 5 · 3 controls

ACSC Essential Eight · 2 controls

  • E8-PATCHAPP-ML1 Patch Applications (ML1)
  • E8-PATCHOS-ML1 Patch Operating Systems (ML1)
  • 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

FedRAMP High · 2 controls

  • RA-5 Vulnerability Monitoring and Scanning
  • SI-2 Flaw Remediation

ISO 27701:2019 · 2 controls

  • 5.6.3 Information security risk treatment
  • 6.9.6 Technical vulnerability management
  • 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-161 Rev 1 · 2 controls

NIST SP 800-171 Rev 3 · 2 controls

  • ANSSI-HYG-34 Define an Update Policy for Information System Components
  • CPS230-P31 Remediation of Material Operational Risk Weaknesses

APRA CPS 234 · 1 control

  • CPS234-21 Implementation of Information Security Controls
  • AUCDR-IS-4 Formal vulnerability management program
  • ASBv3-PV-6 Rapidly and automatically remediate vulnerabilities
  • CFTC-SS-21 Remediation of Vulnerabilities and Deficiencies

HIPAA Security Rule · 1 control

ISO 22301:2019 · 1 control

  • 10.2 Continual improvement

ISO 27001:2022 · 1 control

  • 8.8 Management of technical vulnerabilities

ISO 27002:2022 · 1 control

  • 8.8 Management of technical vulnerabilities

ISO/IEC 42001:2023 · 1 control

  • 10.2 Nonconformity and corrective action

NIS2 Directive · 1 control

  • Art.21.4 Take corrective measures without undue delay on finding that the measures are not met

NIST SP 800-172 · 1 control

  • 3.11.5e Assess Effectiveness of Security Solutions

UK Cyber Essentials · 1 control

  • CE-SU.3 Critical and High Updates within 14 Days

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 Risk Assessment

You are reading one control. How much of CMMC 2.0 have you already done?

CMMC 2.0 RA.L2-3.11.3 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CMMC 2.0 your existing evidence covers. Hold FedRAMP Moderate and 108 of 110 CMMC 2.0 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. 1 were rejected on the FedRAMP Moderate pair alone.

Query this from an agent

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