NIST SP 800-171 ↔ CMMC Control Mapper

A searchable cross-walk of all 110 NIST SP 800-171 Rev 2 requirements to their CMMC Level 2 identifiers, families, DoD Assessment Methodology point values, and 32 CFR 170.21 POA&M eligibility. Identifiers and point weights come from the authoritative DoD methodology and 32 CFR Part 170.

Assessing for CMMC?Start a full self-assessment

Showing 110 of 110 requirements

RequirementPOA&M
3.1.1AC.L2-3.1.1Access Control
5
Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems).
No
3.1.2AC.L2-3.1.2Access Control
5
Limit system access to the types of transactions and functions that authorized users are permitted to execute.
No
3.1.3AC.L2-3.1.3Access Control
1
Control the flow of CUI in accordance with approved authorizations.
Yes
3.1.4AC.L2-3.1.4Access Control
1
Separate the duties of individuals to reduce the risk of malevolent activity without collusion.
Yes
3.1.5AC.L2-3.1.5Access Control
3
Employ the principle of least privilege, including for specific security functions and privileged accounts.
No
3.1.6AC.L2-3.1.6Access Control
1
Use non-privileged accounts or roles when accessing nonsecurity functions.
Yes
3.1.7AC.L2-3.1.7Access Control
1
Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs.
Yes
3.1.8AC.L2-3.1.8Access Control
1
Limit unsuccessful logon attempts.
Yes
3.1.9AC.L2-3.1.9Access Control
1
Provide privacy and security notices consistent with applicable CUI rules.
Yes
3.1.10AC.L2-3.1.10Access Control
1
Use session lock with pattern-hiding displays to prevent access and viewing of data after a period of inactivity.
Yes
3.1.11AC.L2-3.1.11Access Control
1
Terminate (automatically) a user session after a defined condition.
Yes
3.1.12AC.L2-3.1.12Access Control
5
Monitor and control remote access sessions.
No
3.1.13AC.L2-3.1.13Access Control
5
Employ cryptographic mechanisms to protect the confidentiality of remote access sessions.
No
3.1.14AC.L2-3.1.14Access Control
1
Route remote access via managed access control points.
Yes
3.1.15AC.L2-3.1.15Access Control
1
Authorize remote execution of privileged commands and remote access to security-relevant information.
Yes
3.1.16AC.L2-3.1.16Access Control
5
Authorize wireless access prior to allowing such connections.
No
3.1.17AC.L2-3.1.17Access Control
5
Protect wireless access using authentication and encryption.
No
3.1.18AC.L2-3.1.18Access Control
5
Control connection of mobile devices.
No
3.1.19AC.L2-3.1.19Access Control
3
Encrypt CUI on mobile devices and mobile computing platforms.
No
3.1.20AC.L2-3.1.20Access Control
1
Verify and control/limit connections to and use of external systems.
No
3.1.21AC.L2-3.1.21Access Control
1
Limit use of organizational portable storage devices on external systems.
Yes
3.1.22AC.L2-3.1.22Access Control
1
Control CUI posted or processed on publicly accessible systems.
No
3.2.1AT.L2-3.2.1Awareness and Training
5
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.
No
3.2.2AT.L2-3.2.2Awareness and Training
5
Ensure that organizational personnel are adequately trained to carry out their assigned information security-related duties and responsibilities.
No
3.2.3AT.L2-3.2.3Awareness and Training
1
Provide security awareness training on recognizing and reporting potential indicators of insider threat.
Yes
3.3.1AU.L2-3.3.1Audit and Accountability
5
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.
No
3.3.2AU.L2-3.3.2Audit and Accountability
3
Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions.
No
3.3.3AU.L2-3.3.3Audit and Accountability
1
Review and update logged events.
Yes
3.3.4AU.L2-3.3.4Audit and Accountability
1
Alert in the event of an audit logging process failure.
Yes
3.3.5AU.L2-3.3.5Audit and Accountability
5
Correlate audit record review, analysis, and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious, or unusual activity.
No
3.3.6AU.L2-3.3.6Audit and Accountability
1
Provide audit record reduction and report generation to support on-demand analysis and reporting.
Yes
3.3.7AU.L2-3.3.7Audit and Accountability
1
Provide a system capability that compares and synchronizes internal system clocks with an authoritative source to generate time stamps for audit records.
Yes
3.3.8AU.L2-3.3.8Audit and Accountability
1
Protect audit information and audit logging tools from unauthorized access, modification, and deletion.
Yes
3.3.9AU.L2-3.3.9Audit and Accountability
1
Limit management of audit logging functionality to a subset of privileged users.
Yes
3.4.1CM.L2-3.4.1Configuration Management
5
Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles.
No
3.4.2CM.L2-3.4.2Configuration Management
5
Establish and enforce security configuration settings for information technology products employed in organizational systems.
No
3.4.3CM.L2-3.4.3Configuration Management
1
Track, review, approve or disapprove, and log changes to organizational systems.
Yes
3.4.4CM.L2-3.4.4Configuration Management
1
Analyze the security impact of changes prior to implementation.
Yes
3.4.5CM.L2-3.4.5Configuration Management
5
Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems.
No
3.4.6CM.L2-3.4.6Configuration Management
5
Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities.
No
3.4.7CM.L2-3.4.7Configuration Management
5
Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.
No
3.4.8CM.L2-3.4.8Configuration Management
5
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.
No
3.4.9CM.L2-3.4.9Configuration Management
1
Control and monitor user-installed software.
Yes
3.5.1IA.L2-3.5.1Identification and Authentication
5
Identify system users, processes acting on behalf of users, and devices.
No
3.5.2IA.L2-3.5.2Identification and Authentication
5
Authenticate (or verify) the identities of users, processes, or devices, as a prerequisite to allowing access to organizational systems
No
3.5.3IA.L2-3.5.3Identification and Authentication
3 or 5
Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts.
No
3.5.4IA.L2-3.5.4Identification and Authentication
1
Employ replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts.
Yes
3.5.5IA.L2-3.5.5Identification and Authentication
1
Prevent reuse of identifiers for a defined period.
Yes
3.5.6IA.L2-3.5.6Identification and Authentication
1
Disable identifiers after a defined period of inactivity.
Yes
3.5.7IA.L2-3.5.7Identification and Authentication
1
Enforce a minimum password complexity and change of characters when new passwords are created.
Yes
3.5.8IA.L2-3.5.8Identification and Authentication
1
Prohibit password reuse for a specified number of generations.
Yes
3.5.9IA.L2-3.5.9Identification and Authentication
1
Allow temporary password use for system logons with an immediate change to a permanent password
Yes
3.5.10IA.L2-3.5.10Identification and Authentication
5
Store and transmit only cryptographically-protected passwords.
No
3.5.11IA.L2-3.5.11Identification and Authentication
1
Obscure feedback of authentication information.
Yes
3.6.1IR.L2-3.6.1Incident response
5
Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities.
No
3.6.2IR.L2-3.6.2Incident response
5
Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization.
No
3.6.3IR.L2-3.6.3Incident response
1
Test the organizational incident response capability.
Yes
3.7.1MA.L2-3.7.1Maintenance
3
Perform maintenance on organizational systems.
No
3.7.2MA.L2-3.7.2Maintenance
5
Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance.
No
3.7.3MA.L2-3.7.3Maintenance
1
Ensure equipment removed for off-site maintenance is sanitized of any CUI.
Yes
3.7.4MA.L2-3.7.4Maintenance
3
Check media containing diagnostic and test programs for malicious code before the media are used in organizational systems
No
3.7.5MA.L2-3.7.5Maintenance
5
Require multifactor authentication to establish nonlocal maintenance sessions via external network connections and terminate such connections when nonlocal maintenance is complete.
No
3.7.6MA.L2-3.7.6Maintenance
1
Supervise the maintenance activities of maintenance personnel without required access authorization.
Yes
3.8.1MP.L2-3.8.1Media Protection
3
Protect (i.e., physically control and securely store) system media containing CUI, both paper and digital.
No
3.8.2MP.L2-3.8.2Media Protection
3
Limit access to CUI on system media to authorized users.
No
3.8.3MP.L2-3.8.3Media Protection
5
Sanitize or destroy system media containing CUI before disposal or release for reuse.
No
3.8.4MP.L2-3.8.4Media Protection
1
Mark media with necessary CUI markings and distribution limitations.
Yes
3.8.5MP.L2-3.8.5Media Protection
1
Control access to media containing CUI and maintain accountability for media during transport outside of controlled areas.
Yes
3.8.6MP.L2-3.8.6Media Protection
1
Implement cryptographic mechanisms to protect the confidentiality of CUI stored on digital media during transport unless otherwise protected by alternative physical safeguards.
Yes
3.8.7MP.L2-3.8.7Media Protection
5
Control the use of removable media on system components.
No
3.8.8MP.L2-3.8.8Media Protection
3
Prohibit the use of portable storage devices when such devices have no identifiable owner.
No
3.8.9MP.L2-3.8.9Media Protection
1
Protect the confidentiality of backup CUI at storage locations.
Yes
3.9.1PS.L2-3.9.1Personnel Security
3
Screen individuals prior to authorizing access to organizational systems containing CUI.
No
3.9.2PS.L2-3.9.2Personnel Security
5
Ensure that organizational systems containing CUI are protected during and after personnel actions such as terminations and transfers.
No
3.10.1PE.L2-3.10.1Physical Protection
5
Limit physical access to organizational systems, equipment, and the respective operating environments to authorized individuals.
No
3.10.2PE.L2-3.10.2Physical Protection
5
Protect and monitor the physical facility and support infrastructure for organizational systems.
No
3.10.3PE.L2-3.10.3Physical Protection
1
Escort visitors and monitor visitor activity.
No
3.10.4PE.L2-3.10.4Physical Protection
1
Maintain audit logs of physical access.
No
3.10.5PE.L2-3.10.5Physical Protection
1
Control and manage physical access devices.
No
3.10.6PE.L2-3.10.6Physical Protection
1
Enforce safeguarding measures for CUI at alternate work sites.
Yes
3.11.1RA.L2-3.11.1Risk Assessment
3
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
No
3.11.2RA.L2-3.11.2Risk Assessment
5
Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified.
No
3.11.3RA.L2-3.11.3Risk Assessment
1
Remediate vulnerabilities in accordance with risk assessments.
Yes
3.12.1CA.L2-3.12.1Security Assessment
5
Periodically assess the security controls in organizational systems to determine if the controls are effective in their application.
No
3.12.2CA.L2-3.12.2Security Assessment
3
Develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems
No
3.12.3CA.L2-3.12.3Security Assessment
5
Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls.
No
3.12.4CA.L2-3.12.4Security Assessment
N/A
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
3.13.1SC.L2-3.13.1System and Communications Protection
5
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.
No
3.13.2SC.L2-3.13.2System and Communications Protection
5
Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.
No
3.13.3SC.L2-3.13.3System and Communications Protection
1
Separate user functionality from system management functionality.
Yes
3.13.4SC.L2-3.13.4System and Communications Protection
1
Prevent unauthorized and unintended information transfer via shared system resources.
Yes
3.13.5SC.L2-3.13.5System and Communications Protection
5
Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.
No
3.13.6SC.L2-3.13.6System and Communications Protection
5
Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception).
No
3.13.7SC.L2-3.13.7System and Communications Protection
1
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).
Yes
3.13.8SC.L2-3.13.8System and Communications Protection
3
Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards.
No
3.13.9SC.L2-3.13.9System and Communications Protection
1
Terminate network connections associated with communications sessions at the end of the sessions or after a defined period of inactivity.
Yes
3.13.10SC.L2-3.13.10System and Communications Protection
1
Establish and manage cryptographic keys for cryptography employed in organizational systems.
Yes
3.13.11SC.L2-3.13.11System and Communications Protection
3 or 5
Employ FIPS-validated cryptography when used to protect the confidentiality of CUI.
Conditional
3.13.12SC.L2-3.13.12System and Communications Protection
1
Yes
3.13.13SC.L2-3.13.13System and Communications Protection
1
Control and monitor the use of mobile code.
Yes
3.13.14SC.L2-3.13.14System and Communications Protection
1
Control and monitor the use of Voice over Internet Protocol (VoIP) technologies
Yes
3.13.15SC.L2-3.13.15System and Communications Protection
5
Protect the authenticity of communications sessions
No
3.13.16SC.L2-3.13.16System and Communications Protection
1
Protect the confidentiality of CUI at rest.
Yes
3.14.1SI.L2-3.14.1System and Information Integrity
5
Identify, report, and correct system flaws in a timely manner.
No
3.14.2SI.L2-3.14.2System and Information Integrity
5
Provide protection from malicious code at designated locations within organizational systems.
No
3.14.3SI.L2-3.14.3System and Information Integrity
5
Monitor system security alerts and advisories and take action in response.
No
3.14.4SI.L2-3.14.4System and Information Integrity
5
Update malicious code protection mechanisms when new releases are available.
No
3.14.5SI.L2-3.14.5System and Information Integrity
3
Perform periodic scans of organizational systems and real-time scans of files from external sources as files are downloaded, opened, or executed.
No
3.14.6SI.L2-3.14.6System and Information Integrity
5
Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks
No
3.14.7SI.L2-3.14.7System and Information Integrity
3
Identify unauthorized use of organizational systems.
No

Want to track your compliance across all 110 requirements, manage POA&Ms, and generate SPRS-ready records?

Sign in to track your compliance →