{"data":{"id":"SR-01","name":"Policy and Procedures","family":"SR","family_name":"Supply Chain Risk Management","withdrawn":false,"description":"a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]:\n1. [Selection (one or more): Organization-level; Mission/business process-level; System-level] supply chain risk management policy that:\n(a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and\n(b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and\n2. Procedures to facilitate the implementation of the supply chain risk management policy and the associated supply chain risk management controls;\nb. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the supply chain risk management policy and procedures; and\nc. Review and update the current supply chain risk management:\n1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and\n2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].","supplemental_guidance":"Supply chain risk management policy and procedures address the controls in the SR family as well as supply chain-related controls in other families that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of supply chain risk management policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to supply chain risk management policy and procedures include assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.","enhancements":[],"baseline_low":true,"baseline_moderate":true,"baseline_high":true,"nist_800_53":{"rev5":{"id":"SR-01","name":"Policy and Procedures","description":"a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]:\n1. [Selection (one or more): Organization-level; Mission/business process-level; System-level] supply chain risk management policy that:\n(a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and\n(b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and\n2. Procedures to facilitate the implementation of the supply chain risk management policy and the associated supply chain risk management controls;\nb. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the supply chain risk management policy and procedures; and\nc. Review and update the current supply chain risk management:\n1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and\n2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].","discussion":"Supply chain risk management policy and procedures address the controls in the SR family as well as supply chain-related controls in other families that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of supply chain risk management policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to supply chain risk management policy and procedures include assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.","related_controls":["PM-09","PM-30","PS-08","SI-12"],"baseline_low":true,"baseline_moderate":true,"baseline_high":true,"baseline_privacy":false,"new_in_rev5":true,"changes_from_rev4":"New control family introduced in Rev 5"}},"compliance_mappings":{"iso_27001_2022":["4.2","5.2","5.3","7.5","A.5.1","A.5.2","A.5.4","A.5.19","A.5.21","A.5.31","A.5.36","A.5.37"],"iso_27002_2022":["5.1","5.19","5.21"],"cobit_2019":["APO10"],"pci_dss_v4":["12.8","12.9"],"nist_csf_2":["GV.OC-03","GV.OV-01","GV.PO-01","GV.PO-02","GV.RM-05","GV.SC-01","GV.SC-02","GV.SC-03","GV.SC-05","GV.SC-09","GV.SC-10","ID.IM-01","ID.IM-02","ID.IM-03"],"cis_controls_v8":["CIS 15","CIS 15.2"],"soc2_tsc":["CC1.2-POF1","CC1.4-POF1","CC1.4-POF2","CC1.4-POF3","CC2.2-POF1","CC2.2-POF7","CC2.3-POF12","CC3.3","CC5.3","CC5.3-POF1","CC5.3-POF6","CC7.2-POF1","CC9.1","CC9.2","CC9.2-POF1","P1.1-POF5"],"finos_ccc":[],"iso_42001_2023":["A.10.2","A.10.3"],"iec_62443":[],"asd_e8":[],"nis2":["Art. 21(2)(d)"],"apra_cps_234":["Para 29-33"],"mas_trm":["16"],"pra_op_resilience":["SS1/21-5.3","SS2/21-3.1","SS2/21-8.1","SS2/21-12.1","SS2/21-16.1"],"bsi_grundschutz":[],"anssi":["Hygiene.2","Hygiene.36","Hygiene.42","SecNumCloud.6.1","SecNumCloud.16.1"],"osfi_b13":["B-13.4.1"],"finma_circular":["IV.A(23)","IV.F(100)","V(101)"],"gdpr":["Art.28(1)","Art.28(3)","Art.28(4)"],"dora":["Art.28(1)(a)","Art.28(2)","Art.28(4)"],"bio2":["5.1","5.19","5.21"],"rbi_csf":["Annex1.11","ITGRCA.10"],"fisc":[],"lgpd_bcb":[],"hkma_tme1":[],"mlps_2":["8.1.9.3","8.1.9.7","8.1.10.12","8.2"],"dnb_good_practice":["DNB.1.2","DNB.14.2"],"cra":["CRA.I.1"],"swift_cscf":["SWIFT.2.8"],"cbb_tm":["TM-15"],"cbuae":["CR-12"],"nca_ecc":["1-3","4-1","4-2"],"qatar_nia":["SD"],"sama_csf":["1.2","4.1","4.2","4.3"],"uae_ia":["T3","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","Ch5.2"],"cpmi_pfmi":["CG.ID","PFMI.P17"],"eba_ict":["3.2.3","3.4.1"],"ecb_croe":["CROE.2.2.3"],"ffiec_is":["II.C.1","II.C.14","II.C.20"],"hipaa_sr":["§164.314(a)(1)","§164.316(a)"],"iosco_cyber":["GOV-1","GOV-5","PROT-7"],"nydfs_500":["500.3","500.11"],"sebi_cscrf":["GV.SC","PR.CS"],"nerc_cip":["CIP-013-2"],"nrc_73_54":["RG5.71-C-SR"],"tsa_psd":[],"ieee_1686":[],"ferc_cip":["Order 829","Order 850"],"doe_c2m2":["THIRD"],"api_1164":["Sec 12"],"awia":["AWWA Sec 7"],"iaea_nss":["Sec 6"],"pci_pts":["G"],"fips_140":[],"cbest":[],"tiber_eu":["TIBER.PROV"],"pci_hsm":[],"common_criteria":[],"isae_3402":["Clause 7","Clause 8"],"fca_sysc_13":["SYSC 13.9.1"],"fda_21_cfr_11":[],"fda_cyber":[],"hitrust_csf":["04.a","05.b"],"iso_27799":["5.1","14.1","15.1","15.2"],"lloyds_ms":["MS8.2","MS8.8","MS9.3","MS13.1"],"naic_ds":["4D"],"nhs_dspt":["NDG-10.1","NDG-10.3","NDG-10.4"],"pra_ss1_23":[],"solvency_ii":["Art.41(3)","Art.49(1)","Art.49(2)","DR.272","DR.274","EIOPA-Cloud-GL11"],"owasp_masvs_v2":[],"csa_ccm_v4":["STA-01","STA-02","STA-03","STA-04","STA-05","STA-06","STA-07","STA-08","STA-10","STA-12","STA-13","STA-14","UEM-14"],"csa_aicm":["STA-01","STA-02","STA-03","STA-04","STA-05","STA-06","STA-07","STA-08","STA-10","STA-12","STA-13","STA-14","STA-15","STA-16","UEM-14"],"ccss_v9":[],"mica":["Art.66(1)"],"basel_sco60":["SCO60.54"],"bssc":["GSP-07"],"sec_custody_digital":["SEC-CD-10"],"dpdpa":[]},"attack_techniques":[],"metadata":{"last_reviewed":"2026-10-03","review_notes":"2026-10-03: iso_27001_2022 5.2, 5.3, 7.5, A.5.2, A.5.31, A.5.36, A.5.37, A.5.4 added from NIST's SP 800-53 Rev 5 to ISO/IEC 27001:2022 crosswalk (OLIR entry 155), which OSA's mapping now takes as its base. 2026-10-03: nist_csf_2 GV.OC-03, GV.OV-01, GV.PO-01, GV.PO-02, ID.IM-01, ID.IM-02, ID.IM-03 added from NIST's CSF 2.0 to SP 800-53 Rev 5.2.0 crosswalk (OLIR entry 186), which OSA's mapping now takes as its base. 2026-10-03: statement, discussion and related controls taken from NIST SP 800-53 Release 5.2.0, which this file lacked.","mapping_status":"complete"},"function":"preventative","used_by_patterns":["SP-018","SP-028"]}}