All 110 CMMC Level 2 requirements
Every NIST SP 800-171 requirement, with its own plain-English page: the objectives an assessor scores, how a C3PAO examines, interviews, and tests it, its point value, and whether it can go on a POA&M. Built from the official CMMC Assessment Guide Level 2 (v2.13).
Last updated July 5, 2026~6 minute readPrimary sources cited
110
Requirements, one page each
320
Assessment objectives
14
Requirement families
1 / 3 / 5
Point weights per requirement
5 pt3 pt1 pt✕ = cannot POA&M
- 3.1.1Authorized Access ControlLimit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems).5 pt✕ POA&M
- 3.1.2Transaction & Function ControlLimit system access to the types of transactions and functions that authorized users are permitted to execute.5 pt✕ POA&M
- 3.1.3Control CUI FlowControl the flow of CUI in accordance with approved authorizations.1 pt
- 3.1.4Separation Of DutiesSeparate the duties of individuals to reduce the risk of malevolent activity without collusion.1 pt
- 3.1.5Least PrivilegeEmploy the principle of least privilege, including for specific security functions and privileged accounts.3 pt✕ POA&M
- 3.1.6Non-privileged Account UseUse non-privileged accounts or roles when accessing nonsecurity functions.1 pt
- 3.1.7Privileged FunctionsPrevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs.1 pt
- 3.1.8Unsuccessful Logon AttemptsLimit unsuccessful logon attempts.1 pt
- 3.1.9Privacy & Security NoticesProvide privacy and security notices consistent with applicable CUI rules.1 pt
- 3.1.10Session LockUse session lock with pattern-hiding displays to prevent access and viewing of data after a period of inactivity.1 pt
- 3.1.11Session TerminationTerminate (automatically) a user session after a defined condition.1 pt
- 3.1.12Control Remote AccessMonitor and control remote access sessions.5 pt✕ POA&M
- 3.1.13Remote Access ConfidentialityEmploy cryptographic mechanisms to protect the confidentiality of remote access sessions.5 pt✕ POA&M
- 3.1.14Remote Access RoutingRoute remote access via managed access control points.1 pt
- 3.1.15Privileged Remote AccessAuthorize remote execution of privileged commands and remote access to security-relevant information.1 pt
- 3.1.16Wireless Access AuthorizationAuthorize wireless access prior to allowing such connections.5 pt✕ POA&M
- 3.1.17Wireless Access ProtectionProtect wireless access using authentication and encryption.5 pt✕ POA&M
- 3.1.18Mobile Device ConnectionControl connection of mobile devices.5 pt✕ POA&M
- 3.1.19Encrypt CUI On MobileEncrypt CUI on mobile devices and mobile computing platforms.3 pt✕ POA&M
- 3.1.20External ConnectionsVerify and control/limit connections to and use of external systems.1 pt✕ POA&M
- 3.1.21Portable Storage UseLimit use of portable storage devices on external systems.1 pt
- 3.1.22Control Public InformationControl CUI posted or processed on publicly accessible systems.1 pt✕ POA&M
- 3.2.1Role-based Risk AwarenessEnsure 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.5 pt✕ POA&M
- 3.2.2Role-based TrainingEnsure that personnel are trained to carry out their assigned information security-related duties and responsibilities.5 pt✕ POA&M
- 3.2.3Insider Threat AwarenessProvide security awareness training on recognizing and reporting potential indicators of insider threat.1 pt
- 3.3.1System AuditingCreate 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.5 pt✕ POA&M
- 3.3.2User AccountabilityEnsure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions.3 pt✕ POA&M
- 3.3.3Event ReviewReview and update logged events.1 pt
- 3.3.4Audit Failure AlertingAlert in the event of an audit logging process failure.1 pt
- 3.3.5Audit CorrelationCorrelate audit record review, analysis, and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious, or unusual activity.5 pt✕ POA&M
- 3.3.6Reduction & ReportingProvide audit record reduction and report generation to support on-demand analysis and reporting.1 pt
- 3.3.7Authoritative Time SourceProvide a system capability that compares and synchronizes internal system clocks with an authoritative source to generate time stamps for audit records.1 pt
- 3.3.8Audit ProtectionProtect audit information and audit logging tools from unauthorized access, modification, and deletion.1 pt
- 3.3.9Audit ManagementLimit management of audit logging functionality to a subset of privileged users.1 pt
- 3.4.1System BaseliningEstablish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles.5 pt✕ POA&M
- 3.4.2Security Configuration EnforcementEstablish and enforce security configuration settings for information technology products employed in organizational systems.5 pt✕ POA&M
- 3.4.3System Change ManagementTrack, review, approve or disapprove, and log changes to organizational systems.1 pt
- 3.4.4Security Impact AnalysisAnalyze the security impact of changes prior to implementation.1 pt
- 3.4.5Access Restrictions For ChangeDefine, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems.5 pt✕ POA&M
- 3.4.6Least FunctionalityEmploy the principle of least functionality by configuring organizational systems to provide only essential capabilities.5 pt✕ POA&M
- 3.4.7Nonessential FunctionalityRestrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.5 pt✕ POA&M
- 3.4.8Application Execution PolicyApply 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.5 pt✕ POA&M
- 3.4.9User-installed SoftwareControl and monitor user-installed software.1 pt
- 3.5.1IdentificationIdentify system users, processes acting on behalf of users, and devices.5 pt✕ POA&M
- 3.5.2AuthenticationAuthenticate (or verify) the identities of users, processes, or devices, as a prerequisite to allowing access to organizational systems.5 pt✕ POA&M
- 3.5.3Multifactor AuthenticationUse multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts.5 pt✕ POA&M
- 3.5.4Replay-resistant AuthenticationEmploy replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts.1 pt
- 3.5.5Identifier ReusePrevent reuse of identifiers for a defined period.1 pt
- 3.5.6Identifier HandlingDisable identifiers after a defined period of inactivity.1 pt
- 3.5.7Password ComplexityEnforce a minimum password complexity and change of characters when new passwords are created.1 pt
- 3.5.8Password ReuseProhibit password reuse for a specified number of generations.1 pt
- 3.5.9Temporary PasswordsAllow temporary password use for system logons with an immediate change to a permanent password.1 pt
- 3.5.10Cryptographically-protected PasswordsStore and transmit only cryptographically-protected passwords.5 pt✕ POA&M
- 3.5.11Obscure FeedbackObscure feedback of authentication information.1 pt
- 3.6.1Incident HandlingEstablish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities.5 pt✕ POA&M
- 3.6.2Incident ReportingTrack, document, and report incidents to designated officials and/or authorities both internal and external to the organization.5 pt✕ POA&M
- 3.6.3Incident Response TestingTest the organizational incident response capability.1 pt
- 3.7.1Perform MaintenancePerform maintenance on organizational systems.3 pt✕ POA&M
- 3.7.2System Maintenance ControlProvide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance.5 pt✕ POA&M
- 3.7.3Equipment SanitizationEnsure equipment removed for off-site maintenance is sanitized of any CUI.1 pt
- 3.7.4Media InspectionCheck media containing diagnostic and test programs for malicious code before the media are used in organizational systems.3 pt✕ POA&M
- 3.7.5Nonlocal MaintenanceRequire multifactor authentication to establish nonlocal maintenance sessions via external network connections and terminate such connections when nonlocal maintenance is complete.5 pt✕ POA&M
- 3.7.6Maintenance PersonnelSupervise the maintenance activities of maintenance personnel without required access authorization.1 pt
- 3.8.1Media ProtectionProtect (i.e., physically control and securely store) system media containing CUI, both paper and digital.3 pt✕ POA&M
- 3.8.2Media AccessLimit access to CUI on system media to authorized users.3 pt✕ POA&M
- 3.8.3Media DisposalSanitize or destroy system media containing CUI before disposal or release for reuse.5 pt✕ POA&M
- 3.8.4Media MarkingsMark media with necessary CUI markings and distribution limitations.1 pt
- 3.8.5Media AccountabilityControl access to media containing CUI and maintain accountability for media during transport outside of controlled areas.1 pt
- 3.8.6Portable Storage EncryptionImplement cryptographic mechanisms to protect the confidentiality of CUI stored on digital media during transport unless otherwise protected by alternative physical safeguards.1 pt
- 3.8.7Removeable MediaControl the use of removable media on system components.5 pt✕ POA&M
- 3.8.8Shared MediaProhibit the use of portable storage devices when such devices have no identifiable owner.3 pt✕ POA&M
- 3.8.9Protect BackupsProtect the confidentiality of backup CUI at storage locations.1 pt
- 3.10.1Limit Physical AccessLimit physical access to organizational systems, equipment, and the respective operating environments to authorized individuals.5 pt✕ POA&M
- 3.10.2Monitor FacilityProtect and monitor the physical facility and support infrastructure for organizational systems.5 pt✕ POA&M
- 3.10.3Escort VisitorsEscort visitors and monitor visitor activity.1 pt✕ POA&M
- 3.10.4Physical Access LogsMaintain audit logs of physical access.1 pt✕ POA&M
- 3.10.5Manage Physical AccessControl and manage physical access devices.1 pt✕ POA&M
- 3.10.6Alternative Work SitesEnforce safeguarding measures for CUI at alternate work sites.1 pt
- 3.11.1Risk AssessmentsPeriodically 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.3 pt✕ POA&M
- 3.11.2Vulnerability ScanScan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified.5 pt✕ POA&M
- 3.11.3Vulnerability RemediationRemediate vulnerabilities in accordance with risk assessments.1 pt
- 3.12.1Security Control AssessmentPeriodically assess the security controls in organizational systems to determine if the controls are effective in their application.5 pt✕ POA&M
- 3.12.2Operational Plan Of ActionDevelop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems.3 pt✕ POA&M
- 3.12.3Security Control MonitoringMonitor security controls on an ongoing basis to ensure the continued effectiveness of the controls.5 pt✕ POA&M
- 3.12.4System Security PlanDevelop, 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.✕ POA&M
- 3.13.1Boundary ProtectionMonitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems.5 pt✕ POA&M
- 3.13.2Security EngineeringEmploy architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.5 pt✕ POA&M
- 3.13.3Role SeparationSeparate user functionality from system management functionality.1 pt
- 3.13.4Shared Resource ControlPrevent unauthorized and unintended information transfer via shared system resources.1 pt
- 3.13.5Public-access System SeparationImplement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.5 pt✕ POA&M
- 3.13.6Network Communication By ExceptionDeny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception).5 pt✕ POA&M
- 3.13.7Split TunnelingPrevent 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).1 pt
- 3.13.8Data In TransitImplement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards.3 pt✕ POA&M
- 3.13.9Connections TerminationTerminate network connections associated with communications sessions at the end of the sessions or after a defined period of inactivity.1 pt
- 3.13.10Key ManagementEstablish and manage cryptographic keys for cryptography employed in organizational systems.1 pt
- 3.13.11CUI EncryptionEmploy FIPS-validated cryptography when used to protect the confidentiality of CUI.5 pt✕ POA&M
- 3.13.12Collaborative Device ControlProhibit remote activation of collaborative computing devices and provide indication of devices in use to users present at the device.1 pt
- 3.13.13Mobile CodeControl and monitor the use of mobile code.1 pt
- 3.13.14Voice Over Internet ProtocolControl and monitor the use of Voice over Internet Protocol (VoIP) technologies.1 pt
- 3.13.15Communications AuthenticityProtect the authenticity of communications sessions.5 pt✕ POA&M
- 3.13.16Data At RestProtect the confidentiality of CUI at rest.1 pt
- 3.14.1Flaw RemediationIdentify, report, and correct system flaws in a timely manner.5 pt✕ POA&M
- 3.14.2Malicious Code ProtectionProvide protection from malicious code at designated locations within organizational systems.5 pt✕ POA&M
- 3.14.3Security Alerts & AdvisoriesMonitor system security alerts and advisories and take action in response.5 pt✕ POA&M
- 3.14.4Update Malicious Code ProtectionUpdate malicious code protection mechanisms when new releases are available.5 pt✕ POA&M
- 3.14.5System & File ScanningPerform periodic scans of organizational systems and real-time scans of files from external sources as files are downloaded, opened, or executed.3 pt✕ POA&M
- 3.14.6Monitor Communications For AttacksMonitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks.5 pt✕ POA&M
- 3.14.7Identify Unauthorized UseIdentify unauthorized use of organizational systems.3 pt✕ POA&M
Prove all 110, with an officer alongside you
The Level 2 workspace walks all 110 requirements with you at the objective level, generates your SSP, POA&M, and Audit Room from real evidence, gives your assessor a read only seat, and puts a Registered Practitioner alongside you year round.
No credit card, and Level 1 and Level 2 are both open, so sign up for the level your contracts call for. Self assessment and self attestation are law today, DFARS 252.204-7012 is unaffected, and the NIST SP 800-171 Rev 2 baseline is unchanged, so the Level 2 work counts either way.
Questions, answered
What are the CMMC Level 2 requirements?+
CMMC Level 2 is the 110 security requirements of NIST SP 800-171 Revision 2, organized into 14 families from Access Control to System and Information Integrity, and assessed against 320 objectives in NIST SP 800-171A. Every requirement has its own page here.
How many families does CMMC Level 2 have?+
14 families: Access Control, Awareness and Training, Audit and Accountability, Configuration Management, Identification and Authentication, Incident Response, Maintenance, Media Protection, Personnel Security, Physical Protection, Risk Assessment, Security Assessment, System and Communications Protection, and System and Information Integrity.
Are all 110 requirements weighted the same?+
No. Under 32 CFR 170.24 each requirement is worth 1, 3, or 5 points against a maximum of 110. Higher-risk requirements cost more, and a short set can never be placed on a POA&M. Each requirement page shows its exact weight and eligibility.
Source: NIST SP 800-171 r2 · NIST SP 800-171A · CMMC Assessment Guide Level 2 v2.13 (DoD-CIO-00003) · 32 CFR § 170.24.