Australia SOCI Act compliance, incident reporting and risk management
Determine which duties apply to each critical infrastructure asset. Prepare the register, incident reporting and board-approved reporting evidence before you need it.
Australian Cyber and Infrastructure Security Centre (CISC)
Timing
The initial reporting clock is up to 12 hours for a qualifying critical incident and up to 72 hours for other qualifying incidents. Where applicable, submit the annual risk program report within 90 days after financial year-end.
Reviewed
Inside this guide
4 steps · 4 templates
Who it applies to
Responsible entities and direct interest holders where the Act and applicable rules impose obligations. Check the asset definition, declaration, applicable parts, commencement and exemptions separately.
What you’ll produce
A signed asset and obligations map, applicable register submissions, a tested incident reporting procedure and, where required, an implemented risk management program and approved annual report.
Baseline, enhanced and telecommunications risk management requirements have different applicability and timing. Resolve the obligations per asset, including any instrument or notice applying to a system of national significance.
What applies to each entity, product and activity?
Have Legal or Regulatory confirm scope and applicable deadlines for each entity, activity and jurisdiction. Assign owners for incident reporting, filings and lifecycle changes where required.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.
How to spend the first week
Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts.
Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
What to review each week
Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.
Kickoff brief to share with your team
Fill this in with your sponsor and send it to the people who own the work.
Australia Security of Critical Infrastructure Act kickoff brief
Business reason and required outcome [Contract, obligation or approval]
Scope and exclusions [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones [Date, source and owner]
Executive sponsor and authorized signer [Names]
Project lead and backup [Names]
First workstream Determine asset scope and who is accountable · Legal + asset owner + corporate secretary [Name and due date]
People, effort and external costs [Estimate, owner and contingency]
Evidence folder and reviewer access [Location, access owner and review date]
Decisions and blockers [Item, options, owner and decision date]
First week
1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts.
3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START
How this works in practice
Two questions to check scope
Which essential service and asset is affected, and who is the responsible entity for it?
Who can submit an incident report and record its receipt if the primary decision owner is out of reach?
Worked scenario
A fictional utility acquires an operating asset. Legal verifies which obligations apply and assigns reporting roles to both the operator and relevant interest holders. The board reviews a timed incident exercise and evidence that the risk program operates.
Enhanced risk management has staggered start dates
The enhanced program commenced on 10 June 2026. CISC lists different grace periods for the measures and distinguishes assets already within scope at commencement.
What to check Record the due date and supporting rule for each measure in the asset’s obligations map.
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
01
Determine asset scope and who is accountable
Who Legal + asset owner + corporate secretaryWhen At acquisition, commissioning or material change
Map the asset, sector, responsible entity and direct interest holders. Apply the definitions, rules and any declaration. Record which parts apply, commencement, triggers and regulator. Reconcile operational and ownership information before making applicable register notifications.
What to produce
SOCI asset and obligations recordSpreadsheet
Gather first
Asset list
Operating entities and ownership records
Applicable laws and notices
Current register submissions
How to prepare it
Create one row per asset. Record the regulated asset class, responsible entity, direct interest holders and applicable instrument.
Use separate columns for each statutory obligation, trigger, deadline, owner and regulator. Record the legal basis for each conclusion and who approved it.
Reconcile the operational and ownership information against company records before filing or updating an applicable entry.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional asset row
Southbank Utility records an acquired asset under its legal entity and checks the definition with counsel. The asset owner supplies the operating description and commencement date.
Update evidence
Legal records the due date and approved form. Corporate Secretariat submits where required and saves a receipt with the source records.
Check before handing it over
A second reviewer can identify the obligation, affected asset, legal source and accountable person.
Share the approved map with risk, operations and each entity responsible for a submission.
Who Risk lead + asset operators + governing bodyWhen Before the applicable risk program deadlines
Confirm baseline, enhanced or telecommunications obligations and applicable transition dates. Assign material risks and mitigations under the relevant instrument, document why remaining risk is acceptable, and capture evidence the written program operates.
What to produce
SOCI risk program evidence workbookSpreadsheet
Gather first
Asset scope and applicable rules
Written risk program
Workshop notes
Control records and review calendar
How to prepare it
Check the applicable baseline, enhanced or telecommunications requirements and implementation dates. Match each relevant obligation to the written program section.
Map each material risk to the essential service affected, existing measures, accountable owners and further action. Document why the chosen treatment is reasonably practicable.
Ask control owners for evidence from current operations. Record any exceptions, verification dates and approved treatment or escalation.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional risk row
Reliance on one external maintenance provider creates a continuity risk. Operations records tested fallback arrangements, assurance evidence and the executive who owns remaining actions.
Implementation review
The risk lead reconciles the signed program with the most recent exercise and operating evidence. The board receives the actions and due dates.
Check before handing it over
The written program and evidence agree for each in-scope asset and risk, with unresolved items assigned.
Use the reviewed program map to prepare governing-body reviews and periodic evidence updates.
Who Incident lead + duty officer + LegalWhen At awareness of a qualifying cyber incident
Distinguish significant impact on availability from other relevant impacts under sections 30BC and 30BD. Record awareness, impact, reporting owner and due time. Submit promptly using the approved route and assign any written follow-up following an oral report.
What to produce
SOCI incident reporting decision fileChecklist
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.
Worked example
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.
Check before handing it over
A reviewer can reconstruct awareness, impact, classification, reporting and follow-up from the file.
Share the approved reporting route with the primary and backup incident responders.
Who Board secretary + risk lead + complianceWhen At financial year-end and after material changes
Reconcile asset and risk records, covered incidents, program changes and outstanding actions. Obtain governing-body approval and file in the approved form with the relevant regulator within 90 days where applicable. Keep the receipt and track updates to the register separately.
What to produce
SOCI board and annual reporting packMemo
Gather first
Written risk program
Operating evidence
Incident and change registers
Board calendar
Applicable annual report form
How to prepare it
Identify the covered assets and reporting period. Reconcile material events and changes with the program and identify any required updates or remediation.
Prepare the approved-form report and attach the evidence requested by governance. Obtain board, council or other governing-body approval as applicable.
Submit to the correct regulator by the applicable deadline. Save the approved version, meeting evidence, submission and any follow-up.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional approval file
The secretary records the resolution approving the 2026–27 report. Risk attaches an action log and the current program version.
Submission checkpoint
Compliance verifies the final approval and due date, saves the receipt and assigns any authority follow-up.
Check before handing it over
The filed report can be traced to the approved version and its underlying asset, risk and incident evidence.
Give leadership the receipt, unresolved actions and any next review date.