# SR-03 Supply Chain Controls and Processes

NIST SP 800-53 control. Family: SR Supply Chain Risk Management. Function: preventative. Baselines: low, moderate, high. Mapping licence: CC BY-SA 4.0.

Statement: a. Establish a process or processes to identify and address weaknesses or deficiencies in the supply chain elements and processes of [Assignment: organization-defined system or system component] in coordination with [Assignment: organization-defined supply chain personnel]; b. Employ the following controls to protect against supply chain risks to the system, system component, or system service and to limit the harm or consequences from supply chain-related events: [Assignment: organization-defined supply chain controls]; and c. Document the selected and implemented supply chain processes and controls in [Selection (one): security and privacy plans; supply chain risk management plan; [Assignment: organization-defined document]].
Guidance: Supply chain elements include organizations, entities, or tools employed for the research and development, design, manufacturing, acquisition, delivery, integration, operations and maintenance, and disposal of systems and system components. Supply chain processes include hardware, software, and firmware development processes; shipping and handling procedures; personnel security and physical security programs; configuration management tools, techniques, and measures to maintain provenance; or other programs, processes, or procedures associated with the development, acquisition, maintenance and disposal of systems and system components. Supply chain elements and processes may be provided by organizations, system integrators, or external providers. Weaknesses or deficiencies in supply chain elements or processes represent potential vulnerabilities that can be exploited by adversaries to cause harm to the organization and affect its ability to carry out its core missions or business functions. Supply chain personnel are individuals with roles and responsibilities in the supply chain.

## Enhancements (3)
- SR-03(01) Diverse Supply Base
- SR-03(02) Limitation of Harm
- SR-03(03) Sub-tier Flow Down
Each enhancement's statement: /api/v1/controls/SR-03?fields=enhancements

## Patterns that use it (12)
- Critical (3): SP-012 Secure Software Development Lifecycle; SP-028 Secure DevOps Pipeline Pattern; SP-042 Third Party Risk Management
- Important (6): SP-018 Information Security Management System; SP-039 Client-Side Encryption and Data Privacy; SP-040 Post-Quantum Cryptography and Quantum Readiness; SP-047 Secure Agentic AI Frameworks; SP-050 Mobile Security Architecture (draft); SP-051 Tokenised Asset Security Architecture (draft)
- Standard (3): SP-030 API Security; SP-038 Vulnerability Management and Patching; SP-053 Zero-Knowledge Proof Architecture (draft)

## Clauses by framework (67 frameworks)
- iso_27001_2022: 4.2, A.5.19, A.5.20, A.5.21. OSA's own, not in NIST's crosswalk: 4.2, A.5.19
- iso_27002_2022: 5.19, 5.20, 5.21
- cobit_2019: APO10
- pci_dss_v4: 12.8
- nist_csf_2: GV.OC-02, GV.SC-01, GV.SC-02, GV.SC-03, GV.SC-04, GV.SC-05, GV.SC-06, GV.SC-07, GV.SC-08, GV.SC-09, GV.SC-10, ID.RA-10, RS.CO-02, RS.CO-03, RS.MA-01. OSA's own, not in NIST's crosswalk: GV.SC-04, GV.SC-06, ID.RA-10
- cis_controls_v8: CIS 15, CIS 15.4
- soc2_tsc: CC9.1
- iso_42001_2023: A.10.3
- nis2: Art. 21(2)(d)
- apra_cps_234: Para 29-33
- mas_trm: 16
- pra_op_resilience: SS2/21-6.1, SS2/21-8.1, SS2/21-14.1
- anssi: Hygiene.9, Hygiene.42, SecNumCloud.16.1, SecNumCloud.16.2
- osfi_b13: B-13.4.1
- finma_circular: V(104), V(105), V(106), V(107), V(108)
- gdpr: Art.28(1), Art.28(2), Art.28(4)
- dora: Art.28(2), Art.29(1), Art.30(2)
- bio2: 5.19, 5.20, 5.21
- rbi_csf: Annex1.11, ITGRCA.10
- mlps_2: 8.1.9.4, 8.1.10.12
- dnb_good_practice: DNB.14.2, DNB.16.3
- cra: CRA.I.1
- swift_cscf: SWIFT.2.8
- cbb_tm: TM-15
- cbuae: CR-12
- nca_ecc: 4-1, 4-2
- qatar_nia: SD
- sama_csf: 4.1, 4.2
- uae_ia: T10
- bog_cisd: CISD-XI, CISD-XII, CISD-XVI
- bom_ctrm: 3.9
- cbe_csf: CTO-11, OVM-1
- cbn_csf: Part2.4
- popia: s20, s21
- sa_js2: JS2-8.7
- bot_cyber: Ch5.1
- cpmi_pfmi: CG.PR, PFMI.P17
- eba_ict: 3.2.3
- ecb_croe: CROE.2.2.3
- ffiec_is: II.C.14, II.C.20
- hipaa_sr: §164.314(a)(1), §164.314(a)(2)
- iosco_cyber: GOV-5, PROT-7
- nydfs_500: 500.11
- sebi_cscrf: GV.SC
- nerc_cip: CIP-013-2
- nrc_73_54: RG5.71-C-SR
- ferc_cip: Order 829, Order 850
- doe_c2m2: THIRD
- api_1164: Sec 12
- awia: AWWA Sec 7
- iaea_nss: Sec 6
- pci_pts: G
- isae_3402: Clause 7
- fca_sysc_13: SYSC 13.9.1, SYSC 13.9.3, SYSC 13.9.5
- hitrust_csf: 05.b
- iso_27799: 14.1, 15.1, 15.2
- lloyds_ms: MS8.8, MS9.3
- naic_ds: 4D
- nhs_dspt: NDG-10.1, NDG-10.3, NDG-10.4
- solvency_ii: Art.49(1), Art.49(2), DR.272, EIOPA-Cloud-GL3
- owasp_masvs_v2: MASVS-CODE-3
- csa_ccm_v4: STA-02, STA-08, STA-14
- csa_aicm: STA-02, STA-08, STA-14
- mica: Art.66(1)
- basel_sco60: SCO60.4, SCO60.41, SCO60.54
- bssc: GSP-07, NOS-02
- sec_custody_digital: SEC-CD-10
OSA's mapping for iso_27001_2022 and nist_csf_2 takes NIST's published crosswalk as its base. A clause not marked as OSA's own is in that crosswalk.

## More
- This control as JSON, with guidance and ATT&CK techniques: /api/v1/controls/SR-03
- Clauses only: /api/v1/controls/SR-03?fields=mappings
- Page for people: /controls/sr-03/
- Found an error? Open an issue at https://github.com/opensecurityarchitecture/osa-data/issues with the id, what OSA says and what the source says.