NIST SP 800-53 Rev. 5 AC-4(22) — Access Only

What this control requires

Organizations must provide access from a single device to computing platforms, applications, or data residing in multiple security domains, while preventing information flow between these domains. This ensures that users can access information from different domains without mechanisms that allow data transfer between them. This control supports the Governance capability within the Access Control family.

In plain English

Organizations must provide access from a single device to computing platforms, applications, or data residing in multiple security domains, while preventing information flow between these domains. In practice, this means you can prove you access management-level controls on a defined cadence.

Why it matters

SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed.

This control is rated critical in the source catalogue. Treat gaps here as production incidents in the risk register, not housekeeping.

What an auditor looks for

A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan.

Within Access Control, the assessor will trace your implementation back to the catalogue reference (Control AC-4(22)) and look for objective evidence on the latest two assessment cycles.

How to implement

Endpoint Protection

MDM. Make MDM enrollment a hard gate for device access (Intune compliance + Conditional Access, or Jamf + Okta device trust). Unmanaged devices simply don't get a session token.

EDR. Deploy CrowdStrike / SentinelOne / Defender for Endpoint to every server and laptop; alert on any host that stops sending telemetry for >24h.

Operational checklist

• Access. Document the trigger, the owner and the cadence.
• Information. Document the trigger, the owner and the cadence.
• Security. Document the trigger, the owner and the cadence.
• Data. Document the trigger, the owner and the cadence.
• Review. Document the trigger, the owner and the cadence.
• Scope: management, access control, information, domains, only, protection, identity, review.

Evidence to collect

• Identity Scan. IAM / IdP exports — Entra ID, Okta, IAM Identity Center, Workspace directory — showing accounts, roles, MFA state and last sign-in.

Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Focus: Access Only.

Common pitfalls

• Pilot MDM rollouts that quietly exclude executives or engineers; carving out the highest-risk users is the most common audit failure.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

• NIST SP 800-171 Rev. 3 3.1.11 — Session Termination
• CIS Controls v8 6.7 — Centralize Access Control
• ISO/IEC 27001:2022 A.5.2 — Information security roles and responsibilities
• BSI C5:2020 PS-04 — Physical site access control
• SOC 2 (2017 TSC) CC6.4 — Physical Access Controls

Related controls in NIST SP 800-53 Rev. 5

• Control AC-4(28) — Linear Filter Pipelines
• Control AC-17(6) — Protection Of Mechanism Information
• Control AC-6(3) — Network Access To Privileged Commands
• Control AC-9(4) — Additional Logon Information
• Control MP-2(1) — Automated Restricted Access
• Control AC-3(8) — Revocation Of Access Authorizations

References

• NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5
• Catalogue identifier: Control AC-4(22)

Topics: identity accessidentity managementaccess reviewprivileged accessendpoint protection