5.0 on Google & Clutch 96%LIVE of calls answered in under 60 seconds by our local Huntington Beach team

Free estimator · all 110 requirements · runs in your browser

What’s your SPRS score?

Your SPRS (Supplier Performance Risk System) score is the Department of Defense’s rating, from −203 to 110, of how many of the 110 NIST SP 800-171 requirements you meet. Contracts that require CMMC Level 2 (Self) need a current score posted in SPRS before award. Estimate yours the way the DoD does: start at 110 and subtract 5, 3 or 1 points for every requirement that isn’t met. Mark all 110 requirements, see your score live, and find out which gaps cost the most and whether a POA&M could cover them. Nothing is sent anywhere.

1

Mark

Go through the 110 NIST SP 800-171 requirements and mark each one met, not met or unsure (unsure counts as not met).

2

Score

Once all 110 are marked, you get your estimated SPRS score, using the DoD’s 5-, 3- and 1-point weights.

3

Plan

See your biggest gaps, whether a POA&M could cover them, and print the list for your team.

01

Access Control

Who can get into your systems and CUI, and what they can do once inside.

  1. 3.1.15 pts

    Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems).

    Status 3.1.1
  2. 3.1.25 pts

    Limit system access to the types of transactions and functions that authorized users are permitted to execute.

    Status 3.1.2
  3. 3.1.31 pts

    Control the flow of CUI in accordance with approved authorizations.

    Status 3.1.3
  4. 3.1.41 pts

    Separate the duties of individuals to reduce the risk of malevolent activity without collusion.

    Status 3.1.4
  5. 3.1.53 pts

    Employ the principle of least privilege, including for specific security functions and privileged accounts.

    Status 3.1.5
  6. 3.1.61 pts

    Use non-privileged accounts or roles when accessing non-security functions.

    Status 3.1.6
  7. 3.1.71 pts

    Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs.

    Status 3.1.7
  8. 3.1.81 pts

    Limit unsuccessful logon attempts.

    Status 3.1.8
  9. 3.1.91 pts

    Provide privacy and security notices consistent with applicable CUI rules.

    Status 3.1.9
  10. 3.1.101 pts

    Use session lock with pattern-hiding displays to prevent access and viewing of data after a period of inactivity.

    Status 3.1.10
  11. 3.1.111 pts

    Terminate (automatically) a user session after a defined condition.

    Status 3.1.11
  12. 3.1.125 pts

    Monitor and control remote access sessions.

    Status 3.1.12
  13. 3.1.135 pts

    Employ cryptographic mechanisms to protect the confidentiality of remote access sessions.

    Status 3.1.13
  14. 3.1.141 pts

    Route remote access via managed access control points.

    Status 3.1.14
  15. 3.1.151 pts

    Authorize remote execution of privileged commands and remote access to security-relevant information.

    Status 3.1.15
  16. 3.1.165 pts

    Authorize wireless access prior to allowing such connections.

    Status 3.1.16
  17. 3.1.175 pts

    Protect wireless access using authentication and encryption.

    Status 3.1.17
  18. 3.1.185 pts

    Control connection of mobile devices.

    Status 3.1.18
  19. 3.1.193 pts

    Encrypt CUI on mobile devices and mobile computing platforms.

    Status 3.1.19
  20. 3.1.201 pts

    Verify and control/limit connections to and use of external systems.

    Status 3.1.20
  21. 3.1.211 pts

    Limit use of portable storage devices on external systems.

    Status 3.1.21
  22. 3.1.221 pts

    Control CUI posted or processed on publicly accessible systems.

    Status 3.1.22
02

Awareness and Training

Making sure everyone knows the risks and their security duties.

  1. 3.2.15 pts

    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.

    Status 3.2.1
  2. 3.2.25 pts

    Ensure that personnel are trained to carry out their assigned information security-related duties and responsibilities.

    Status 3.2.2
  3. 3.2.31 pts

    Provide security awareness training on recognizing and reporting potential indicators of insider threat.

    Status 3.2.3
03

Audit and Accountability

Logging activity so you can trace what happened and who did it.

  1. 3.3.15 pts

    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.

    Status 3.3.1
  2. 3.3.23 pts

    Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions.

    Status 3.3.2
  3. 3.3.31 pts

    Review and update logged events.

    Status 3.3.3
  4. 3.3.41 pts

    Alert in the event of an audit logging process failure.

    Status 3.3.4
  5. 3.3.55 pts

    Correlate audit record review, analysis, and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious, or unusual activity.

    Status 3.3.5
  6. 3.3.61 pts

    Provide audit record reduction and report generation to support on-demand analysis and reporting.

    Status 3.3.6
  7. 3.3.71 pts

    Provide a system capability that compares and synchronizes internal system clocks with an authoritative source to generate time stamps for audit records.

    Status 3.3.7
  8. 3.3.81 pts

    Protect audit information and audit logging tools from unauthorized access, modification, and deletion.

    Status 3.3.8
  9. 3.3.91 pts

    Limit management of audit logging functionality to a subset of privileged users.

    Status 3.3.9
04

Configuration Management

Secure, documented settings and control over changes and software.

  1. 3.4.15 pts

    Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles.

    Status 3.4.1
  2. 3.4.25 pts

    Establish and enforce security configuration settings for information technology products employed in organizational systems.

    Status 3.4.2
  3. 3.4.31 pts

    Track, review, approve or disapprove, and log changes to organizational systems.

    Status 3.4.3
  4. 3.4.41 pts

    Analyze the security impact of changes prior to implementation.

    Status 3.4.4
  5. 3.4.55 pts

    Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems.

    Status 3.4.5
  6. 3.4.65 pts

    Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities.

    Status 3.4.6
  7. 3.4.75 pts

    Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.

    Status 3.4.7
  8. 3.4.85 pts

    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.

    Status 3.4.8
  9. 3.4.91 pts

    Control and monitor user-installed software.

    Status 3.4.9
05

Identification and Authentication

Unique accounts, strong passwords and multifactor authentication.

  1. 3.5.15 pts

    Identify system users, processes acting on behalf of users, and devices.

    Status 3.5.1
  2. 3.5.25 pts

    Authenticate (or verify) the identities of users, processes, or devices, as a prerequisite to allowing access to organizational systems.

    Status 3.5.2
  3. 3.5.35 pts

    Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts.

    Status 3.5.3
  4. 3.5.41 pts

    Employ replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts.

    Status 3.5.4
  5. 3.5.51 pts

    Prevent reuse of identifiers for a defined period.

    Status 3.5.5
  6. 3.5.61 pts

    Disable identifiers after a defined period of inactivity.

    Status 3.5.6
  7. 3.5.71 pts

    Enforce a minimum password complexity and change of characters when new passwords are created.

    Status 3.5.7
  8. 3.5.81 pts

    Prohibit password reuse for a specified number of generations.

    Status 3.5.8
  9. 3.5.91 pts

    Allow temporary password use for system logons with an immediate change to a permanent password.

    Status 3.5.9
  10. 3.5.105 pts

    Store and transmit only cryptographically-protected passwords.

    Status 3.5.10
  11. 3.5.111 pts

    Obscure feedback of authentication information.

    Status 3.5.11
06

Incident Response

Detecting, reporting and handling security incidents.

  1. 3.6.15 pts

    Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities.

    Status 3.6.1
  2. 3.6.25 pts

    Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization.

    Status 3.6.2
  3. 3.6.31 pts

    Test the organizational incident response capability.

    Status 3.6.3
07

Maintenance

Controlling who maintains your systems, and how.

  1. 3.7.13 pts

    Perform maintenance on organizational systems.

    Status 3.7.1
  2. 3.7.25 pts

    Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance.

    Status 3.7.2
  3. 3.7.31 pts

    Ensure equipment removed for off-site maintenance is sanitized of any CUI.

    Status 3.7.3
  4. 3.7.43 pts

    Check media containing diagnostic and test programs for malicious code before the media are used in organizational systems.

    Status 3.7.4
  5. 3.7.55 pts

    Require multifactor authentication to establish nonlocal maintenance sessions via external network connections and terminate such connections when nonlocal maintenance is complete.

    Status 3.7.5
  6. 3.7.61 pts

    Supervise the maintenance activities of maintenance personnel without required access authorization.

    Status 3.7.6
08

Media Protection

Protecting, marking and destroying drives, USB sticks and paper that hold CUI.

  1. 3.8.13 pts

    Protect (i.e., physically control and securely store) system media containing CUI, both paper and digital.

    Status 3.8.1
  2. 3.8.23 pts

    Limit access to CUI on system media to authorized users.

    Status 3.8.2
  3. 3.8.35 pts

    Sanitize or destroy system media containing CUI before disposal or release for reuse.

    Status 3.8.3
  4. 3.8.41 pts

    Mark media with necessary CUI markings and distribution limitations.

    Status 3.8.4
  5. 3.8.51 pts

    Control access to media containing CUI and maintain accountability for media during transport outside of controlled areas.

    Status 3.8.5
  6. 3.8.61 pts

    Implement cryptographic mechanisms to protect the confidentiality of CUI stored on digital media during transport unless otherwise protected by alternative physical safeguards.

    Status 3.8.6
  7. 3.8.75 pts

    Control the use of removable media on system components.

    Status 3.8.7
  8. 3.8.83 pts

    Prohibit the use of portable storage devices when such devices have no identifiable owner.

    Status 3.8.8
  9. 3.8.91 pts

    Protect the confidentiality of backup CUI at storage locations.

    Status 3.8.9
09

Personnel Security

Screening people before they get access, and removing it when they leave.

  1. 3.9.13 pts

    Screen individuals prior to authorizing access to organizational systems containing CUI.

    Status 3.9.1
  2. 3.9.25 pts

    Ensure that organizational systems containing CUI are protected during and after personnel actions such as terminations and transfers.

    Status 3.9.2
10

Physical Protection

Securing offices, visitors and equipment that hold CUI.

  1. 3.10.15 pts

    Limit physical access to organizational systems, equipment, and the respective operating environments to authorized individuals.

    Status 3.10.1
  2. 3.10.25 pts

    Protect and monitor the physical facility and support infrastructure for organizational systems.

    Status 3.10.2
  3. 3.10.31 pts

    Escort visitors and monitor visitor activity.

    Status 3.10.3
  4. 3.10.41 pts

    Maintain audit logs of physical access.

    Status 3.10.4
  5. 3.10.51 pts

    Control and manage physical access devices.

    Status 3.10.5
  6. 3.10.61 pts

    Enforce safeguarding measures for CUI at alternate work sites.

    Status 3.10.6
11

Risk Assessment

Assessing risk regularly and scanning for vulnerabilities.

  1. 3.11.13 pts

    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.

    Status 3.11.1
  2. 3.11.25 pts

    Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified.

    Status 3.11.2
  3. 3.11.31 pts

    Remediate vulnerabilities in accordance with risk assessments.

    Status 3.11.3
12

Security Assessment

Your system security plan, checking your controls and tracking fixes on a POA&M.

  1. 3.12.15 pts

    Periodically assess the security controls in organizational systems to determine if the controls are effective in their application.

    Status 3.12.1
  2. 3.12.23 pts

    Develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems.

    Status 3.12.2
  3. 3.12.35 pts

    Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls.

    Status 3.12.3
  4. 3.12.40 pts

    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 points, but required: without a system security plan there is no valid score.

    Status 3.12.4
13

System and Communications Protection

Firewalls, network boundaries, encryption and secure communications.

  1. 3.13.15 pts

    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.

    Status 3.13.1
  2. 3.13.25 pts

    Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.

    Status 3.13.2
  3. 3.13.31 pts

    Separate user functionality from system management functionality.

    Status 3.13.3
  4. 3.13.41 pts

    Prevent unauthorized and unintended information transfer via shared system resources.

    Status 3.13.4
  5. 3.13.55 pts

    Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.

    Status 3.13.5
  6. 3.13.65 pts

    Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception).

    Status 3.13.6
  7. 3.13.71 pts

    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).

    Status 3.13.7
  8. 3.13.83 pts

    Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards.

    Status 3.13.8
  9. 3.13.91 pts

    Terminate network connections associated with communications sessions at the end of the sessions or after a defined period of inactivity.

    Status 3.13.9
  10. 3.13.101 pts

    Establish and manage cryptographic keys for cryptography employed in organizational systems.

    Status 3.13.10
  11. 3.13.115 pts

    Employ FIPS-validated cryptography when used to protect the confidentiality of CUI.

    Status 3.13.11
  12. 3.13.121 pts

    Prohibit remote activation of collaborative computing devices and provide indication of devices in use to users present at the device.

    Status 3.13.12
  13. 3.13.131 pts

    Control and monitor the use of mobile code.

    Status 3.13.13
  14. 3.13.141 pts

    Control and monitor the use of Voice over Internet Protocol (VoIP) technologies.

    Status 3.13.14
  15. 3.13.155 pts

    Protect the authenticity of communications sessions.

    Status 3.13.15
  16. 3.13.161 pts

    Protect the confidentiality of CUI at rest.

    Status 3.13.16
14

System and Information Integrity

Patching, malware protection, security alerts and monitoring.

  1. 3.14.15 pts

    Identify, report, and correct system flaws in a timely manner.

    Status 3.14.1
  2. 3.14.25 pts

    Provide protection from malicious code at designated locations within organizational systems.

    Status 3.14.2
  3. 3.14.35 pts

    Monitor system security alerts and advisories and take action in response.

    Status 3.14.3
  4. 3.14.45 pts

    Update malicious code protection mechanisms when new releases are available.

    Status 3.14.4
  5. 3.14.53 pts

    Perform periodic scans of organizational systems and real-time scans of files from external sources as files are downloaded, opened, or executed.

    Status 3.14.5
  6. 3.14.65 pts

    Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks.

    Status 3.14.6
  7. 3.14.73 pts

    Identify unauthorized use of organizational systems.

    Status 3.14.7

Mark each requirement to estimate your score.

CMMC and SPRS score questions

What is an SPRS score?

The Supplier Performance Risk System (SPRS) score summarizes how many of the 110 NIST SP 800-171 security requirements a defense contractor has implemented. It starts at 110 and subtracts 5, 3 or 1 points for each requirement that isn’t met, so it can range from 110 down to −203. Contractors post it in SPRS when a contract requires a CMMC Level 2 (Self) assessment; since February 2026, DFARS 7012 alone no longer requires a posted self-assessment score.

What score do we need for CMMC Level 2?

Final Level 2 status means every requirement is met — a score of 110. Conditional status is possible with a score of at least 88, as long as every open item is allowed on a Plan of Action and Milestones (POA&M); those items must be closed within 180 days.

Which gaps can go on a POA&M?

Generally only requirements worth 1 point, plus 3.13.11 when encryption is used but isn’t FIPS-validated. A few requirements can never be left open, whatever their points — including the system security plan (3.12.4). The estimator flags those for you.

Why do MFA and encryption have a middle option?

The DoD methodology gives partial credit for two requirements: multifactor authentication (3.5.3) costs 3 points instead of 5 if it’s in place for remote and privileged users but not everyone, and FIPS-validated encryption (3.13.11) costs 3 instead of 5 if data is encrypted but the module isn’t FIPS-validated.

Is this an official assessment?

No. It’s an estimate for planning. An official self-assessment checks each requirement against its NIST SP 800-171A assessment objectives, with evidence. Our free CMMC gap assessment does exactly that before you submit a score or sign an affirmation.

Customer service first · we re-earn your business on every ticket

Obsessive about service. Relentless about the details.

CAL IT Group brings enterprise-class IT, cybersecurity and SOC 2 Type II–audited operational excellence to small and midsize businesses across Southern California — a customer service organization first and foremost, proven day in and day out for over 10 years.

Call 866.24.CALIT