The Supplier Performance Risk System (SPRS) cybersecurity score is one of the first indicators DoD contracting officers review when evaluating contract eligibility. Required under DFARS 252.204-7019, contractors must self-assess against NIST SP 800-171 and submit their score to the SPRS portal (sprs.apps.mil) before DoD contract award. The scoring model defined in the DoD Assessment Methodology (version 1.2.1, published by DODCIO) starts at a maximum of 110 points — one per control — with deductions for each unimplemented practice based on its assigned weight. Critically, false SPRS submissions create exposure under the False Claims Act, as the DoJ has already pursued cases against contractors who overstated their cybersecurity posture.
Understanding the SPRS Scoring Formula
The SPRS cybersecurity score is based on the DoD's assessment methodology from DFARS 252.204-7019 and NIST SP 800-171 DoD Assessment Methodology. You start with a maximum possible score of 110 points. Each of the 110 NIST 800-171 practices has a point value: most are worth 1 point, but a subset of higher-impact practices are worth 3 or 5 points. For every practice that is NOT implemented, the corresponding point value is subtracted from 110. A perfect implementation of all 110 practices yields a score of 110; a single unimplemented 5-point practice reduces your score to 105.
- Starting score: 110 points (maximum possible)
- 1-point practices: majority of the 110 controls — each gap costs 1 point
- 3-point practices: moderate-weight controls — each gap costs 3 points
- 5-point practices: highest-weight controls — each gap costs 5 points
- Score can be negative if a large number of high-weight controls are unimplemented
- Score must be submitted to SPRS portal and updated within 30 days of any material change
- DoD assesses scores below 110 as indicators of risk; scores below 70 are considered high risk
Top 10 Controls by SPRS Point Impact
The following table identifies the ten highest-impact NIST 800-171 controls by SPRS point weight. Implementing any of these from an unimplemented state delivers the maximum score improvement per remediation effort. Prioritize these if your score is significantly negative.
| Practice # | Control Description | Domain | Point Value | Typical Effort to Implement |
|---|---|---|---|---|
| 3.5.3 | Use multifactor authentication for local and network access to privileged accounts | IA | 5 pts | Low-Medium (1–2 weeks) |
| 3.5.4 | Use multifactor authentication for network access to non-privileged accounts | IA | 5 pts | Low-Medium (1–2 weeks) |
| 3.13.8 | Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission | SC | 5 pts | Low (days for TLS config) |
| 3.13.10 | Establish and manage cryptographic keys for cryptography employed in organizational systems | SC | 5 pts | Medium (2–4 weeks) |
| 3.1.1 | Limit system access to authorized users, processes, and devices | AC | 3 pts | Medium (2–3 weeks) |
| 3.1.2 | Limit system access to the types of transactions and functions authorized users are permitted to execute | AC | 3 pts | Medium (2–3 weeks) |
| 3.3.1 | Create and retain system audit logs to enable monitoring, analysis, investigation, and reporting | AU | 3 pts | Medium (1–3 weeks) |
| 3.3.2 | Ensure that the actions of individual system users can be traced to those users | AU | 3 pts | Low (days if logging is enabled) |
| 3.14.6 | Monitor organizational systems to detect attacks and indicators of potential attacks | SI | 3 pts | Medium-High (3–6 weeks) |
| 3.14.7 | Identify unauthorized use of organizational systems | SI | 3 pts | Medium-High (3–6 weeks) |
Quick Wins: 30-Day Score Improvements
These are controls that a technically capable team can typically implement within 30 days using existing infrastructure and widely available tools — without a major capital investment.
1. Deploy MFA — Highest Single-Control Score Impact
Multi-factor authentication (MFA) practices 3.5.3 and 3.5.4 together account for 10 SPRS points — the single highest combined impact of any two adjacent controls. If MFA is not deployed, this is always the first remediation. Microsoft 365 and Google Workspace both support MFA enforcement through native policy with no additional licensing cost for basic TOTP/authenticator app MFA. For on-premises environments, Microsoft Entra ID (formerly Azure AD) MFA or a third-party solution like Duo Security can be deployed in days. The key is enforcing MFA at the policy level — not just offering it optionally — and documenting that enforcement in your SSP.
2. Enable Encryption for Data in Transit (TLS) — 5 Points
Practice 3.13.8 requires cryptographic mechanisms for CUI in transit. If your web applications, file transfer mechanisms, or email relay are using unencrypted protocols (HTTP, FTP, unencrypted SMTP), this gap costs 5 points. Enforcing HTTPS with TLS 1.2 or 1.3, configuring email servers to require STARTTLS, and disabling legacy protocols (SSLv3, TLS 1.0) can typically be completed in a day or two of configuration work. Confirm implementation with a TLS scan tool (SSL Labs, Nessus, or equivalent) and document the results.
3. Encrypt CUI at Rest (FIPS 140-2) — 3–5 Points
BitLocker (Windows) and FileVault (macOS) are built-in, FIPS 140-2 validated disk encryption tools that can be enforced via Group Policy or MDM (Intune, Jamf) across your endpoint fleet. For servers, encrypt volumes storing CUI using OS-native encryption or a FIPS-validated encryption product. Ensure cloud storage buckets/blobs storing CUI use server-side encryption with customer-managed keys (CMK) where possible. Document the encryption standard, key length (AES-256), and management process in your SSP.
4. Implement an Incident Response Plan
Practice 3.6.1 (3 points) requires an operational incident response capability. Many small contractors have no documented IR plan at all. NIST SP 800-61 Rev. 2 provides a free, comprehensive framework. A basic but compliant IR plan can be drafted in 1–2 weeks using available templates, then approved by leadership. More important than perfection is that the plan is documented, assigned to named individuals, and can be demonstrated as tested (even a basic tabletop exercise with notes counts as evidence).
5. Establish a Configuration Management Baseline
Practices 3.4.1 and 3.4.2 (2 points combined) require documented baseline configurations for CUI systems. Export current configurations for your key systems — Windows Server Group Policy, firewall rulesets, router configs — and document them as the 'approved baseline.' This is a documentation task as much as a technical one; if your systems are reasonably hardened already, this can be completed quickly. Pair this with a change management log to demonstrate ongoing control.
Long-Term Fixes: 60–180 Day Improvements
Access Control Audit and Remediation
A complete access control remediation — reviewing every user account, enforcing least privilege, removing stale accounts, eliminating shared credentials, and implementing role-based access control (RBAC) — is a 4–8 week project for most organizations. It touches Active Directory, cloud IAM (AWS IAM, Azure RBAC, Google IAM), application user databases, and shared service accounts. This work is foundational: access control practices collectively account for 22 of the 110 NIST 800-171 requirements.
Audit Log Implementation and SIEM
Audit logging practices (3.3.1 through 3.3.9) collectively carry 9 points and are among the most frequently cited gaps in assessments. The challenge is not just enabling logs — it is ensuring they are retained for at least 90 days online (1 year archived), protected from tampering, and reviewed. A cloud-based SIEM such as Microsoft Sentinel, Splunk Cloud, or even a self-hosted ELK stack can consolidate logs from endpoints, servers, firewalls, and cloud services. Budget 4–8 weeks for implementation and tuning.
Vulnerability Management Program
A mature vulnerability management program — running authenticated scans monthly, tracking findings in a risk register, and meeting patch SLAs — addresses practices in the Risk Assessment (RA) and System Integrity (SI) domains for a combined impact of 6+ points. Tools like Tenable.io, Qualys, or the free OpenVAS can be stood up in a few days; the ongoing discipline of reviewing and remediating findings is what takes time to institutionalize.
Tracking and Submitting Your Score
After remediation, you must recalculate your SPRS score using the official DoD Assessment Methodology and update your submission in the SPRS portal (sprs.apps.mil). Your score is tied to your CAGE code and is visible to DoD contracting officers. The calculation must be supported by your SSP and any POA&Ms for partially implemented controls. Do not inflate your score — false SPRS submissions are a federal contracting violation under the False Claims Act, with significant legal exposure.
After remediating gaps, recalculate your SPRS score using the official NIST SP 800-171 DoD Assessment Methodology, update your System Security Plan, and submit the new score through the SPRS portal at sprs.apps.mil. Score updates must be submitted within 30 days of any material change to your security posture. Remember: the score must be supportable — SPRS submissions are a representation to the federal government about your cybersecurity controls.
Authoritative Sources
- NIST SP 800-171 Rev. 2 — csrc.nist.gov: 'Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations' — the 110 controls your SPRS score measures
- DoD Assessment Methodology v1.2.1 — dodcio.defense.gov: the scoring algorithm defining point weights for each NIST 800-171 control
- DFARS 252.204-7019 — acquisition.gov: 'Notice of NIST SP 800-171 DoD Assessment Requirements' — the clause mandating SPRS submission
- SPRS Portal — sprs.apps.mil: the official system where contractors submit and maintain their NIST 800-171 self-assessment scores
- DoJ False Claims Act Enforcement — justice.gov: the DoJ Civil Cyber-Fraud Initiative, launched 2021, pursues false cybersecurity certifications to DoD
- ISACA CMMC Practice Guide — isaca.org: practitioner-level implementation guidance for NIST 800-171 controls in enterprise environments