EvidenceSheet
ASD Strategies to Mitigate Cyber Security Incidents · Detecting Cyber Security Incidents and Responding

28 Continuous incident detection and response (Excellent)

Continuous incident detection and response with a 24/7 cyber security operations capability for automated and manual analysis of security events.

Source: ASD Strategies to Mitigate Cyber Security Incidents, 28. 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 ASD Strategies to Mitigate Cyber Security Incidents in the compliance library.

4
artefacts
0
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

none for this control

periodic reviewEvidence produced at each review

  • Sample of alert tickets showing triage time, manual analyst investigation notes and escalation to incident response · SIEM / log platform

governing documentDocuments that govern the control

  • Incident response escalation matrix defining severity levels, response time targets and who is called out after hours · Policy repository / GRC workspace
  • SOC operating model and roster showing 24/7 analyst cover, including after-hours and on-call escalation arrangements · Document repository
  • SIEM log source inventory reconciled to the asset register, with automated correlation rules and their last tuning date · 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

27 Outbound data loss prevention (Very Good) · 29 Host-based IDS/IPS (Very Good)