Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission.
Also written as GV-PO-02, GV.PO-2, CSF 2.0 GV.PO-02, NIST CSF GV.PO.
GV.PO-02 is one of 31 subcategories in the Govern (GV) function, under the Policy category (GV.PO). The Core states: “Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission.” Govern is the function CSF 2.0 added, and it is the one most organisations score lowest on: the outcome is not a tool you deploy but a decision someone with authority has to make, record, and revisit.
To demonstrate this outcome in an assessment or audit, gather artefacts such as:
GV.PO-02 corresponds to the following ISO 27001:2022 Annex A control(s): A.5.1, A.5.36. Evidence collected for one framework typically supports the other.
No. CSF 2.0 is a voluntary framework of outcomes rather than a set of requirements, and there is no certification against it. GV.PO-02 becomes binding only when something else makes it so — a contract, a regulator that references CSF, or your own Target Profile. That is the practical difference between CSF and an auditable standard like ISO 27001 or SOC 2.
Through profiles rather than pass/fail testing. You record how fully the outcome is achieved today in a Current Profile, state where it needs to be in a Target Profile, and the gap between them becomes your action plan. Implementation Tiers (Partial, Risk Informed, Repeatable, Adaptive) describe how rigorous your governance around the outcome is, not whether you have met it.
Govern outcomes sit with leadership rather than with the security team — executives, risk owners, and in many organisations the board. If GV.PO-02 has no named owner outside IT, that is usually the finding, because CSF 2.0 introduced Govern precisely to make cybersecurity a management-level accountability.
Yes — GV.PO-02 corresponds to ISO 27001:2022 Annex A control(s) A.5.1, A.5.36. Evidence collected for one framework typically supports the other, so a single control library can serve both.