Capital Cyber News
Reporting for United States defense contractors and small business KEV catalog 2026.08.14

CMMC and NIST 800-171

POA&Ms: What They Cover and the 180 Day Clock

Level 2 of the Cybersecurity Maturity Model Certification (CMMC) and NIST SP 800-171 both require a POA&M, or Plan of Action and Milestones. This document lays out your plans for addressing gaps in security controls and helps you track remediation efforts. The 180 day clock applies only when a POA&M is used to reach a Conditional CMMC Status, and it starts on the Conditional CMMC Status Date.

What is a POA&M and why do you need one?

A POA&M is a documented plan that outlines specific actions your company will take to address cybersecurity gaps identified during a self assessment or internal review. For each gap, the POA&M must define what needs to be fixed, who is responsible, and the timeline for completion. This process is not optional if you find that any of the 320 assessment objectives under the 110 NIST SP 800-171 controls are not fully met. The requirement for plans of action comes from NIST SP 800-171 requirement 3.12.2 (CA.L2-3.12.2), and CMMC sets its own POA&M rules in 32 CFR 170.21.

DFARS 252.204-7012 and NIST SP 800-171 Rev 2 require you to safeguard CUI and document both your System Security Plan (SSP) and any gaps through a POA&M. These documents must be available for review during a government-led assessment, and your SPRS score must reflect your actual state of compliance.

How does a POA&M work at CMMC Level 2?

At Level 2, you are required to implement all 110 NIST SP 800-171 Rev 2 controls. The CMMC Scoping and Assessment Guide Level 2 v2.13 is clear: every assessment objective under each control must be met for the control to be considered fully implemented. If you identify a gap, meaning an objective is not met, you must document it in a POA&M.

The POA&M must include:

  • The specific control and objective not met (for example, AC.L2-3.1.5 for Least Privilege).
  • The reason for the gap.
  • The actions planned to remediate the gap.
  • The responsible party.
  • The scheduled completion date.

Importantly, you cannot simply leave a gap unaddressed. Under 32 CFR 170.21, a POA&M is permitted only for reaching a Conditional CMMC Status, only when your assessment score meets the minimum the rule sets, and only for eligible requirements. Every item on it must then be closed, and confirmed by a POA&M closeout assessment, within 180 days of the Conditional CMMC Status Date. If that does not happen, the Conditional status expires.

What happens to POA&Ms at Level 3?

Level 3 adds 24 enhanced controls from NIST SP 800-172 to the 110 NIST SP 800-171 Rev 2 controls, and the assessment is conducted by the Defense Industrial Base Cybersecurity Assessment Center (DIBCAC). The POA&M rules follow the same pattern as Level 2, with their own conditions. Under 32 CFR 170.21, a POA&M is permitted only for reaching Conditional Level 3 (DIBCAC) status, only with a minimum assessment score, and only for eligible requirements. DIBCAC must confirm the closeout within 180 days of the Conditional CMMC Status Date, or the Conditional status expires.

What does the 180 day POA&M clock mean for your business?

Identifying a gap starts no clock, whether you find it in a gap assessment, an internal review or a self assessment. The 180 day timeline starts on the Conditional CMMC Status Date, the date you achieve a Conditional status with a POA&M. Within 180 days of that date you must remediate every open item and confirm it with a POA&M closeout assessment. For Level 2 (Self), that is a closeout self assessment with the results posted to SPRS. Your senior official submits an affirmation when you reach Conditional status and again after the closeout. The government has stated it will continue to enforce compliance through self assessments and select government-led reviews, even while third party certification is suspended.

If the POA&M is not closed out within 180 days, the Conditional status expires. If that happens during a contract's period of performance, standard contractual remedies apply, and you are ineligible for new awards that require that status until you achieve a new one. Inaccurately representing your state of compliance increases your exposure to False Claims Act liability. The signature of your senior official on the affirmation is now the primary assurance to the government, as the requirement for third party certification is currently suspended.

What must a POA&M contain to satisfy CMMC and NIST SP 800-171?

A valid POA&M must be specific and actionable. It cannot be a general statement that you will fix something at some point. State the control, the specific gap, planned actions, responsible party, and deadline. The POA&M must tie directly to your SSP and be updated as you make progress. Documentation alone is not proof; you must be able to show evidence of execution, system logs, configuration screenshots, or other timestamped artifacts.

What are the risks of ignoring or mishandling POA&Ms?

If you fail to maintain accurate POA&Ms, you risk both compliance violations and contractual liability. The government has taken enforcement action against companies that falsely certified compliance or failed to remediate known vulnerabilities. For example, Health Net Federal Services was found to have certified compliance without scanning and remediating vulnerabilities, and Aero Turbine was cited for failing controls and sharing defense data with an unauthorized foreign entity. In the Aero Turbine case, the private equity owner was named in the settlement, and False Claims Act liability can also extend to prime contractors, subcontractors and affiliates.

Maintaining accurate POA&Ms is more than a paperwork exercise. It is a core part of your legal and contractual obligations to the government.

Can you use POA&Ms to manage partial compliance at Level 2?

You should use POA&Ms to document and manage gaps at Level 2, because NIST SP 800-171 calls for plans of action to correct deficiencies. What a POA&M cannot do is stand in for a met requirement. It supports a Conditional CMMC Status only when the conditions in 32 CFR 170.21 are met, and the 180 day window starts on the Conditional CMMC Status Date. Your SPRS score must accurately reflect your current state, including any open POA&M items. You must update your SSP and POA&M as you close gaps. If a Conditional status reaches the end of its 180 days with open items, that status expires.

Common questions

What is the difference between an SSP and a POA&M? An SSP (System Security Plan) describes your system and how you meet each required control. A POA&M documents the specific actions you will take to address any gaps found during assessment.

Can I submit a POA&M instead of being fully compliant at Level 2? A POA&M documents gaps. It does not replace compliance. Under 32 CFR 170.21 it can support a Conditional CMMC Status only if your score meets the minimum and every item on it is eligible, and then every item must be closed within 180 days of the Conditional CMMC Status Date. Your SPRS score must reflect your actual status, and your affirmation must be accurate.

What happens if I do not remediate a POA&M item within 180 days? If you hold a Conditional CMMC Status and the POA&M is not closed out within 180 days of the Conditional CMMC Status Date, the Conditional status expires. Affirming compliance you do not have increases your risk of enforcement action or False Claims Act liability.

For more on CMMC and NIST SP 800-171 requirements, you can review NIST SP 800-171 Rev 2 directly from NIST.

How to Track Your 180 Day POA&M Timeline

If you need help assessing your current compliance or closing POA&M items, consider applying for the Cyber Grants Alliance CMMC Gap Assessment Grant. This in kind grant is delivered as services and covers all 110 NIST 800-171 controls for qualifying defense contractors. Learn more and apply at https://cybergrantsalliance.org/cmmc-gap-assessment-grant/.

At a glance

The proof chain from policy to assessmentDocumentation shows intent. Evidence proves execution.Policydefines intentProceduredescribes howEvidenceproves executionAssessmentvalidates realityA control is not met because you wrote it down. It is met because you can prove it happened.
The proof chain from policy to assessment
Policy, procedure, evidence, assessment
Policy, procedure, evidence, assessment

More on CMMC