DefenseEye.ai

CMMC Knowledge Hub

SPRS Score Explained: How to Calculate, Submit, and Improve Your Score

Learn how NIST SP 800-171 DoD Assessment scores work for DoD contractors, including weighted deductions, SPRS submission, CMMC status distinctions, and remediation priorities.

Quick Answer

An SPRS score (Supplier Performance Risk System) is a numerical rating from -203 to +110 produced by the NIST SP 800-171 DoD Assessment Methodology for the 110 Revision 2 security requirements. A score of 110 means all scored requirements are implemented; each NOT MET requirement reduces the score by its assigned value, subject to two expressly defined partial-implementation cases. When DFARS 252.204-7019 applies, an offeror must have a current assessment score in SPRS for each relevant covered contractor information system before award. This NIST assessment score is distinct from a CMMC Status and from any solicitation-specific minimum or status requirement.

What is an SPRS Score?

The Supplier Performance Risk System (SPRS) stores summary results for NIST SP 800-171 DoD Assessments. A contractor performs a Basic Assessment, while DoD personnel perform Medium and High Assessments; Basic, Medium, and High describe the confidence level of the NIST assessment, not a CMMC level or status.

DFARS 252.204-7019 requires a current NIST SP 800-171 DoD Assessment for each relevant covered contractor information system when the provision applies. Current means not more than three years old unless the solicitation specifies a shorter period. The provision requires a current assessment in SPRS, but it does not establish one universal minimum numerical score for every award.

CMMC is a separate assessment and status framework. CMMC Level 1 and some Level 2 assessments are self-assessments; other Level 2 assessments are conducted by a C3PAO, and Level 3 assessments are conducted by DCMA DIBCAC. CMMC affirmations are submitted in SPRS by an Affirming Official after assessment and annually thereafter; that affirmation process is not part of submitting a NIST SP 800-171 Basic Assessment score.

Arithmetic minimum under the weighted deductions
-203
Maximum score (all scored requirements implemented)
110
Authorized submission access
PIEE / SPRS

How SPRS Scores Are Calculated

The NIST SP 800-171 DoD Assessment Methodology, Version 1.2.1, defines the score stored in SPRS. CMMC Level 2 uses the same weighted scoring structure in 32 CFR 170.24, but a numerical NIST assessment score and a CMMC Status remain distinct records and requirements.

Scoring Formula

Starting Score = 110
For each NOT MET requirement: subtract its assigned value
Final score = 110 - (sum of deductions for NOT MET requirements)

Each scorable requirement has a deduction value of 1, 3, or 5 based on the DoD methodology. For example, if every other scored requirement is implemented, one NOT MET 5-point requirement produces a score of 105. The maximum deductions total 313 points, so applying every maximum deduction to the starting score of 110 produces the arithmetic minimum of -203. An up-to-date System Security Plan is required to conduct the assessment; its absence does not simply produce another numerical deduction.

Assessment results and scoring are handled as follows: MET (all applicable assessment objectives are satisfied — no deduction), NOT MET (one or more applicable objectives are not satisfied — the assigned deduction applies), or Limited partial-implementation scoring (only IA.L2-3.5.3 (MFA) and SC.L2-3.13.11 (FIPS-validated encryption) have expressly defined 3-point versus 5-point deductions; there is no generic partial-credit category).

Illustrative Score Examples — Not Official Risk Bands

Example ScoreHow It Could Be ProducedWhat It Does and Does Not Mean
110All scored requirements are implementedMaximum NIST assessment score; it is not by itself a CMMC certificate or a guarantee of award
105Illustrative example: one 5-point requirement is NOT MET and all other scored requirements are implementedShows weighted scoring; it does not identify which requirement is missing
88Any combination of weighted deductions totaling 22 pointsThis is the numerical threshold for Conditional CMMC Level 2, but Conditional status also requires that every NOT MET item be POA&M-eligible; meeting any 88 requirements is not sufficient
Below 88Weighted deductions total more than 22 pointsCannot support Conditional CMMC Level 2 under 32 CFR 170.21; it can still be a NIST assessment score stored in SPRS
-203Illustrative arithmetic result when every maximum deduction is appliedMinimum produced by the published weighting table; not an official SPRS risk-band label

The 110 NIST 800-171 Requirements and Their Weighted Deductions

The 110 Revision 2 requirements are distributed across 14 families. Requirement count is not the same as point impact: NOT MET requirements deduct 1, 3, or 5 points. The table totals the maximum published deductions by family; CA.L2-3.12.4 is required for an assessment but is not assigned a numerical deduction.

FamilyRequirementsMaximum Possible DeductionKey Notes
Access Control (AC)2254Seven 5-point, two 3-point, and thirteen 1-point requirements
Awareness and Training (AT)311Two 5-point and one 1-point requirements
Audit and Accountability (AU)919Two 5-point, one 3-point, and six 1-point requirements
Configuration Management (CM)933Six 5-point and three 1-point requirements
Identification and Authentication (IA)1127Includes IA.L2-3.5.3, with defined 3-point or 5-point deductions
Incident Response (IR)311Two 5-point and one 1-point requirements
Maintenance (MA)618Two 5-point, two 3-point, and two 1-point requirements
Media Protection (MP)923Two 5-point, three 3-point, and four 1-point requirements
Personnel Security (PS)28One 5-point and one 3-point requirement
Physical Protection (PE)614Two 5-point and four 1-point requirements
Risk Assessment (RA)39One 5-point, one 3-point, and one 1-point requirement
Security Assessment (CA)413Two 5-point and one 3-point requirement; the SSP requirement is not numerically scored
System & Communications Protection (SC)1642Includes SC.L2-3.13.11, with defined 3-point or 5-point deductions
System & Information Integrity (SI)731Five 5-point and two 3-point requirements
TOTAL110313Maximum deductions from a starting score of 110 produce an arithmetic minimum of -203

How to Submit Your SPRS Score to the DoD

When DFARS 252.204-7019 applies, the offeror must verify before award that SPRS contains a current NIST SP 800-171 DoD Assessment for every relevant covered contractor information system. The NIST Basic Assessment entry process is separate from entering and affirming a CMMC self-assessment:

  1. 1 — Complete the NIST SP 800-171 Basic Assessment

    Apply the DoD Assessment Methodology to the 110 Revision 2 requirements and calculate the summary score. Generic partial credit is not available; only MFA and FIPS-validated encryption have the methodology's defined adjusted deductions. CMMCLens can automate this assessment from your cloud evidence.

  2. 2 — Verify the CAGE hierarchy sourced from SAM

    SPRS imports the company CAGE hierarchy from SAM. Confirm that the applicable CAGE codes and ownership hierarchy are correct so the assessment can be associated with the relevant covered contractor information systems.

  3. 3 — Obtain authorized PIEE and SPRS access

    Access SPRS through PIEE. A user entering or editing Basic Assessment information needs the SPRS Cyber Vendor User role and approval for the applicable company hierarchy.

  4. 4 — Enter the Basic Assessment summary in SPRS

    In Cyber Reports, open the NIST SP 800-171 Assessments tab and add a Basic Assessment. Enter the assessment date, summary score, scope, applicable POA&M completion date, SSP identification and date, and included CAGE codes. SPRS stores the result; it does not conduct the assessment.

  5. 5 — Keep NIST assessment and CMMC records distinct

    Basic, Medium, and High are NIST SP 800-171 DoD Assessment confidence levels. CMMC Level 1, Level 2 (Self), Level 2 (C3PAO), and Level 3 are separate CMMC statuses and workflows. A CMMC Affirming Official submits CMMC affirmations in SPRS; DFARS 252.204-7019 does not turn the NIST Basic Assessment entry into a CMMC affirmation.

  6. 6 — Maintain the assessment required by the solicitation

    Under DFARS 252.204-7019, a NIST assessment is current for no more than three years unless the solicitation specifies a shorter period. Separately, CMMC Level 1 self-assessment is annual, Level 2 assessment is generally triennial, and CMMC affirmation is required after assessment and annually thereafter. Implementation is phased under 32 CFR 170.3(e); confirm the current phase with official DoD CIO guidance and the CMMC requirement stated in each solicitation.

10 Ways to Improve Your SPRS Score Fast

Not all controls are equal. Focus on high-impact, relatively low-effort controls first for the fastest score improvement. These ten actions consistently deliver the most SPRS score gain per hour of implementation effort:

  1. 1 — Enable Multi-Factor Authentication (MFA) organization-wide

    IA.L2-3.5.3 is a 5-point requirement with an expressly defined 3-point deduction when MFA is implemented only for remote and privileged users. Correctly scoped MFA for all applicable privileged, non-privileged, and network access can close this gap when every applicable assessment objective is supported by evidence.

  2. 2 — Deploy endpoint malware protection on all workstations and servers

    SI.L2-3.14.2, SI.L2-3.14.4, and SI.L2-3.14.5 address malicious-code protection, updates, and scans. Microsoft Defender or an equivalent platform may support these requirements when it is correctly deployed, configured, monitored, and evidenced throughout the assessed scope.

  3. 3 — Implement a formal patch management process

    SI.L2-3.14.1 requires organizations to identify, report, and correct information-system flaws in a timely manner. Windows Update, WSUS, or Intune policies can support implementation, but the assessed process and evidence must also cover identification, reporting, remediation timing, and the applicable system scope.

  4. 4 — Configure centralized audit logging

    AU requirements address event definition, logging, review, protection, and related capabilities. Microsoft 365 Unified Audit Log or Azure Monitor may support those objectives, but the required events, review process, protection, and organization-defined retention must be established for the assessed environment; there is no universal three-year operational-log retention rule here.

  5. 5 — Implement network segmentation between CUI and non-CUI systems

    Segmentation can reduce scope and support boundary-protection objectives when it is correctly designed, documented, and enforced. A VLAN or subnet alone does not establish that SC.L2-3.13.1, SC.L2-3.13.3, or another requirement is MET.

  6. 6 — Enforce encryption for CUI data at rest and in transit

    BitLocker, TLS, and other cryptographic mechanisms can support applicable SC and MP requirements, but sufficiency depends on where CUI is stored or transmitted, configuration, key management, and FIPS validation where required.

  7. 7 — Document and enforce access restrictions

    AC.L2-3.1.1 through AC.L2-3.1.3 address authorized access, permitted transactions and functions, and CUI flow. IAM documentation, removal of unnecessary privileges, technical enforcement, and access reviews can support these requirements, but each requirement must be assessed against all applicable objectives.

  8. 8 — Deploy a Security Awareness Training program

    AT.L2-3.2.1, AT.L2-3.2.2, and AT.L2-3.2.3 address awareness, role-based training, and insider-threat awareness. A training platform and completion records can provide evidence, but content, role coverage, timing, and actual implementation must match the applicable objectives.

  9. 9 — Conduct and document a formal risk assessment

    RA.L2-3.11.1 requires periodic assessment of risk to operations, assets, and individuals resulting from operating systems and processing, storing, or transmitting CUI. A documented assessment can support this requirement only when its scope, method, results, and review satisfy the applicable objectives.

  10. 10 — Write and implement a formal incident response plan

    IR.L2-3.6.1, IR.L2-3.6.2, and IR.L2-3.6.3 address an operational incident-handling capability, tracking and reporting, and testing. A plan, assigned roles, exercises, and records can support those objectives; documentation alone does not establish that every requirement is MET.

SPRS Score vs. CMMC Certification: What's the Difference?

SPRS scores and CMMC certification are related but distinct requirements. Here's how they differ:

DimensionSPRS ScoreCMMC Certification
NatureWeighted numerical NIST SP 800-171 assessment scoreConditional or Final CMMC Status at the applicable level and assessment type
Performed byContractor for Basic; DoD personnel for Medium or HighOSA for Level 1 and Level 2 Self; C3PAO for Level 2 certification; DCMA DIBCAC for Level 3
BasisDoD NIST SP 800-171 Assessment MethodologyCMMC assessment scope, objectives, scoring, status, and affirmation requirements in 32 CFR part 170
PeriodNo more than 3 years old unless the solicitation specifies lessLevel 1 self-assessment annually; Level 2 generally every 3 years; affirmation after assessment and annually thereafter
Systems of recordSummary score stored in SPRSCMMC Status and affirmations stored in SPRS; C3PAO results uploaded through CMMC eMASS
Award relevanceA current score is required when DFARS 252.204-7019 applies; no universal numerical minimum is statedThe solicitation or contract identifies the required CMMC Status; current rollout policy is separate from the regulatory assessment framework

How CMMCLens Tracks and Improves Your SPRS Score

CMMCLens provides a live, always-accurate SPRS score dashboard that shows your current score, the projected score after implementing pending POA&M items, and a prioritized remediation queue ranked by score impact per hour of effort.

SPRS Score Management in CMMCLens

Real-time visibility and automated improvement tracking

  • SPRS readiness tracking based on mapped evidence
  • Score trend chart showing improvement over time
  • Drill-down by domain to identify score improvement opportunities
  • Projected score after implementing each POA&M item
  • SPRS submission report formatted for SPRS.mil upload
  • Annual self-assessment workflow with senior official attestation
  • Readiness monitoring that flags changes that may affect your score
  • Remediation task assignment and tracking with evidence re-collection

Frequently Asked Questions

Is there a minimum SPRS score required to win a DoD contract?
DFARS 252.204-7019 does not set one universal minimum numerical score. When it applies, the offeror must have a current NIST SP 800-171 DoD Assessment in SPRS for each relevant covered contractor information system, and the solicitation may specify a shorter currency period or additional requirements. CMMC is separate: Conditional Level 2 requires at least 88 of 110 weighted points plus compliance with every POA&M eligibility restriction. A solicitation-specific requirement controls eligibility for that procurement.
What are the consequences of submitting a false SPRS score?
Submitting a false SPRS score can expose a company and its executives to prosecution under the False Claims Act (31 U.S.C. § 3729), which allows for treble damages (3x the amount of the contract) plus civil penalties. In 2022, Aerojet Rocketdyne settled a False Claims Act case for $9 million related to misrepresentation of its cybersecurity practices. The DoJ has made clear that CMMC and SPRS fraud is a prosecutorial priority.
Can I submit an SPRS score lower than 110 and still win contracts?
A NIST SP 800-171 Basic Assessment score below 110 can be entered in SPRS. Whether an offeror remains eligible depends on the applicable solicitation and contract requirements; DFARS 252.204-7019 itself requires a current assessment but does not state a universal numerical floor. A remediation POA&M does not convert a NOT MET NIST requirement into an implemented one. For Conditional CMMC Level 2, separate rules require at least 88 weighted points, allow only specified requirements on the CMMC POA&M, and require closeout within 180 days.
How quickly can I improve my SPRS score?
Score improvement often comes fastest from high-impact, lower-effort controls such as enabling MFA, deploying endpoint protection, implementing centralized logging, and documenting key policies. CMMCLens prioritizes remediation to help you focus on the highest-impact requirements first.
Does a C3PAO assessment replace or update my SPRS score?
A C3PAO Level 2 certification assessment is not a Medium NIST SP 800-171 DoD Assessment and does not turn a Basic confidence level into a CMMC level. The C3PAO uploads CMMC assessment results into the CMMC instantiation of eMASS; the resulting Conditional or Final Level 2 (C3PAO) status is officially stored in SPRS. The organization's Affirming Official must submit the CMMC affirmation in SPRS after the assessment and annually thereafter. These CMMC records are distinct from Basic, Medium, and High NIST assessment confidence levels.