CMMC 2.0 access control (AC) practices
CMMC Level 2 applies the access control requirements of NIST SP 800-171 Rev. 2: limit system access to authorized users, processes and devices, separate duties, use least privilege, and log privileged functions (AC.L2-3.1.1 to 3.1.7). Assessors ask for account lists tied to authorized users, privileged account inventories and privileged-action logs; Autharva supports that evidence by mapping what every account and AI agent can reach and naming its owner.
Who it applies to: Defense contractors and subcontractors whose information systems process, store or transmit Federal Contract Information or Controlled Unclassified Information under DoD contracts that include CMMC requirements.
What the rule asks for
- AC.L2-3.1.1 (Level 1: AC.L1-b.1.i)Authorized access. Limit system access to authorized users, processes acting on behalf of authorized users, and devices, including other systems.
- AC.L2-3.1.2 (Level 1: AC.L1-b.1.ii)Transaction and function control. Limit system access to the types of transactions and functions that authorized users are permitted to execute.
- 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 least privilege, including for specific security functions and privileged accounts.
- AC.L2-3.1.6Non-privileged accounts. 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.
Dates that matter
- CMMC Program rule (32 CFR Part 170) takes effect.
- DFARS CMMC acquisition rule takes effect and Phase 1 begins: Level 1 and Level 2 self-assessments as a condition of award in applicable contracts.
- Phase 2 begins: DoD intends to require Level 2 certification by a C3PAO as a condition of award for applicable contracts.
- Phase 3 begins: Level 2 certification for all applicable contracts, including as a condition of exercising option periods, and Level 3 for applicable contracts.
Where access evidence usually falls short
- Shared and service accounts in the CUI environment are not tied to an authorized individual.
- Administrators use one account for daily work and privileged tasks, contrary to 3.1.6.
- Supplier, MSP and help-desk accounts keep access after the contract or task ends.
- Privileged functions are not captured in audit logs, so 3.1.7 cannot be shown as met.
- Role definitions do not show which duties are separated, leaving 3.1.4 without evidence.
How Autharva helps
- Assigns every shared login and service account to a person, with its real reach shown.
- Finds, scopes and closes help-desk, MSP and supplier access when the contract ends, with the owner's approval.
- Shows what every employee, contractor, service account, OAuth grant and AI agent can reach, including through the apps it administers and the keys it holds.
- Produces access-control evidence for CMMC from one record, alongside your existing IGA.
- Runs as a container in your data center or VPC, starts read-only, and is built to work without outbound internet access.
Autharva produces evidence that supports these controls. It does not by itself make an organization compliant; your auditor or examiner decides.
Evidence your examiner or auditor will ask for
- List of authorized users, processes and devices for systems in the CMMC assessment scope
- Role definitions showing permitted transactions and separated duties
- Privileged account inventory with separate non-privileged accounts for daily work
- Audit logs capturing execution of privileged functions
- Records of access removal for departed staff and ended supplier contracts
- System security plan sections describing access control implementation
Questions.
Which NIST revision does CMMC Level 2 use?+
32 CFR 170.14(c)(3) states that Level 2 requirements are identical to NIST SP 800-171 Rev. 2. NIST has since published Rev. 3, but the CMMC rule references Rev. 2.
Is CMMC in contracts now?+
Yes. Phase 1 began with the DFARS rule on November 10, 2025, and Phase 2, which adds Level 2 C3PAO certification for applicable contracts, began on November 10, 2026.
What is the difference between Level 1 and Level 2 access control?+
Level 1 covers the 15 safeguarding requirements in FAR 52.204-21(b)(1), including limiting access to authorized users and permitted transactions. Level 2 adds the full NIST SP 800-171 Rev. 2 set, including separation of duties, least privilege and privileged function controls.
Does Autharva make us CMMC certified?+
No. Certification comes from a self-assessment or a C3PAO or DIBCAC assessment. Autharva produces access-control evidence that supports it.
Sources
- eCFR, 32 CFR Part 170 Cybersecurity Maturity Model Certification (CMMC) Program, current as of 2026-11-09
- Federal Register, Cybersecurity Maturity Model Certification (CMMC) Program final rule (89 FR 83092), 2024-10-15
- Federal Register, DFARS: Assessing Contractor Implementation of Cybersecurity Requirements final rule (90 FR 43560), 2025-09-10
- NIST SP 800-171 Rev. 2, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, 2020-02
Summaries are in our own words for orientation, not legal advice. Read the official text and check with your counsel.
Have a requirement we haven't covered?
Describe your environment, a system you're unsure about, or an audit finding. An Autharva SME reads every message and replies by email.
- Answered by a person, not a script.
- Please don't include passwords, customer data or account numbers.
What can your identities really reach?
Find out before an attacker or an examiner does.