# NIST SP 800-53 Rev. 5 PM-5(1) — Inventory Of Personally Identifiable Information - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pm-5-1-inventory-of-personally-identifiable-information - 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) › PM — Program Management - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-53 Rev. 5**·Control `PM-5(1)`·critical·Component: **Program Management** ## What this control requires > Establish and maintain an inventory of all systems, applications, and projects that process personally identifiable information (PII) to support data mapping, privacy notices, and ensure that PII is only processed for authorized and necessary purposes. This control supports the PII System Inventory Management capability within the Program Management family. > > — NIST SP 800-53 Rev. 5, Control PM-5(1) ### In plain English Establish and maintain an inventory of all systems, applications, and projects that process personally identifiable information (PII) to support data mapping, privacy notices, and ensure that PII is only processed for authorized and necessary purposes. 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. 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 **Program Management**, the assessor will trace your implementation back to the catalogue reference (Control PM-5(1)) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Asset Inventory **AWS.** AWS Config Aggregator across every account + region gives a real-time inventory; ship the daily snapshot to S3 and surface drift in Security Hub. **Azure.** Azure Resource Graph plus Defender for Cloud's inventory blade enumerates every subscription; export to Log Analytics for retention and Workbooks for reporting. **GCP.** Cloud Asset Inventory exports a daily feed of every resource and IAM binding; query via BigQuery and alert on appearance/disappearance. **Endpoints.** Pipe MDM telemetry (Intune / Jamf / Workspace ONE) into your CMDB so laptops and phones are inventoried with the same rigour as cloud resources. #### 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. - **Information.** Document the trigger, the owner and the cadence. - **Process.** Document the trigger, the owner and the cadence. - **Data.** Document the trigger, the owner and the cadence. - **Protection.** Document the trigger, the owner and the cadence. - **Scope:** management, information, privacy, system, only, personally identifiable information, protection, capability. ## Evidence to collect - **Policy Document.** A signed and version-controlled policy / standard / procedure document. Signed policy or standard documents the safeguard. Focus: Inventory Of Personally Identifiable Information. ## Common pitfalls - Inventories that exclude SaaS, shadow IT and ephemeral cloud resources (Lambda, Cloud Run, K8s pods) miss the assets where most modern incidents start. - Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced. ## Related controls in NIST SP 800-53 Rev. 5 - [**Control SI-19(3)** — Release](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/si-19-3-release) - [**Control SI-18(5)** — Notice Of Correction Or Deletion](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/si-18-5-notice-of-correction-or-deletion) - [**Control SI-12(1)** — Limit Personally Identifiable Information Elements](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/si-12-1-limit-personally-identifiable-information-elements) - [**Control SA-8(33)** — Minimization](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-8-33-minimization) - [**Control SI-18(1)** — Automation Support](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/si-18-1-automation-support) - [**Control SI-19** — De-Identification](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/si-19-de-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 PM-5(1)` Topics: governance riskdata protectionprivacy managementasset inventorypolicy 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.