What evidence do auditors commonly ask for on SEF-08 Security Breach Notification?

Breach notification procedure with materiality criteria and decision record template; Register of notification obligations by jurisdiction, regulation and contract with deadlines; Records of past notifications to regulators or customers with timestamps; Supplier contract clauses requiring the supplier to report breaches to the organisation; Awareness or training records for staff who make notification decisions.

What is the most common gap auditors find on SEF-08?

No documented test for when a breach counts as material

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

`SEF-08` Security Breach Notification

The organisation defines and operates processes, procedures and technical measures for notifying others of security breaches. Breaches judged material, including those originating in its supply chain, are reported in line with the applicable service level agreements, laws and regulations.

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

artefacts

held by a system

at each review

hard

to go live

Vendor register / contract 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

none for this control

periodic reviewEvidence produced at each review

Records of past notifications to regulators or customers with timestamps · Regulator portal / correspondence
Awareness or training records for staff who make notification decisions · HR system / LMS

governing documentDocuments that govern the control

Breach notification procedure with materiality criteria and decision record template · Policy repository / GRC workspace
Register of notification obligations by jurisdiction, regulation and contract with deadlines · Vendor register / contract repository
Supplier contract clauses requiring the supplier to report breaches to the organisation · Vendor register / contract repository

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

No documented test for when a breach counts as material
Notification deadlines across jurisdictions not mapped, so the shortest is missed
Breaches at suppliers not captured because contracts lack a duty to report

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

SEF-07 Incident Management and Response · SEF-09 Incident Records Management