What evidence do auditors commonly ask for on SEF-04 Incident Response Testing?

Annual exercise calendar for incident response tabletop and technical simulations; Exercise reports with scenario, participants, observations and findings; Action log showing plan updates made from exercise findings; Record of an exercise run after a significant change such as a new region or major release; Sign-off by the incident response owner on the exercise outcome.

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

Exercises planned but repeatedly postponed with no record of completion

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

`SEF-04` Incident Response Testing

The organisation runs exercises of its incident response plans on a planned schedule and again when significant changes occur, and uses the outcome to judge whether the plans still work.

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

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

Action log showing plan updates made from exercise findings · SIEM / log platform

periodic reviewEvidence produced at each review

Annual exercise calendar for incident response tabletop and technical simulations · Document repository
Exercise reports with scenario, participants, observations and findings · Document repository
Record of an exercise run after a significant change such as a new region or major release · Source control / CI pipeline
Sign-off by the incident response owner on the exercise outcome · Document repository

governing documentDocuments that govern the control

none for this control

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

Exercises planned but repeatedly postponed with no record of completion
Findings recorded but the plan never revised
Exercises limited to the security team without business, legal or communications staff

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-03 Incident Response Plans · SEF-05 Incident Response Metrics