Skip to content
All CMMC practices
CMMC · Rev 2.13L1AC · Access Control

AC.L1-b.1.i

Authorized Access Control [FCI Data]

Requirement

Limit information system access to authorized users, processes acting on behalf of authorized users, or devices (including other information systems).

Assessment objectives

An assessor checks each lettered objective separately. The letters in brackets elsewhere on this page, such as [a] or [b,c], refer to these.

Determine if:

  1. aauthorized users are identified;
  2. bprocesses acting on behalf of authorized users are identified;
  3. cdevices (and other systems) authorized to connect to the system are identified;
  4. dsystem access is limited to authorized users;
  5. esystem access is limited to processes acting on behalf of authorized users; and
  6. fsystem access is limited to authorized devices (including other systems).

From the CMMC Level 1 Assessment Guide v2.13 · publisher approved 2026-10-31.

How to implement

Know exactly who and what may use the systems that handle Federal Contract Information (FCI), and make the systems enforce it. For a small shop that means one identity source (Microsoft 365, Google Workspace, or a local directory), named accounts for every person, an inventory of company devices, and nothing else allowed in. The same practice appears at Level 2 as AC.L2-3.1.1 for CUI.

The minimum for a small organization · Expert CMMC's reading, not official text

Know who and what may use the systems that hold FCI, and make those systems let in only them. At minimum: a current list of the people who need access [a], the service accounts and integrations that sign in on their own [b] and the company devices allowed to connect [c]; each person signs in with their own account, and anything not on the lists is disabled or blocked [d] [e] [f]. A spreadsheet and the user and device settings of the systems you already use are the usual way to do it.

Required outcome: what the requirement or its objectives call for. Recommended way: one common way to get there. Going further: worth doing, more than this practice asks.

  1. 1
    Required outcomeProcessIdentify the people authorized to use the systems that hold FCI: a list with each person's name, role and the systems they may use, updated when people join, change roles or leave.[a]
  2. 2
    Required outcomeProcessIdentify the processes that act for users (service accounts, scheduled tasks, integrations such as a backup agent or an accounting connector), each with an owner and what it may do. Disable any you cannot explain.[b]
  3. 3
    Required outcomeProcessIdentify the devices and other systems authorized to connect (laptops, desktops, phones, servers, printers), with enough to tell each one apart, such as the owner and a serial number or asset tag.[c]
  4. 4
    Required outcomeTechnicalLimit access to what is on those lists: accounts and devices are added only after the request is approved, every person signs in with their own account, accounts and service accounts not on the lists are disabled, and devices not on the device list cannot reach FCI systems.[d][e][f]

    You can tell it worked when an account or device that is not on your lists is refused, and the system's own user list matches yours.

  5. 5
    Recommended wayPolicyWrite a short access control policy (one or two pages): who approves accounts, that every user gets a named account, how service accounts and shared devices are approved, and that only company devices may reach FCI systems. It gives the assessor the rule behind your lists.[a][b][c]
  6. 6
    Recommended wayTechnicalEnforce the device list technically: enroll company devices in device management and allow sign-in to FCI systems only from enrolled devices (in Microsoft 365, Intune with a Conditional Access rule; in Google Workspace, endpoint management with context-aware access; check which plan includes it). A very small shop can reach the same outcome with company laptops only and no personal devices.[c][f]
  7. 7
    Recommended wayTechnicalWhere a sign-in rule requires a compliant device (Conditional Access with Intune), make sure only devices you manage can pass it: assign an Intune compliance policy for each platform you allow (Windows, macOS, iOS, Android); set 'Mark devices with no compliance policy assigned as' to Not compliant (Endpoint security > Device compliance > Compliance policy settings; Microsoft's default is Compliant, so a device with no policy passes); choose the compliance status validity period (default 30 days) and any grace period on the 'Mark device noncompliant' action on purpose; and pilot the rule on a small group, or in report-only mode, before enforcing it so nobody is locked out.[c][f]

    You can tell it worked when an enrolled device with no compliance policy assigned, and an unmanaged laptop, are both refused at sign-in to the FCI apps, while a pilot user's compliant device gets in.

  8. 8
    Recommended wayTechnicalTurn on multifactor authentication for every account. Level 1 does not require it, but it is built into Microsoft 365 and Google Workspace and it stops most stolen-password sign-ins.[d]
  9. 9
    Recommended wayProcessAdd a same-day disable step to your offboarding checklist, so a departed person's account is closed the day they leave.[d]
  10. 10
    Recommended wayProcessReview the user and device lists on a schedule you set (quarterly is common) and record the date, the reviewer and what was removed. Level 1 sets no frequency; a dated review is the easiest way to show the lists are kept current.[a][c]

Evidence to collect

Artifacts that show the practice is implemented and operating. Tags show which assessment objectives each one supports.

A process you started recently is shown honestly by its dated procedure, the first record it produced and the date it began. No evidence row needs more history than the process has existed, and the review periods shown are suggestions unless a guide page or regulation is named beside them.

The detail for 6 evidence items: how to produce each, how fresh it must be, what it must include and what it does not show.

Free with an account. Create a free account or sign in.

How assessors check

What an assessor examines, asks and tests: 3 notes.

Free with an account. Create a free account or sign in.

Tools and products

Named options a contractor can adopt, with an honest cost tier. The industry standard is listed even when it is expensive, alongside what is free and acceptable for a very small shop.

Microsoft 365 Business PremiumIdentity and device managementPaid
Google WorkspaceIdentity and device managementPaid
JumpCloudCloud directoryPaid
Okta Workforce IdentityIdentity providerPaid
Spreadsheet inventories (users, service accounts, devices)RecordsFree

53 dated vendor facts and notes on 5 products for this practice: what each assumes, what it does not cover and what stays yours.

Free with an account. Create a free account or sign in.

Editorial mentions, not endorsements. Pricing and tiers change; confirm with the vendor and check FedRAMP or GCC High availability where CUI is involved.

Common pitfalls

  • A shared 'frontdesk' or 'shop' login that several people use: there is no way to show who had access.
  • Forgetting devices: the practice covers devices and other systems, not just people. A printer or a vendor's laptop on the office Wi-Fi counts.
  • Leaving former employees enabled 'in case we need their mailbox'. Convert the mailbox to a shared mailbox and disable the account.
  • No dated review record. Assessors want to see that the list is maintained, not just that it exists.

Platform notes

  • Microsoft 365 (GCC / GCC High)
  • Google Workspace
  • On-premises or MSP-managed

Notes for 3 platforms.

Free with an account. Create a free account or sign in.

Related practices: AC.L1-b.1.ii, IA.L1-b.1.v, IA.L1-b.1.vi, AC.L2-3.1.1

Editorial implementation guidance published November 14, 2026. It is not part of the official requirement and does not replace the assessment guide.

Worked paths

Step-by-step recipes, organised by the job, that support this practice. A recipe supports the objectives shown; it does not by itself meet the practice.

The NIST requirements this practice is built on, what NIST made of each in the newer edition, and the SP 800-53 controls behind them, each from an official NIST or DoD table. Open any one to read it and see every CMMC practice it supports.

NIST SP 800-171 Rev 2

3.1.1

SP 800-171 Rev 3

03.01.01

SP 800-53 Rev 4

AC-2AC-3AC-17

SP 800-53 Rev 5

AC-2DSAC-2(3)SAC-2(5)SAC-2(13)SAC-3DAC-17D
How these were reached
  • AC-2 · Account Management
    • D SP 800-171 Rev 2 Appendix D → SP 800-53 Rev 4 control → NIST's Rev 4 → Rev 5 comparison · via 800-53 Rev 4 AC-2 → 800-53 Rev 5 AC-2
    • S source control of the SP 800-171 Rev 3 or SP 800-172 Rev 3 requirement (NIST OSCAL) · via 800-171 Rev 3 03.01.01 → 800-53 Rev 5 AC-2NIST: 03.01.01 also: 3.13.3 addressed by; SP 800-172 (Feb 2021) 3.9.2e addressed by (SP 800-171 Rev 3)
  • AC-2(3) · Account Management | Disable Accounts
    • S source control of the SP 800-171 Rev 3 or SP 800-172 Rev 3 requirement (NIST OSCAL) · via 800-171 Rev 3 03.01.01 → 800-53 Rev 5 AC-2(3)NIST: 03.01.01 also: 3.13.3 addressed by; SP 800-172 (Feb 2021) 3.9.2e addressed by (SP 800-171 Rev 3)
  • AC-2(5) · Account Management | Inactivity Logout
    • S source control of the SP 800-171 Rev 3 or SP 800-172 Rev 3 requirement (NIST OSCAL) · via 800-171 Rev 3 03.01.01 → 800-53 Rev 5 AC-2(5)NIST: 03.01.01 also: 3.13.3 addressed by; SP 800-172 (Feb 2021) 3.9.2e addressed by (SP 800-171 Rev 3)
  • AC-2(13) · Account Management | Disable Accounts for High-risk Individuals
    • S source control of the SP 800-171 Rev 3 or SP 800-172 Rev 3 requirement (NIST OSCAL) · via 800-171 Rev 3 03.01.01 → 800-53 Rev 5 AC-2(13)NIST: 03.01.01 also: 3.13.3 addressed by; SP 800-172 (Feb 2021) 3.9.2e addressed by (SP 800-171 Rev 3)
  • AC-3 · Access Enforcement
    • D SP 800-171 Rev 2 Appendix D → SP 800-53 Rev 4 control → NIST's Rev 4 → Rev 5 comparison · via 800-53 Rev 4 AC-3 → 800-53 Rev 5 AC-3
  • AC-17 · Remote Access
    • D SP 800-171 Rev 2 Appendix D → SP 800-53 Rev 4 control → NIST's Rev 4 → Rev 5 comparison · via 800-53 Rev 4 AC-17 → 800-53 Rev 5 AC-17

Rev 5 paths: D SP 800-171 Rev 2 Appendix D → SP 800-53 Rev 4 control → NIST's Rev 4 → Rev 5 comparison; S source control of the SP 800-171 Rev 3 or SP 800-172 Rev 3 requirement (NIST OSCAL); C SP 800-172 (Feb 2021) Appendix C. NIST also names this Rev 3 requirement as the successor of other withdrawn requirements: open “How these were reached” under the Rev 5 controls for which, in NIST's words.

Where each link comes from (12 links from 5 official documents)

CMMC Assessment Guide Level 1 v2.13 DoD CIO

NIST SP 800-171 Rev 2 → Rev 3 change analysis NIST

  • 3.1.1 → 03.01.01“Significant Change”sheet "Change Analysis 800-171 R2-R3" row 2

NIST SP 800-171 Rev 2 NIST

  • 3.1.1 → AC-2“Appendix D mapping”p.75 Table D-1
  • 3.1.1 → AC-3“Appendix D mapping”p.75 Table D-1
  • 3.1.1 → AC-17“Appendix D mapping”p.75 Table D-1

NIST SP 800-53 Rev 4 → Rev 5 comparison NIST

  • AC-2 → AC-2“Removes parameter Adds parameter Changes discussion”sheet "Rev4 Rev5 Compared" row 4
  • AC-3 → AC-3“Changes discussion”sheet "Rev4 Rev5 Compared" row 18
  • AC-17 → AC-17“Changes control text Changes discussion”sheet "Rev4 Rev5 Compared" row 112

NIST SP 800-171 Rev 3 (OSCAL) NIST

  • 03.01.01 → AC-2“Source control”control 03.01.01 link rel=reference (AC-02)
  • 03.01.01 → AC-2(3)“Source control”control 03.01.01 link rel=reference (AC-02(03))
  • 03.01.01 → AC-2(5)“Source control”control 03.01.01 link rel=reference (AC-02(05))
  • 03.01.01 → AC-2(13)“Source control”control 03.01.01 link rel=reference (AC-02(13))

Trace notes

Notes marked NIST state what the owners' own files say. Notes marked Expert CMMC note are our reading of the links, not official guidance. Neither is a crosswalk link.

About this practice

  • Expert CMMC note

    Appendix D maps 3.1.1 and 3.1.2 together to AC-2, AC-3 and AC-17. AC-2 is the direct source for 3.1.1; AC-3 mainly supports 3.1.2; AC-17 (remote access) is general support, with the specific remote-access requirements in 3.1.12-3.1.15.

    Relies on: NIST SP 800-171 Rev 2, Appendix D, Table D-1

  • Expert CMMC note

    Rev 3 03.01.01 adds account lifecycle, monitoring, disabling and inactivity-logout duties (AC-2(3), AC-2(5), AC-2(13)) that 800-171r2 3.1.1 did not state explicitly. Level 1 (FAR 52.204-21) does not require them.

    Relies on: NIST SP 800-171 Rev 2; NIST SP 800-171 Rev 3; FAR 52.204-21

About SP 800-171 Rev 2 3.1.1

  • Expert CMMC note3.1.1 ↔ AC-17 (SP 800-53 Rev 4)

    NIST SP 800-171 Rev 2 Appendix D maps basic requirements 3.1.1 and 3.1.2 jointly to AC-2, AC-3, AC-17. AC-17 mainly supports the group as a whole, not 3.1.1 specifically.

    Relies on: NIST SP 800-171 Rev 2, p.75, Appendix D, Table D-1

About SP 800-171 Rev 3 03.01.01

  • NIST

    NIST's own files disagree on the Rev 3 requirement carrying AC-2(5). NIST SP 800-171 Rev 3 CUI overlay, sheet "CUI Overlay" row 46: AC-2(5) is CUI with no Rev 3 requirement given. NIST SP 800-171 Rev 3 (OSCAL), control 03.01.01 link rel=reference (AC-02(05)): 03.01.01 references AC-2(5).

    Sources: NIST SP 800-171 Rev 3 CUI overlay, sheet "CUI Overlay" row 46; NIST SP 800-171 Rev 3 (OSCAL), control 03.01.01 link rel=reference (AC-02(05))

  • Expert CMMC note

    The crosswalk follows 03.01.01 for AC-2(5), where the publication and NIST's OSCAL agree; the overlay cell is empty. (Precedence: the publication of record over OSCAL over supplemental workbooks.)

    Relies on: NIST SP 800-171 Rev 3 CUI overlay; NIST SP 800-171 Rev 3 (OSCAL)

Further discussion

Identify users, processes, and devices that are allowed to use company computers and can log on to the company network. Automated updates and other automatic processes should be associated with the user who initiated (authorized) the process. Limit the devices (e.g., printers) that can be accessed by company computers. Set up your system so that only authorized users, processes, and devices can access the company network. This requirement, AC.L1-b.1.i, controls system access based on user, process, or device identity. AC.L1-b.1.i leverages IA.L1-b.1.v which provides a vetted and trusted identity for access control. Example 1 Your company maintains a list of all personnel authorized to use company information systems [a]. This list is used to support identification and authentication activities conducted by IT when authorizing access to systems [a,d]. Example 2 A coworker wants to buy a new multi-function printer/scanner/fax device and make it available on the company network. You explain that the company controls system and device access to the network, and will prevent network access by unauthorized systems and devices [c]. You help the coworker submit a ticket that asks for the printer to be granted access to the network, and appropriate leadership approves the device [f]. Potential Assessment Considerations • Is a list of authorized users maintained that defines their identities and roles [a]? • Are account requests authorized before system access is granted [d,e,f]?

Practice guide notes

Implementation guidance

Editorial examples to help you plan. Adapt them to your environment; the official requirement and objectives remain authoritative.

In plain language

Keep an approved list of people, automated processes, and devices that can access the system, and enforce it.

Implementation example

Example from the source assessment guide (not a mandatory implementation): Your company maintains a list of all personnel authorized to use company information systems [a]. This list is used to support identification and authentication activities conducted by IT when authorizing access to systems [a,d]. Example 2 A coworker wants to buy a new multi- function printer/scanner/fax device and make it available on the company network. You explain that the company controls system and device access to the network, and will prevent network access by unauthorized systems and devices [c]. You help the coworker submit a ticket that asks for the printer to be granted access to the network, and appropriate leadership approves the device [f].

Evidence examples

Examples suggested by the source guide (not an exhaustive or mandatory checklist): Access control policy; procedures addressing account management; system security plan45; system design documentation; system configuration settings and associated documentation; list of active system accounts and the name of the individual associated with each account; notifications or records of recently transferred, separated, or terminated employees; list of conditions for group and role membership; list of recently disabled system accounts along with the name of the individual associated with each account; access authorization records; account management compliance reviews; system monitoring records; system audit logs and records; list of devices and systems authorized to connect to organizational systems; other relevant documents or records

Common mistakes

Listing employees but overlooking service accounts, connected devices, or prompt removal of access.

Track this in a workspace

The compliance workspace tracks each objective, its evidence and the tasks to close gaps. It is open to invited contractors while in pilot: request access below.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Source: DoD CIO · https://dodcio.defense.gov/CMMC/