# NIST SP 800-53 Rev. 5 AT-3(2) — Physical Security Controls

- Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/at-3-2-physical-security-controls
- Section: [Compliance](https://support.icompaas.com/compliance) › [NIST SP 800-53 Rev. 5 Controls](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5) › AT — Awareness and Training
- Last updated: 2026-06-05
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**NIST SP 800-53 Rev. 5**·Control `AT-3(2)`·medium·Component: **Awareness and Training**

## What this control requires

> Trains personnel on operating physical security controls like access devices and alarms, ensuring proper facility security management. This control supports the Physical Access Control System capability within the Awareness and Training family.
> 
> — NIST SP 800-53 Rev. 5, Control AT-3(2)

### In plain English

Trains personnel on operating physical security controls like access devices and alarms, ensuring proper facility security management. 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.

## 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 **Awareness and Training**, the assessor will trace your implementation back to the catalogue reference (Control AT-3(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.

#### Physical Security

**Inheritance.** For cloud-only operations, inherit physical controls from the provider's SOC 2 / ISO 27001 report and document the inheritance in the SoA.

### Operational checklist

-   **Access.** Document the trigger, the owner and the cadence.
-   **Security.** Document the trigger, the owner and the cadence.
-   **Physical.** Document the trigger, the owner and the cadence.
-   **Protection.** Document the trigger, the owner and the cadence.
-   **Access Control.** Document the trigger, the owner and the cadence.
-   **Scope:** management, access control, system, personnel, controls, security controls, protection, capability.

## 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: Physical Security Controls.

## 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.10.7** — Physical Access Control](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-10-7-physical-access-control)

## Related controls in NIST SP 800-53 Rev. 5

-   [**Control PE-3(4)** — Lockable Casings](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-3-4-lockable-casings)
-   [**Control PE-3** — Physical Access Control](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-3-physical-access-control)
-   [**Control PE-2(3)** — Restrict Unescorted Access](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-2-3-restrict-unescorted-access)
-   [**Control PE-3(1)** — System Access](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-3-1-system-access)
-   [**Control AC-19** — Access Control For Mobile Devices](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-19-access-control-for-mobile-devices)
-   [**Control PE-2(2)** — Two Forms Of Identification](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-2-2-two-forms-of-identification)

## References

-   [NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5](https://csrc.nist.gov/Projects/risk-management/sp800-53-controls)
-   Catalogue identifier: `Control AT-3(2)`

Topics: endpoint securityphysical securityendpoint protection

## Related compliance guidance

- [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): Start with the full NIST SP 800-53 implementation guide — scope, roadmap, evidence and how the assessment runs.
- [NIST SP 800-171 and CMMC: a practical guide to protecting CUI in the cloud](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3): If your obligation is protecting CUI in your own systems for a federal or defence contract, this derived subset — not the full catalogue — is the requirement.
- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most commercial SaaS already hold a SOC 2 Type 2, and FedRAMP 20x Class A is designed for providers that have one.