NIST SP 800-53 Rev. 5·Control AC-20(2)·medium·Component: Access Control

What this control requires

Restricts use of organization-controlled portable storage devices on external systems with organization-defined restrictions to limit risks to organizational data. This control supports the Portable Storage Device Policy capability within the Access Control family.
— NIST SP 800-53 Rev. 5, Control AC-20(2)

In plain English

Restricts use of organization-controlled portable storage devices on external systems with organization-defined restrictions to limit risks to organizational data. In practice, this means you can prove you policy access control-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.

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-20(2)) 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

  • Policy. Document the trigger, the owner and the cadence.
  • Restrictions. Document the trigger, the owner and the cadence.
  • Access. 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.
  • Scope: access control, organization, external systems, protection, capability, storage, policy, security.

Evidence to collect

  • User Device Scan. MDM compliance state per user device (Intune / Jamf / Workspace ONE).
  • Infra Scan. Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings.

Endpoint compliance telemetry (Intune, Jamf) proves managed coverage. Focus: Portable Storage Devices -- Restricted Use.

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.

Related controls in NIST SP 800-53 Rev. 5

References

Topics: governance riskendpoint securityendpoint protection