SPRS Scoring

    SPRS Scoring for CMMC and NIST SP 800-171

    SPRS scoring is the number DoD contracting officers see when they evaluate you for CUI-handling work. Athena calculates your Supplier Performance Risk System score live against all 110 NIST SP 800-171 controls, shows the math behind every deduction, updates the moment a control state changes, and gives your Affirming Official the audit trail required by 32 CFR Part 170 to attest.

    What is an SPRS score?

    The Supplier Performance Risk System (SPRS) is the DoD's repository for contractor self-assessment scores against NIST SP 800-171. The score starts at 110 and deducts weighted points — 1, 3, or 5 — for each unimplemented control. A perfect score is 110. A fully unimplemented environment scores -203. Contracting officers see the score when evaluating contractors for CUI-handling work, which makes the SPRS submission directly tied to bid eligibility. Under 32 CFR Part 170, the score must be current and the Affirming Official must attest to its accuracy.

    How SPRS scoring works (the math)

    Each of the 110 NIST SP 800-171 controls carries a weight reflecting its impact on the protection of CUI: most controls deduct 1 point if unimplemented, security-critical controls deduct 3, and the highest-impact controls deduct 5. The deductions stack. A contractor who has implemented 90 of 110 controls but missed three 5-point items and two 3-point items lands at 110 − (20 × 1 base − partial-credit adjustments) − 15 − 6 = a much lower number than the simple "20 missing" suggests.

    Partial implementation does not produce partial credit under the standard SPRS methodology — a control is either implemented or it is not. That makes accurate scoring depend on accurate per-objective evidence at the 320-objective level, not at the 110-control level.

    Why manual SPRS scoring fails

    • Spreadsheet drift. The scoring sheet at the bottom of the control tracker silently breaks the moment someone reorders rows or edits a formula cell.
    • Stale evidence. Controls scored as implemented in Q1 quietly drift out of compliance by Q3, but no one re-checks until the next quarterly review.
    • No audit trail. The Affirming Official has no way to show DIBCAC why a specific deduction was taken or removed.
    • POA&M disconnection. Items close in the POA&M spreadsheet without updating the scoring sheet.

    What Athena's SPRS scoring does

    • Live calculation. The score recalculates the moment a control state changes — no quarterly recompute.
    • Visible math. Every deduction shows the weight, the missing objective, and the evidence (or absence of evidence) behind it.
    • Affirming Official trail. Each score change is timestamped, hashed, and attributed to the evidence and reviewer that drove it.
    • What-if simulation. See the score impact of closing a specific POA&M item before you commit the work.
    • Defensible submission. The score you submit to SPRS is the score the platform calculates from the same evidence your C3PAO will review.

    SPRS scoring in the full assessment workflow

    The SPRS score is a function of the live state of the 110 controls. Athena drives the score from the same evidence ledger that powers SSP automation and POA&M management. The score, the SSP, and the POA&M ship together in the eMASS submission with cryptographic provenance on every artifact — see the pillar page for the end-to-end loop.

    Frequently asked questions

    Is the SPRS score the same as the CMMC certification level?

    No. The SPRS score is the self-assessment metric against NIST SP 800-171; the CMMC certification level is granted by a C3PAO after a third-party assessment. The SPRS score affects bid eligibility today; CMMC Level 2 certification becomes a contract requirement as DFARS 252.204-7021 rolls out under 32 CFR Part 170.

    How often should the SPRS score be updated?

    Per DoD guidance, no less than annually and any time the environment materially changes. Athena's live calculation means the score is always current, so the annual submission is just a snapshot of the current state — not a quarterly scramble to recompute before the deadline.

    Can partial credit be applied to a control?

    Under the standard SPRS methodology, a control is either implemented (no deduction) or not (full weighted deduction). Partial implementations score as not-implemented. That makes per-objective evidence at the 320-objective level critical — a control is only "implemented" if every underlying objective is.

    Further reading

    Related Athena pages and authoritative external references.

    Ready to act on this?

    Run the free Quick Score, then walk through the Assessment Pack.