Malware alert flashing on screen

Mandatory Ransomware Payment Reporting in Australia, Explained

Quick answer

Since May 2025, Australian businesses with annual turnover of more than $3 million, and responsible entities for critical infrastructure assets, must report any ransomware or cyber extortion payment to the Government within 72 hours, through the Australian Signals Directorate (ASD). The obligation only applies when a payment is made. Recovery that has been tested before an incident is what makes not paying a realistic option.

Most coverage of mandatory ransomware payment reporting treats it as paperwork: a form, a deadline and a penalty. That’s accurate, but it starts at the wrong end. A report is triggered by a decision to pay, and that decision is most likely when an organisation isn’t confident it can recover any other way. This article covers what the rules require, then what it takes to make sure paying is never the only option on the table.

What is mandatory ransomware payment reporting?

Mandatory ransomware payment reporting is an obligation under Part 3 of the Cyber Security Act 2024. It requires a reporting business to report to the Government, through the ASD’s reporting form, when it makes a payment in connection with a ransomware or cyber extortion incident, or becomes aware that someone has made one on its behalf. The obligation took effect in May 2025.

Who has to report a ransomware payment?

You must report a payment if your business made it, or is aware someone made it on its behalf, and either of these applies:

  • Your business carries on business in Australia and had annual turnover of more than $3 million in the previous financial year. Commonwealth and state bodies are excluded from this test. If the business operated for only part of the previous financial year, the threshold is adjusted using a formula set out in the rules.
  • Your business is the responsible entity for a critical infrastructure asset covered by Part 2B of the Security of Critical Infrastructure Act 2018, whatever its turnover.

The obligation sits with the business, not with a named person. The Act doesn’t specify who inside the organisation has to lodge the report, so it’s worth deciding before an incident. A third party can submit the report on the business’s behalf, but the business remains responsible for making sure it’s lodged within 72 hours.

What the rules sayDetail
DeadlineWithin 72 hours of making the payment, or of becoming aware it was made
Who receives the reportThe Government, through the ASD's reporting form on cyber.gov.au
What counts as a paymentAny monetary or non-monetary benefit, such as services or data. There is no minimum amount
What the report coversDetails of who paid, the incident and its impact, the demand, the payment, and communications with the attacker
If a demand isn't paidNo report is required under this obligation, although voluntary reporting is encouraged
PenaltyThe Act sets a civil penalty of 60 penalty units for failing to report

It’s the payment, not the attack, that triggers a report. There is no minimum payment threshold, and the Act defines a benefit as including “any advantage”, so non-cash payments count too.

Has enforcement started?

Yes. The Department of Home Affairs took an education-first approach from the start of the regime to 31 December 2025, when it aimed to pursue regulatory action only for egregious non-compliance. From 1 January 2026, it moved to a more active regulatory approach.

Payments are being reported. Between seven and 13 organisations with turnover of at least $3 million paid a ransom each month, according to figures iTnews obtained from Home Affairs, and critical infrastructure entities made 19 payment reports in the eight months to January 2026.

What happens if you pay a ransom?

For a reporting business, paying starts a 72-hour reporting clock, but the bigger problems are practical. The ASD’s advice is direct: “Never pay a ransom.” Its guidance gives three reasons:

  • Paying doesn’t guarantee recovery. There’s no guarantee you’ll regain access to your data.
  • Paying doesn’t protect stolen data. It doesn’t stop criminals selling or leaking information they’ve already taken.
  • Paying can invite another attack. The ASD warns you may be targeted again.

In the middle of an incident, leadership is weighing an uncertain recovery against a demand with a deadline. If nobody can say, with evidence, how long recovery would take, paying can look like the faster path.

How do you recover from ransomware without paying?

The ASD puts it simply: “The best recovery method from a ransomware attack is to restore from an unaffected backup.” That sentence contains three conditions that are easy to assume and hard to prove.

The backup has to be unaffected. The ASD warns that backups may be affected if they were stored on the infected device or connected to the same network, and that a backup should be checked for infection before it’s used. Copies that can’t be altered or deleted once written protect against tampering, although immutability has limits worth understanding.

The restore has to work at the scale you need. Restoring a file proves very little about restoring the systems the business runs on, in the right order, within a time leadership can accept.

Someone has to own it. If recovery ownership is agreed before an incident, nobody has to work it out while the systems are down.

Prevention matters too. Our guide to ransomware protection controls covers the controls that reduce the chance and the impact of an attack. This article focuses on the decision you face if one gets through.

How do you know your backups would hold up in a ransomware attack?

A backup job completing tells you data was copied. It doesn’t tell you how long recovery would take, whether dependent systems come back in the right order, or whether the copy you’re restoring is clean.

Only a recovery test shows that, and it has to be one that is timed, covers the workloads the business depends on, and is documented so leadership, an insurer or a regulator can see the result. We’ve written about what a recovery test should produce.

What should be in place before an incident?

  • Know whether you’re a reporting business. Check your turnover and whether you’re responsible for a critical infrastructure asset, so nobody is working it out against a 72-hour deadline.
  • Agree who decides. Name who makes the call on a ransom demand, and who lodges a report if one is needed.
  • Keep copies that can’t be altered or deleted. If an attacker can change or remove your backups, recovery isn’t really an option.
  • Test recovery recently, timed and documented. It should cover the critical systems, not a sample file.
  • Write down recovery ownership. It shouldn’t depend on one or two people being available.
  • Map your other notification duties. Obligations such as the Privacy Act’s Notifiable Data Breaches scheme, or critical infrastructure incident reporting, can apply whether or not you pay.

Reporting is a consequence of paying. Recoverability is what decides whether paying is ever on the table.

Evolution Data Resilience is a managed recovery service built around recovery that’s tested and documented before an incident, immutable copies, and a single point of accountability during recovery events. There are three levels to choose from, and you can price yours in 30 seconds, or ask about a custom setup.

Last reviewed November 2026. This article summarises the ransomware payment reporting obligation and is not legal advice. Whether it applies to a specific organisation depends on the Cyber Security Act 2024, its rules and the organisation’s circumstances.

FAQs

Do you have to report a ransomware attack if you don’t pay?

Not under this obligation. A demand that isn’t paid doesn’t trigger a ransomware payment report, although Home Affairs encourages businesses to report incidents voluntarily. Other obligations, such as the Notifiable Data Breaches scheme or critical infrastructure incident reporting, can still apply.

What is the deadline for reporting a ransomware payment?

72 hours from making the payment, or from becoming aware it was made. If a third party pays on the business’s behalf, the business must still report within 72 hours of becoming aware of the payment.

Does a small or non-cash payment have to be reported?

Yes. There is no minimum amount, and the obligation covers non-monetary benefits such as services or data as well as money.

What is the penalty for not reporting a ransomware payment?

The Act sets a civil penalty of 60 penalty units for failing to report. Home Affairs moved from an education-first approach to a more active regulatory approach on 1 January 2026.

Does restoring from backup stop stolen data being published?

No. Recovery restores your systems and data, but it can’t undo data theft. Paying doesn’t either: the ASD warns that paying doesn’t guarantee criminals won’t sell or leak your information.

How do you prove your backups will work in a ransomware attack?

Run a recovery test that is timed, covers the systems the business depends on, and restores from copies that can’t be altered or deleted. Then document the result so it can be shown to leadership, an insurer or a regulator.

Let's see how we can personalise your IT

Evolution Systems is ISO 27001 Certified

Information Security ISO 27001 Certification