What a POA&M is in CMMC
The CMMC rule defines a POA&M as a document that identifies tasks needing to be accomplished, with the resources required, milestones and scheduled completion dates.
Under 32 CFR 170.21, a POA&M is permitted only for select requirements scored NOT MET during the assessment, and only to achieve a Conditional CMMC Status.
The scoring rule also requires a POA&M for each NOT MET requirement, and a POA&M is not a substitute for a completed requirement: a requirement that is not implemented is assessed NOT MET whether or not it is on a POA&M.
This guide covers Level 1 and Level 2.
Level 1: no POA&M
A POA&M is not permitted at any time for a Level 1 self-assessment, so every requirement has to be MET before you can achieve the status.
The Level 1 self-assessment guide covers the 15 requirements and how each is scored.
Level 2: the three conditions
At Level 2, a self-assessment or a C3PAO certification assessment can result in a Conditional status only if all three of these conditions are met:
- the score divided by 110, the total number of Level 2 requirements, is 0.8 or more, which means at least 88;
- no requirement on the POA&M is worth more than 1 point, except 3.13.11 (CUI encryption), which may be on it at 3 points when encryption is employed but not FIPS-validated;
- none of six named requirements is on the POA&M.
For a CMMC Level 2 Conditional status, the score must be at least 0.8 of the maximum, which is 88 of 110, and no item on the POA&M may be worth more than 1 point, except 3.13.11 when encryption is employed but not FIPS-validated.
The SPRS score guide explains where the point values come from, with a worked example.
Requirements that can never go on a POA&M
32 CFR 170.21 keeps off a POA&M any requirement worth more than 1 point, except 3.13.11 when encryption is employed but not FIPS-validated, and six requirements by name: 3.1.20, 3.1.22, 3.10.3, 3.10.4, 3.10.5 and 3.12.4.
| Requirement | As named in 32 CFR 170.21 | Points (Annex A) |
|---|---|---|
| 3.1.20 | AC.L2-3.1.20 External Connections (CUI Data) | 1 |
| 3.1.22 | AC.L2-3.1.22 Control Public Information (CUI Data) | 1 |
| 3.10.3 | PE.L2-3.10.3 Escort Visitors (CUI Data) | 1 |
| 3.10.4 | PE.L2-3.10.4 Physical Access Logs (CUI Data) | 1 |
| 3.10.5 | PE.L2-3.10.5 Manage Physical Access (CUI Data) | 1 |
| 3.12.4 | CA.L2-3.12.4 System Security Plan | No value (NA) |
The first five are each worth 1 point, so the point limit alone would allow them; the rule keeps them off by name.
3.12.4 is the system security plan, which must be in place at the time of assessment; the system security plan guide explains why there is no score without one.
The point limits, by value
| Point value of the NOT MET requirement | Can it go on a POA&M? |
|---|---|
| 5 | No |
| 3 | No, except 3.13.11 when encryption is employed but not FIPS-validated |
| 3 (3.5.3, multi-factor authentication for remote and privileged users only) | No |
| 1 | Yes, unless it is 3.1.20, 3.1.22, 3.10.3, 3.10.4 or 3.10.5 |
| No value (3.12.4, the system security plan) | No |
The SPRS score calculator applies these limits to the gaps you mark.
The 180-day closeout
A POA&M closeout assessment assesses only the NOT MET requirements that were on the POA&M in the initial assessment.
The closing of the POA&M must be confirmed by a closeout assessment within 180 days of the Conditional CMMC Status Date.
After a Level 2 self-assessment, you perform the closeout self-assessment yourself, in the same manner as the initial self-assessment, and post the results to SPRS.
After a Level 2 certification assessment, the closeout must be performed by an authorized or accredited C3PAO.
DFARS 252.204-7021 requires a contractor with a Conditional status to close out a valid POA&M to achieve a Final status.
The Affirming Official submits a new affirmation following the closeout assessment.
After a successful closeout, the CMMC Status Date stays the date of the Conditional status; a Final that follows a Conditional gets no new date.
If items stay open
If the POA&M is not successfully closed out within the 180-day timeframe, the Conditional CMMC Status for the information system expires.
If a Conditional status expires during a contract, standard contractual remedies apply, and the company is ineligible for new awards that require that status, or higher, for that information system until it achieves a new one.
Under DFARS 252.204-7021, a Conditional Level 2 status is current for no more than 180 days.
A POA&M is not an operational plan of action
32 CFR 170.4 defines an operational plan of action separately: the artifact, used for requirement 3.12.2, that identifies temporary vulnerabilities and temporary deficiencies and documents how they will be mitigated, corrected or eliminated.
You define its format and content, and it does not set a timeline for remediation.
The rule says it is not the same as a POA&M, which is tied to an assessment and must be completed within 180 days.
A temporary deficiency is one that arises after a requirement was implemented, where a fix is feasible and known or in process; addressed in an operational plan of action, it is assessed as MET.
An enduring exception, where remediation is not feasible, needs no operational plan of action but must be documented in the system security plan.
| POA&M | Operational plan of action | |
|---|---|---|
| Defined in | 32 CFR 170.4 and 170.21 | 32 CFR 170.4, for requirement 3.12.2 |
| What it holds | NOT MET requirements from an assessment | Temporary vulnerabilities and deficiencies found after implementation |
| Timeline | Closed out within 180 days of the Conditional status date | No remediation timeline |
| Format | Tasks, resources, milestones and completion dates | Format and content are yours to define |
| Effect on the finding | The requirement stays NOT MET until closed | A temporary deficiency addressed in it is assessed as MET |
How CMMCSync helps
POA&M management and SPRS score tracking are on the Maintain plan. The Foundations plan (Free) has no POA&M tool, and Level 1 allows no POA&M. Compare plans on the pricing page.
Sources
- 32 CFR 170.4, Acronyms and definitions
- 32 CFR 170.16, CMMC Level 2 self-assessment and affirmation requirements
- 32 CFR 170.17, CMMC Level 2 certification assessment and affirmation requirements
- 32 CFR 170.21, Plan of Action and Milestones requirements
- 32 CFR 170.22, Affirmation
- 32 CFR 170.24, CMMC Scoring Methodology
- DFARS 252.204-7021, Contractor Compliance with the CMMC Level Requirements
- NIST SP 800-171 DoD Assessment Methodology, Version 1.2.1 (June 24, 2020), Annex A scoring template
General information, not legal advice.