DefenseEye.ai

Assessment Preparation

CMMC POA&M: What Assessors Actually Look For (And What Gets You Failed)

A Plan of Action & Milestones (POA&M) is required for any NIST SP 800-171 control not yet fully implemented — and most contractors write them in ways that hurt rather than help their assessments. This guide covers what C3PAO assessors evaluate in a POA&M per the CMMC Assessment Process, the required fields, high-risk items that block certification, and what assessors call out as signs of a poorly managed program.

A Plan of Action & Milestones (POA&M) is a required artifact for any NIST SP 800-171 control your organization has not yet fully implemented. Under the CMMC 2.0 final rule, POA&Ms are formally recognized as part of the assessment process — a contractor with a well-structured POA&M can receive conditional CMMC Level 2 certification for certain gaps, with a 180-day window to close them. What the rule does not allow is using a POA&M to indefinitely defer critical controls. The CMMC 2.0 rule establishes that high-priority practices — including MFA and CUI encryption — cannot remain in POA&M status at initial certification.

The problem most contractors face is not whether to have a POA&M, but how to write one that demonstrates security program maturity rather than confirming the assessor's concerns about program immaturity. A well-written POA&M communicates: 'We know what's missing, we understand the risk, we have credible mitigations in place, and we have a realistic plan.' A poorly written one communicates the opposite.

What a POA&M Is Supposed to Do

A POA&M documents every security control that isn't fully implemented, describes the weakness specifically, identifies who is responsible for fixing it, establishes a realistic completion timeline, and describes any interim mitigating controls in place while the gap exists. It gives the C3PAO visibility into your risk awareness and your remediation discipline. A well-crafted POA&M tells the assessor: 'We know exactly what's missing, we understand the risk, and we have a credible plan to close it.'

The Required Fields (Don't Omit Any)

  • NIST 800-171 Practice Number (e.g., 3.5.3) — The specific control being addressed, not a general category
  • Weakness description — What specifically is not implemented and on which systems or user populations
  • Point of contact — Named individual (not a role or department) responsible for remediation
  • Scheduled completion date — A specific calendar date, not 'Q3' or 'end of year'
  • Milestones with intermediate dates — For items taking more than 30 days, break the work into stages with dates
  • Mitigation approach — Detailed steps being taken to close the gap
  • Interim/compensating controls — What you're doing right now to reduce risk while the gap exists
  • Resources required — Budget, tools, personnel, or vendor engagement needed
  • Status update date — When was the POA&M item last reviewed and updated

The Completion Date Problem

The scheduled completion date is where most POA&Ms fall apart. Assessors are trained to scrutinize these dates carefully because they reveal whether the organization actually understands the remediation effort or just wrote something optimistic to look good on paper.

  • Unrealistic timelines: If MFA is listed as 'completion: 2 weeks' but the organization has 300 endpoints, active directory migration in progress, and no IT staff dedicated to the project, the assessor will probe whether the timeline is credible during interviews.
  • Dates already past: If POA&M items show completion dates that have already passed and the item is marked 'open,' this is a serious red flag. It signals either poor program management or that dates were fabricated. Either way, assessors will dig in.
  • Everything due 'in 180 days': Putting a 180-day completion date on every item — regardless of actual effort — signals the organization copy-pasted a template without thinking through the remediation. Assessors see this constantly and view it as a sign of program immaturity.
  • The right approach: Estimate each item independently. Simple configuration changes (e.g., enabling a security setting in M365) should have short timelines (1–2 weeks). Major architecture changes (e.g., network segmentation) should have realistic longer timelines with intermediate milestones.

High-Risk POA&M Items That Block Certification

Not all POA&M items are created equal for certification purposes. The CMMC Level 2 rules establish that certain 'critical' controls cannot remain on a POA&M at initial certification — they must be implemented. The following categories of controls are considered too high-risk to defer:

  • Multi-factor authentication (3.5.3, 3.5.4) — Any practice related to MFA for privileged or non-privileged users. If MFA isn't implemented, conditional certification is not available.
  • Incident response capability (3.6.1) — No plan at all, not just an untested plan
  • CUI encryption at rest and in transit (3.13.8, 3.13.10) — Storing CUI in plaintext or transmitting unencrypted is a critical gap
  • Audit logging (3.3.1, 3.3.2) — No audit logging capability at all, as opposed to incomplete coverage

Interim Compensating Controls: What Actually Counts

For every POA&M item, you should document what you're doing to reduce risk while the gap is being remediated. Assessors evaluate whether the compensating control is genuine or performative. Generic statements like 'we are monitoring the environment' do not constitute a compensating control.

  • Specific technical controls: 'CUI access is restricted to the VPN-connected segment while endpoint MFA implementation is in progress' is a real compensating control.
  • Admin procedure controls: 'Privileged accounts require manual supervisor approval before login credentials are used while PAM deployment is in progress' is real.
  • Not real: 'Management is aware of the risk.' 'The IT team is working on it.' These are awareness statements, not compensating controls.

POA&M Formatting That Makes Assessors' Lives Easier

Assessors work through hundreds of documents. POA&Ms that are clearly organized, consistently formatted, and easy to navigate create goodwill that disorganized documents destroy. Practical formatting tips:

  • Use the NIST 800-171 practice number as the primary sort key — assessors think in control numbers
  • Group items by domain (AC, IA, AU, etc.) for visual organization
  • Color-code status: Open (gray), In Progress (blue), Complete (green) — even in a spreadsheet
  • Include a dashboard summary: total items open, count by priority, count closed since last update
  • Date every update clearly — assessors want to see this is a live document, not a one-time creation
  • Cross-reference the SSP — each POA&M item should reference the SSP section where the control implementation is described
  • Keep a separate 'closed items' tab — show assessors what you've already fixed since starting the program

The Bottom Line

Your POA&M is a direct reflection of your security program's sophistication. A well-structured POA&M with realistic dates, specific mitigations, named owners, and evidence of regular review tells the assessor you run a real program. A sloppy POA&M with vague language, past-due items, and wishful timelines tells them the opposite — and they'll look much harder at everything else.

Your POA&M is a direct representation of your security program's discipline. A well-structured POA&M with specific control references, realistic remediation timelines, named owners, genuine compensating controls, and evidence of regular updates demonstrates program maturity. A disorganized POA&M with vague language, past-due items, and no evidence of ongoing management tells the assessor to look harder at everything else.

Authoritative Sources

  • CMMC 2.0 Final Rule (32 CFR Part 170) — federalregister.gov: Section 170.21 covers POA&M requirements for conditional CMMC certification, including the 180-day closeout window
  • NIST SP 800-171 DoD Assessment Methodology — dodcio.defense.gov: defines how unimplemented controls affect SPRS score and POA&M treatment during assessment
  • NIST SP 800-171A — csrc.nist.gov: assessment procedures assessors use to verify each control — understanding 171A shows you what evidence to provide for each POA&M item
  • OMB Circular A-130 — whitehouse.gov/omb: 'Managing Information as a Strategic Resource' — the foundational federal policy requirement for POA&Ms across all federal information systems
  • CMMC Assessment Process (CAP) — cyberab.org/Resources/Downloads: describes how C3PAOs handle POA&M items during assessment; conditional status criteria are set in 32 CFR 170.17 and 170.21