EvidenceSheet
CSA CCM v4.1 · GRC - Governance, Risk and Compliance

GRC-07 Information System Regulatory Mapping

Every relevant standard, regulation, legal or contractual obligation and statutory requirement that applies to the organisation is identified and recorded. The record is revisited every year, and sooner after a significant change.

Source: CSA CCM v4.1, GRC-07. 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.

5
artefacts
1
held by a system
1
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

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

  • Regulatory change monitoring outputs · Regulator portal / correspondence

periodic reviewEvidence produced at each review

  • Review records · Document repository

governing documentDocuments that govern the control

  • Register of applicable laws, regulations, standards and contracts · Vendor register / contract repository
  • Mapping of obligations to the control set (for example CCM controls) · Document repository
  • Gap actions from the mapping · Document repository

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your Regulator portal / correspondence on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.

Common gaps auditors find

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 sheet

GRC-06 Governance Responsibility Model · GRC-08 Special Interest Groups