# NIST SP 800-53 Rev. 5 SR-12 — Component Disposal - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sr-12-component-disposal - 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) › SR — Supply Chain Risk Management - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-53 Rev. 5**·Control `SR-12`·high·Component: **Supply Chain Risk Management** ## What this control requires > Dispose of \[Assignment: organization-defined data, documentation, tools, or system components\] using the following techniques and methods: \[Assignment: organization-defined techniques and methods\]. This control supports the System components capability within the Supply Chain Risk Management family. > > — NIST SP 800-53 Rev. 5, Control SR-12 ### In plain English Dispose of \[Assignment: organization-defined data, documentation, tools, or system components\] using the following techniques and methods: \[Assignment: organization-defined techniques and methods\]. 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 **high**. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation. ## 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 **Supply Chain Risk Management**, the assessor will trace your implementation back to the catalogue reference (Control SR-12) and look for objective evidence on the latest two assessment cycles. ## How to implement #### 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. - **Data.** Document the trigger, the owner and the cadence. - **Chain.** Document the trigger, the owner and the cadence. - **System.** Document the trigger, the owner and the cadence. - **Control.** Document the trigger, the owner and the cadence. - **Scope:** management, organization, system, components, capability, tools, techniques, system components. ## Evidence to collect - **Policy Document.** A signed and version-controlled policy / standard / procedure document. Signed policy or standard documents the safeguard. Focus: Component Disposal. ## Common pitfalls - 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. - [**SOC 2 (2017 TSC) P4.3** — Secure Disposal of Personal Information](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/p4-3-secure-disposal-of-personal-information) - [**HIPAA (45 CFR Part 164) 164.308(a)(5)(i)** — Security Awareness and Training](https://support.icompaas.com/compliance/hipaa/164-308-a-5-i-security-awareness-and-training) - [**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 SR-10** — Inspection Of Systems Or Components](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sr-10-inspection-of-systems-or-components) - [**Control SR-11(3)** — Anti-Counterfeit Scanning](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sr-11-3-anti-counterfeit-scanning) - [**Control SR-9** — Tamper Resistance And Detection](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sr-9-tamper-resistance-and-detection) - [**Control SR-4** — Provenance](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sr-4-provenance) - [**Control SC-29** — Heterogeneity](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sc-29-heterogeneity) - [**Control PE-21** — Electromagnetic Pulse Protection](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-21-electromagnetic-pulse-protection) ## 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 SR-12` Topics: governance riskpolicy 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.