All 110 NIST SP 800-171 Rev 2 requirements pre-loaded. Fill in status, describe gaps, assign owners, and track remediation dates — then print or export to PDF.
A gap register is a structured inventory of every security requirement your organization must meet, recording which controls are fully implemented, partially implemented, or not yet in place. It is the foundation document for building your CMMC POA&M and driving your remediation roadmap before a C3PAO assessment.
| Req ID | Requirement Title | Family | Points | Status | Gap Description | Owner | Compensating Control | Target Close | Notes |
|---|---|---|---|---|---|---|---|---|---|
| AC — Access Control (3.1) — 22 Requirements | |||||||||
| 3.1.1 | Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems) | AC | 5 | ||||||
| 3.1.2 | Limit system access to the types of transactions and functions that authorized users are permitted to execute | AC | 5 | ||||||
| 3.1.3 | Control the flow of CUI in accordance with approved authorizations | AC | 3 | ||||||
| 3.1.4 | Separate the duties of individuals to reduce the risk of malevolent activity without collusion | AC | 3 | ||||||
| 3.1.5 | Employ the principle of least privilege, including for specific security functions and privileged accounts | AC | 5 | ||||||
| 3.1.6 | Use non-privileged accounts or roles when accessing non-security functions | AC | 3 | ||||||
| 3.1.7 | Prevent non-privileged users from executing privileged functions and capture in audit logs | AC | 3 | ||||||
| 3.1.8 | Limit unsuccessful logon attempts | AC | 3 | ||||||
| 3.1.9 | Provide privacy and security notices consistent with CUI rules | AC | 1 | ||||||
| 3.1.10 | Use session lock with pattern-hiding displays after a period of inactivity | AC | 3 | ||||||
| 3.1.11 | Terminate (automatically) a user session after a defined condition | AC | 3 | ||||||
| 3.1.12 | Monitor and control remote access sessions | AC | 3 | ||||||
| 3.1.13 | Employ cryptographic mechanisms to protect the confidentiality of remote access sessions | AC | 5 | ||||||
| 3.1.14 | Route remote access via managed access control points | AC | 3 | ||||||
| 3.1.15 | Authorize remote execution of privileged commands and access to security-relevant information via remote access only for documented operational needs | AC | 3 | ||||||
| 3.1.16 | Authorize wireless access prior to allowing connections | AC | 3 | ||||||
| 3.1.17 | Protect wireless access using authentication and encryption | AC | 5 | ||||||
| 3.1.18 | Control connection of mobile devices | AC | 3 | ||||||
| 3.1.19 | Encrypt CUI on mobile devices and mobile computing platforms | AC | 5 | ||||||
| 3.1.20 | Verify and control/limit connections to external systems | AC | 3 | ||||||
| 3.1.21 | Limit use of portable storage devices on external systems | AC | 3 | ||||||
| 3.1.22 | Control CUI posted or processed on publicly accessible systems | AC | 3 | ||||||
| AT — Awareness and Training (3.2) — 3 Requirements | |||||||||
| 3.2.1 | Ensure that personnel are aware of the security risks associated with their activities and of applicable policies, standards, and procedures | AT | 3 | ||||||
| 3.2.2 | Ensure that personnel are trained to carry out their assigned information security responsibilities | AT | 3 | ||||||
| 3.2.3 | Provide security awareness training on recognizing and reporting potential threats including social engineering and phishing | AT | 3 | ||||||
| AU — Audit and Accountability (3.3) — 9 Requirements | |||||||||
| 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 activity | AU | 5 | ||||||
| 3.3.2 | Ensure that the actions of individual users can be uniquely traced to those users so they can be held accountable for their actions | AU | 5 | ||||||
| 3.3.3 | Review and update logged events | AU | 3 | ||||||
| 3.3.4 | Alert in the event of an audit logging process failure | AU | 3 | ||||||
| 3.3.5 | Correlate audit record review, analysis, and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious, or unusual activity | AU | 3 | ||||||
| 3.3.6 | Provide audit record reduction and report generation to support on-demand analysis and reporting | AU | 3 | ||||||
| 3.3.7 | Provide a system capability that compares and synchronizes internal clocks with an authoritative source to generate timestamps for audit records | AU | 1 | ||||||
| 3.3.8 | Protect audit information and tools from unauthorized access, modification, and deletion | AU | 3 | ||||||
| 3.3.9 | Limit management of audit logging to a subset of privileged users | AU | 1 | ||||||
| CM — Configuration Management (3.4) — 9 Requirements | |||||||||
| 3.4.1 | Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) | CM | 5 | ||||||
| 3.4.2 | Establish and enforce security configuration settings for IT products employed in organizational systems | CM | 5 | ||||||
| 3.4.3 | Track, review, approve, and log changes to organizational systems | CM | 3 | ||||||
| 3.4.4 | Analyze the security impact of changes prior to implementation | CM | 3 | ||||||
| 3.4.5 | Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems | CM | 3 | ||||||
| 3.4.6 | Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities | CM | 3 | ||||||
| 3.4.7 | Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services | CM | 3 | ||||||
| 3.4.8 | Apply deny-by-exception (blacklisting) policy to prevent the use of unauthorized software or deny-all, permit-by-exception (whitelisting) policy | CM | 3 | ||||||
| 3.4.9 | Control and monitor user-installed software | CM | 1 | ||||||
| IA — Identification and Authentication (3.5) — 11 Requirements | |||||||||
| 3.5.1 | Identify system users, processes acting on behalf of users, and devices | IA | 5 | ||||||
| 3.5.2 | Authenticate (or verify) the identities of users, processes, or devices, as a prerequisite to allowing access | IA | 5 | ||||||
| 3.5.3 | Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts | IA | 5 | ||||||
| 3.5.4 | Employ replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts | IA | 3 | ||||||
| 3.5.5 | Employ identifier management: prevent reuse of identifiers for a defined period | IA | 3 | ||||||
| 3.5.6 | Disable identifiers after a defined inactivity period | IA | 3 | ||||||
| 3.5.7 | Enforce a minimum password complexity and change of characters when new passwords are created | IA | 3 | ||||||
| 3.5.8 | Prohibit password reuse for a specified number of generations | IA | 3 | ||||||
| 3.5.9 | Allow temporary password use for system logons with an immediate change to a permanent password | IA | 1 | ||||||
| 3.5.10 | Store and transmit only cryptographically-protected passwords | IA | 5 | ||||||
| 3.5.11 | Obscure feedback of authentication information | IA | 1 | ||||||
| IR — Incident Response (3.6) — 3 Requirements | |||||||||
| 3.6.1 | Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities | IR | 5 | ||||||
| 3.6.2 | Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization | IR | 5 | ||||||
| 3.6.3 | Test the organizational incident response capability | IR | 3 | ||||||
| MA — Maintenance (3.7) — 6 Requirements | |||||||||
| 3.7.1 | Perform maintenance on organizational systems | MA | 3 | ||||||
| 3.7.2 | Provide controls on the tools, techniques, mechanisms, and personnel for the conduct of system maintenance | MA | 3 | ||||||
| 3.7.3 | Ensure equipment removed for off-site maintenance is sanitized | MA | 3 | ||||||
| 3.7.4 | Check media containing diagnostic and test programs for malicious code before the media are used in organizational systems | MA | 3 | ||||||
| 3.7.5 | Require MFA to establish nonlocal maintenance sessions via external networks and terminate sessions when nonlocal maintenance is complete | MA | 5 | ||||||
| 3.7.6 | Supervise the maintenance activities of personnel without required access authorization | MA | 3 | ||||||
| MP — Media Protection (3.8) — 9 Requirements | |||||||||
| 3.8.1 | Protect (i.e., physically control and securely store) system media containing CUI, both paper and digital | MP | 3 | ||||||
| 3.8.2 | Limit access to CUI on system media to authorized users | MP | 3 | ||||||
| 3.8.3 | Sanitize or destroy system media before disposal or reuse | MP | 5 | ||||||
| 3.8.4 | Mark media with necessary CUI markings and distribution limitations | MP | 3 | ||||||
| 3.8.5 | Control access to media containing CUI and maintain accountability for media during transport | MP | 3 | ||||||
| 3.8.6 | Implement cryptographic mechanisms to protect the confidentiality of CUI during transport unless otherwise protected by alternative physical safeguards | MP | 5 | ||||||
| 3.8.7 | Control the use of removable media on system components | MP | 3 | ||||||
| 3.8.8 | Prohibit the use of portable storage devices when such devices have no identifiable owner | MP | 3 | ||||||
| 3.8.9 | Protect the confidentiality of backup CUI at storage locations | MP | 3 | ||||||
| PS — Personnel Security (3.9) — 2 Requirements | |||||||||
| 3.9.1 | Screen individuals prior to authorizing access to organizational systems containing CUI | PS | 3 | ||||||
| 3.9.2 | Ensure that CUI is protected during and after personnel actions such as terminations and transfers | PS | 5 | ||||||
| PE — Physical Protection (3.10) — 6 Requirements | |||||||||
| 3.10.1 | Limit physical access to organizational systems, equipment, and the respective operating environments to authorized individuals | PE | 5 | ||||||
| 3.10.2 | Protect and monitor the physical facility and support infrastructure for organizational systems | PE | 3 | ||||||
| 3.10.3 | Escort visitors and monitor visitor activity | PE | 3 | ||||||
| 3.10.4 | Maintain audit logs of physical access | PE | 3 | ||||||
| 3.10.5 | Control and manage physical access devices | PE | 3 | ||||||
| 3.10.6 | Enforce safeguarding measures for CUI at alternate work sites | PE | 3 | ||||||
| RA — Risk Assessment (3.11) — 3 Requirements | |||||||||
| 3.11.1 | Periodically assess the risk to organizational operations, assets, and individuals resulting from the operation of organizational systems and the associated processing of CUI | RA | 5 | ||||||
| 3.11.2 | Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems are identified | RA | 5 | ||||||
| 3.11.3 | Remediate vulnerabilities in accordance with risk assessments | RA | 5 | ||||||
| CA — Security Assessment (3.12) — 4 Requirements | |||||||||
| 3.12.1 | Periodically assess the security controls in organizational systems to determine if the controls are effective in their application | CA | 5 | ||||||
| 3.12.2 | Develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems | CA | 5 | ||||||
| 3.12.3 | Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls | CA | 3 | ||||||
| 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 | CA | 5 | ||||||
| SC — System and Communications Protection (3.13) — 16 Requirements | |||||||||
| 3.13.1 | Monitor, control, and protect communications (i.e., information transmitted or received) at the external boundaries and key internal boundaries of organizational systems | SC | 5 | ||||||
| 3.13.2 | Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems | SC | 3 | ||||||
| 3.13.3 | Separate user functionality from system management functionality | SC | 3 | ||||||
| 3.13.4 | Prevent unauthorized and unintended information transfer via shared system resources | SC | 3 | ||||||
| 3.13.5 | Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks | SC | 3 | ||||||
| 3.13.6 | Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception) | SC | 3 | ||||||
| 3.13.7 | Prevent remote devices from simultaneously connecting to the system and to other resources (i.e., split tunneling) | SC | 3 | ||||||
| 3.13.8 | Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards | SC | 5 | ||||||
| 3.13.9 | Terminate network connections after a defined period of inactivity | SC | 3 | ||||||
| 3.13.10 | Establish and manage cryptographic keys for cryptography employed in organizational systems | SC | 3 | ||||||
| 3.13.11 | Employ FIPS-validated cryptography when used to protect the confidentiality of CUI | SC | 5 | ||||||
| 3.13.12 | Prohibit remote activation of collaborative computing devices and provide notification to present users | SC | 3 | ||||||
| 3.13.13 | Control and monitor the use of mobile code | SC | 3 | ||||||
| 3.13.14 | Control and monitor the use of VoIP technologies | SC | 3 | ||||||
| 3.13.15 | Protect the authenticity of communications sessions | SC | 3 | ||||||
| 3.13.16 | Protect CUI at rest | SC | 5 | ||||||
| SI — System and Information Integrity (3.14) — 7 Requirements | |||||||||
| 3.14.1 | Identify, report, and correct information and information system flaws in a timely manner | SI | 5 | ||||||
| 3.14.2 | Provide protection from malicious code at appropriate locations within organizational systems | SI | 5 | ||||||
| 3.14.3 | Monitor system security alerts and advisories and take action in response | SI | 3 | ||||||
| 3.14.4 | Update malicious code protection mechanisms when new releases are available | SI | 3 | ||||||
| 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 | SI | 3 | ||||||
| 3.14.6 | Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks | SI | 3 | ||||||
| 3.14.7 | Identify unauthorized use of organizational systems | SI | 3 | ||||||
Point values reflect the NIST SP 800-171 DoD Assessment Methodology scoring weights. The maximum achievable SPRS score is 110 points; each deficiency reduces the score by its point value, with a floor of −203. Requirements marked with a 5-point value cannot be addressed through compensating controls under C3PAO assessment methodology — they must be met.