GV.OC-03 Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil…
Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed
Source: NIST CSF 2.0, GV.OC-03. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open NIST CSF 2.0 in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Change log when new obligations are added · SIEM / log platform
periodic reviewEvidence produced at each review
- Compliance calendar tracking filings and attestations · Document repository
governing documentDocuments that govern the control
- Legal and regulatory obligations register with owners · Policy repository / GRC workspace
- Contractual security clauses summary across customer base · Document repository
- Counsel sign off on obligations interpretation · Document repository
First move
Common gaps auditors find
- Register not maintained when laws change
- Customer contracts not parsed for security clauses
- Cross border data flows missing from the register
- No owner assigned to emerging regulations
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetGV.OC-02 Internal and external stakeholders are understood, and their needs and expectations regarding cybersecurity… · GV.OC-04 Critical objectives, capabilities, and services that external stakeholders depend on or expect from the…