Free tool

SPRS score calculator

Score your organization against all 110 NIST SP 800-171 requirements using the official DoD weights. Every requirement starts as met: mark the ones you have not fully implemented. Nothing you enter leaves your browser.

Access Control22 requirements
3.1.1 Limit system access to authorized users, processes, and devices5 points
3.1.2 Limit users to the transactions and functions they are permitted to perform5 points
3.1.3 Control the flow of CUI according to approved authorizations1 point
3.1.4 Separate duties so no single person can misuse access without collusion1 point
3.1.5 Apply least privilege, including for security functions and privileged accounts3 points
3.1.6 Use non-privileged accounts for non-security tasks1 point
3.1.7 Block non-privileged users from privileged functions and log privileged use1 point
3.1.8 Limit unsuccessful logon attempts1 point
3.1.9 Display privacy and security notices consistent with CUI rules1 point
3.1.10 Use session lock with a pattern-hiding display after inactivity1 point
3.1.11 Automatically end user sessions after a defined condition1 point
3.1.12 Monitor and control remote access sessions5 points
3.1.13 Encrypt remote access sessions to protect confidentiality5 points
3.1.14 Route remote access through managed access control points1 point
3.1.15 Authorize remote privileged commands and remote access to security information1 point
3.1.16 Authorize wireless access before allowing connections5 points
3.1.17 Protect wireless access with authentication and encryption5 points
3.1.18 Control the connection of mobile devices5 points
3.1.19 Encrypt CUI on mobile devices and mobile computing platforms3 points
3.1.20 Verify and control or limit connections to and use of external systems1 point · cannot go on a POA&M
3.1.21 Limit use of portable storage devices on external systems1 point
3.1.22 Control CUI posted or processed on publicly accessible systems1 point · cannot go on a POA&M
Awareness and Training3 requirements
3.2.1 Make managers, admins, and users aware of security risks and policies5 points
3.2.2 Train personnel to carry out their security duties and responsibilities5 points
3.2.3 Provide security awareness training on spotting and reporting insider threats1 point
Audit and Accountability9 requirements
3.3.1 Create and keep audit logs to support investigation of unauthorized activity5 points
3.3.2 Make sure user actions can be traced back to individual users3 points
3.3.3 Review and update the events that are logged1 point
3.3.4 Alert when audit logging fails1 point
3.3.5 Correlate audit review, analysis, and reporting to investigate suspicious activity5 points
3.3.6 Provide audit reduction and on-demand report generation1 point
3.3.7 Sync system clocks to an authoritative time source for audit timestamps1 point
3.3.8 Protect audit logs and logging tools from unauthorized access, change, or deletion1 point
3.3.9 Limit management of audit logging to a subset of privileged users1 point
Configuration Management9 requirements
3.4.1 Establish and maintain baseline configurations and system inventories5 points
3.4.2 Establish and enforce security configuration settings5 points
3.4.3 Track, review, approve or reject, and log system changes1 point
3.4.4 Analyze the security impact of changes before making them1 point
3.4.5 Define and enforce physical and logical access restrictions for changes5 points
3.4.6 Apply least functionality so systems provide only essential capabilities5 points
3.4.7 Restrict or disable nonessential programs, functions, ports, protocols, and services5 points
3.4.8 Use blocklisting or allowlisting to control which software can run5 points
3.4.9 Control and monitor user-installed software1 point
Identification and Authentication11 requirements
3.5.1 Identify system users, processes acting for users, and devices5 points
3.5.2 Authenticate users, processes, and devices before granting access5 points
3.5.3 Use MFA for privileged accounts and for network access by all users5 points
3.5.4 Use replay-resistant authentication for network access1 point
3.5.5 Prevent reuse of identifiers for a defined period1 point
3.5.6 Disable identifiers after a defined period of inactivity1 point
3.5.7 Enforce minimum password complexity and character changes for new passwords1 point
3.5.8 Prohibit password reuse for a set number of generations1 point
3.5.9 Allow temporary passwords only with an immediate change to a permanent one1 point
3.5.10 Store and transmit only cryptographically protected passwords5 points
3.5.11 Obscure authentication feedback such as typed passwords1 point
Incident Response3 requirements
3.6.1 Establish an operational incident handling capability5 points
3.6.2 Track, document, and report incidents to internal and external officials5 points
3.6.3 Test the incident response capability1 point
Maintenance6 requirements
3.7.1 Perform maintenance on organizational systems3 points
3.7.2 Control the tools, techniques, mechanisms, and people used for maintenance5 points
3.7.3 Sanitize equipment of CUI before it leaves for off-site maintenance1 point
3.7.4 Scan diagnostic and test media for malicious code before use3 points
3.7.5 Require MFA for remote maintenance sessions and end them when done5 points
3.7.6 Supervise maintenance work by personnel without required access authorization1 point
Media Protection9 requirements
3.8.1 Physically control and securely store paper and digital media containing CUI3 points
3.8.2 Limit access to CUI on system media to authorized users3 points
3.8.3 Sanitize or destroy media containing CUI before disposal or reuse5 points
3.8.4 Mark media with required CUI markings and distribution limits1 point
3.8.5 Control and keep accountability for CUI media transported outside controlled areas1 point
3.8.6 Encrypt CUI on digital media in transport unless physically safeguarded1 point
3.8.7 Control the use of removable media on system components5 points
3.8.8 Prohibit portable storage devices that have no identifiable owner3 points
3.8.9 Protect the confidentiality of backup CUI at storage locations1 point
Personnel Security2 requirements
3.9.1 Screen individuals before granting access to systems containing CUI3 points
3.9.2 Protect CUI systems during and after terminations and transfers5 points
Physical Protection6 requirements
3.10.1 Limit physical access to systems, equipment, and work areas to authorized people5 points
3.10.2 Protect and monitor the physical facility and supporting infrastructure5 points
3.10.3 Escort visitors and monitor visitor activity1 point · cannot go on a POA&M
3.10.4 Keep audit logs of physical access1 point · cannot go on a POA&M
3.10.5 Control and manage physical access devices such as keys and badges1 point · cannot go on a POA&M
3.10.6 Enforce safeguards for CUI at alternate work sites1 point
Risk Assessment3 requirements
3.11.1 Periodically assess risk from operating systems that handle CUI3 points
3.11.2 Scan for vulnerabilities periodically and when new ones are identified5 points
3.11.3 Remediate vulnerabilities according to risk assessments1 point
Security Assessment4 requirements
3.12.1 Periodically assess security controls to confirm they are effective5 points
3.12.2 Develop and implement plans of action to fix deficiencies3 points
3.12.3 Monitor security controls on an ongoing basis5 points
3.12.4 Develop, document, and periodically update a system security plan (SSP)Required to score at all
System and Communications Protection16 requirements
3.13.1 Monitor, control, and protect communications at external and key internal boundaries5 points
3.13.2 Use architecture, development, and engineering practices that promote security5 points
3.13.3 Separate user functionality from system management functionality1 point
3.13.4 Prevent unauthorized information transfer through shared system resources1 point
3.13.5 Put publicly accessible components in subnetworks separated from internal networks5 points
3.13.6 Deny network traffic by default and allow it only by exception5 points
3.13.7 Prevent split tunneling on remote devices1 point
3.13.8 Encrypt CUI in transit unless protected by alternative physical safeguards3 points
3.13.9 End network connections at session end or after inactivity1 point
3.13.10 Establish and manage cryptographic keys1 point
3.13.11 Use FIPS-validated cryptography to protect the confidentiality of CUI5 points
3.13.12 Block remote activation of collaborative devices and show when they are in use1 point
3.13.13 Control and monitor the use of mobile code1 point
3.13.14 Control and monitor the use of VoIP technologies1 point
3.13.15 Protect the authenticity of communications sessions5 points
3.13.16 Protect the confidentiality of CUI at rest1 point
System and Information Integrity7 requirements
3.14.1 Identify, report, and correct system flaws in a timely manner5 points
3.14.2 Provide malicious code protection at designated locations5 points
3.14.3 Monitor security alerts and advisories and act on them5 points
3.14.4 Update malicious code protection when new releases are available5 points
3.14.5 Run periodic scans and real-time scans of files from external sources3 points
3.14.6 Monitor systems and network traffic to detect attacks and signs of attack5 points
3.14.7 Identify unauthorized use of organizational systems3 points

Weights from the NIST SP 800-171 DoD Assessment Methodology, Version 1.2.1 (June 24, 2020), Annex A. POA&M eligibility and the 88-point threshold for Conditional Level 2 status come from the CMMC rule, 32 CFR 170. This is an estimate for planning, not an assessment, and it does not submit anything to SPRS.

Next step

A score is only as good as the evidence behind it

As a Cyber AB Registered Practitioner Organization, we help contractors turn a self-score into a defensible one: scoping, gap remediation, an SSP that matches the tenant, and evidence an assessor can verify.

Talk about your score
How is an SPRS score calculated?

Under the DoD Assessment Methodology, you start at 110 and subtract the value of every NIST SP 800-171 requirement that is not fully implemented. Requirements are worth 5, 3 or 1 point, so the lowest possible score is -203.

Does a POA&M count as implemented?

No. The methodology scores a requirement as not implemented even if a plan of action exists for it. Separately, if you have unmet requirements and no plan of action, 3.12.2 itself is scored not implemented.

Is there partial credit?

Only for two requirements. MFA (3.5.3) costs 3 points instead of 5 if it covers remote and privileged access but not all users. Encryption of CUI (3.13.11) costs 3 points instead of 5 if encryption is used but is not FIPS-validated.

What score do we need for CMMC Level 2?

Under the CMMC rule (32 CFR 170), Conditional Level 2 status needs a score of at least 88, with only eligible requirements on a POA&M, and every POA&M item closed within 180 days. Final status means all 110 are met.

Let's talk

Ready for your new vision?

Book a free security assessment and threat briefing. We will map where you stand, what matters most, and which plan fits.