NIST SP 800-171 Rev 3
03.12 CA (Security Assessment and Monitoring)

NIST SP 800-171 Rev 3 03.12.02: Plan of Action and Milestones

Develop and update a POAM to document planned remediation actions for weaknesses identified during assessments; track to closure.

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

What else in your programme already covers this

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

HIPAA Security Rule · 2 controls

ISO 27001:2022 · 2 controls

  • 5.36 Compliance with policies, rules and standards for information security
  • 8.8 Management of technical vulnerabilities
  • 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 SP 800-161 Rev 1 · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

  • ANSSI-HYG-38 Carry Out Regular Security Checks and Audits and Apply the Corrective Actions
  • CPS230-P31 Remediation of Material Operational Risk Weaknesses

APRA CPS 234 · 1 control

  • CPS234-28 Escalation of Unremediated Testing Deficiencies
  • AUCDR-IS-STEP4 Step 4 - Implement a formal controls assessment program
  • ASBv3-PV-6 Rapidly and automatically remediate vulnerabilities

C5 (Germany) · 1 control

  • C5-OPS-22 Testing and Documentation of known Vulnerabilities
  • CFTC-SS-21 Remediation of Vulnerabilities and Deficiencies

CIS Controls v8 · 1 control

  • CIS-7.2 Establish and Maintain a Remediation Process

CMMC 2.0 · 1 control

FedRAMP High · 1 control

  • CA-5 Plan of Action and Milestones

FedRAMP Moderate · 1 control

  • CA-5 Plan of Action and Milestones

ISO 27701:2019 · 1 control

  • 5.8.1 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-218 · 1 control

  • 53A-3.4 Analyze Assessment Report Results

PCI DSS 4.0 · 1 control

  • 11.4.4 11.4.4 Correct exploitable findings from penetration tests

SOC 2 · 1 control

  • SOC2-CC4.2 CC4.2 Evaluating and communicating control deficiencies (COSO principle 17)

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 03.12 CA (Security Assessment and Monitoring)

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

NIST SP 800-171 Rev 3 03.12.02 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-171 Rev 3 your existing evidence covers. Hold PCI DSS 4.0 and 69 of 97 NIST SP 800-171 Rev 3 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. 0 were rejected on the PCI DSS 4.0 pair alone.

Query this from an agent

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