Checklist · Technology, Media & Telecommunications / IT Contracts
Ransomware or cyber extortion payment report: fields on the ACSC form
Field list for the ransomware and cyber extortion payment report on the cyber.gov.au form. The form cites section 27 of the Cyber Security Act 2024 and a 72-hour period. It is not the SOCI Act incident report, which uses different clocks.
- 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 business may have made a ransomware or cyber extortion payment, or another entity may have made one on its behalf. The how-to-report PDF was not opened. Do not use the 12-hour SOCI clock for this form.
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 place facts the lawyer has already confirmed into the field names on the form. The lawyer decides whether a reporting business entity made a payment and what is lodged.
AI may
- List each field on the form and the fact, if any, the file already states
- Record the date of the payment and the date the entity became aware, from documents the lawyer supplies
- Flag that a SOCI Part 2B incident report is a different obligation
AI must not
- Must not lodge the report
- Must not invent malware, a vulnerability, or what was said to the extorting entity
- Must not apply the 12-hour significant-impact clock. That clock is on the CISC page, not this form
The lawyer checks
- The entity is one of the three kinds the form lists
- The 72 hours is counted from the event the form describes, on the lawyer's instructions
- Only information the entity knows, or can find by reasonable search or enquiry, is included
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)
- 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)
- SOCI Act cyber incident report: 12-hour and 72-hour clocks
- 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