How to Calculate Your SPRS Score (NIST SP 800-171)

An SPRS score for NIST SP 800-171 starts at 110, the number of requirements. For each requirement not implemented, you subtract its value of 1, 3 or 5 points, so the score can go negative. Without a system security plan there is no score at all, and the summary score is posted in SPRS.

By Hemant Bundele

Last reviewed: November 16, 2026

What the score is and who requires it

The score comes from the NIST SP 800-171 DoD Assessment Methodology, which DoD uses to assess how much of NIST SP 800-171 a contractor has implemented.

DFARS 252.204-7012 is the clause that makes covered contractor information systems subject to the security requirements in NIST SP 800-171.

The codified text of DFARS 252.204-7019 says that, to be considered for award, an offeror required to implement NIST SP 800-171 must have a current assessment, not more than three years old unless the solicitation sets a shorter time.

Since February 1, 2026, DoD contracting officers have used a revised DFARS Part 240, issued as class deviation 2026-O0025, in place of the codified text.

Neither the deviation's original text nor its Revision 3 of September 3, 2026, prescribes 252.204-7019 or 252.204-7020.

Instead it prescribes 252.240-7997, which defines only two kinds of assessment, Medium and High, both conducted by Government personnel.

A self-assessed score still goes into SPRS through CMMC: when a contract carries 252.204-7021 at CMMC Level 2 (Self), 32 CFR 170.16 has you submit the self-assessment results, including the score, in SPRS.

CMMC Level 2 uses the same arithmetic: under 32 CFR 170.24, the maximum is the number of Level 2 requirements, and the value of each NOT MET requirement is subtracted from it.

How points are deducted

Start at 110, the total number of NIST SP 800-171 security requirements, and subtract the value of each requirement that is not implemented.

Each requirement is worth 5, 3 or 1 points, weighted by how much its absence would affect the system and the CUI on it.

PointsIf not implementedRequirementsCount
5Could lead to significant exploitation of the network, or exfiltration of CUI3.1.1, 3.1.2, 3.1.12, 3.1.13, 3.1.16, 3.1.17, 3.1.18, 3.2.1, 3.2.2, 3.3.1, 3.3.5, 3.4.1, 3.4.2, 3.4.5, 3.4.6, 3.4.7, 3.4.8, 3.5.1, 3.5.2, 3.5.10, 3.6.1, 3.6.2, 3.7.2, 3.7.5, 3.8.3, 3.8.7, 3.9.2, 3.10.1, 3.10.2, 3.11.2, 3.12.1, 3.12.3, 3.13.1, 3.13.2, 3.13.5, 3.13.6, 3.13.15, 3.14.1, 3.14.2, 3.14.3, 3.14.4, 3.14.642
3Has a specific and confined effect on the network and its data3.1.5, 3.1.19, 3.3.2, 3.7.1, 3.7.4, 3.8.1, 3.8.2, 3.8.8, 3.9.1, 3.11.1, 3.12.2, 3.13.8, 3.14.5, 3.14.714
3 or 5Partially effective (see partial credit below)3.5.3, 3.13.112
1Has a limited or indirect effect on the network and its dataAll remaining requirements51
NoneNot scored: no plan means no assessment (see below)3.12.41
Total110

Counts tallied from the scoring template in Annex A of the methodology.

Partial credit: 3.5.3 and 3.13.11

Only two requirements can earn partial credit.

Multi-factor authentication (3.5.3) costs 3 points if it is implemented only for remote and privileged users, and 5 points if it is not implemented for any users.

FIPS-validated encryption (3.13.11) costs 3 points if encryption is employed but not FIPS-validated, and 5 points if encryption is not employed.

What counts as not implemented

A plan of action does not earn the points: a requirement that is not implemented is scored that way whether or not a plan of action is in place.

Without a plan of action for each unimplemented requirement, 3.12.2 itself is assessed as not implemented.

Temporary deficiencies handled in a plan of action, and isolated enduring exceptions described in the system security plan, are assessed as implemented.

The lowest possible score

Neither the methodology nor 32 CFR 170.24 states a minimum; both say only that subtracting may result in a negative score.

Adding every value in the methodology's Annex A scoring template gives 313 points: 42 requirements at 5, 14 at 3, 51 at 1, and up to 5 each for 3.5.3 and 3.13.11, with 3.12.4 carrying no value.

So the lowest possible score is 110 minus 313, or -203.

32 CFR 170.24 sets the CMMC weights by category rather than in a per-requirement template, so treat -203 as the methodology's arithmetic, not a figure printed in the CMMC rule.

Why the system security plan comes first

The methodology scores by reviewing a system security plan, so it is not possible to conduct the assessment without one.

The absence of a system security plan results in a finding that “an assessment could not be completed due to incomplete information and noncompliance with DFARS clause 252.204-7012.”

That is why 3.12.4, the requirement to have a system security plan, carries no point value in the template: without the plan there is no score, not a lower one.

The CMMC rule is the same: an up-to-date system security plan must be in place at the time of assessment, and it is one of the requirements that can never go on a CMMC POA&M.

What the plan has to describe is covered in the system security plan guide.

A worked example

A made-up small manufacturer runs its self-assessment and finds these gaps. Everything else is implemented.

RequirementFindingPoints
3.3.1 Create and retain system audit logsNot implemented-5
3.5.3 Multi-factor authenticationRemote and privileged users only-3
3.13.11 FIPS-validated encryptionEncryption used, not FIPS-validated-3
3.14.7 Identify unauthorized useNot implemented-3
3.1.8 Limit unsuccessful logon attemptsNot implemented-1
3.1.10 Session lockNot implemented-1
3.5.5 Prevent reuse of identifiersNot implemented-1
Total-17

The score is 110 minus 17, or 93.

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.

Here 93 clears the threshold, but 3.3.1, 3.5.3 and 3.14.7 are worth more than 1 point and cannot go on the POA&M, so this result does not reach a Conditional status until they are fixed.

The three 1-point gaps and 3.13.11 could go on a POA&M, which must be closed out within 180 days.

To run the same arithmetic on your own answers, use the SPRS score calculator.

The DoD methodology and CMMC Level 2 scoring: the differences

  • Same weights. The 5-point and 3-point lists in 32 CFR 170.24 match the methodology's, including the partial credit for 3.5.3 and 3.13.11.
  • Findings. CMMC records MET, NOT MET or N/A, and an N/A objective counts as MET.
  • POA&M. CMMC requires a POA&M for each NOT MET requirement, limits what it may contain, and requires a closeout assessment within 180 days of the Conditional status date.
  • Who scores. A Basic assessment, in the methodology's terms, is your own self-assessment, with a confidence level of “Low”; CMMC Level 2 is either a self-assessment or a certification assessment by a C3PAO.

For where third-party assessment stands today, see the CMMC compliance overview.

Where the score is posted

Under the methodology, summary level scores are posted in SPRS, and a contractor may post the results of its own Basic assessment. SPRS still gives a contractor an entry for a NIST SP 800-171 Basic self-assessment: the SPRS user guide for contractors, Version 4.1.5 of May 2026, describes a Basic sub-tab for contractor self-assessments, the only kind vendors can add, edit or delete. The guide labels the NIST SP 800-171 Assessments tab that holds it as supporting DFARS 252.240-7997, previously 252.204-7019 and 7020.

Under 252.240-7997, DoD posts Medium and High assessment results for each system security plan assessed: the standard assessed, who assessed it, the company entities covered, the date and level of the assessment, the summary score (not the value of each requirement) and the date by which all requirements are expected to be implemented.

For a CMMC Level 2 self-assessment, the SPRS entry records the CMMC level, the CMMC Status Date, the assessment scope, the overall score and any POA&M use.

A C3PAO enters its assessment results into the CMMC instance of eMASS, which sends them to SPRS automatically.

How CMMCSync helps

On the Maintain plan, SPRS score tracking applies these point values as you record findings, including the partial credit for 3.5.3 and 3.13.11, and keeps daily snapshots of the score. The SSP Generator drafts the system security plan the score depends on. See the features page.

Sources

  1. NIST SP 800-171 DoD Assessment Methodology, Version 1.2.1 (June 24, 2020)
  2. DFARS 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting
  3. DFARS 252.204-7019, Notice of NIST SP 800-171 DoD Assessment Requirements (codified text, not prescribed for DoD solicitations under class deviation 2026-O0025)
  4. DFARS 252.204-7020, NIST SP 800-171 DoD Assessment Requirements (codified text, not prescribed for DoD solicitations under class deviation 2026-O0025)
  5. DFARS 252.204-7021, Contractor Compliance with the CMMC Level Requirements
  6. DoD class deviation 2026-O0025, FAR Overhaul Part 40 and DFARS Part 240 (effective February 1, 2026)
  7. DoD class deviation 2026-O0025, Revision 3 (September 3, 2026), with the revised DFARS Part 240 text (Attachment 1)
  8. SPRS Software User’s Guide for Awardees/Contractors, Version 4.1.5 (May 2026)
  9. 32 CFR 170.16, CMMC Level 2 self-assessment and affirmation requirements
  10. 32 CFR 170.17, CMMC Level 2 certification assessment and affirmation requirements
  11. 32 CFR 170.21, Plan of Action and Milestones requirements
  12. 32 CFR 170.24, CMMC Scoring Methodology

General information, not legal advice.

Stay assessment-ready between assessments.

Start with Foundations (Free) for the Level 1 self-assessment, or talk to the founder about what your contract requires.

Free to start — no application, no quote call. Cancel paid plans anytime.