# PM-15 Security and Privacy Groups and Associations

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

Statement: Establish and institutionalize contact with selected groups and associations within the security and privacy communities: a. To facilitate ongoing security and privacy education and training for organizational personnel; b. To maintain currency with recommended security and privacy practices, techniques, and technologies; and c. To share current security and privacy information, including threats, vulnerabilities, and incidents.
Guidance: Ongoing contact with security and privacy groups and associations is important in an environment of rapidly changing technologies and threats. Groups and associations include special interest groups, professional associations, forums, news groups, users’ groups, and peer groups of security and privacy professionals in similar organizations. Organizations select security and privacy groups and associations based on mission and business functions. Organizations share threat, vulnerability, and incident information as well as contextual insights, compliance techniques, and privacy problems consistent with applicable laws, executive orders, directives, policies, regulations, standards, and guidelines.

## Clauses by framework (40 frameworks)
- iso_27001_2022: 7.4, A.5.5, A.5.6. OSA's own, not in NIST's crosswalk: A.5.5
- iso_27002_2022: 5.5, 5.6
- cobit_2019: APO08
- nist_csf_2: DE.AE-06, GV.OC-02, GV.RM-05, ID.RA-02, ID.RA-08, RS.CO-03. OSA's own, not in NIST's crosswalk: GV.OC-02, GV.RM-05, ID.RA-08, RS.CO-03
- cis_controls_v8: CIS 17.2
- nis2: Art. 29
- dora: Art.45(1)
- bio2: 5.5, 5.6
- rbi_csf: Annex1.11, ITGRCA.10
- mlps_2: 8.1.7.2
- dnb_good_practice: DNB.3.1, DNB.16.4
- cra: CRA.Art14, CRA.II.4, CRA.II.5, CRA.II.6, CRA.Info.2
- cbb_tm: TM-3
- cbuae: CR-11
- qatar_nia: GV
- sama_csf: 1.6
- uae_ia: T1
- bom_ctrm: 3.8, 4.1, 5.3
- cbe_csf: GOV-3, GOV-4
- cbn_csf: Part4, Part8
- sa_js2: JS2-7.6
- bcbs_239: Principle 14
- bot_cyber: Ch1.3, Ch8.1
- cpmi_pfmi: CG.SA
- ecb_croe: CROE.2.2.3, CROE.2.5.3, CROE.2.7.1, CROE.2.7.2, CROE.2.8.2
- ffiec_is: II.A, II.A.1, III.A
- iosco_cyber: GOV-5, LE-3, REG-1, RR-4, SA-1, SA-2
- nydfs_500: 500.10
- sebi_cscrf: CAPACITY, PR.AT, RS.CO
- nrc_73_54: 73.54(d)
- tsa_psd: SD-1 Sec 2
- doe_c2m2: THREAT
- cbest: CBEST.2
- tiber_eu: TIBER.GTL, TIBER.XB
- fda_cyber: 524B-2, 524B-3, CVD-1, CVD-2, MON-1, MON-3
- iso_27799: 16.1, 16.3
- lloyds_ms: CRM.2
- csa_ccm_v4: GRC-08, SEF-08
- csa_aicm: GRC-08, GRC-15, SEF-08
- basel_sco60: SCO60.84
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-15
- Clauses only: /api/v1/controls/PM-15?fields=mappings
- Page for people: /controls/pm-15/
- 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.