# PM-02 Information Security Program Leadership Role

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

Statement: Appoint a senior agency information security officer with the mission and resources to coordinate, develop, implement, and maintain an organization-wide information security program.
Guidance: The senior agency information security officer is an organizational official. For federal agencies (as defined by applicable laws, executive orders, regulations, directives, policies, and standards), this official is the senior agency information security officer. Organizations may also refer to this official as the senior information security officer or chief information security officer.

## Patterns that use it (1)
- Critical (1): SP-018 Information Security Management System

## Clauses by framework (66 frameworks)
- iso_27001_2022: 4.4, 5.1, 5.3, A.5.2, A.5.4. OSA's own, not in NIST's crosswalk: 4.4, A.5.4
- iso_27002_2022: 5.2, 5.4
- cobit_2019: APO01, APO13, EDM01, EDM05
- nist_csf_2: GV.RR-01, GV.RR-02
- cis_controls_v8: CIS 17.1, CIS 17.5
- iec_62443: 2-1 4.2
- apra_cps_234: Para 16-17, Para 18
- mas_trm: 3
- pra_op_resilience: SS1/21-3.2, SS2/21-17.1
- bsi_grundschutz: ISMS.1, ORP.1
- anssi: Hygiene.4
- dora: Art.5(1)
- bio2: 5.2, 5.4
- rbi_csf: ITGRCA.8, ITGRCA.24
- fisc: FISC.O1
- lgpd_bcb: BCB.Art.17, BCB.Art.17-Supp, LGPD.Art.41
- hkma_tme1: TME1.2.1, TME1.2.4, TME1.7.1
- mlps_2: 8.1.7.1
- dnb_good_practice: DNB.5.1, DNB.5.2
- cbb_tm: TM-1, TM-3
- cbuae: CR-1
- nca_ecc: 1-2, 1-4
- qatar_nia: GV
- sama_csf: 1.1, 1.5
- uae_ia: T1
- bog_cisd: CISD-I, CISD-II, CISD-ISMS
- bom_ctrm: 1.1, 1.2
- cbe_csf: GOV-1, GOV-2
- cbn_csf: Part1.1, Part1.2
- popia: s8, s55
- sa_js2: JS2-4
- bcbs_239: Principle 1
- bot_cyber: Ch1.1
- cpmi_pfmi: CG.GOV, PFMI.P2
- eba_ict: 3.2.1, 3.3.1
- ecb_croe: CROE.2.1.1, CROE.2.1.2
- ffiec_is: I.A, I.B
- hipaa_sr: §164.308(a)(2)
- iosco_cyber: GOV-2, GOV-4, PFMI-2
- nydfs_500: 500.2, 500.4, 500.10
- sebi_cscrf: GV.RR
- nerc_cip: CIP-003-9
- nrc_73_54: 73.54(b)
- tsa_psd: SD-1 Sec 1
- ferc_cip: Order 706
- doe_c2m2: PROGRAM
- awia: AWWA Sec 1
- iaea_nss: Sec 3
- cbest: CBEST.1
- tiber_eu: TIBER.PREP
- pci_hsm: 1
- common_criteria: CC Part 2 — FMT
- fca_sysc_13: SYSC 13.1-2, SYSC 13.6.3, SYSC 13.G.1
- hitrust_csf: 00.a, 04.a, 05.a, 13.a
- iso_27799: 6.1, 6.2
- lloyds_ms: CRM.1, GOV.1, MS8.1
- naic_ds: 4, 4-personnel, 4C
- nhs_dspt: NDG-1.2
- pra_ss1_23: P2.1, P2.2
- solvency_ii: Art.41(1), DR.258, DR.260, EIOPA-ICT-4.1
- csa_ccm_v4: GRC-01, GRC-05, GRC-06, HRS-09, STA-04
- csa_aicm: GRC-01, GRC-05, GRC-06, GRC-10, GRC-13, HRS-09, HRS-14, HRS-15, STA-04
- mica: Art.34(1), Art.54(1), Art.59(1)
- basel_sco60: SCO60.3, SCO60.60
- bssc: GSP-01
- sec_custody_digital: SEC-CD-01, SEC-CD-17, SEC-CD-19
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-02
- Clauses only: /api/v1/controls/PM-02?fields=mappings
- Page for people: /controls/pm-02/
- 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.