SPRS Score Calculator
Your SPRS Basic Assessment score is not “how many of the 110 controls did you do”. DoD weights them 5, 3 and 1 — 44 requirements carry 220 of the 313 points at stake, two carry partial credit, and one carries none at all because it decides whether the assessment can happen. This tool runs the real arithmetic, from 110 down to -203.
Weights verified July 27, 2026 against NIST SP 800-171 DoD Assessment Methodology, Version 1.2.1 (June 24, 2020), Annex A / §5. Free, no signup, and nothing you enter leaves your browser.
SPRS Basic Assessment score
Not started — the range runs +110 to -203
Start with the System Security Plan question, then work the 44 five-point requirements — they carry 220 of the 313 points at stake.
Points given up
0
Answered
0/110
Do you have a current System Security Plan?
One that describes the system boundary, the environment of operation, and how each requirement is implemented.
Answer the System Security Plan question first
Requirement 3.12.4 has no point value, but it gates everything else: without an SSP the assessment cannot be conducted at all.
The five-point requirements
DoD deducts 5 points when a requirement’s absence could allow significant exploitation of the network or exfiltration of CUI. These 44 carry 220 of the 313 deductible points — answer only this section and you already know most of your score.
3.1Access Control7 × 5 pts
3.1.1Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems)
3.1.2Limit system access to the types of transactions and functions that authorized users are permitted to execute
3.1.12Monitor and control remote access sessions
3.1.13Employ cryptographic mechanisms to protect the confidentiality of remote access sessions
3.1.16Authorize wireless access prior to allowing such connections
3.1.17Protect wireless access using authentication and encryption
3.1.18Control connection of mobile devices
3.2Awareness and Training2 × 5 pts
3.2.1Ensure that managers, systems administrators, and users of organizational systems are made aware of the security risks associated with their activities and of the applicable policies, standards, and procedures related to the security of those systems
3.2.2Ensure that personnel are trained to carry out their assigned information security-related duties and responsibilities
3.3Audit and Accountability2 × 5 pts
3.3.1Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity
3.3.5Correlate audit record review, analysis, and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious, or unusual activity
3.4Configuration Management6 × 5 pts
3.4.1Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles
3.4.2Establish and enforce security configuration settings for information technology products employed in organizational systems
3.4.5Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems
3.4.6Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities
3.4.7Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services
3.4.8Apply deny-by-exception (blacklisting) policy to prevent the use of unauthorized software or deny-all, permit-by-exception (whitelisting) policy to allow the execution of authorized software
3.5Identification and Authentication4 × 5 pts
3.5.1Identify system users, processes acting on behalf of users, and devices
3.5.2Authenticate (or verify) the identities of users, processes, or devices, as a prerequisite to allowing access to organizational systems
3.5.3Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts
Partial credit applies: Partial means “MFA covers remote access and privileged accounts only — not all users.” and deducts 3 instead of 5.
3.5.10Store and transmit only cryptographically-protected passwords
3.6Incident Response2 × 5 pts
3.6.1Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities
3.6.2Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization
3.7Maintenance2 × 5 pts
3.7.2Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance
3.7.5Require multifactor authentication to establish nonlocal maintenance sessions via external network connections and terminate such connections when nonlocal maintenance is complete
3.8Media Protection2 × 5 pts
3.8.3Sanitize or destroy system media containing CUI before disposal or release for reuse
3.8.7Control the use of removable media on system components
3.9Personnel Security1 × 5 pts
3.9.2Ensure that organizational systems containing CUI are protected during and after personnel actions such as terminations and transfers
3.10Physical Protection2 × 5 pts
3.10.1Limit physical access to organizational systems, equipment, and the respective operating environments to authorized individuals
3.10.2Protect and monitor the physical facility and support infrastructure for organizational systems
3.11Risk Assessment1 × 5 pts
3.11.2Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified
3.12Security Assessment2 × 5 pts
3.12.1Periodically assess the security controls in organizational systems to determine if the controls are effective in their application
3.12.3Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls
3.13System and Communications Protection6 × 5 pts
3.13.1Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems
3.13.2Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems
3.13.5Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks
3.13.6Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception)
3.13.11Employ FIPS-validated cryptography when used to protect the confidentiality of CUI
Partial credit applies: Partial means “Encryption is employed, but it is not FIPS-validated.” and deducts 3 instead of 5.
3.13.15Protect the authenticity of communications sessions
3.14System and Information Integrity5 × 5 pts
3.14.1Identify, report, and correct system flaws in a timely manner
3.14.2Provide protection from malicious code at designated locations within organizational systems
3.14.3Monitor system security alerts and advisories and take action in response
3.14.4Update malicious code protection mechanisms when new releases are available
3.14.6Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks
Answer these in bulk if you already know the shape of your program, or open a tier to work it requirement by requirement. They cannot rescue a score the five-pointers have sunk, but they are what stands between a good score and 110.
The 14 three-point requirements42 points · media protection, maintenance, screening, awareness · 0/14 answeredOpen ▾Close ▴
3.1Access Control
3.1.5Employ the principle of least privilege, including for specific security functions and privileged accounts
3.1.19Encrypt CUI on mobile devices and mobile computing platforms
3.3Audit and Accountability
3.3.2Ensure that the actions of individual system users can be uniquely traced to those users, so they can be held accountable for their actions
3.7Maintenance
3.7.1Perform maintenance on organizational systems
3.7.4Check media containing diagnostic and test programs for malicious code before the media are used in organizational systems
3.8Media Protection
3.8.1Protect (i.e., physically control and securely store) system media containing CUI, both paper and digital
3.8.2Limit access to CUI on system media to authorized users
3.8.8Prohibit the use of portable storage devices when such devices have no identifiable owner
3.9Personnel Security
3.9.1Screen individuals prior to authorizing access to organizational systems containing CUI
3.11Risk Assessment
3.11.1Periodically assess the risk to organizational operations (including mission, functions, image, or reputation), organizational assets, and individuals, resulting from the operation of organizational systems and the associated processing, storage, or transmission of CUI
3.12Security Assessment
3.12.2Develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems
3.13System and Communications Protection
3.13.8Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards
3.14System and Information Integrity
3.14.5Perform periodic scans of organizational systems and real-time scans of files from external sources as files are downloaded, opened, or executed
3.14.7Identify unauthorized use of organizational systems
The 51 one-point requirements51 points · necessary for a clean 110, never the reason a bid is lost · 0/51 answeredOpen ▾Close ▴
3.1Access Control
3.1.3Control the flow of CUI in accordance with approved authorizations
3.1.4Separate the duties of individuals to reduce the risk of malevolent activity without collusion
3.1.6Use non-privileged accounts or roles when accessing nonsecurity functions
3.1.7Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs
3.1.8Limit unsuccessful logon attempts
3.1.9Provide privacy and security notices consistent with applicable CUI rules
3.1.10Use session lock with pattern-hiding displays to prevent access and viewing of data after a period of inactivity
3.1.11Terminate (automatically) a user session after a defined condition
3.1.14Route remote access via managed access control points
3.1.15Authorize remote execution of privileged commands and remote access to security-relevant information
3.1.20Verify and control/limit connections to and use of external systems
3.1.21Limit use of portable storage devices on external systems
3.1.22Control CUI posted or processed on publicly accessible systems
3.2Awareness and Training
3.2.3Provide security awareness training on recognizing and reporting potential indicators of insider threat
3.3Audit and Accountability
3.3.3Review and update logged events
3.3.4Alert in the event of an audit logging process failure
3.3.6Provide audit record reduction and report generation to support on-demand analysis and reporting
3.3.7Provide a system capability that compares and synchronizes internal system clocks with an authoritative source to generate time stamps for audit records
3.3.8Protect audit information and audit logging tools from unauthorized access, modification, and deletion
3.3.9Limit management of audit logging functionality to a subset of privileged users
3.4Configuration Management
3.4.3Track, review, approve or disapprove, and log changes to organizational systems
3.4.4Analyze the security impact of changes prior to implementation
3.4.9Control and monitor user-installed software
3.5Identification and Authentication
3.5.4Employ replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts
3.5.5Prevent reuse of identifiers for a defined period
3.5.6Disable identifiers after a defined period of inactivity
3.5.7Enforce a minimum password complexity and change of characters when new passwords are created
3.5.8Prohibit password reuse for a specified number of generations
3.5.9Allow temporary password use for system logons with an immediate change to a permanent password
3.5.11Obscure feedback of authentication information
3.6Incident Response
3.6.3Test the organizational incident response capability
3.7Maintenance
3.7.3Ensure equipment removed for off-site maintenance is sanitized of any CUI
3.7.6Supervise the maintenance activities of maintenance personnel without required access authorization
3.8Media Protection
3.8.4Mark media with necessary CUI markings and distribution limitations
3.8.5Control access to media containing CUI and maintain accountability for media during transport outside of controlled areas
3.8.6Implement cryptographic mechanisms to protect the confidentiality of CUI stored on digital media during transport unless otherwise protected by alternative physical safeguards
3.8.9Protect the confidentiality of backup CUI at storage locations
3.10Physical Protection
3.10.3Escort visitors and monitor visitor activity
3.10.4Maintain audit logs of physical access
3.10.5Control and manage physical access devices
3.10.6Enforce safeguarding measures for CUI at alternate work sites
3.11Risk Assessment
3.11.3Remediate vulnerabilities in accordance with risk assessments
3.13System and Communications Protection
3.13.3Separate user functionality from system management functionality
3.13.4Prevent unauthorized and unintended information transfer via shared system resources
3.13.7Prevent remote devices from simultaneously establishing non-remote connections with organizational systems and communicating via some other connection to resources in external networks (i.e., split tunneling)
3.13.9Terminate network connections associated with communications sessions at the end of the sessions or after a defined period of inactivity
3.13.10Establish and manage cryptographic keys for cryptography employed in organizational systems
3.13.12Prohibit remote activation of collaborative computing devices and provide indication of devices in use to users present at the device
3.13.13Control and monitor the use of mobile code
3.13.14Control and monitor the use of Voice over Internet Protocol (VoIP) technologies
3.13.16Protect the confidentiality of CUI at rest
Your deduction breakdown
Nothing answered yet — every requirement you mark unmet will appear here with the points it costs.
Nothing you enter leaves your browser: the shareable link encodes your answers in the URL itself, and no answer is sent to us or to any government system. This is a self-assessment aid, not an SPRS submission — see how it differs from our 12-family readiness assessment.
Point values: NIST SP 800-171 DoD Assessment Methodology, Version 1.2.1 (June 24, 2020), Annex A / §5.
The weights almost nobody publishes correctly
Search “SPRS score” and you will mostly be told there are 110 controls and that you start at 110. Both are true and neither is the scoring rule. The DoD Assessment Methodology assigns each requirement a value by the risk its absence creates, and the spread is what makes a score move:
| Weight | How many | Points at stake | Why |
|---|---|---|---|
| 5 points | 44 requirements | 220 points | Deducted in full when the requirement is not met, because its absence could allow significant exploitation of the network or exfiltration of CUI. Seventy percent of everything at stake sits here. |
| 3 points | 14 requirements | 42 points | Serious but not existential — media handling, maintenance, personnel screening, awareness. Cheap to close, disproportionately visible to an assessor. |
| 1 point | 51 requirements | 51 points | Necessary for a clean 110 and almost never the reason a score collapses. Sweep them last. |
| No score | 3.12.4 (System Security Plan) | — | Carries no point value, and that is the opposite of leniency: without an SSP the assessment cannot be conducted at all. It is a gate, not a deduction. |
44 × 5 + 14 × 3 + 51 × 1 = 313 deductible points. Subtract them all from 110 and you get -203 — which is where the published floor comes from, not from a rounding convention. Our unit tests assert that arithmetic on every build, so the calculator above cannot quietly drift away from the methodology.
The two partial-credit requirements
Annex A values 3.5.3 and 3.13.11at “3 to 5”. MFA covering remote access and privileged accounts but not all users costs 3, not 5. Encryption that is employed but not FIPS-validated costs 3, not 5. These are the two most commonly misscored requirements in self-assessments — in both directions.
The requirement worth zero points
3.12.4, the System Security Plan, has no point value — because without it the assessment cannot be conducted. A tool that scores it as a −5, or ignores it, is wrong in the same way for opposite reasons. This calculator surfaces it as a gate.
We publish two scores. Here is which one you want.
They are not competing versions of the same thing, and a strong result on one implies nothing about the other. Read the difference before quoting either number.
| This SPRS calculator | CMMC readiness assessment | |
|---|---|---|
| Unit of measure | All 110 individual requirements | 12 control families, one question each |
| Weighting | DoD weights: 5 / 3 / 1 points | Unweighted — every family counts the same |
| Scale | +110 to −203 | 0 to 100 |
| Answers | Met / partial / not met, per requirement | A four-level maturity rating per family |
| Time | 10–20 minutes (or 5 for the 44 that matter most) | About 5 minutes |
| Use it when | You need the number a contracting officer can see, or a POA&M ordered by points recovered | You want a fast directional readout of where to look first |
The trap the comparison exists to prevent: an organisation that answers “implemented” across all 12 families scores 67 on the readiness assessment — a respectable-looking result — while sitting well below zero in SPRS if a dozen five-point requirements are unmet. Neither tool is wrong; they measure different things. The readiness assessment’s scoring methodology states the same distinction from the other side.
Does this still matter after the Phase 2 suspension?
Yes — and the suspension is precisely why the arithmetic on this page got more consequential, not less. On July 13, 2026 the Department of War suspended CMMC Phase 2 pending a 60-day program review. That removed a certification gate: third-party C3PAO certification as a condition of award. It removed nothing else.
- • DFARS 252.204-7012 — CUI safeguarding, incident reporting, and NIST SP 800-171 implementation: unchanged, still in the CFR, still in your contracts.
- • SPRS score submission (252.204-7019/7020) — still required, still expected to be current, still computed with the weights above.
- • Annual affirmations — still binding.
What got sharper: with third-party verification paused, your SPRS score is an unverified self-representation to the government. The Department of Justice Civil Cyber-Fraud Initiative treats false cybersecurity self-attestations as False Claims Act material. The deadline moved; the exposure did not — and a score you can defend line by line is now worth more than a high one you cannot.
Frequently asked questions
How is an SPRS score calculated?
You start at 110 — one point for each NIST SP 800-171 requirement, all implemented — and subtract the weight of every requirement you have not met. The weights are not equal: 44 requirements are worth 5 points each, 14 are worth 3, and 51 are worth 1, which totals 313 deductible points. That is why the scale runs from +110 down to -203. The weights come from the NIST SP 800-171 DoD Assessment Methodology, Version 1.2.1 (June 24, 2020), Annex A / §5.
What is the lowest possible SPRS score?
−203. Subtracting all 313 deductible points from the starting 110 leaves −203, and a negative score is not an error — it is the normal position for an organisation that has not yet run a scored assessment. What matters to a prime or a contracting officer is that the score is current, defensible line by line, and paired with a POA&M completion date.
Why do some people say all 110 NIST 800-171 controls are worth one point each?
Because the starting score of 110 makes it look that way. The 110 is the count of requirements, not a flat scoring scheme: the DoD Assessment Methodology assigns 5, 3, or 1 point to each requirement by the risk its absence creates. Treating them as equal is the single most common error in self-assessment spreadsheets, and it flatters the score — a company with a dozen unmet five-point requirements is 60 points down, not 12.
How does multi-factor authentication (3.5.3) score in SPRS?
Requirement 3.5.3 is one of only two requirements with built-in partial credit. If MFA is enforced for all users, you lose nothing. If it covers remote access and privileged accounts but not all users, you lose 3 points instead of 5. If no MFA is in place at all, you lose the full 5.
How does FIPS-validated cryptography (3.13.11) score in SPRS?
Like 3.5.3, requirement 3.13.11 carries partial credit. If encryption is employed but is not FIPS-validated, the deduction is 3 rather than 5. If no encryption protects CUI, the full 5 points come off. Annex A of the methodology expresses both of these as "3 to 5" rather than a flat value.
What happens to my SPRS score if I do not have a System Security Plan?
Nothing — and that is the problem. Requirement 3.12.4 has no point value, so a missing System Security Plan does not deduct anything. It stops the assessment instead: without an SSP describing the system boundary and how each requirement is implemented, there is nothing to assess against, and any score you compute is arithmetic rather than a Basic Assessment you could submit. If you have no SSP, that is the first item on the plan regardless of what the number says.
Does the SPRS score still matter after CMMC Phase 2 was suspended?
Yes, and in one respect it matters more. The Department of War suspended CMMC Phase 2 on July 13, 2026 pending a 60-day review, which removed the third-party certification gate — and nothing else. DFARS 252.204-7012, NIST SP 800-171 implementation, SPRS score submission under 252.204-7019/7020, and annual affirmations all remain contractually binding. With third-party verification paused, your score is an unverified self-representation to the government, and the Department of Justice Civil Cyber-Fraud Initiative treats false cybersecurity self-attestations as False Claims Act material. Accuracy is now the sharp edge, not certification timing.
Is this the same as the Cabrillo Club CMMC readiness assessment?
No, and the two answer different questions on purpose. The readiness assessment asks 12 questions, one per control family, and reports an unweighted maturity average from 0 to 100 — a five-minute directional readout. This calculator implements the official DoD Assessment Methodology at requirement level with the real 5/3/1 weights and reports a score on the +110 to −203 SPRS scale. A healthy family average and a deeply negative SPRS score are entirely compatible, which is exactly why we publish both.
Take it further
NIST 800-171 Priority Map (PDF)
All 110 requirements on one page, colour-coded by these same point values
CMMC Readiness Assessment
The 5-minute, 12-family maturity readout — a different measure, not a rival score
Scoring methodology
How the readiness average is built, and exactly how it differs from this SPRS score
CMMC Cost Estimator
What DoD itself priced the assessment at, cited to the Federal Register
All 110 NIST 800-171 requirements
Assessment objectives, common gaps and implementation guidance, requirement by requirement
DFARS 252.204-7012
The clause that makes all of this contractual, suspension or no suspension
Turn this gap analysis into a remediation plan
This SPRS score is the start, not the answer. Book a 25-minute compliance assessment — you leave with a prioritized roadmap and a fixed-fee implementation quote.
Book a 25-min assessmentSource for every point value on this page: NIST SP 800-171 DoD Assessment Methodology, Version 1.2.1 (June 24, 2020), Annex A / §5 — the same weights used in SPRS scoring. Regulatory status as of July 27, 2026. This calculator produces a self-assessment aid for planning purposes; it is not an SPRS submission, not a formal CMMC assessment, and not legal advice.