How to Use This Checklist
This checklist maps all 110 NIST SP 800-171 requirements that make up CMMC Level 2. Each requirement shows its SPRS point weight (5, 3, or 1) and whether it can appear on a Plan of Action & Milestones (POA&M).
Requirements weighted at 5 or 3 points cannot go on a POA&M — they must be fully implemented before your C3PAO assessment. Requirements at 1 point are generally POA&M-eligible, meaning a credible remediation plan allows conditional certification.
Scoring Note
Your SPRS score starts at 110 and each unmet requirement deducts its point value. To qualify for conditional certification, your score must meet or exceed the 80% threshold. Requirement 3.12.4 (System Security Plan) is a prerequisite: without an SSP, no assessment score is possible. Counts above reflect worst-case (maximum deduction) scoring.
| Req | Description | Pts | POA&M | Status |
|---|---|---|---|---|
| 3.1.1 | Limit system access to authorized users, processes acting on behalf of authorized users, and devices | 5 | No | |
| 3.1.2 | Limit system access to the types of transactions and functions that authorized users are permitted to execute | 5 | No | |
| 3.1.3 | Control the flow of CUI in accordance with approved authorizations | 1 | Yes | |
| 3.1.4 | Separate the duties of individuals to reduce the risk of malevolent activity without collusion | 1 | Yes | |
| 3.1.5 | Employ the principle of least privilege, including for specific security functions and privileged accounts | 3 | No | |
| 3.1.6 | Use non-privileged accounts or roles when accessing non-security functions | 1 | Yes | |
| 3.1.7 | Prevent non-privileged users from executing privileged functions and capture the execution in audit logs | 1 | Yes | |
| 3.1.8 | Limit unsuccessful logon attempts | 1 | Yes | |
| 3.1.9 | Provide privacy and security notices consistent with CUI rules | 1 | Yes | |
| 3.1.10 | Use session lock with pattern-hiding displays after a period of inactivity | 1 | Yes | |
| 3.1.11 | Terminate (automatically) a user session after a defined condition | 1 | Yes | |
| 3.1.12 | Monitor and control remote access sessions | 5 | No | |
| 3.1.13 | Employ cryptographic mechanisms to protect the confidentiality of remote access sessions | 5 | No | |
| 3.1.14 | Route remote access via managed access control points | 1 | Yes | |
| 3.1.15 | Authorize remote execution of privileged commands and access to security-relevant information via remote access only for documented operational needs | 1 | Yes | |
| 3.1.16 | Authorize wireless access prior to allowing such connections | 5 | No | |
| 3.1.17 | Protect wireless access using authentication and encryption | 5 | No | |
| 3.1.18 | Control connection of mobile devices | 5 | No | |
| 3.1.19 | Encrypt CUI on mobile devices and mobile computing platforms | 3 | No | |
| 3.1.20 | Verify and control/limit connections to external systems | 1 | Yes | |
| 3.1.21 | Limit use of portable storage devices on external systems | 1 | Yes | |
| 3.1.22 | Control CUI posted or processed on publicly accessible systems | 1 | Yes |
| Req | Description | Pts | POA&M | Status |
|---|---|---|---|---|
| 3.2.1 | Ensure personnel are aware of the security risks associated with their activities and of the policies and procedures designed to reduce risks | 5 | No | |
| 3.2.2 | Ensure personnel are trained to carry out assigned security responsibilities | 5 | No | |
| 3.2.3 | Provide security awareness training on recognizing and reporting potential threats | 1 | Yes |
| Req | Description | Pts | POA&M | Status |
|---|---|---|---|---|
| 3.3.1 | Create and retain system audit logs to enable monitoring, analysis, investigation, and reporting of unlawful or unauthorized activity | 5 | No | |
| 3.3.2 | Ensure that the actions of individual users can be traced to those users so they can be held accountable | 3 | No | |
| 3.3.3 | Review and update logged events | 1 | Yes | |
| 3.3.4 | Alert in the event of an audit logging process failure | 1 | Yes | |
| 3.3.5 | Correlate audit record review, analysis, and reporting processes for investigation and response | 5 | No | |
| 3.3.6 | Provide audit record reduction and report generation to support on-demand analysis and reporting | 1 | Yes | |
| 3.3.7 | Provide a system capability that compares and synchronizes internal system clocks | 1 | Yes | |
| 3.3.8 | Protect audit information and tools from unauthorized access, modification, and deletion | 1 | Yes | |
| 3.3.9 | Limit management of audit logging to a subset of privileged users | 1 | Yes |
| Req | Description | Pts | POA&M | Status |
|---|---|---|---|---|
| 3.4.1 | Establish and maintain baseline configurations and inventories of organizational systems | 5 | No | |
| 3.4.2 | Establish and enforce security configuration settings for information technology products | 5 | No | |
| 3.4.3 | Track, review, approve, and log changes to organizational systems | 1 | Yes | |
| 3.4.4 | Analyze the security impact of changes prior to implementation | 1 | Yes | |
| 3.4.5 | Define, document, approve, and enforce physical and logical access restrictions associated with changes | 5 | No | |
| 3.4.6 | Employ the principle of least functionality by configuring systems to provide only essential capabilities | 5 | No | |
| 3.4.7 | Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services | 5 | No | |
| 3.4.8 | Apply deny-by-exception policy to prevent use of unauthorized software or deny-all, permit-by-exception policy | 5 | No | |
| 3.4.9 | Control and monitor user-installed software | 1 | Yes |
| Req | Description | Pts | POA&M | Status |
|---|---|---|---|---|
| 3.5.1 | Identify system users, processes acting on behalf of users, and devices | 5 | No | |
| 3.5.2 | Authenticate (or verify) the identities of users, processes, or devices, as a prerequisite to allowing access | 5 | No | |
| 3.5.3 | Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts | 5 | Cond. | |
| 3.5.4 | Employ replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts | 1 | Yes | |
| 3.5.5 | Employ identifier management | 1 | Yes | |
| 3.5.6 | Disable identifiers after a defined period of inactivity | 1 | Yes | |
| 3.5.7 | Enforce a minimum password complexity and change of characters when new passwords are created | 1 | Yes | |
| 3.5.8 | Prohibit password reuse for a specified number of generations | 1 | Yes | |
| 3.5.9 | Allow temporary password use for system logons with an immediate change requirement | 1 | Yes | |
| 3.5.10 | Store and transmit only cryptographically-protected passwords | 5 | No | |
| 3.5.11 | Obscure feedback of authentication information | 1 | Yes |
| Req | Description | Pts | POA&M | Status |
|---|---|---|---|---|
| 3.6.1 | Establish an operational incident-handling capability including preparation, detection, analysis, containment, recovery, and user response activities | 5 | No | |
| 3.6.2 | Track, document, and report incidents to appropriate officials and/or authorities | 5 | No | |
| 3.6.3 | Test the organizational incident response capability | 1 | Yes |
| Req | Description | Pts | POA&M | Status |
|---|---|---|---|---|
| 3.7.1 | Perform maintenance on organizational systems | 3 | No | |
| 3.7.2 | Provide controls on the tools, techniques, mechanisms, and personnel that conduct system maintenance | 5 | No | |
| 3.7.3 | Ensure equipment removed for maintenance is sanitized | 1 | Yes | |
| 3.7.4 | Check media containing diagnostic and test programs for malicious code before use | 3 | No | |
| 3.7.5 | Require MFA to establish nonlocal maintenance sessions and terminate such connections when finished | 5 | No | |
| 3.7.6 | Supervise the maintenance activities of maintenance personnel without required access authorization | 1 | Yes |
| Req | Description | Pts | POA&M | Status |
|---|---|---|---|---|
| 3.8.1 | Protect (i.e., physically control and securely store) system media containing CUI, both paper and digital | 3 | No | |
| 3.8.2 | Limit access to CUI on system media to authorized users | 3 | No | |
| 3.8.3 | Sanitize or destroy system media before disposal or reuse | 5 | No | |
| 3.8.4 | Mark media with necessary CUI markings and distribution limitations | 1 | Yes | |
| 3.8.5 | Control access to media containing CUI and maintain accountability for media during transport | 1 | Yes | |
| 3.8.6 | Implement cryptographic mechanisms to protect CUI during transport unless otherwise protected by alternative physical safeguards | 1 | Yes | |
| 3.8.7 | Control the use of removable media on system components | 5 | No | |
| 3.8.8 | Prohibit the use of portable storage devices when such devices have no identifiable owner | 3 | No | |
| 3.8.9 | Protect the confidentiality of backup CUI at storage locations | 1 | Yes |
| Req | Description | Pts | POA&M | Status |
|---|---|---|---|---|
| 3.9.1 | Screen individuals prior to authorizing access to organizational systems containing CUI | 3 | No | |
| 3.9.2 | Ensure that CUI is protected during and after personnel actions such as terminations and transfers | 5 | No |
| Req | Description | Pts | POA&M | Status |
|---|---|---|---|---|
| 3.10.1 | Limit physical access to organizational systems, equipment, and the respective operating environments to authorized individuals | 5 | No | |
| 3.10.2 | Protect and monitor the physical facility and support infrastructure for organizational systems | 5 | No | |
| 3.10.3 | Escort visitors and monitor visitor activity | 1 | Yes | |
| 3.10.4 | Maintain audit logs of physical access | 1 | Yes | |
| 3.10.5 | Control and manage physical access devices | 1 | Yes | |
| 3.10.6 | Enforce safeguarding measures for CUI at alternate work sites | 1 | Yes |
| Req | Description | Pts | POA&M | Status |
|---|---|---|---|---|
| 3.11.1 | Periodically assess the risk to organizational operations, assets, and individuals resulting from system operation and the processing, storage, or transmission of CUI | 3 | No | |
| 3.11.2 | Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities are identified | 5 | No | |
| 3.11.3 | Remediate vulnerabilities in accordance with risk assessments | 1 | Yes |
| Req | Description | Pts | POA&M | Status |
|---|---|---|---|---|
| 3.12.1 | Periodically assess the security controls in organizational systems to determine if they are effective | 5 | No | |
| 3.12.2 | Develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities | 3 | No | |
| 3.12.3 | Monitor security controls on an ongoing basis to ensure the continued effectiveness | 5 | No | |
| 3.12.4 | Develop, document, and periodically update system security plans that describe system boundaries, operating environments, how security requirements are implemented, and relationships with other systems | 0 | No |
| Req | Description | Pts | POA&M | Status |
|---|---|---|---|---|
| 3.13.1 | Monitor, control, and protect communications at the external boundaries and key internal boundaries of organizational systems | 5 | No | |
| 3.13.2 | Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security | 5 | No | |
| 3.13.3 | Separate user functionality from system management functionality | 1 | Yes | |
| 3.13.4 | Prevent unauthorized and unintended information transfer via shared system resources | 1 | Yes | |
| 3.13.5 | Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks | 5 | No | |
| 3.13.6 | Deny network communications traffic by default and allow network communications traffic by exception | 5 | No | |
| 3.13.7 | Prevent remote devices from simultaneously using a VPN tunnel and local network access (split tunneling) | 1 | Yes | |
| 3.13.8 | Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards | 3 | No | |
| 3.13.9 | Terminate network connections associated with communications sessions after a defined period of inactivity | 1 | Yes | |
| 3.13.10 | Establish and manage cryptographic keys when cryptography is employed | 1 | Yes | |
| 3.13.11 | Employ FIPS-validated cryptography when used to protect the confidentiality of CUI | 5 | Cond. | |
| 3.13.12 | Prohibit remote activation of collaborative computing devices and provide indication of use to present users | 1 | Yes | |
| 3.13.13 | Control and monitor the use of mobile code | 1 | Yes | |
| 3.13.14 | Control and monitor the use of VoIP technologies | 1 | Yes | |
| 3.13.15 | Protect the authenticity of communications sessions | 5 | No | |
| 3.13.16 | Protect CUI at rest | 1 | Yes |
| Req | Description | Pts | POA&M | Status |
|---|---|---|---|---|
| 3.14.1 | Identify, report, and correct information and system flaws in a timely manner | 5 | No | |
| 3.14.2 | Provide protection from malicious code at appropriate locations within organizational systems | 5 | No | |
| 3.14.3 | Monitor system security alerts and advisories and take action in response | 5 | No | |
| 3.14.4 | Update malicious code protection mechanisms when new releases are available | 5 | No | |
| 3.14.5 | Perform periodic scans of organizational systems and real-time scans of files from external sources | 3 | No | |
| 3.14.6 | Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks | 5 | No | |
| 3.14.7 | Identify unauthorized use of organizational systems | 3 | No |
Frequently Asked Questions
How many requirements are in CMMC Level 2?
CMMC Level 2 contains 110 security requirements derived directly from NIST SP 800-171 Rev 2, organized across 14 security domains. Every requirement must be addressed — either fully implemented or documented on an approved POA&M — for certification.
What are the SPRS point weights?
Each requirement carries a weight of 5, 3, or 1 point. There are 44 five-point requirements, 14 at three points, and 51 at one point, plus two conditional requirements (3.5.3 MFA and 3.13.11 FIPS encryption) and one prerequisite (3.12.4 SSP) at zero points. The total worst-case deduction is 313 points, producing a minimum possible SPRS score of −203.
Which requirements cannot go on a POA&M?
Requirements weighted at 5 or 3 points generally cannot appear on a POA&M for CMMC Level 2 certification. There is a limited exception for SC.L2-3.13.11 (FIPS-validated cryptography), which can be conditionally deferred. Your total score must also meet the 80% threshold to qualify for conditional certification with any open POA&M items.
What is the minimum possible SPRS score?
The minimum possible SPRS score is −203, reflecting worst-case deductions across all 110 requirements including conditional scoring for MFA and FIPS encryption. A perfect score of 110 means all requirements are fully implemented with no deductions.