# PM-28 Risk Framing

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

Statement: a. Identify and document: 1. Assumptions affecting risk assessments, risk responses, and risk monitoring; 2. Constraints affecting risk assessments, risk responses, and risk monitoring; 3. Priorities and trade-offs considered by the organization for managing risk; and 4. Organizational risk tolerance; b. Distribute the results of risk framing activities to [Assignment: organization-defined personnel]; and c. Review and update risk framing considerations [Assignment: organization-defined frequency].
Guidance: Risk framing is most effective when conducted at the organization level and in consultation with stakeholders throughout the organization including mission, business, and system owners. The assumptions, constraints, risk tolerance, priorities, and trade-offs identified as part of the risk framing process inform the risk management strategy, which in turn informs the conduct of risk assessment, risk response, and risk monitoring activities. Risk framing results are shared with organizational personnel, including mission and business owners, information owners or stewards, system owners, authorizing officials, senior agency information security officer, senior agency official for privacy, and senior accountable official for risk management.

## Patterns that use it (1)
- Important (1): SP-045 AI Governance and Responsible AI

## Clauses by framework (37 frameworks)
- iso_27001_2022: 4.3, 6.1, 6.2, 7.4, 7.5
- iso_27002_2022: 5.34
- cobit_2019: APO12, EDM03
- nist_csf_2: DE.AE-04, GV.OC-03, GV.OV-02, GV.RM-01, GV.RM-02, GV.RM-03, GV.RM-04, GV.RM-06, GV.RM-07, GV.SC-09. OSA's own, not in NIST's crosswalk: GV.OV-02, GV.RM-01, GV.RM-02, GV.RM-03
- mas_trm: 4
- bio2: 5.34
- rbi_csf: ITGRCA.22, ITGRCA.25
- fisc: FISC.O1
- hkma_tme1: TME1.2.3, TME1.7.1
- dnb_good_practice: DNB.4.1, DNB.4.2
- cbb_tm: TM-2, TM-3, TM-4
- cbuae: CR-1, CR-2
- nca_ecc: 1-5
- qatar_nia: GV, RM
- sama_csf: 1.8
- uae_ia: T2
- bog_cisd: CISD-II, CISD-III
- bom_ctrm: 1.1, 1.4
- cbe_csf: CRM-1, GOV-1
- cbn_csf: Part1.1, Part2.1, Part2.2
- sa_js2: JS2-4, JS2-5, JS2-6.2
- bcbs_239: Principle 1
- bot_cyber: Ch1.2
- cpmi_pfmi: PFMI.P3
- eba_ict: 3.3.1, 3.3.3
- ecb_croe: CROE.2.1.1, CROE.2.2.1
- ffiec_is: II.B
- sebi_cscrf: GV.OC, GV.RM
- cmmc_2: RA
- doe_c2m2: RISK
- tiber_eu: TIBER.CONF, TIBER.PREP
- fca_sysc_13: SYSC 13.5.2, SYSC 13.G.2
- fda_cyber: SPDF-2
- hitrust_csf: 00.b, 03.a
- lloyds_ms: MS10.1
- solvency_ii: Art.44(1), Art.44(2), Art.45, DR.260, EIOPA-ICT-4.2
- basel_sco60: SCO60.3
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-28
- Clauses only: /api/v1/controls/PM-28?fields=mappings
- Page for people: /controls/pm-28/
- 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.