Who must report a ransomware payment in Australia within 72 hours?

A small rusted padlock hangs from a twisted steel cable against a blurred sky.
Photo: Matej Bizjak, Pexels
In short A company carrying on business in Australia with turnover above $3 million, and affected by a ransomware attack, must report a ransom payment within 72 hours of paying, or of learning that someone else paid. The rule covers overseas companies that carry on business here, and some critical infrastructure operators whatever their size. A data breach notice under the Privacy Act 1988 (Cth) (‘Privacy Act’) is a separate duty, which can apply even if nothing is paid.

Key points

  • The report is triggered by a payment, not by the attack or the demand. A refused demand creates no duty to report under the ransomware rules.
  • The report is due within 72 hours of paying, or of becoming aware that another company or person, such as an overseas parent, paid on the company’s behalf.
  • The test is annual turnover above $3 million in the previous financial year, which runs from 1 July to 30 June. Unlike the Privacy Act’s small business exemption, the test has no rule about related companies.
  • The information in the report is protected. It generally cannot be used to enforce other laws against the company, or be admitted in evidence against it, although a regulator can still gather the same facts in other ways.
  • An attack that reaches personal information may also be a notifiable data breach, which must be reported to the Australian Information Commissioner under the Privacy Act, with its own test and deadlines.

Suppose a ransomware attack has locked your company’s servers. The attackers have encrypted the data so that it cannot be read, and they want a payment in cryptocurrency before they will restore it. The decision to pay is being made at head office, perhaps in another time zone. If the attack has affected a company in the group that carries on business in Australia, paying can start a 72-hour clock for that company.

A company that carries on business in Australia with annual turnover above $3 million, and that the attack affected, must report the payment to the federal government within 72 hours. So must certain operators of critical infrastructure, the assets that basic services depend on, whatever their size.1 The duty reaches overseas companies, and it reaches a payment that someone else makes on the company’s behalf.2 It applies in addition to the data breach notice that the Privacy Act may also require, not in place of it.3

The clock does not start with the attack or with the demand. It starts with the payment or, where another company or person pays, with the moment the company learns that the payment was made.4

Which businesses must report a ransomware payment?

Since 29 May 2025, Part 3 of the Cyber Security Act 2024 (Cth) (‘Cyber Security Act’) has required two kinds of ‘reporting business entity’ to report a ransomware payment. The Cyber Security (Ransomware Payment Reporting) Rules 2025 (Cth), the detailed rules made under it, started on the same day.5

  1. The first is a business carried on in Australia whose annual turnover exceeded $3 million in the previous financial year, other than a government body or a critical infrastructure operator.6
  2. The second is the responsible entity for a critical infrastructure asset to which Part 2B of the Security of Critical Infrastructure Act 2018 (Cth) (‘Security of Critical Infrastructure Act’) applies, whatever its turnover. The responsible entity is the entity that the Security of Critical Infrastructure Act names for each kind of asset, such as the carrier for a telecommunications asset.7

The two categories do not cover every critical infrastructure operator. Part 2B applies only to assets listed in rules made under the Security of Critical Infrastructure Act, or declared to be covered. Those rules leave some assets out, such as four named Queensland sugar mills. A company responsible only for assets outside Part 2B is outside both categories, whatever its turnover, because the first category excludes every critical infrastructure operator.8

The turnover test is applied when the payment is made, using the previous Australian financial year, the 12 months starting on 1 July, whatever year the group’s own accounts use.9 For a business carried on for only part of that year, the threshold is reduced. It is $3 million multiplied by the number of days the business was carried on in that year, divided by the number of days in the year.10

The Cyber Security Act requires turnover above the threshold. Two government documents treat turnover equal to it as enough: the Explanatory Statement published with the rules to explain them, and the government’s online reporting form.11 In practice, a company whose turnover is exactly $3 million should not assume that it is outside the duty.

Does the turnover test look at the whole group?

As written, the turnover test looks at the company that reports, not at its whole group, because it refers to that company’s own annual turnover. The Privacy Act removes its small business exemption from a company related to one whose business is above that Act’s small business limit. The Cyber Security Act has no rule of that kind.12 On that reading, a small Australian subsidiary of a large group can fall below the ransomware threshold while still being bound by the Privacy Act.

Does the duty reach a company based overseas?

The duty can reach a company based overseas, because the Cyber Security Act applies outside Australia as well as within it. A foreign company that itself carries on a business in Australia is a reporting business entity if its turnover is above the threshold.13 The Cyber Security Act does not define ‘carrying on a business in Australia’, and says only that ‘business’ has the meaning it has in income tax law.14 A separate article explains how courts have read the same words in the Privacy Act.

When does a ransomware payment have to be reported?

A ransomware payment has to be reported, within 72 hours, when four things are true:15

  1. a cyber security incident has happened, is happening or is imminent;
  2. it has had, or could reasonably be expected to have, a direct or indirect impact on a reporting business entity;
  3. someone, usually the attacker, has made a demand, of that company or of anyone else, to benefit from the incident or from its impact on that company; and
  4. the company has given a payment or benefit directly related to the demand, or knows that another entity gave it on the company’s behalf.

A demand that is refused creates no duty under Part 3, because nothing has been paid.16 The payment need not be money: a benefit includes any advantage and is not limited to property.17 Part 3 sets out the duty to report and protects the information in a report, but it does not decide whether a company should or may pay.18

Our head office paid the ransom. Who reports, and by when?

The Australian company that the attack affected reports, if it meets the turnover test, within 72 hours of becoming aware that the payment was made on its behalf.19 It does not matter whether the payer was an overseas parent or a negotiator, so long as the payment was made on the company’s behalf.20 The parent may also have a duty of its own, if it is a reporting business entity in its own right and the four conditions are met for it. For example, a parent that carries on business in Australia, has turnover above $3 million and was affected by the attack, even indirectly, has its own 72 hours, running from when it paid.21

What goes in the report, and who receives it?

The report covers the following, so far as the company knows it, or can find it out by reasonable search or enquiry, when it reports:22

  • the contact and business details, including the ABN (if any) and address, of whichever entity paid: the company itself, or the other entity that paid on its behalf;
  • the incident: when it happened and when the company found out, its impact on the company’s systems and customers, the ransomware variant (which strain of ransomware was used), the vulnerabilities exploited (the weaknesses the attackers used to get in), and anything that could help government bodies respond;
  • the demand: the amount, or a description of a non-cash demand, and the method of payment demanded;
  • the payment: the amount, or a description, and the method; and
  • the communications with the attacker, including any negotiation before payment.23

The report goes to the ‘designated Commonwealth body’. No rules name another body, so under the Cyber Security Act’s definition the report goes to the Department of Home Affairs and the Australian Signals Directorate, the government’s cyber security and signals intelligence agency. If the Secretary of the Department of Home Affairs, its most senior official, has approved a form, the report must be in that form.24 The Australian Signals Directorate’s website says that a reporting business entity must use the online form published there.25

Can the report be used against the company?

Information supplied in the report generally cannot be used against the company, but the same facts gathered in another way can be. The Department of Home Affairs and the Australian Signals Directorate may use that information only for purposes that the Cyber Security Act lists, mainly helping the company and government bodies respond to the incident. Any body they pass it to is bound in the same way.26 None of them may use it to investigate or enforce a breach by the company of any other law, except Part 3 itself and laws that create criminal offences.27 Nor can that information generally be admitted as evidence against the company, including in a case under another Act, such as the Privacy Act, in which a regulator asks a court for a penalty.28

These protections do not cover information that a government body obtains in another way. A regulator, such as the Australian Information Commissioner under the Privacy Act, can still gather the same facts with its own powers.29

Giving the report generally does not affect legal professional privilege, the right to keep communications with lawyers confidential, except in a few proceedings, such as a coronial inquiry or a Royal Commission. The company also cannot be ordered to pay damages for anything it does in good faith to comply.30

What happens if the company does not report?

A company that does not report can be ordered by a court to pay a civil penalty. The Secretary of the Department of Home Affairs, or a senior official whom the Secretary appoints in writing, can apply for one. The application can be made to the Federal Court, the Federal Circuit and Family Court of Australia (Division 2) or a state or territory court that can hear the case.31

The maximum is 60 penalty units for an individual. For a company it is 300 penalty units, five times as much. For a failure to report on or after 1 July 2026, when a penalty unit rose to $364, that is $21,840 and $109,200.32 Instead of going to court, a senior official authorised by the Secretary can give the company an infringement notice, which sets a fixed amount to pay.33 A missed deadline does not end the duty, which continues until the report is made, although each extra day of delay does not count as a new breach.34

Is the ransomware report the same as a notifiable data breach?

A ransomware payment report is not the same as a notifiable data breach notice. The two duties have different triggers, deadlines and recipients, and neither Act treats one notice as satisfying the other.35 A ransomware attack that reaches personal information can engage both, so a company that pays may owe both notices within days of each other. The Privacy Act’s rules on assessing and reporting data breaches, known as the Notifiable Data Breaches scheme, are explained in the article on overseas companies and the Privacy Act. The table brings together how the two duties differ for a company that has paid a ransom.

Ransomware payment report36 Notifiable data breach37
Triggered by A ransomware payment by the company or on its behalf Unauthorised access to personal information, its unauthorised disclosure, or its loss, likely to cause someone serious harm
Who A business carried on in Australia with turnover above $3 million, or a covered critical infrastructure operator Organisations bound by the Privacy Act: generally turnover above $3 million, or related to a company whose business is not a small business
Deadline 72 hours from paying, or from learning of the payment A suspected breach assessed within 30 days; once believed on reasonable grounds, notice as soon as practicable
Goes to Home Affairs and the Australian Signals Directorate The Australian Information Commissioner, and the individuals affected
No ransom paid No report under this regime Still assessed, and notified if the test is met
Duty missed Civil penalty of up to 60 penalty units, five times that for a company A breach of the Privacy Act (an ‘interference with privacy’), which the Commissioner can act on

Worked example: who reports when a Shenzhen parent pays the ransom?

The group in this example is fictitious. The example applies the reporting rules above, step by step.

Take a Shenzhen electronics maker whose Australian distribution subsidiary had turnover of $18 million in the year to 30 June 2026. On Friday 9 October 2026, attackers encrypt the subsidiary’s warehouse system and copy its customer database. The parent’s security team pays the ransom at 10 pm Sydney time on Saturday 10 October. Nobody at the subsidiary knows of the payment until the parent tells the Australian managing director at 9 am on Monday 12 October. The example assumes that the subsidiary is not a critical infrastructure operator.

First, Part 3 applies to the subsidiary. It carries on business in Australia with turnover above $3 million, and the attack, the demand and the parent’s payment on its behalf meet the four conditions.38

Second, the subsidiary’s 72 hours run from 9 am on Monday, when it learned of the payment, so its report is due by 9 am on Thursday 15 October. If someone at the subsidiary whose knowledge counts as the company’s, such as a director, had known of the payment earlier, the clock could have started then. The report must give the parent’s details as the payer.39

Third, the parent has its own duty only if it also qualifies as a reporting business entity and the four conditions apply to it. It would qualify if, for example, it had its own Australian business turning over more than $3 million and was affected by the attack. Its report was then due by 10 pm on Tuesday 13 October, 72 hours after it paid.40

Fourth, the copied database is a separate question under the Privacy Act, whether or not a ransom was paid. The subsidiary must assess whether the copying is likely to cause customers serious harm, which would broadly make it an eligible data breach. If it has reasonable grounds to believe that it is, it must tell the Commissioner and the customers as soon as practicable.41

Finally, if the subsidiary misses the Thursday deadline, it risks a civil penalty of up to $109,200, and the report is still owed.42

What steps should a group take before and after a ransomware payment?

A group with a business in Australia, such as the electronics maker in the example, should take four steps.

  1. Work out now which companies in the group must report, using each company’s own turnover for the last Australian financial year, as explained above.43
  2. Make sure that whoever may pay a ransom for the group, including a negotiator, tells each affected Australian company at once, because its 72 hours run from when it learns of the payment.44
  3. From the start of an attack, record the incident, the demand, the payment and every communication with the attacker, which the report must describe.45
  4. Put both deadlines, for the ransomware report and for the data breach notice, in the group’s data breach response plan, its written plan for handling a breach.46

What is not settled (as at 4 November 2026)

  • It is unclear whose turnover counts, because neither the Cyber Security Act nor the rules made under it define ‘annual turnover’ or say whether a group’s turnover is added together. Income tax law defines a company’s own annual turnover, and separately an ‘aggregated turnover’ that adds in connected companies, but the Cyber Security Act borrows only its meaning of ‘business’.47 For an overseas company that carries on business here directly, the words could mean the turnover of the whole company or only of its Australian business. In practice, the cautious course is to count the turnover of the whole company.
  • Part 3 does not require the incident, the demand or the payment to take place in Australia. What Part 3 requires is that the company that reports carries on business in Australia and was affected by the incident.48 Read literally, the words mean that a foreign company that carries on business in Australia, and pays a ransom after an attack on its plant in Europe, must report the payment in Australia.
  • The Cyber Security Act does not say whether one report can meet the duties of two companies that must each report.49 In practice, where a parent and a subsidiary both qualify, the cautious course is to make a report for each.
  • The data breach deadline may come into line with the ransomware one. Under the exposure draft of the Privacy Amendment (Personal Data Protection) Bill 2026, a company would have 72 hours to give the Commissioner its statement about an eligible data breach.50 The consultation paper reasons that this period aligns with other laws, including the Cyber Security Act, and confirms that the 30 days for assessing a suspected breach would stay.51

Questions

Do we have to report a ransomware attack if we do not pay?
There is no duty to report under the ransomware payment rules, which apply only once a payment or other benefit is given. If personal information was accessed or taken, the Privacy Act may still require an assessment and a statement to the Australian Information Commissioner.
A negotiator paid the ransom for us. Do we still report?
The company still reports if it meets the turnover test, because the duty covers a payment that another entity makes on the company’s behalf. Its 72 hours run from when it becomes aware that the payment was made.
Does giving the report waive legal professional privilege?
Giving the report generally does not affect a claim of legal professional privilege, although the protection is lost in a coronial inquiry, a Royal Commission and certain cases against Commonwealth officers. Nor can anyone sue the company for damages over steps it takes in good faith to make the report.
Is a report made after the 72 hours have passed still required?
A late report is still required. The duty to report outlasts the 72 hours and continues until the report is made, but the delay counts as one breach, not a new breach for every extra day.
Anna Zheng, principal of SQ Legal
About the author

Anna Zheng is an Australian lawyer and the principal of SQ Legal. She advises Australian and international companies on data breaches and privacy. Her data and privacy work includes breach response plans that cover both the ransomware payment report and the data breach notice.

Contact Anna at [email protected]Email[email protected]Open in your default email appGmailOutlook (personal)Outlook (work or school)Or copy the address:[email protected].

This article is general information about Australian law as at the date shown above. It is not legal advice and does not take account of your circumstances. Reading it does not create a lawyer–client relationship with SQ Legal. Obtain advice on your own matter before acting. See the terms of use.

More on data and privacy, or contact SQ Legal about a matter.

Cite this article

Anna Zheng, ‘Who must report a ransomware payment in Australia within 72 hours?’, SQ Legal (Web Page, 16 November 2026) <https://sqlegal.com.au/insights/ransomware-payment-reporting-australia/>.

You may quote short extracts with attribution and a link to this page. To republish the article in full, write to [email protected]Email[email protected]Open in your default email appGmailOutlook (personal)Outlook (work or school)Or copy the address:[email protected].

Footnotes

  1. Cyber Security Act 2024 (Cth) ss 26(2), 27(1) (‘Cyber Security Act’); Cyber Security (Ransomware Payment Reporting) Rules 2025 (Cth) s 6(1) (‘Ransomware Rules’). ↩

  2. Cyber Security Act (n 1) ss 5, 26(1)(e), (2)(a). ↩

  3. Neither Act deems a notice under the other to satisfy its own requirements: Cyber Security Act (n 1) pt 3; Privacy Act 1988 (Cth) pt IIIC (‘Privacy Act’). ↩

  4. Cyber Security Act (n 1) s 27(1). ↩

  5. Ibid ss 2(1) table item 3, 26(2); Ransomware Rules (n 1) s 2(1). ↩

  6. Cyber Security Act (n 1) s 26(2)(a); Ransomware Rules (n 1) s 6(1). ↩

  7. Cyber Security Act (n 1) s 26(2)(b); Security of Critical Infrastructure Act 2018 (Cth) s 12L (‘Security of Critical Infrastructure Act’). ↩

  8. Security of Critical Infrastructure Act (n 7) s 30BB(1); Security of Critical Infrastructure (Application) Rules (LIN 22/026) 2022 (Cth) s 5(1), (3); Cyber Security Act (n 1) s 26(2)(a)(iii), (b). ↩

  9. Cyber Security Act (n 1) s 26(2); Acts Interpretation Act 1901 (Cth) s 2B (definition of ‘financial year’) (‘Acts Interpretation Act’). ↩

  10. Ransomware Rules (n 1) s 6(2); Cyber Security Act (n 1) s 26(3)(a). ↩

  11. Cyber Security Act (n 1) s 26(2)(a)(i); Explanatory Statement, Cyber Security (Ransomware Payment Reporting) Rules 2025 (Cth) attachment A (notes on s 6), attachment B; ‘Ransomware Payment and Cyber Extortion Payment Reporting’, Australian Signals Directorate (Web Page) <https://www.cyber.gov.au/ransomware-payment-and-cyber-extortion-payment-reporting>. ↩

  12. Cyber Security Act (n 1) s 26(2)(a)(i); Privacy Act (n 3) s 6D(9). ↩

  13. Cyber Security Act (n 1) ss 5, 26(2)(a). ↩

  14. Ibid s 8 (definition of ‘business’). ↩

  15. Ibid ss 26(1), 27(1). ↩

  16. Ibid s 26(1)(e). ↩

  17. Ibid s 8 (definition of ‘benefit’). ↩

  18. Ibid ss 25–32. ↩

  19. Ibid s 27(1). ↩

  20. Ibid s 26(1)(e). ↩

  21. Ibid ss 26(1)(c)–(e), (2), 27(1). ↩

  22. Ibid s 27(2). ↩

  23. Ransomware Rules (n 1) s 7(2)–(7). ↩

  24. Cyber Security Act (n 1) ss 8 (definition of ‘designated Commonwealth body’), 27(4); Acts Interpretation Act (n 9) s 19A(1). ↩

  25. ‘Ransomware Payment and Cyber Extortion Payment Reporting’ (n 11). ↩

  26. Cyber Security Act (n 1) ss 29(1), 30(1)–(2). ↩

  27. Ibid ss 29(2), 30(3). ↩

  28. Ibid s 32(1)–(3). ↩

  29. Ibid ss 30(1), 32(1) and the notes to those subsections. ↩

  30. Ibid ss 28(1), 31(1)–(2). ↩

  31. Cyber Security Act (n 1) ss 8 (definition of ‘Secretary’), 27(5), 79(1), (3)–(4), (7); Acts Interpretation Act (n 9) s 19A(1). ↩

  32. Cyber Security Act (n 1) ss 27(5), 79(1); Regulatory Powers (Standard Provisions) Act 2014 (Cth) s 82(5) (‘Regulatory Powers Act’); Crimes Act 1914 (Cth) s 4AA(1), (3); Crimes (Amount of a Penalty Unit) Instrument 2026 (Cth) s 5; ‘Fines and Penalties’, Australian Securities and Investments Commission (Web Page) <https://www.asic.gov.au/about-asic/asic-investigations-and-enforcement/fines-and-penalties>. ↩

  33. Cyber Security Act (n 1) s 82(1)–(3). ↩

  34. Regulatory Powers Act (n 32) s 93(1); Cyber Security Act (n 1) s 27(6). ↩

  35. Cyber Security Act (n 1) pt 3; Privacy Act (n 3) pt IIIC. ↩

  36. Cyber Security Act (n 1) ss 26–27; Ransomware Rules (n 1) s 6. ↩

  37. Privacy Act (n 3) ss 6C(1), 6D(1), 6D(9), 13(4A), 26WE(2), 26WH(2), 26WK(2), 26WL. ↩

  38. Cyber Security Act (n 1) s 26(1), (2)(a); Ransomware Rules (n 1) s 6(1). ↩

  39. Cyber Security Act (n 1) s 27(1)–(2). The Regulatory Powers Act attributes to a company an element of a civil penalty provision done by its employee, agent or officer acting within their actual or apparent authority: Regulatory Powers Act (n 32) s 97. ↩

  40. Cyber Security Act (n 1) ss 26(1)–(2), 27(1). ↩

  41. Privacy Act (n 3) ss 26WE(2), 26WH(2), 26WK(2), 26WL(3). ↩

  42. Cyber Security Act (n 1) s 27(5); Regulatory Powers Act (n 32) ss 82(5), 93(1). ↩

  43. Cyber Security Act (n 1) s 26(2)–(3); Ransomware Rules (n 1) s 6. ↩

  44. Cyber Security Act (n 1) s 27(1). ↩

  45. Ibid s 27(2); Ransomware Rules (n 1) s 7. ↩

  46. Cyber Security Act (n 1) s 27(1); Privacy Act (n 3) ss 26WH(2), 26WK(2). ↩

  47. Cyber Security Act (n 1) ss 8, 26(2)(a)(i); Ransomware Rules (n 1) s 6; Income Tax Assessment Act 1997 (Cth) ss 328-115, 328-120. ↩

  48. Cyber Security Act (n 1) ss 5, 26(1), (2)(a). ↩

  49. Ibid ss 26(2), 27(1). ↩

  50. Exposure Draft, Privacy Amendment (Personal Data Protection) Bill 2026 (Cth) sch 3 item 10, inserting proposed s 26WK(1)–(2). ↩

  51. Attorney-General’s Department, Privacy Reform (Consultation Paper, August 2026) 25 <https://consultations.ag.gov.au/rights-and-protections/privacy-reform/user_uploads/consultation_paper.pdf>. ↩

Sources

  1. Cyber Security Act 2024 (Cth)
  2. Cyber Security (Ransomware Payment Reporting) Rules 2025 (Cth)
  3. Security of Critical Infrastructure Act 2018 (Cth)
  4. Security of Critical Infrastructure (Application) Rules (LIN 22/026) 2022 (Cth)
  5. Income Tax Assessment Act 1997 (Cth)
  6. Acts Interpretation Act 1901 (Cth)
  7. Privacy Act 1988 (Cth)
  8. Regulatory Powers (Standard Provisions) Act 2014 (Cth)
  9. Crimes Act 1914 (Cth)
  10. Crimes (Amount of a Penalty Unit) Instrument 2026 (Cth)
  11. Explanatory Statement, Cyber Security (Ransomware Payment Reporting) Rules 2025 (Cth)
  12. Exposure Draft, Privacy Amendment (Personal Data Protection) Bill 2026 (Cth)
  13. Attorney-General’s Department, Privacy Reform (Consultation Paper, August 2026)
  14. ‘Fines and Penalties’, Australian Securities and Investments Commission (Web Page)
  15. ‘Ransomware Payment and Cyber Extortion Payment Reporting’, Australian Signals Directorate (Web Page)