EvidenceSheet
CSA CCM v4.1 · SEF - Security Incident Management, E-Discovery, & Cloud Forensics

SEF-01 Security Incident Management Policy and Procedures

The organisation keeps an approved, published and enforced set of policies and procedures covering how it handles security incidents, how it responds to e-discovery demands and how it carries out forensic work in cloud environments, and it checks those documents for effectiveness. They are revisited and refreshed every year at minimum and also whenever a major change occurs.

Source: CSA CCM v4.1, SEF-01. 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
0
held by a system
2
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

none for this control

periodic reviewEvidence produced at each review

  • Record of the latest annual review and of any review triggered by a significant change, with reviewer sign-off · Policy repository / GRC workspace
  • Distribution or attestation records showing incident staff received the current documents · Vendor register / contract repository

governing documentDocuments that govern the control

  • Approved incident management policy with version history and named owner · Policy repository / GRC workspace
  • E-discovery and legal hold procedure, including how preservation requests from customers or courts are received and actioned · Policy repository / GRC workspace
  • Cloud forensics procedure covering evidence acquisition from virtual machines, containers and provider logs with chain-of-custody forms · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

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

LOG-14 Failures and Anomalies Reporting · SEF-02 Service Management Policy and Procedures