EvidenceSheet
CSA CCM v4.1 · DSP - Data Security and Privacy Lifecycle Management

DSP-18 Disclosure Notification

The service provider puts in place, and explains to its customers, a procedure for handling and answering law enforcement requests to disclose personal data, in line with applicable law.

Source: CSA CCM v4.1, DSP-18. 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
Policy repository / GRC workspace
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

  • Request log with legal review and approvals · SIEM / log platform

periodic reviewEvidence produced at each review

  • Legal counsel review records · Document repository

governing documentDocuments that govern the control

  • Law enforcement request handling procedure · Policy repository / GRC workspace
  • Customer-facing description of the procedure (for example in a trust centre or transparency report) · Policy repository / GRC workspace
  • Transparency report figures · Document repository

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your SIEM / log platform 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

DSP-17 Sensitive Data Protection · DSP-19 Data Location