NIST PF GV.RM-P - Risk Management Strategy
Agree privacy-risk management processes and express risk tolerance informed by the organization's roles in the data processing ecosystem.
Where this comes from
Provision: GV.RM-P - Risk Management Strategy
Instrument: NIST Privacy Framework Version 1.0
Citation: NIST Privacy Framework Version 1.0 (16 January 2020), Core, GV.RM-P1 through GV.RM-P3
Text version: NIST Privacy Framework 1.0 Core, 16 January 2020 (not PF 1.1)
Checked against the source: 6 September 2026
Who it applies to
It applies when all of these are true:
- NIST PF 1.0 Target Profile adopted: YES
- GV.RM-P: Which outcomes are selected in this project's Target Profile? is GV.RM-P1, GV.RM-P2 or GV.RM-P3
What engineering work it implies
Sample acceptance criteria Landfall generates for this obligation:
- Process is documented and accessible
- Process steps are implemented in system
- Process outcomes are recorded
- Process can be audited
- Process documentation is complete
Questions people ask
- Does NIST PF GV.RM-P - Risk Management Strategy apply to my service?
- It applies when NIST PF 1.0 Target Profile adopted: YES; GV.RM-P: Which outcomes are selected in this project's Target Profile? is GV.RM-P1, GV.RM-P2 or GV.RM-P3.
- From when does this apply?
- NIST PF GV.RM-P - Risk Management Strategy applies from 16 January 2020. Its current status is: in force.
Find out whether this one lands on you
Landfall's pre-scan answers the applicability question above for your product in minutes, then turns every obligation that applies into traceable engineering tickets with a citation chain your auditors can follow.
Not legal advice. Landfall maps regulatory obligations to engineering work for planning purposes. Its verdicts are not legal advice and create no attorney-client relationship — verify with qualified counsel before relying on them.