COPRSETR WORKSHEET
SOCI incident reporting decision file
Australia Security of Critical Infrastructure Act · Step 3 · Rehearse incident classification and reporting- Who prepares it
- Incident lead + duty officer + Legal
- When to prepare it
- At awareness of a qualifying cyber incident
Worked example
This example uses fictional details. Use the same fields with evidence from your work.
- Fictional 12-hour exercise
- A duty officer becomes aware at 09:15 local time on a day with no clock change that a cyber incident has significantly affected availability of a covered asset. The team records 21:15 as the outer deadline and reports earlier.
- Evidence handoff
- The duty officer records the reporting time, authority reference and facts communicated. The designated backup confirms the required written follow-up.
Gather first
- Asset obligations map
- Incident timeline
- Service impact evidence
- On-call authorisation
- Approved submission channels
How to prepare it
- Record awareness using a local timestamp and UTC equivalent. Identify the affected asset, actual or likely impacts, known facts and required decision owner.
- Check sections 30BC and 30BD. Use the applicable deadline and submit as soon as practicable. Retain the report, recipient, time and reference.
- When the initial report is oral, assign the written form and follow-up deadline. Keep updates and source evidence together with the original decision.
Review
A reviewer can reconstruct awareness, impact, classification, reporting and follow-up from the file.
Handoff
Share the approved reporting route with the primary and backup incident responders.
Use the issuer’s current instructions and any required forms when you submit.
SOCI Act, sections 30BC and 30BD (opens in a new tab)