NIST SP 800-218
NIST SP 800-218: Cryptography

NIST SP 800-218 SP800-218-RV.2.2: Develop and Implement Remediation Plans

Plan and implement risk responses for vulnerabilities, including remediation, mitigation, or acceptance with rationale.

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

What else in your programme already covers this

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

NIST SP 800-53 Rev 5 · 4 controls

CIS Controls v8 · 3 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
  • CIS-7.7 Remediate Detected Vulnerabilities

CMMC 2.0 · 3 controls

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 3 controls

FedRAMP Moderate · 3 controls

  • CA-5 Plan of Action and Milestones
  • SI-2 Flaw Remediation
  • RA-7 Risk Response

NIST SP 800-161 Rev 1 · 3 controls

NIST SP 800-171 Rev 3 · 3 controls

PCI DSS 4.0 · 3 controls

  • 11.3.1.1 11.3.1.1 Lower-risk vulnerabilities handled per risk analysis
  • 6.2.3.1 6.2.3.1 Manual code review independence and approval
  • 6.3.3 6.3.3 Timely installation of security patches

Azure Security Benchmark · 2 controls

  • ASBv3-PV-6 Rapidly and automatically remediate vulnerabilities
  • PV-5 Perform vulnerability assessments

C5 (Germany) · 2 controls

  • C5-OPS-18 Managing Vulnerabilities, Malfunctions and Errors - Concept
  • C5-SP-03 Exceptions from Existing Policies and Instructions

FedRAMP High · 2 controls

  • CA-5 Plan of Action and Milestones
  • SI-2 Flaw Remediation

NIST Cybersecurity Framework 2.0 · 2 controls

  • 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

SOC 2 · 2 controls

  • SOC2-CC7.5 CC7.5 Recovering from security incidents
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

AWS Well-Architected Security Pillar · 1 control

ISO 27001:2022 · 1 control

  • 8.8 Management of technical vulnerabilities

ISO 27002:2022 · 1 control

  • 8.8 Management of technical vulnerabilities

OpenSSF Best Practices Badge Criteria · 1 control

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 NIST SP 800-218: Cryptography

You are reading one control. How much of NIST SP 800-218 have you already done?

NIST SP 800-218 SP800-218-RV.2.2 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-218 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 30 of 42 NIST SP 800-218 controls already carry evidence.

If you hold NIST SP 800-53 Rev 571.4% covered · 12 gapsIf you hold C5 (Germany)61.9% covered · 16 gapsIf you hold NIST SP 800-161 Rev 161.9% covered · 16 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.152.4% covered · 20 gapsIf you hold ISO 27002:202252.4% covered · 20 gapsIf you hold Azure Security Benchmark50% covered · 21 gaps

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. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll NIST SP 800-218 controls