NIST SP 800-171
System Security Plan vs POA&M: What Assessors Read First
Your System Security Plan is the first thing an assessor reads, every time. If it is thin or wrong, strong technology will still score badly.
Cybersecurity Consulting, a Capital Cyber practice in Leesburg, Virginia, provides CISO level leadership for CMMC, NIST SP 800-171 and federal authorization, with a program for ITAR technical data.
What is a System Security Plan?
It sets out your system boundary, your setup, and how each of the 110 NIST SP 800-171 requirements is met. Requirement 3.12.4 calls for it. So the SSP is itself checked.
A useful SSP is specific. For each requirement it names the tool, the setting, the owner and the procedure. An outsider could go and check it.
"We use multifactor authentication" is a claim. Compare this: "Multifactor authentication is enforced by a conditional access policy for all users of the enclave tenant, with exceptions reviewed quarterly by the IT lead." That is a statement an assessor can test.
What is a POA&M?
A Plan of Action and Milestones lists the requirements not yet fully met. For each, it says the fix, the owner and the date.
Requirement 3.12.2 asks for plans of action that fix gaps and reduce or remove weak points. Most contractors meet it with the POA&M.
Each entry names the requirement and the gap in plain words. It gives the fix, an owner and a real date. Stopgap steps that cut risk in the meantime go there too.
A POA&M with no dates, or with dates that have all passed, tells an assessor the program is not being managed.
Which does an assessor read first?
The SSP, because it defines what is assessed. Its boundary, asset list, diagram and statements become the map. Interviews, reviews and tests are planned from it.
Under the DoD Assessment Methodology, a missing SSP is not just a lower score. Without one, the assessment cannot be finished at all.
That is why a contractor with strong tools and a thin SSP often scores worse than expected. The assessor can only credit what the SSP explains and the evidence proves.
How do the SSP and POA&M fit together?
They describe one setup from two angles and must never clash. The SSP says how each requirement is met. Where one is not, the SSP says so and points to the POA&M entry.
Clashes are the most common problem we find. Picture an SSP that says a requirement is in place, and a POA&M that lists it as open. Which does the assessor believe?
Usually the answer is neither. After that, every other statement in both documents gets read with more doubt.
What makes a System Security Plan statement hold up?
It holds up when it traces to evidence an assessor can see. Name the system, the setting and the owner. Describe the procedure in the order it really happens.
Then cite where the evidence lives. That could be a policy section, a settings export, a log query or a ticket history.
Write to the assessment objectives in NIST SP 800-171A, not just the requirement text. Many requirements have several objectives, and each one is judged.
A statement that answers the headline but misses one objective leaves the requirement unmet. That holds however good the rest of it is.
How many items can stay open on the POA&M?
Fewer than most hope. For CMMC Level 2 conditional status, 32 CFR part 170 needs a score of at least 88 out of 110.
It limits which items may stay open. Each must close within 180 days.
The highest weighted requirements generally cannot be put off.
For the SPRS score under DFARS 252.204-7019, open POA&M items still count as not met. The POA&M records the plan, but it does not earn the points. Finishing the work is what lifts the score.
How often should you update both?
Update both whenever the setup changes. Review them on a schedule even when nothing seems to have changed.
A new cloud service, a new office, a new managed provider or a change in how CUI arrives all change the SSP. Closing a gap, slipping a date or finding a new gap all change the POA&M.
A sensible minimum is a documented review before each annual affirmation, with version history kept for both. The person who signs should see that the SSP is current and the POA&M dates are real.
Where do most contractors go wrong?
Most treat the SSP as a template to fill in, not a picture of their own setup. Generic vendor text is easy to spot. So are tools the company does not use, and a diagram that does not match the network.
The second mistake is leaving evidence to the end. Evidence gathered as you build is easier to find and more convincing. It is also less stressful than a last minute scramble.
Write the SSP as you build and keep the POA&M honest. The assessment then becomes a review of work already written down.
Next step: book a 30 minute call with the practice to have your System Security Plan read the way an assessor would.