# NIST SP 800-53 Rev. 5 PE-20 — Asset Monitoring And Tracking - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-20-asset-monitoring-and-tracking - 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) › PE — Physical and Environmental Protection - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-53 Rev. 5**·Control `PE-20`·medium·Component: **Physical and Environmental Protection** ## What this control requires > Use organization-defined asset location technologies to track and monitor the location and movement of assets (e.g., vehicles, equipment, system components) within designated controlled areas, ensuring compliance with privacy considerations. This control supports the Asset Tracking System capability within the Physical and Environmental Protection family. > > — NIST SP 800-53 Rev. 5, Control PE-20 ### In plain English Use organization-defined asset location technologies to track and monitor the location and movement of assets (e.g., vehicles, equipment, system components) within designated controlled areas, ensuring compliance with privacy considerations. In practice, this means you can prove you policy 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 **Physical and Environmental Protection**, the assessor will trace your implementation back to the catalogue reference (Control PE-20) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Logging Monitoring **AWS.** Org-trail CloudTrail to a central log archive account, GuardDuty in every region, and Security Hub for cross-source correlation. **Azure.** Pipe every diagnostic setting into a central Log Analytics workspace; onboard Microsoft Sentinel for SIEM/SOAR. **GCP.** Aggregate audit logs in a dedicated logging project with sink to BigQuery; enable Security Command Center Premium and route findings to Chronicle SIEM. #### Policy Management **Docs.** Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA. ### Operational checklist - **Policy.** 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. - **Environmental.** Document the trigger, the owner and the cadence. - **Monitor.** Document the trigger, the owner and the cadence. - **Scope:** management, privacy, organization, system, location, e, protection, monitor. ## Evidence to collect - **Policy Document.** A signed and version-controlled policy / standard / procedure document. - **Infra Scan.** Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings. Signed policy or standard documents the safeguard. Focus: Asset Monitoring And Tracking. ## Common pitfalls - Per-account logging that nobody stitches together at the org level — incidents that cross accounts go undetected for days. - Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced. ## 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.4.11** — Information Location](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-4-11-information-location) ## Related controls in NIST SP 800-53 Rev. 5 - [**Control PE-21** — Electromagnetic Pulse Protection](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-21-electromagnetic-pulse-protection) - [**Control SC-7(24)** — Personally Identifiable Information](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sc-7-24-personally-identifiable-information) - [**Control CM-12(1)** — Automated Tools To Support Information Location](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cm-12-1-automated-tools-to-support-information-location) - [**Control PE-17** — Alternate Work Site](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-17-alternate-work-site) - [**Control AC-17(1)** — Monitoring And Control](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-17-1-monitoring-and-control) - [**Control PE-9(2)** — Automatic Voltage Controls](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-9-2-automatic-voltage-controls) ## 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 PE-20` Topics: governance risklogging monitoringcontinuous monitoringpolicy managementprivacy management ## 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.