# NIST SP 800-53 Rev. 5 SA-12(4) — Diversity Of Suppliers - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-12-4-diversity-of-suppliers - 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) › SA — System and Services Acquisition - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-53 Rev. 5**·Control `SA-12(4)`·medium·Component: **System and Services Acquisition** ## What this control requires > Use trusted shipping and warehousing processes to ensure secure transport and storage of system components. This control supports the Supplier Diversity Plan capability within the System and Services Acquisition family. > > — NIST SP 800-53 Rev. 5, Control SA-12(4) ### In plain English Use trusted shipping and warehousing processes to ensure secure transport and storage of system components. 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 **System and Services Acquisition**, the assessor will trace your implementation back to the catalogue reference (Control SA-12(4)) 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. - **Security.** Document the trigger, the owner and the cadence. - **Storage.** 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. - **Scope:** management, system, encryption, components, services, capability, storage, transport. ## Evidence to collect - **Vendor Risk Management.** `vendor_risk_management` evidence - **Policy Document.** A signed and version-controlled policy / standard / procedure document. Third-party risk management evidence (assessments, contracts, due diligence) shows supplier oversight. Signed policy or standard documents the safeguard. Focus: Diversity Of Suppliers. ## 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. - [**ISO/IEC 27001:2022 A.5.19** — Information security in supplier relationships](https://support.icompaas.com/compliance/iso-27001-2022/a-5-19-information-security-in-supplier-relationships) - [**NIST SP 800-171 Rev. 3 3.16.3** — External System Services](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-16-3-external-system-services) - [**HIPAA (45 CFR Part 164) 164.312(e)(2)(ii)** — Transmission Security - Encryption](https://support.icompaas.com/compliance/hipaa/164-312-e-2-ii-transmission-security-encryption) ## Related controls in NIST SP 800-53 Rev. 5 - [**Control SA-12(3)** — Trusted Shipping And Warehousing](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-12-3-trusted-shipping-and-warehousing) - [**Control SA-12(12)** — Inter-Organizational Agreements](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-12-12-inter-organizational-agreements) - [**Control SA-22(1)** — Alternative Sources For Continued Support](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-22-1-alternative-sources-for-continued-support) - [**Control SA-12(10)** — Validate As Genuine And Not Altered](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-12-10-validate-as-genuine-and-not-altered) - [**Control SA-19** — Component Authenticity](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-19-component-authenticity) - [**Control SA-8(17)** — Secure Distributed Composition](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-8-17-secure-distributed-composition) ## 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 SA-12(4)` Topics: governance riskvendor riskvendor managementsupply chain securityencryption in transitpolicy 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.