# PM-30 Supply Chain Risk Management Strategy

NIST SP 800-53 control. Family: PM Program Management. Function: preventative. In no baseline. Mapping licence: CC BY-SA 4.0.

Statement: a. Develop an organization-wide strategy for managing supply chain risks associated with the development, acquisition, maintenance, and disposal of systems, system components, and system services; b. Implement the supply chain risk management strategy consistently across the organization; and c. Review and update the supply chain risk management strategy on [Assignment: organization-defined frequency] or as required, to address organizational changes.
Guidance: An organization-wide supply chain risk management strategy includes an unambiguous expression of the supply chain risk appetite and tolerance for the organization, acceptable supply chain risk mitigation strategies or controls, a process for consistently evaluating and monitoring supply chain risk, approaches for implementing and communicating the supply chain risk management strategy, and the associated roles and responsibilities. Supply chain risk management includes considerations of the security and privacy risks associated with the development, acquisition, maintenance, and disposal of systems, system components, and system services. The supply chain risk management strategy can be incorporated into the organization’s overarching risk management strategy and can guide and inform supply chain policies and system-level supply chain risk management plans. In addition, the use of a risk executive function can facilitate a consistent, organization-wide application of the supply chain risk management strategy. The supply chain risk management strategy is implemented at the organization and mission/business levels, whereas the supply chain risk management plan (see SR-02) is implemented at the system level.

## Enhancements (1)
- PM-30(01) Suppliers of Critical or Mission-essential Items
Each enhancement's statement: /api/v1/controls/PM-30?fields=enhancements

## Patterns that use it (1)
- Important (1): SP-034 Cyber Resilience

## Clauses by framework (23 frameworks)
- iso_27001_2022: 4.4, 6.2, 7.5
- nist_csf_2: DE.AE-04, GV.OC-02, GV.OC-05, GV.OV-01, GV.OV-02, GV.RM-03, GV.RM-04, GV.RM-05, GV.RM-06, GV.RM-07, GV.SC-01, GV.SC-03, GV.SC-09, ID.RA-06
- pra_op_resilience: SS2/21-16.1
- rbi_csf: Annex1.11, ITGRCA.10
- cra: CRA.I.1
- cbuae: CR-12
- qatar_nia: GV
- sama_csf: 1.8, 4.1
- bog_cisd: CISD-XVI
- bom_ctrm: 1.5, 3.9
- cbe_csf: CTO-11, OVM-1
- cbn_csf: Part2.4
- sa_js2: JS2-8.7
- bcbs_239: Principle 1
- bot_cyber: Ch5.1, Ch5.2
- ffiec_is: II.C.20
- nydfs_500: 500.11
- sebi_cscrf: GV.RM, GV.SC
- doe_c2m2: THIRD
- isae_3402: Clause 7
- fca_sysc_13: SYSC 13.9.1
- lloyds_ms: MS10.1
- naic_ds: 4D
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/PM-30
- Clauses only: /api/v1/controls/PM-30?fields=mappings
- Page for people: /controls/pm-30/
- 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.