Checklist · Technology, Media & Telecommunications / IT Contracts
SOCI Act cyber incident report: 12-hour and 72-hour clocks
The CISC description of mandatory cyber incident reporting for a critical infrastructure asset. A significant impact is 12 hours. A relevant impact is 72 hours. An oral report has a further written deadline. This is not the ransomware payment form.
- Kind
- Checklist. Steps or checks to work through and tick off.
- Where it applies
- Australia, Commonwealth
- AI use
- Yellow You and the tool draft together, with you directing. You check every statement you rely on.
- Law stated as at
- 22 October 2026
- Status
- Maintained. Checked on 22 October 2026 against the authority it cites, for Australia and Commonwealth.
- Version
- 1
- Source
- Written for this library
When to use it
Use when a responsible entity may have to report a cyber security incident affecting a critical infrastructure asset. The application rules that list which asset classes must report were not opened. Call 000 if there is a threat to life.
Used for these tasks
Each task page says how far AI may help with the task and what the lawyer must review.
How AI may be used
AI may record the time the entity became aware and which impact the lawyer has selected. The lawyer decides whether the impact is significant or relevant, and whether the asset class must report.
AI may
- Record the time the entity became aware, from a document the lawyer supplies
- Place the facts against the page's definition of a cyber security incident
- Remind the file that a ransomware payment report is a separate form
AI must not
- Must not decide that an impact is significant or relevant
- Must not list the asset classes that must report. Section 5 of the application rules was not opened
- Must not lodge the report
The lawyer checks
- The asset is in a class required to report under the application rules
- The clock is 12 hours or 72 hours according to the impact, counted from awareness
- An oral report is followed by the written report within 84 hours or 48 hours, as the page states for that impact
Method: how the Green, Yellow and Red levels are decided. This is guidance for planning, not legal advice.
Read the full text
The full text is available after you log in. It is free. When you log in you can:
- read the whole precedent, with its drafting notes beside it;
- copy it, or download it as a Word file or Markdown;
- add it to your firm’s knowledge base, so colleagues can find it;
- let the AI tools you connect read it from that knowledge base.
The summary, the law it rests on and the AI-use guidance above stay public. Privacy.
More in Technology, Media & Telecommunications / IT Contracts
- IT services statement of work template (under a master services agreement)
- Ransomware or cyber extortion payment report: fields on the ACSC form
- SaaS / cloud services agreement (Australian law, business customers)
- CCPA service provider and contractor addendum
- SaaS subscription and negative-option checklist
- Website and online platform terms of use (Australian business, with Australian Consumer Law carve-outs)
- AI standard clauses for AI features in cloud services (Bonterms AI Standard Clauses v1.0, CC0)
- Deed of assignment of intellectual property and moral rights consent (contractor or developer software)
- Service level schedule with service credits (SaaS, managed or hosted services)
- Register of Critical Infrastructure Assets: what the CISC page asks for
- Checklist for electronic consumer records
- SaaS subscription agreement
- AI addendum: ownership of AI-generated output, training-data rights and AI-specific warranties (customer-side)
- Email and SMS marketing campaign checklist (Spam Act consent, sender identification and unsubscribe)
- Software source code escrow agreement (three-party: supplier, customer and escrow agent)
- AI vendor terms review checklist
- Statement of work
- Cross-border disclosure assessment for a technology vendor (APP 8 and s 16C checklist and record)
- Critical infrastructure risk management program: annual report contents
- Australian Government AI model clauses (DTA, BuyICT ClauseBank): use guide for agencies and suppliers
- Open source licence compliance review checklist (technology transactions and product releases)
- Security incident clause
- Consumer Data Right: data holder obligations on the CDR site
- Data protection, security and breach-notification schedule (processor terms)
- Software development agreement with AI coding-assistant and open-source terms
- Checklist: reviewing a vendor SaaS or technology contract (customer side, including AI terms)
All precedents for Technology, Media & Telecommunications / IT Contracts · Tasks and AI use in this area