SPRS score calculator

Mark each of the 110 NIST SP 800-171 requirements as implemented or not, and this calculator applies the DoD Assessment Methodology's arithmetic: start at 110 and subtract 5, 3 or 1 point for each requirement not implemented, with partial credit for 3.5.3 and 3.13.11. Without a system security plan, there is no score.

Your answers stay in this browser tab: nothing you select is sent to CMMCSync or saved. Reloading the page clears them.

1. System security plan

Do you have a system security plan?

2. The 110 requirements

Every requirement starts as Implemented. Change the ones you have not implemented.

3.1 Access Control

3.1.1 Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems). (5 points)
3.1.2 Limit system access to the types of transactions and functions that authorized users are permitted to execute. (5 points)
3.1.3 Control the flow of CUI in accordance with approved authorizations. (1 point)
3.1.4 Separate the duties of individuals to reduce the risk of malevolent activity without collusion. (1 point)
3.1.5 Employ the principle of least privilege, including for specific security functions and privileged accounts. (3 points)
3.1.6 Use non-privileged accounts or roles when accessing nonsecurity functions. (1 point)
3.1.7 Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs. (1 point)
3.1.8 Limit unsuccessful logon attempts. (1 point)
3.1.9 Provide privacy and security notices consistent with applicable CUI rules. (1 point)
3.1.10 Use session lock with pattern-hiding displays to prevent access and viewing of data after a period of inactivity. (1 point)
3.1.11 Terminate (automatically) a user session after a defined condition. (1 point)
3.1.12 Monitor and control remote access sessions. (5 points)

Methodology note: “Do not subtract points if remote access not permitted”.

3.1.13 Employ cryptographic mechanisms to protect the confidentiality of remote access sessions. (5 points)

Methodology note: “Do not subtract points if remote access not permitted”.

3.1.14 Route remote access via managed access control points. (1 point)
3.1.15 Authorize remote execution of privileged commands and remote access to security-relevant information. (1 point)
3.1.16 Authorize wireless access prior to allowing such connections. (5 points)

Methodology note: “Do not subtract points if wireless access not permitted”.

3.1.17 Protect wireless access using authentication and encryption. (5 points)

Methodology note: “Do not subtract points if wireless access not permitted”.

3.1.18 Control connection of mobile devices. (5 points)

Methodology note: “Do not subtract points if connection of mobile devices is not permitted”.

3.1.19 Encrypt CUI on mobile devices and mobile computing platforms. (3 points)
3.1.20 Verify and control/limit connections to and use of external systems. (1 point)
3.1.21 Limit use of portable storage devices on external systems. (1 point)
3.1.22 Control CUI posted or processed on publicly accessible systems. (1 point)

3.2 Awareness and Training

3.2.1 Ensure 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. (5 points)
3.2.2 Ensure that personnel are trained to carry out their assigned information security-related duties and responsibilities. (5 points)
3.2.3 Provide security awareness training on recognizing and reporting potential indicators of insider threat. (1 point)

3.3 Audit and Accountability

3.3.1 Create 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. (5 points)
3.3.2 Ensure that the actions of individual system users can be uniquely traced to those users, so they can be held accountable for their actions. (3 points)
3.3.3 Review and update logged events. (1 point)
3.3.4 Alert in the event of an audit logging process failure. (1 point)
3.3.5 Correlate audit record review, analysis, and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious, or unusual activity. (5 points)
3.3.6 Provide audit record reduction and report generation to support on-demand analysis and reporting. (1 point)
3.3.7 Provide a system capability that compares and synchronizes internal system clocks with an authoritative source to generate time stamps for audit records. (1 point)
3.3.8 Protect audit information and audit logging tools from unauthorized access, modification, and deletion. (1 point)
3.3.9 Limit management of audit logging functionality to a subset of privileged users. (1 point)

3.4 Configuration Management

3.4.1 Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles. (5 points)
3.4.2 Establish and enforce security configuration settings for information technology products employed in organizational systems. (5 points)
3.4.3 Track, review, approve or disapprove, and log changes to organizational systems. (1 point)
3.4.4 Analyze the security impact of changes prior to implementation. (1 point)
3.4.5 Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems. (5 points)
3.4.6 Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities. (5 points)
3.4.7 Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services. (5 points)
3.4.8 Apply 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. (5 points)
3.4.9 Control and monitor user-installed software. (1 point)

3.5 Identification and Authentication

3.5.1 Identify system users, processes acting on behalf of users, and devices. (5 points)
3.5.2 Authenticate (or verify) the identities of users, processes, or devices, as a prerequisite to allowing access to organizational systems. (5 points)
3.5.3 Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts. (3 or 5 points)
3.5.4 Employ replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts. (1 point)
3.5.5 Prevent reuse of identifiers for a defined period. (1 point)
3.5.6 Disable identifiers after a defined period of inactivity. (1 point)
3.5.7 Enforce a minimum password complexity and change of characters when new passwords are created. (1 point)
3.5.8 Prohibit password reuse for a specified number of generations. (1 point)
3.5.9 Allow temporary password use for system logons with an immediate change to a permanent password. (1 point)
3.5.10 Store and transmit only cryptographically-protected passwords. (5 points)
3.5.11 Obscure feedback of authentication information. (1 point)

3.6 Incident Response

3.6.1 Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities. (5 points)
3.6.2 Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization. (5 points)
3.6.3 Test the organizational incident response capability. (1 point)

3.7 Maintenance

3.7.1 Perform maintenance on organizational systems. (3 points)
3.7.2 Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance. (5 points)
3.7.3 Ensure equipment removed for off-site maintenance is sanitized of any CUI. (1 point)
3.7.4 Check media containing diagnostic and test programs for malicious code before the media are used in organizational systems. (3 points)
3.7.5 Require multifactor authentication to establish nonlocal maintenance sessions via external network connections and terminate such connections when nonlocal maintenance is complete. (5 points)
3.7.6 Supervise the maintenance activities of maintenance personnel without required access authorization. (1 point)

3.8 Media Protection

3.8.1 Protect (i.e., physically control and securely store) system media containing CUI, both paper and digital. (3 points)
3.8.2 Limit access to CUI on system media to authorized users. (3 points)
3.8.3 Sanitize or destroy system media containing CUI before disposal or release for reuse. (5 points)
3.8.4 Mark media with necessary CUI markings and distribution limitations. (1 point)
3.8.5 Control access to media containing CUI and maintain accountability for media during transport outside of controlled areas. (1 point)
3.8.6 Implement cryptographic mechanisms to protect the confidentiality of CUI stored on digital media during transport unless otherwise protected by alternative physical safeguards. (1 point)
3.8.7 Control the use of removable media on system components. (5 points)
3.8.8 Prohibit the use of portable storage devices when such devices have no identifiable owner. (3 points)
3.8.9 Protect the confidentiality of backup CUI at storage locations. (1 point)

3.9 Personnel Security

3.9.1 Screen individuals prior to authorizing access to organizational systems containing CUI. (3 points)
3.9.2 Ensure that organizational systems containing CUI are protected during and after personnel actions such as terminations and transfers. (5 points)

3.10 Physical Protection

3.10.1 Limit physical access to organizational systems, equipment, and the respective operating environments to authorized individuals. (5 points)
3.10.2 Protect and monitor the physical facility and support infrastructure for organizational systems. (5 points)
3.10.3 Escort visitors and monitor visitor activity. (1 point)
3.10.4 Maintain audit logs of physical access. (1 point)
3.10.5 Control and manage physical access devices. (1 point)
3.10.6 Enforce safeguarding measures for CUI at alternate work sites. (1 point)

3.11 Risk Assessment

3.11.1 Periodically 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 points)
3.11.2 Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified. (5 points)
3.11.3 Remediate vulnerabilities in accordance with risk assessments. (1 point)

3.12 Security Assessment

3.12.1 Periodically assess the security controls in organizational systems to determine if the controls are effective in their application. (5 points)
3.12.2 Develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems. (3 points)
3.12.3 Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls. (5 points)

3.12.4 Develop, document, and periodically update system security plans that describe system boundaries, system environments of operation, how security requirements are implemented, and the relationships with or connections to other systems.

No point value. This requirement is the system security plan, so it is answered by the system security plan question above.

3.13 System and Communications Protection

3.13.1 Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. (5 points)
3.13.2 Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems. (5 points)
3.13.3 Separate user functionality from system management functionality. (1 point)
3.13.4 Prevent unauthorized and unintended information transfer via shared system resources. (1 point)
3.13.5 Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. (5 points)
3.13.6 Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception). (5 points)
3.13.7 Prevent 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). (1 point)
3.13.8 Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards. (3 points)
3.13.9 Terminate network connections associated with communications sessions at the end of the sessions or after a defined period of inactivity. (1 point)
3.13.10 Establish and manage cryptographic keys for cryptography employed in organizational systems. (1 point)
3.13.11 Employ FIPS-validated cryptography when used to protect the confidentiality of CUI. (3 or 5 points)
3.13.12 Prohibit remote activation of collaborative computing devices and provide indication of devices in use to users present at the device. (1 point)
3.13.13 Control and monitor the use of mobile code. (1 point)
3.13.14 Control and monitor the use of Voice over Internet Protocol (VoIP) technologies. (1 point)
3.13.15 Protect the authenticity of communications sessions. (5 points)
3.13.16 Protect the confidentiality of CUI at rest. (1 point)

3.14 System and Information Integrity

3.14.1 Identify, report, and correct system flaws in a timely manner. (5 points)
3.14.2 Provide protection from malicious code at designated locations within organizational systems. (5 points)
3.14.3 Monitor system security alerts and advisories and take action in response. (5 points)
3.14.4 Update malicious code protection mechanisms when new releases are available. (5 points)
3.14.5 Perform periodic scans of organizational systems and real-time scans of files from external sources as files are downloaded, opened, or executed. (3 points)
3.14.6 Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks. (5 points)
3.14.7 Identify unauthorized use of organizational systems. (3 points)

110 of 110

0 points deducted · gaps at 5 points: 0, at 3 points: 0, at 1 point: 0

How the score is calculated

The values come from the scoring template in Annex A of the methodology: 42 requirements are worth 5 points, 14 are worth 3, 51 are worth 1, two can cost 3 or 5, and 3.12.4 has no value.

The requirement text is NIST SP 800-171 Revision 2, word for word, because the CMMC rule says the Level 2 requirements are identical to it, even though NIST has withdrawn Revision 2 and replaced it with Revision 3.

Where Annex A says not to subtract points, for example for remote access controls when remote access is not permitted, leave the requirement marked Implemented.

For the rules behind the numbers, the lowest possible score and a worked example, read How to calculate your SPRS score.

What this calculator does not do

  • It is not an assessment. It adds up the answers you give and checks no evidence.
  • It does not submit a score to SPRS or send it anywhere else.
  • It does not judge whether a requirement is really implemented. Under the CMMC scoring rule, a requirement is MET only when its objectives are satisfied based on evidence.
  • It does not give you a CMMC status. The CMMC Level 2 block is arithmetic on your answers; the Level 2 self-assessment guide covers what a status takes.

Sources

  1. NIST SP 800-171 DoD Assessment Methodology, Version 1.2.1 (June 24, 2020), Annex A scoring template
  2. NIST SP 800-171 Revision 2, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations
  3. NIST SP 800-171 Revision 2, security requirements (CSV, csrc.nist.gov)
  4. 32 CFR 170.14, CMMC Model
  5. 32 CFR 170.21, Plan of Action and Milestones requirements
  6. 32 CFR 170.24, CMMC Scoring Methodology

General information, not legal advice.

How CMMCSync helps

A calculator gives you one number on one day. On the Maintain plan, CMMCSync keeps SPRS score tracking in your workspace next to POA&M management and the SSP Generator, so the score follows your findings as they change. See the features.

Keep the score current, not just calculated.

Start with Foundations for the Level 1 self-assessment, move to Maintain for Level 2 readiness and SPRS score tracking, or talk to the founder about what your contract requires.

Free to start — no application, no quote call. Cancel paid plans anytime.