CMMC and DFARSPublished Last reviewed November 20269 min read
Short answer
A defensible SPRS self assessment score is one you can prove requirement by requirement. Score from 110 with the 32 CFR 170.24 method, claim MET only when every NIST SP 800-171A objective has evidence, use a POA&M only within CMMC limits (at least 88 of 110, closed within 180 days), and have a senior affirming official review the evidence before signing.
Check where you stand: take the CMMC readiness check. About two minutes, no email needed.
Update, November 2026
On July 13, 2026, DoD suspended the CMMC Phase 2 requirements that had been scheduled for November 10, 2026, and no restart date had been announced as of November 15, 2026. Level 2 self assessments, the POA&M and scoring rules in 32 CFR 170, annual affirmations in SPRS and DFARS 252.204-7012 remain in effect, and DoD said it would keep enforcing NIST SP 800-171 Rev 2 through self assessments and selected government assessments.
Your SPRS score is not a target you report toward. It is a statement to the Department of Defense about how your systems protect controlled unclassified information (CUI), and under CMMC it comes with an affirmation from a senior official. A defensible score claims only what you can prove today, requirement by requirement, and lets the plan of action and milestones (POA&M) rules carry what is not done yet.
Our view is that a lower score backed by evidence is worth more than a higher one you cannot demonstrate. With CMMC Phase 2 scheduled for November 10, 2026, it is also the best preparation for an outside assessor.
How is an SPRS self assessment score calculated?
You start at 110, the number of NIST SP 800-171 Revision 2 requirements, and subtract 5, 3 or 1 point for every requirement that is NOT MET. CMMC adopted this scoring from the NIST SP 800-171 DoD Assessment Methodology, and 32 CFR 170.24 now sets it out in regulation.
The weights follow security impact. Requirements such as AC.L2-3.1.1 (authorized access), AU.L2-3.3.1 (audit logs), IR.L2-3.6.1 (incident handling) and SI.L2-3.14.2 (malicious code protection) cost 5 points. A smaller group, including AU.L2-3.3.2 and CA.L2-3.12.2, costs 3, and the rest cost 1. DOJ has described the possible range as negative 203 to 110.
Only two requirements earn partial credit. IA.L2-3.5.3 costs 3 points instead of 5 if multifactor authentication covers remote and privileged users but not everyone. SC.L2-3.13.11 costs 3 instead of 5 if CUI is encrypted with cryptography that is not FIPS validated. A requirement with eight of nine objectives in place is NOT MET.
What evidence backs each requirement you claim as MET?
Evidence that someone else could check without taking your word for it. Under 32 CFR 170.24, a requirement is MET only when every applicable objective is satisfied based on evidence, so the unit of proof is the assessment objective in NIST SP 800-171A, not the requirement.
NIST SP 800-171A describes three assessment methods: examine, interview and test. In practice that means a document that says what you do, a record or configuration that shows you do it, and a person who can explain it. Here is what holds up for requirements that move a score the most.
| Requirement | Points if NOT MET | Evidence that holds up in Microsoft 365 |
|---|---|---|
| IA.L2-3.5.3 multifactor authentication | 5, or 3 if only remote and privileged users are covered | Conditional Access policy exports covering all users, sign in logs showing MFA satisfied, and a documented approach for break glass accounts |
| SC.L2-3.13.11 FIPS validated cryptography | 5, or 3 if encryption is not FIPS validated | NIST CMVP certificate numbers for each module that protects CUI and the setting that keeps it in its validated mode |
| AU.L2-3.3.1 audit logging | 5 | Microsoft Purview audit turned on, a defined retention period, and log samples that cover the systems in scope |
| SI.L2-3.14.2 malicious code protection | 5 | Microsoft Defender for Endpoint onboarding status for every device in scope, with exceptions explained |
| CA.L2-3.12.4 system security plan | Cannot go on a POA&M | A current, dated and approved SSP that describes the boundary and how each requirement is met |
N/A is a claim too. It counts the same as MET, so record why each one does not apply. Wireless requirements are a reasonable N/A only if you can show there is no wireless access into the environment in scope.
Keep the evidence dated and tied to the score you posted. Screenshots taken months later do not show how you arrived at your number. Our NIST SP 800-171 implementation work is built around keeping that evidence trail current.
What are the POA&M rules for a CMMC Level 2 self assessment?
A POA&M is allowed only if your score is at least 88 of 110, and only for low weight requirements. Meet them and you hold Conditional Level 2 (Self) status while you close the items. The rules sit in 32 CFR 170.21.
- Your score divided by 110 must be at least 0.8, which means 88 points or more.
- Every requirement on the POA&M must have a point value of 1. The one exception is SC.L2-3.13.11 when encryption is in place but is not FIPS validated.
- Six requirements can never be on a POA&M: AC.L2-3.1.20, AC.L2-3.1.22, CA.L2-3.12.4, PE.L2-3.10.3, PE.L2-3.10.4 and PE.L2-3.10.5.
- You must close the POA&M within 180 days of your Conditional status date through a closeout self assessment and post the result in SPRS. Miss that window and the Conditional status expires.
- A POA&M is not credit. Under 32 CFR 170.24 it is not a substitute for a completed requirement, so your score still reflects every open item.
Do not confuse a POA&M with an operational plan of action. A temporary deficiency, where a known fix is available or in process for something already implemented, can still be scored MET if an operational plan of action documents it. A requirement that was never implemented belongs on the POA&M.
We wrote a Level 2 POA&M that an Air Force Research Laboratory program office accepted as the basis for releasing CUI. That shapes our view of a credible one: each item names the requirement, the objective that is not met, the interim mitigation, an owner and a closeout date. Our CMMC compliance work starts from that standard.
What does the annual affirmation commit you to?
It commits a named senior person to the statement that your company has implemented, and will maintain, every applicable CMMC requirement. Under 32 CFR 170.22, the affirming official is a senior level representative of the organization, and affirmations are entered in SPRS after every assessment, including POA&M closeout, and annually after that.
DFARS 252.204-7021 makes this contractual. It requires you to maintain the CMMC status your contract calls for and to complete the affirmation of continuous compliance each year, or sooner when your compliance status changes. The DFARS 252.204-7025 provision makes a current status and affirmation in SPRS a condition of award.
Our advice: the affirming official should see the evidence before signing, not a summary slide. If the person signing cannot explain how multifactor authentication is enforced or where CUI is stored, the affirmation rests on someone else’s assurance.
How does the False Claims Act apply to SPRS scores?
An inaccurate score can support False Claims Act liability when it is part of how a contractor wins or gets paid on a contract. DOJ launched its Civil Cyber-Fraud Initiative in October 2021 to use the False Claims Act against contractors that knowingly misrepresent their cybersecurity practices or knowingly provide deficient cybersecurity products or services.
Knowingly is a lower bar than most people expect. Under 31 U.S.C. 3729, it includes deliberate ignorance and reckless disregard of the truth, with no proof of specific intent to defraud required. Liability can include three times the government’s damages plus a civil penalty for each claim, and whistleblowers can file suit and share in the recovery.
The MORSECORP settlement shows how a score figures in. According to DOJ, the company reported a score of 104 in January 2021, a third party consultant put its actual score at negative 142 in July 2022, and the company did not update SPRS until June 2023, after a government subpoena. In March 2025 it agreed to pay $4.6 million. When you learn your score is wrong, correct it promptly and keep a record of when and why. This is general information, not legal advice, so talk with counsel about your own exposure.
What changed in the DFARS cybersecurity clauses in early 2026?
DoD reorganized them. Class deviations that took effect in February 2026, issued as part of the Revolutionary FAR Overhaul, moved DFARS cybersecurity coverage into a new Part 240. The 252.204-7019 notice is no longer prescribed, and 252.204-7020 is replaced by 252.240-7997, NIST SP 800-171 DoD Assessment Requirements, under class deviation 2026-O0025.
The new clause drops the Basic Assessment. It keeps the government Medium and High assessments, posting of their summary scores in SPRS, the 14 business day window to respond before those scores post, and flowdown to subcontractors. DFARS 252.204-7012, 252.204-7021 and 252.204-7025 kept their numbers.
This is not the end of the SPRS score. Where a solicitation or contract carries a CMMC Level 2 (Self) requirement, 32 CFR 170.16 still requires you to enter your results in SPRS, including the score, scope, CAGE codes and POA&M status, and DFARS 252.204-7012 still requires you to implement NIST SP 800-171. Older contracts can still carry the earlier clause numbers until they are modified, so read the clause list in each one.
The reorganization changed clause numbers. It did not change what a posted Level 2 (Self) score is: a representation, backed by an affirming official, that needs evidence behind it.
If you want a second set of eyes on your score, your evidence or your POA&M before your next affirmation, book a 30 minute call with our team.
PDF, 6 pages, updated November 2026
Get the CMMC self assessment readiness checklist
- Where CMMC stands after the Phase 2 pause, with dated primary sources.
- 24 checks across scope, documentation, controls and evidence, each tied to its NIST SP 800-171 requirement.
- How to score yourself, and the POA&M rules if your score lands under 110.
Where should we send it?
We email you the checklist and may follow up about it. Read our privacy policy.
Frequently asked questions
Can we count a requirement as MET if most of it is in place?
No. A requirement is MET only when every applicable assessment objective is satisfied. The only partial credit in the scoring method is for multifactor authentication and for encryption that is not FIPS validated. Anything else that is mostly done is NOT MET and should be scored that way, with a POA&M if it qualifies.
Who should serve as our affirming official?
A senior leader who is accountable for the company’s compliance and can attest to it, often the owner, president or a senior operations executive. It should not be your outside IT provider. Pick someone who will review the evidence personally, because the affirmation is made in that person’s name.
What should we do if we find a mistake after posting our score?
Correct it. Document what you found, when you found it and how you rescored, then update SPRS and, if needed, your POA&M. A prompt correction with a clear record is far easier to defend than a score you knew was wrong and left in place.
Does NIST SP 800-171 Revision 3 change how we score?
Not for CMMC as of May 2026. The CMMC rule at 32 CFR 170 defines Level 2 as the 110 requirements of NIST SP 800-171 Revision 2, and scoring follows that version even though NIST has published Revision 3. Watch your contract language for any change.
Do subcontractors need their own SPRS score?
Yes, when the requirements flow down to them. Primes must flow down the NIST SP 800-171 and CMMC clauses and confirm subcontractor status before award, so a subcontractor handling CUI needs its own assessment, evidence and affirmation rather than relying on the prime’s work.