Study guide
6.1 Access Control (AC) Domain: 22 Practices & Core Implementation
CMMC Certified CMMC Professional CCP
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction & Exam Logistics
1.1 Exam Structure, Current Logistics & Official Blueprint 1.2 Eligibility, Training, Retakes & Certification Maintenance 1.3 Study Strategy, Blueprint Mapping & Authoritative Sources
2 Chapter 2: The CMMC Ecosystem & Stakeholder Roles
2.1 Governance & Oversight: DoD, DIBCAC, Cyber AB & ISACA 2.2 Industry Roles: C3PAOs, OSCs, Consultants, ATPs & APPs 2.3 Assessor Roles: CCP, CCA, Lead CCA, QA & Certifying Official
3 Chapter 3: Code of Professional Conduct & Ethics
3.1 Applying the CMMC Code of Professional Conduct 3.2 Conflicts of Interest, Independence & Consulting vs Assessment Boundaries 3.3 Confidentiality, Incident Escalation & Misconduct Reporting
4 Chapter 4: Legal Authorities, Federal Rules & Standards
4.1 FCI vs CUI: Statutory Foundations, E.O. 13556 & 32 CFR Part 2002 4.2 FAR, DFARS & 32 CFR Part 170 4.3 NIST Standards Hierarchy: SP 800-171, SP 800-171A & SP 800-172
5 Chapter 5: CMMC Model Architecture & Maturity Levels
5.1 CMMC Three-Level Architecture, Assessment Types & Affirmation 5.2 Level 1: 15 FAR Safeguarding Requirements & Annual Self-Assessment 5.3 Level 2 & Level 3: CUI Protection and Assessment Authority
6 Chapter 6: CMMC Domains: Access Control, Identity & Boundary Defense
6.1 Access Control (AC) Domain: 22 Practices & Core Implementation 6.2 Identification & Authentication (IA) Domain: MFA & Credential Management 6.3 System & Communications Protection (SC) Domain: Boundary Defense & Cryptography
7 Chapter 7: CMMC Domains: Audit, Configuration, Maintenance & Media
7.1 Audit & Accountability (AU) Domain: Logging, Review & Non-Repudiation 7.2 Configuration Management (CM) Domain: Baselines, Changes & Least Functionality 7.3 Maintenance (MA) & Media Protection (MP) Domains: Sanitization & Tool Control
8 Chapter 8: CMMC Domains: People, Physical, Incident Response & Integrity
8.1 Awareness & Training (AT) & Personnel Security (PS) Domains: Screening & Training 8.2 Physical Protection (PE): Level 1 FAR Requirements & Level 2 Mapping 8.3 Incident Response (IR), System Integrity (SI) & Risk Assessment (RA/CA) Domains
9 Chapter 9: CMMC Scoping Methodology & Boundary Definition
9.1 Scoping Fundamentals: Organizational Scope, Level 1 & Level 2 9.2 The 5 Asset Categories: CUI, SPA, CRMA, Specialized & Out-of-Scope 9.3 Boundary Definition, Data Flow Diagrams & Secure Enclave Isolation
10 Chapter 10: Cloud Service Providers, ESPs & Supply Chain Flowdown
10.1 Cloud Service Providers (CSPs): FedRAMP Moderate Equivalency & DFARS 7012 10.2 External Service Providers (ESPs/MSPs/MSSPs) & Shared Responsibility Matrices 10.3 Subcontractor Flow-Down, Supply Chain Governance & SPRS Scoring
11 Chapter 11: CMMC Assessment Process (CAP): Planning & Evidence Gathering
11.1 CAP Preliminary Proceedings & Phase 1 Pre-Assessment 11.2 CAP Phase 2: Assess Conformity to Security Requirements 11.3 Assessment Objectives, Evidence Sufficiency & Limited Correction
12 Chapter 12: CMMC Assessment Process (CAP): Reporting, POA&M & Closeout
12.1 CAP Phase 3: Complete and Report Assessment Results 12.2 Level 2 POA&M Rules, Exclusions & 180-Day Closeout 12.3 CAP Phase 4: Certificate Issuance & POA&M Closeout
6.1 Access Control (AC) Domain: 22 Practices & Core Implementation
Key Takeaways Explain This Topic AI
Access Control contains 22 Level 2 requirements; four of them—3.1.1, 3.1.2, 3.1.20, and 3.1.22—also map to Level 1 FCI safeguarding requirements.
Core decisions cover authorized users, permitted functions, CUI flow, separation of duties, least privilege, privileged-function control, logon limits, notices, session lock, and session termination.
Remote-access requirements 3.1.12 through 3.1.15 separately address monitoring/control, cryptographic protection, managed access points, and authorization of privileged commands or security-relevant information.
Wireless and mobile requirements authorize connections, require authentication and encryption, control mobile-device connections, and encrypt CUI on mobile devices without prescribing one vendor or management product.
External systems, portable storage, and public posting require verified authorization and controlled use; implementation evidence must satisfy every applicable objective rather than a generic policy statement.
Last updated: August 2026
Access Control: Users, Functions, Remote Access & External Systems
Access Control is the largest NIST SP 800-171 Revision 2 family, with 22 Level 2 requirements . Four—3.1.1, 3.1.2, 3.1.20, and 3.1.22—also correspond to CMMC Level 1 safeguarding requirements. The remaining 18 are additional at Level 2; Level 2 still evaluates all 22.
Authorization and CUI flow
Requirements 3.1.1 and 3.1.2 ask who or what may access the system and which transactions or functions each authorized identity may perform. Evidence can include identity stores, account approvals, roles, device controls, application permissions, and tests using representative accounts. A current roster alone does not prove that configured access matches approval.
Requirement 3.1.3 controls CUI flow according to approved authorizations. It can apply inside the system and across connected systems. Mechanisms may include routing, gateways, labels, data-loss controls, application rules, or manual release procedures, but CMMC does not mandate one product.
Requirements 3.1.4–3.1.7 cover separation of duties, least privilege, use of nonprivileged accounts or roles for nonsecurity functions, and preventing nonprivileged users from executing privileged functions while capturing privileged execution in audit logs. Separation is risk-based; it does not mean every task always needs two people. A privileged administrator must still use an appropriate nonprivileged context for ordinary work.
Logon and session behavior
Requirement 3.1.8 limits unsuccessful logon attempts. The organization defines values and implements a mechanism such as lockout, delay, or another effective limit. The requirement does not publish a universal number of attempts or lockout duration.
Requirement 3.1.9 provides privacy and security notices consistent with applicable CUI rules. 3.1.10 uses a session lock with a pattern-hiding display after inactivity, while 3.1.11 automatically terminates a user session after an organization-defined condition. Lock and termination are different outcomes and can have different triggers.
Remote access: keep the numbers straight
Requirement Decision
3.1.12 Monitor and control remote-access sessions.
3.1.13 Use cryptographic mechanisms to protect confidentiality of remote-access sessions.
3.1.14 Route remote access through managed access-control points.
3.1.15 Authorize remote execution of privileged commands and remote access to security-relevant information.
These requirements do not say that 3.1.12 is “cryptographic authorization” or that 3.1.13 is the managed-gateway rule. A VPN, zero-trust gateway, bastion, or other architecture may implement several objectives, but the team traces each objective to the actual mechanism, authorization, activity, and person.
For 3.1.15, privileged remote actions and access to security-relevant information must be authorized. The requirement does not prohibit every privileged command; it demands controlled authorization tied to legitimate need.
Wireless and mobile devices
Requirement 3.1.16 authorizes wireless access before connection, and 3.1.17 protects wireless using authentication and encryption. The organization identifies the wireless technologies and demonstrates authorized configurations. WPA enterprise modes are common implementations, but the objective is not a vendor checklist.
Requirement 3.1.18 controls connections of mobile devices. 3.1.19 encrypts CUI on mobile devices and mobile computing platforms. Device inventory, connection approval, configured protection, key handling, and a representative test can support the objectives. Mobile-device management may be useful, but the requirement does not prescribe a specific MDM product or demand one architecture for every device.
Where cryptography protects CUI, 3.13.11 separately requires FIPS-validated cryptography. The team verifies the deployed module and validated conditions rather than accepting “AES-256” as sufficient.
External systems, portable storage, and public information
Requirement 3.1.20 verifies and controls or limits connections to, and use of, external systems. 3.1.21 limits use of portable storage devices on external systems. Policies must connect to enforcement and to the actual external systems used by personnel.
Requirement 3.1.22 controls CUI posted or processed on publicly accessible systems. The organization identifies authorized posters, reviews content before posting, and removes CUI discovered on a public system. It does not mean every public website belongs inside the CUI boundary; scope follows the system’s actual capability and relationship.
Evidence sequence
For an Access Control scenario:
Identify the user, process, device, data, function, and connection.
Select the exact requirement and its 800-171A objectives.
Examine approvals, policy, roles, configuration, and records.
Interview the personnel who authorize and administer access.
Test representative access or denial where appropriate.
Confirm the evidence covers the focused sample and current scope.
Suppose policy says terminated users are removed immediately, but a sampled account remains active. The policy supports intent; the directory and test show operation. The relevant objectives are not satisfied merely because the written rule is strong.