Checklist

CMMC Level 2 Readiness Checklist

All 110 NIST SP 800-171 Rev 2 practices organized by the 14 control families. Use this checklist to self-assess your organization's current CMMC Level 2 readiness posture.

How to Use This Checklist

CMMC Level 2 requires implementation of all 110 security practices from NIST SP 800-171 Rev 2. These practices are organized across 14 control families. Review each practice below to determine whether your organization has fully implemented, partially implemented, or not yet addressed each requirement.

110

Total Practices

14

Control Families

Level 2

CMMC Maturity

AC

Access Control (AC)

22 practices
AC.L2-3.1.1Authorized Access Control

Limit system access to authorized users, processes acting on behalf of authorized users, and devices.

AC.L2-3.1.2Transaction and Function Control

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

AC.L2-3.1.3CUI Flow Enforcement

Control the flow of CUI in accordance with approved authorizations.

AC.L2-3.1.4Separation of Duties

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

AC.L2-3.1.5Least Privilege

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

AC.L2-3.1.6Non-Privileged Account Use

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

AC.L2-3.1.7Privileged Functions

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

AC.L2-3.1.8Unsuccessful Logon Attempts

Limit unsuccessful logon attempts.

AC.L2-3.1.9Privacy and Security Notices

Provide privacy and security notices consistent with applicable CUI rules.

AC.L2-3.1.10Session Lock

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

AC.L2-3.1.11Session Termination

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

AC.L2-3.1.12Remote Access Control

Monitor and control remote access sessions.

AC.L2-3.1.13Remote Access Confidentiality

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

AC.L2-3.1.14Remote Access Routing

Route remote access via managed access control points.

AC.L2-3.1.15Privileged Remote Access

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

AC.L2-3.1.16Wireless Access Authorization

Authorize wireless access prior to allowing such connections.

AC.L2-3.1.17Wireless Access Protection

Protect wireless access using authentication and encryption.

AC.L2-3.1.18Mobile Device Connection

Control connection of mobile devices.

AC.L2-3.1.19Encrypt CUI on Mobile Devices

Encrypt CUI on mobile devices and mobile computing platforms.

AC.L2-3.1.20External Connections

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

AC.L2-3.1.21Portable Storage

Limit use of portable storage devices on external systems.

AC.L2-3.1.22Publicly Accessible Content

Control information posted or processed on publicly accessible systems.

AT

Awareness and Training (AT)

3 practices
AT.L2-3.2.1Role-Based Risk Awareness

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.

AT.L2-3.2.2Role-Based Training

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

AT.L2-3.2.3Insider Threat Awareness

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

AU

Audit and Accountability (AU)

9 practices
AU.L2-3.3.1System Auditing

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.

AU.L2-3.3.2User Accountability

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

AU.L2-3.3.3Event Review

Review and update logged events.

AU.L2-3.3.4Audit Failure Alerting

Alert in the event of an audit logging process failure.

AU.L2-3.3.5Audit Correlation

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

AU.L2-3.3.6Audit Reduction and Reporting

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

AU.L2-3.3.7Authoritative Time Source

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

AU.L2-3.3.8Audit Protection

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

AU.L2-3.3.9Audit Management

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

CM

Configuration Management (CM)

9 practices
CM.L2-3.4.1System Baselining

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

CM.L2-3.4.2Security Configuration Enforcement

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

CM.L2-3.4.3System Change Management

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

CM.L2-3.4.4Security Impact Analysis

Analyze the security impact of changes prior to implementation.

CM.L2-3.4.5Access Restrictions for Change

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

CM.L2-3.4.6Least Functionality

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

CM.L2-3.4.7Nonessential Functionality

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

CM.L2-3.4.8Application Execution Policy

Apply deny-by-exception (blocklisting) policy to prevent the use of unauthorized software or deny-all, permit-by-exception (allowlisting) policy to allow the execution of authorized software.

CM.L2-3.4.9User-Installed Software

Control and monitor user-installed software.

IA

Identification and Authentication (IA)

11 practices
IA.L2-3.5.1Identification

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

IA.L2-3.5.2Authentication

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

IA.L2-3.5.3Multi-Factor Authentication

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

IA.L2-3.5.4Replay-Resistant Authentication

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

IA.L2-3.5.5Identifier Reuse Prevention

Prevent reuse of identifiers for a defined period.

IA.L2-3.5.6Identifier Handling

Disable identifiers after a defined period of inactivity.

IA.L2-3.5.7Password Complexity

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

IA.L2-3.5.8Password Reuse

Prohibit password reuse for a specified number of generations.

IA.L2-3.5.9Temporary Passwords

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

IA.L2-3.5.10Cryptographic Key Protection

Store and transmit only cryptographically-protected passwords.

IA.L2-3.5.11Obscure Feedback

Obscure feedback of authentication information.

IR

Incident Response (IR)

3 practices
IR.L2-3.6.1Incident Handling

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

IR.L2-3.6.2Incident Reporting

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

IR.L2-3.6.3Incident Response Testing

Test the organizational incident response capability.

MA

Maintenance (MA)

6 practices
MA.L2-3.7.1System Maintenance

Perform maintenance on organizational systems.

MA.L2-3.7.2System Maintenance Control

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

MA.L2-3.7.3Equipment Sanitization

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

MA.L2-3.7.4Media Inspection

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

MA.L2-3.7.5Nonlocal Maintenance

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

MA.L2-3.7.6Maintenance Personnel

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

MP

Media Protection (MP)

9 practices
MP.L2-3.8.1Media Protection

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

MP.L2-3.8.2Media Access

Limit access to CUI on system media to authorized users.

MP.L2-3.8.3Media Disposal

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

MP.L2-3.8.4Media Markings

Mark media with necessary CUI markings and distribution limitations.

MP.L2-3.8.5Media Accountability

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

MP.L2-3.8.6Portable Storage Encryption

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

MP.L2-3.8.7Removable Media

Control the use of removable media on system components.

MP.L2-3.8.8Shared Media

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

MP.L2-3.8.9CUI Backup Protection

Protect the confidentiality of backup CUI at storage locations.

PS

Personnel Security (PS)

2 practices
PS.L2-3.9.1Screen Individuals

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

PS.L2-3.9.2Personnel Actions

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

PE

Physical Protection (PE)

6 practices
PE.L2-3.10.1Physical Access Limitations

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

PE.L2-3.10.2Physical Access Monitoring

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

PE.L2-3.10.3Escort Visitors

Escort visitors and monitor visitor activity.

PE.L2-3.10.4Physical Access Logs

Maintain audit logs of physical access.

PE.L2-3.10.5Physical Access Devices

Control and manage physical access devices.

PE.L2-3.10.6Alternative Work Sites

Enforce safeguarding measures for CUI at alternate work sites.

RA

Risk Assessment (RA)

3 practices
RA.L2-3.11.1Risk Assessments

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.

RA.L2-3.11.2Vulnerability Scanning

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

RA.L2-3.11.3Vulnerability Remediation

Remediate vulnerabilities in accordance with risk assessments.

CA

Security Assessment (CA)

4 practices
CA.L2-3.12.1Security Control Assessment

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

CA.L2-3.12.2Plans of Action

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

CA.L2-3.12.3Security Control Monitoring

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

CA.L2-3.12.4System Security Plan

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.

SC

System and Communications Protection (SC)

16 practices
SC.L2-3.13.1Boundary Protection

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.

SC.L2-3.13.2Security Engineering

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

SC.L2-3.13.3Role Separation

Separate user functionality from system management functionality.

SC.L2-3.13.4Shared Resource Control

Prevent unauthorized and unintended information transfer via shared system resources.

SC.L2-3.13.5Public Access Protections

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

SC.L2-3.13.6Network Communication by Exception

Deny network communications traffic by default and allow network communications traffic by exception.

SC.L2-3.13.7Split Tunneling

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

SC.L2-3.13.8Data in Transit

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

SC.L2-3.13.9Network Disconnect

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

SC.L2-3.13.10Cryptographic Key Management

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

SC.L2-3.13.11CUI Encryption

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

SC.L2-3.13.12Collaborative Device Control

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

SC.L2-3.13.13Mobile Code

Control and monitor the use of mobile code.

SC.L2-3.13.14Voice over IP

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

SC.L2-3.13.15Communications Authenticity

Protect the authenticity of communications sessions.

SC.L2-3.13.16Data at Rest

Protect the confidentiality of CUI at rest.

SI

System and Information Integrity (SI)

7 practices
SI.L2-3.14.1Flaw Remediation

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

SI.L2-3.14.2Malicious Code Protection

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

SI.L2-3.14.3Security Alerts

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

SI.L2-3.14.4Update Malicious Code Protection

Update malicious code protection mechanisms when new releases are available.

SI.L2-3.14.5System and File Scanning

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

SI.L2-3.14.6Inbound and Outbound Monitoring

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

SI.L2-3.14.7Unauthorized Use Identification

Identify unauthorized use of organizational systems.

Ready to Assess Your CMMC Readiness?

Schedule a readiness assessment with our team to identify gaps, prioritize remediation, and build a clear path to CMMC Level 2 certification.