GRC-03 Organizational Policy Reviews
Every relevant organisational policy and its procedures is reviewed at least yearly or when the organisation goes through a substantial change.
Source: CSA CCM v4.1, GRC-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 CSA CCM v4.1 in the compliance library.
Version 4.1 adds 11 controls (among them API security, log sanitisation and a service bill of materials) and renumbers several domains. CSA accepts v4.0.x during its transition; if your STAR assessment is still on v4.0.1, check the numbering against it.
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 events that triggered reviews · Policy repository / GRC workspace
- Version history · Policy repository / GRC workspace
periodic reviewEvidence produced at each review
- Review sign-off records · Policy repository / GRC workspace
- Exception records for overdue reviews · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Policy register with last and next review dates · Policy repository / GRC workspace
First move
Common gaps auditors find
- Many policies overdue for review
- Reviews do not occur after reorganisations
- No central register
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 sheetGRC-02 Risk Management Program · GRC-04 Policy Exception Process