Cyber Security Act 2024: the ransomware payment report, the other Parts, and what a website test can show
The Cyber Security Act 2024 provides for security standards for smart devices, a 72-hour report after a ransomware payment, voluntary information sharing with the National Cyber Security Coordinator and a Cyber Incident Review Board.
This guide reads the Act and the ransomware and smart device rules made under it, section by section, places the ransomware payment clock beside the Privacy Act and SOCI Act clocks, and is plain that the Act does not ask for a website test. It comes with a reporting timeline and evidence pack you can fill in.
In this guide
Ransomware payment reporting timeline and evidence pack
A sixteen-row timeline and evidence pack built from Part 3 of the Cyber Security Act 2024 and section 7 of the Ransomware Payment Reporting Rules, with the Privacy Act assessment clock and the SOCI Act incident clocks placed beside the 72-hour report, and a row each for Parts 2, 4 and 5. Rows R1 to R4 are prepared before any incident: whether the duty applies, which other clocks apply, who decides and reports, and the facts about each website and application.
How to use itHide the instructions
Rows R5 to R12 follow an incident from the first sign to the time after the report; the Part 3 clock starts at R9, when the payment is made or the business becomes aware of it. R13 records recovery and any test after the cleanup, and R14 to R16 cover the other Parts. The text column gives each provision in its own words or a close short form with its section. No row sends test requests to any system: each one records facts, decisions or documents, and R13 records a test that runs under its own written scope and authorisation, with that test's limits set out on the row. The test column begins with Nothing in twelve of the sixteen rows, because no duty in the Act is a test of a website or application. The pack records evidence. Whether a duty applies and whether it was met is for the business and its lawyer or privacy adviser, with the Department of Home Affairs administering the Act.
16 rows
Row and record
When it falls
R1. Reporting business entity check
- When it falls
- Before any incident, and again each time a financial year closes.
- What the text says, with its section
- Cyber Security Act 2024 subsection 26(2): an entity is a reporting business entity if, at the time the ransomware payment is made, it is carrying on a business in Australia with an annual turnover for the previous financial year that exceeds the turnover threshold for that year, and is not a Commonwealth body or a State body, and is not a responsible entity for a critical infrastructure asset; or it is a responsible entity for a critical infrastructure asset to which Part 2B of the Security of Critical Infrastructure Act 2018 applies. Ransomware Payment Reporting Rules subsection 6(1): the threshold is $3 million; subsection 6(2) gives a formula for a business carried on for only part of the previous financial year.
- What to keep
- The previous financial year's annual turnover as your accountant states it and the date of that figure; whether the business was carried on for only part of that year; whether the business is the responsible entity for a critical infrastructure asset; the adviser who answered the question, and the date.
- What a website or application test can supply
- Nothing. Turnover and critical infrastructure status are facts about the business, not about a website.
- What it cannot show, and who decides
- Whether the business is a reporting business entity. The business decides with its accountant and lawyer. The Act applies the test at the time a payment is made, so an earlier answer can go out of date.
- Limits of this row
- Read-only row: it records figures and advice and sends no requests to any system.
R2. Which other reporting clocks could apply
- When it falls
- Before any incident, and again when the business, the information it holds or its assets change.
- What the text says, with its section
- Privacy Act 1988 subsection 26WE(1): section 26WE, which defines an eligible data breach, applies in the cases it lists, among them an APP entity that holds personal information and is required under section 15 not to do an act, or engage in a practice, that breaches Australian Privacy Principle 11.1 in relation to it. Security of Critical Infrastructure Act 2018 subsection 30BB(1): Part 2B applies to a critical infrastructure asset that is specified in the rules, or is the subject of a declaration under section 51 that determines Part 2B applies to it, subject to subsection 30BB(3), under which the rules may provide that Part 2B does not apply to an asset for a period after it becomes a critical infrastructure asset.
- What to keep
- For each regime: whether it applies, who said so and when. For the Privacy Act, your privacy adviser's answer; for Part 2B, the rules or the section 51 declaration that brings your asset within it. Name the person who would lead each assessment or report.
- What a website or application test can supply
- Nothing. Whether a regime applies is a legal question.
- What it cannot show, and who decides
- Whether either regime applies. Ask your privacy adviser for the Privacy Act and your lawyer for the SOCI Act.
- Limits of this row
- Read-only row: it records advice and sends no requests.
R3. Decision owners and reporters
- When it falls
- Before any incident, and whenever one of the people named changes.
- What the text says, with its section
- Subsection 27(1): the reporting business entity must give the designated Commonwealth body a ransomware payment report within 72 hours of making the ransomware payment or becoming aware that it has been made. Subsection 85(2): an obligation the Act purports to impose on an entity that is not a legal person is imposed on each person who is an accountable person for the entity at the time the obligation arises or is in operation; subsection 85(4) says who that is for a partnership, a trust and an unincorporated association.
- What to keep
- A named owner and a deputy for each decision an incident forces: who decides how the business responds to a demand, who may approve spending on the business's behalf during an incident, who completes and submits a ransomware payment report, who leads a Privacy Act assessment, who gives any SOCI Act report, and who speaks to the insurer and the police. Add out-of-hours contact details and the lawyer each person calls.
- What a website or application test can supply
- Nothing.
- What it cannot show, and who decides
- Who those people should be. That is the business's own governance decision.
- Limits of this row
- Read-only row: it records names and contacts and sends no requests.
R4. Website and application facts, kept ready
- When it falls
- Before any incident, and again when a site or application is added, moved or materially changed.
- What the text says, with its section
- Ransomware Payment Reporting Rules subsection 7(4): if a report is made, its information about the cyber security incident must include, among other items, the impact of the incident on the reporting business entity's infrastructure (paragraph (c)) and on its customers (paragraph (d)).
- What to keep
- One line for each website, store, portal and API: its addresses, who built it, who hosts it, what personal or payment information it holds, which customers use it and for what, the outside services it depends on, where its backups are kept, and the date and scope of the last security test of it.
- What a website or application test can supply
- A test report gives the scope as tested and the build and dates it covered, which fills the last field. A Clever Ops web application test reports any older API version that still answers, and such a version may be an address missing from this list.
- What it cannot show, and who decides
- The impact of a real incident. That is established during the incident by the business and its responders.
- Limits of this row
- Read-only row: it compiles records you already hold and sends no requests.
R5. Incident noticed: start the log
- When it falls
- Hour 0, when anyone notices something wrong. The clocks in R6 and R7 run from awareness, so they may start here; the Part 3 clock does not start until R9.
- What the text says, with its section
- Ransomware Payment Reporting Rules paragraphs 7(4)(a) and (b): if a report is made, it must include when the incident occurred or is estimated to have occurred, and when the reporting business entity became aware of the incident.
- What to keep
- A written log with the time, what was seen, where, who noticed and how, then every later step with its time and the person who took it. The hacked website guide sets out the first hour for a compromised website, including the evidence to keep.
- What a website or application test can supply
- Nothing while the incident is live. Incident response, forensics and malware cleanup are outside what Clever Ops sells.
- What it cannot show, and who decides
- When the incident began. An incident responder's findings answer that, and the estimate can change as they work.
- Limits of this row
- Read-only row: it records what people saw and sends no requests to the affected systems.
R6. SOCI Act Part 2B clock, only if R2 says it applies
- When it falls
- From the time the responsible entity becomes aware of the incident and its impact: 12 hours or 72 hours, as the next column sets out.
- What the text says, with its section
- Security of Critical Infrastructure Act 2018, compilation of 4 June 2026. Section 30BC: for a cyber security incident that has had, or is having, a significant impact (whether direct or indirect) on the availability of the asset, a report to the relevant Commonwealth body as soon as practicable, and in any event within 12 hours, after the entity becomes so aware; a written record of an oral report within 84 hours after it is given. Section 30BD: for an incident that has occurred, is occurring or is imminent and has had, is having, or is likely to have, a relevant impact on the asset, a report to the relevant Commonwealth body as soon as practicable, and in any event within 72 hours, after the entity becomes so aware; a written record of an oral report within 48 hours after it is given.
- What to keep
- The time of awareness, the asset, the section each report was made under, the time and form of each report and written record, and who gave it.
- What a website or application test can supply
- Nothing towards the report itself.
- What it cannot show, and who decides
- Whether the impact is significant or relevant as that Act defines those words. The responsible entity decides with its lawyer.
- Limits of this row
- Read-only row: it records reports and sends no requests.
R7. Privacy Act assessment clock, only if R2 says it applies
- When it falls
- From the time the entity becomes aware of reasonable grounds to suspect an eligible data breach, while it is not yet aware of grounds to believe there was one: the assessment within 30 days.
- What the text says, with its section
- Privacy Act 1988, compilation of 4 June 2026. Subsection 26WH(1): the section applies if an entity is aware that there are reasonable grounds to suspect that there may have been an eligible data breach of the entity, and is not aware that there are reasonable grounds to believe that the relevant circumstances amount to an eligible data breach of the entity. Subsection 26WH(2): the entity must carry out a reasonable and expeditious assessment of whether there are reasonable grounds to believe that the relevant circumstances amount to an eligible data breach, and take all reasonable steps to ensure that the assessment is completed within 30 days after it becomes aware. Section 26WK: once aware that there are reasonable grounds to believe there has been an eligible data breach, it must prepare a statement and give a copy to the Commissioner as soon as practicable. Subsection 26WL(3): notification under subsection 26WL(2) as soon as practicable after the statement is prepared.
- What to keep
- The date and time the entity became aware of grounds to suspect, who carried out the assessment, the information each affected website or application holds (from R4), the conclusion and its date, and any statement given and notifications made.
- What a website or application test can supply
- A test report from before the incident shows which findings were recorded on the build tested at that time, which the people making the assessment may weigh. It does not show what happened in the incident.
- What it cannot show, and who decides
- Whether there was an eligible data breach. The entity decides with its privacy adviser.
- Limits of this row
- Read-only row: it records the assessment and sends no requests.
R8. Demand received
- When it falls
- When an extorting entity makes a demand of the business, or of any other entity, in order to benefit from the incident or its impact on the business.
- What the text says, with its section
- Paragraph 26(1)(d): an entity (the extorting entity) makes a demand of the reporting business entity, or any other entity, in order to benefit from the incident or the impact on the reporting business entity. Rules subsection 7(5): if a report is made, it must include the amount or quantum demanded, or a description of a non-monetary benefit demanded, and the method of provision demanded. Rules subsection 7(7): the nature and timing of any communications with the extorting entity, a brief description of them (if any), and a brief description of any pre-payment negotiations.
- What to keep
- The demand exactly as received, with the time, the channel and the address or account it came from; every later communication, with its date, time and a brief description; and the people from R3 who were told, and when.
- What a website or application test can supply
- Nothing.
- What it cannot show, and who decides
- What the business does about the demand. This page gives no view on it; the decision belongs to the people in R3 and their advisers. The Department's factsheet says no report is required where a demand was made but no payment was provided.
- Limits of this row
- Read-only row: it records what was received and sends nothing.
R9. Payment made, or the business becomes aware of one: the 72-hour clock starts
- When it falls
- Hour 0 of the Part 3 clock: when the reporting business entity makes the ransomware payment, or becomes aware that the ransomware payment has been made, whichever is applicable.
- What the text says, with its section
- Subsection 27(1): a ransomware payment report within 72 hours of making the ransomware payment or becoming aware that the ransomware payment has been made (whichever is applicable). Paragraph 26(1)(e): a payment or benefit to the extorting entity that is directly related to the demand, provided by the reporting business entity, or provided by another entity on its behalf where the reporting business entity is aware of it. Rules subsection 7(6): the amount or quantum of the payment, or a description of a non-monetary benefit, and the method of provision. Rules subsection 7(3): where another entity made the payment, its contact and business details, including its ABN (if any) and address.
- What to keep
- The date, time and time zone of the payment and of the moment the business became aware of it; who made it; the amount or quantum, or a description of the benefit; the method of provision; any transaction reference; and the reporting deadline, written as the date and time 72 hours later.
- What a website or application test can supply
- Nothing.
- What it cannot show, and who decides
- Whether Part 3 applies to the payment. The business decides with its lawyer, using R1 and the conditions in subsection 26(1).
- Limits of this row
- Read-only row: it records a transaction and sends nothing.
R10. Affected website or application facts for the report
- When it falls
- Between R9 and R11, gathered within the 72 hours.
- What the text says, with its section
- Rules subsection 7(4): the incident information must include (c) the impact on the reporting business entity's infrastructure; (d) the impact on its customers; (e) what variants (if any) of ransomware or other malware were used; (f) what vulnerabilities (if any) in the reporting business entity's system were exploited; and (g) information that could assist the response to, mitigation or resolution of the incident by a Commonwealth body or State body. Note to subsection 7(1): information is only required to the extent the entity knows or is able, by reasonable search or enquiry, to find out within the 72 hour time period.
- What to keep
- For each website or application from R4 that the incident touched: what stopped working and when; what customers could not do, or could have been exposed to; what the responder has found so far about malware and the way in, with the source and time of each finding; and what is still unknown. The Department's how-to guide says you may select Unknown on the form for malware variants or exploited vulnerabilities you do not know at the time you make your report.
- What a website or application test can supply
- A test report from before the incident lists the findings recorded on the build tested at that time, which a responder can compare with the way in they identify.
- What it cannot show, and who decides
- What was exploited in this incident. That comes from incident response and forensic work, which Clever Ops does not provide, and the business decides what goes in its report.
- Limits of this row
- Read-only row: it gathers findings from people and documents and sends no requests to the affected systems. Any examination of those systems is the responder's.
R11. Report given within 72 hours
- When it falls
- Before the deadline written in R9.
- What the text says, with its section
- Subsection 27(1): the report goes to the designated Commonwealth body, which section 8 defines as a Department, or a body established by a law of the Commonwealth, specified in the rules or, if no rules are made for that purpose, the Department and ASD. Subsection 27(2): information that the reporting business entity knows, or is able by reasonable search or enquiry to find out, at the time of making the report, relating to (a) the reporting business entity's contact and business details, if it made the payment; (b) the paying entity's details, if another entity made it; (c) the incident and its impact; (d) the demand; (e) the payment; and (f) communications with the extorting entity. Subsection 27(3): other information about the incident may be included. Subsection 27(4): in the form approved by the Secretary (if any) and in the manner (if any) prescribed by the rules. Subsection 27(5): a civil penalty of 60 penalty units for contravening subsection 27(1).
- What to keep
- A copy of everything you entered, made before you submit; the submission date and time; who submitted it; and the reference number. The Department's how-to guide says the form is reached from the ReportCyber landing page on cyber.gov.au, and its factsheet says a unique reference identification number is generated on submission and a copy of the report will not be provided, so keep your own.
- What a website or application test can supply
- Nothing. The report is the business's own statement.
- What it cannot show, and who decides
- Whether the report met section 27. That is for the business and its lawyer; the Department's factsheet says the Department of Home Affairs monitors compliance with the obligation to report.
- Limits of this row
- Read-only row: it records a submission and sends no requests. The person named in R3 completes the form.
R12. Permitted use of report information
- When it falls
- After the report, and whenever anyone asks how it will be used.
- What the text says, with its section
- Subsection 29(1): a designated Commonwealth body may make a record of, use or disclose the information only for the purposes listed, which include assisting the reporting business entity to respond to, mitigate or resolve the incident. Subsection 29(2): it must not do so to investigate or enforce a contravention by the reporting business entity of a Commonwealth, State or Territory law other than Part 3 or a law that imposes a penalty or sanction for a criminal offence. Subsection 29(4): subsection 29(1) does not prohibit recording, use or disclosure of information already lawfully made available to the public, or of information given to comply with a requirement the subsection lists, such as a requirement in Part 2B of the Security of Critical Infrastructure Act 2018. Section 30: the same limits for others who obtain the information, with exceptions in subsection 30(5). Section 31: providing it does not otherwise affect a claim of legal professional privilege, except in the proceedings listed. Section 32: it is not admissible against the reporting business entity in the proceedings listed, with the exceptions listed.
- What to keep
- Who in the business holds the copy from R11; who it was shared with outside the business, such as an insurer, a responder or a lawyer, and when; and any question asked about its use, with the answer and who gave it.
- What a website or application test can supply
- Nothing.
- What it cannot show, and who decides
- How these sections apply to your report. Ask your lawyer.
- Limits of this row
- Read-only row: it records who holds the report and sends nothing.
R13. Recovery, and a test after the cleanup
- When it falls
- After the cleanup specialist reports the work finished, including how the way in was closed or, where it was never found, what was done in its place.
- What the text says, with its section
- Part 3 contains no testing provision; section 27 sets its reporting duty. Section 23, which mentions testing, concerns the examination of a relevant connectable product.
- What to keep
- The responder's report; the date the site or application went back into service and the build that went back; the scope and dates of any test of it; and the retest status of each finding.
- What a website or application test can supply
- A test of the cleaned site or application shows how its controls behaved on the build and accounts tested, with a negative result kept for each check that found nothing. After the Clever Ops retest, every finding carries a status: fixed, partially fixed, still reproducible or not retested.
- What it cannot show, and who decides
- What happened during the incident, or that nothing was left behind. Section 27 does not ask for a test, and a test result is not a finding that the business meets the Act.
- Limits of this row
- Records row: it sends nothing itself. The test it records runs under its own written scope and signed authorisation, on the business's own systems only and on a staging copy where one matches production, from test accounts that hold invented records and never a real customer's, with no load or denial-of-service testing, and with any email or text it triggers going to an address or number the business controls. If the test shows another person's real data, the tester stops and records where it appeared. Passwords, keys, tokens and links that work for whoever holds them stay out of this record. A vendor's own product or platform is not part of the test: Clever Ops does not test one.
R14. Part 2: smart device security standards
- When it falls
- Part 2 and Schedule 1 of the Smart Devices Rules commence on the day after the end of the period of 12 months beginning on the day the rules were registered; the information column gives 4 March 2026.
- What the text says, with its section
- Sections 15 and 16 of the Act: duties on manufacturers and suppliers of relevant connectable products in a class the rules cover, where they are aware, or could reasonably be expected to be aware, that the product will be acquired in Australia in the specified circumstances, with an exception to section 15 in subsection 15(5). Smart Devices Rules subsection 8(1): relevant connectable products intended by the manufacturer to be used, or of a kind likely to be used, for personal, domestic or household use or consumption, other than the products it excludes, among them desktop computers, laptops, tablet computers and smartphones; subsection 8(2): acquired in Australia by a consumer. Schedule 1: passwords (clause 2), publishing how to report security issues (clause 3) and publishing a defined support period (clause 4), with subclause 4(7) applying where the manufacturer offers to supply the product on its own website or another website under its control.
- What to keep
- Only for a business that manufactures or supplies such products: the statement of compliance for each product, kept for the 5 years section 10 of the rules sets, and, for a manufacturer that offers to supply the product on its own website or another website under its control, where the defined support period is published alongside, or otherwise given equal prominence to, each publication of the product's main characteristics.
- What a website or application test can supply
- Nothing towards the standard. A website test does not examine a product; under section 23 the Secretary may engage an expert to examine one.
- What it cannot show, and who decides
- Whether a product complies. The statement of compliance carries the manufacturer's declaration, and an examination under section 23 is the expert's. A business that neither manufactures nor supplies these products has nothing to keep in this row.
- Limits of this row
- Read-only row: it files documents and reads your own published product pages as any visitor would; it sends no test requests.
R15. Part 4: voluntary sharing with the National Cyber Security Coordinator
- When it falls
- At any time during the response to the incident, if the business chooses to share.
- What the text says, with its section
- Subsection 35(2): an impacted entity, or another entity acting on its behalf, may provide information about the incident to the National Cyber Security Coordinator if the incident is, or could reasonably be expected to be, a significant cyber security incident. Note to subsection 35(3): there is no obligation to provide information in response to a request. Section 44: information provided under Part 4 does not affect any other requirement to provide it under the Act or another law of the Commonwealth.
- What to keep
- What was shared, when, by whom, and in response to what request, if any. The Department's factsheet says voluntarily providing information to the Coordinator does not meet the requirement under section 27. Sharing here does not replace R11.
- What a website or application test can supply
- Nothing.
- What it cannot show, and who decides
- Whether to share. That is the business's choice, with its lawyer.
- Limits of this row
- Read-only row: it records what was shared and sends nothing.
R16. Part 5: a Cyber Incident Review Board review
- When it falls
- Only after the incident and the immediate response have ended, and only if the Board conducts a review.
- What the text says, with its section
- Subsection 46(2): a review may only be conducted if the Board is satisfied the incident meets the criteria in subsection 46(3), after the incident and the immediate response has ended, and if the Minister has approved the terms of reference. Section 48: the Chair may request information or documents, and Note 1 to the section says there is no requirement to comply. Section 49: where the Board reasonably believes that an entity involved in the incident has a document relevant to the review, and the Chair has requested it under section 48, the Chair may require that entity, other than a Commonwealth body or a State body or an officer or employee of one, to produce it or copies of it within a period of not less than 14 days. Section 50: a civil penalty of 60 penalty units for failing to comply, subject to the exceptions in subsection 50(2).
- What to keep
- The log, decisions, reports and the responder's and tester's documents from this table, kept together so a request can be answered from them; and each request or notice, its date, its deadline and what was produced.
- What a website or application test can supply
- Nothing the Part asks for. A test report the business holds is one of its documents like any other.
- What it cannot show, and who decides
- Whether a document is relevant to a review. Section 49 turns on the Board's belief; how to answer a notice is a question for your lawyer.
- Limits of this row
- Read-only row: it records requests and documents and sends nothing.
The Cyber Security Act 2024 at a glance
The Cyber Security Act 2024 is Act No. 98 of 2024, assented to on 29 November 2024.
The Federal Register of Legislation lists it under title ID C2024A00098 as an Act in force, administered by the Department of Home Affairs. When this guide was checked on 15 November 2026, the register's version of the Act was the Act as made on 29 November 2024, registered on 5 December 2024, and this guide quotes that text by section number. Before you rely on a section, check the register for a later version.
Section 4 of the Act, its simplified outline, describes among other things: mandatory security standards for certain products that can directly or indirectly connect to the internet, which it calls relevant connectable products; an obligation to report ransomware payments; voluntary provision of information to the National Cyber Security Coordinator about a significant cyber security incident; and a Cyber Incident Review Board.
The Department of Home Affairs, on its page for the Act, lists four measures: minimum cyber security standards for smart devices, a mandatory ransomware and cyber extortion reporting obligation for certain businesses, a Limited Use obligation for the National Cyber Security Coordinator, and a Cyber Incident Review Board. Section 5 says the Act applies both within and outside Australia.
Each measure has its own audience. The smart device standards bind manufacturers and suppliers of the products a rule covers. The ransomware payment report falls on a reporting business entity, a term subsection 26(2) defines. Information sharing with the Coordinator is voluntary. The Review Board can ask, and in some cases require, an entity involved in an incident under review to produce documents.
This guide concentrates on the second measure. Its duty arises only after a ransomware payment has been made, under the conditions set out below.
The reader in mind is an owner, manager or technical lead who has met the Act in a board paper, an insurer's proposal form, a customer's questionnaire or an incident response plan. The guide reads the text and stops there: it gives no legal advice, audits nothing, and leaves every decision about applying the Act to the business and the advisers it chooses.
How each Part commences, from the Act and the rules
Section 2 of the Act gives the Parts different starts.
Part 1, Part 4, and Parts 6 and 7 commence on the day after the Act receives the Royal Assent, and the table's information column gives that day as 30 November 2024. Parts 2, 3 and 5 were each to commence on a single day fixed by Proclamation.
If Part 2 did not commence within the period of 12 months beginning on the day of Royal Assent, it commences on the day after the end of that period; Parts 3 and 5 carry the same fallback with a period of 6 months. Subsection 2(2) says the information column is not part of the Act.
The rules carry their own commencement clauses. The Cyber Security (Ransomware Payment Reporting) Rules 2025, registered on 3 March 2025, commence at the later of the start of the day after they were registered and the time Part 3 of the Act commences.
The Department of Home Affairs says on its page for the Act that the ransomware payment reporting rules start from 30 May 2025, and its factsheet says mandatory reporting is active from that date.
The same factsheet describes an education-first phase from 30 May 2025 to 31 December 2025, followed by a compliance and education approach from 1 January 2026 onwards.
The Cyber Security (Security Standards for Smart Devices) Rules 2025 were registered on 4 March 2025. Their Part 1 commences on the day of registration, and their Part 2 and Schedule 1, which hold the standard itself, commence on the day after the end of the period of 12 months beginning on that day; the information column gives 4 March 2026.
For the Review Board, the Department's page says members will be appointed after the beginning of the Cyber Security (Cyber Incident Review Board) Rules 2025 on 30 May 2025.
The register lists the ransomware and smart device rules as in force, and due to sunset on 1 April 2035.
Ransomware payment reporting in Australia: who is a reporting business entity
Part 3 applies only when every condition in subsection 26(1) is met: (a) an incident has occurred, is occurring or is imminent; (b) the incident is a cyber security incident; (c) the incident has had, is having, or could reasonably be expected to have, a direct or indirect impact on a reporting business entity; (d) an entity, which the Act calls the extorting entity, makes a demand of the reporting business entity, or any other entity, in order to benefit from the incident or the impact on the reporting business entity; and (e) the reporting business entity provides, or is aware that another entity has provided on their behalf, a payment or benefit to the extorting entity that is directly related to the demand. That payment or benefit is the ransomware payment.
Cyber security incident has a defined meaning. Section 9 defines it partly by reference to the Security of Critical Infrastructure Act 2018 and then narrows it: under subsection 9(2) an incident counts only if one of the listed conditions is met, which include that it involves the activities of a corporation to which paragraph 51(xx) of the Constitution applies, or is or was effected by means of a telegraphic, telephonic or other like service, the Act's example being the internet. Subsection 26(4) adds a presumption for Part 3 that subsection 26(5) limits.
Subsection 26(2) defines who carries the duty. An entity is a reporting business entity if, at the time the ransomware payment is made, either (a) it is carrying on a business in Australia with an annual turnover for the previous financial year that exceeds the turnover threshold for that year, and it is not a Commonwealth body or a State body, and it is not a responsible entity for a critical infrastructure asset; or (b) it is a responsible entity for a critical infrastructure asset to which Part 2B of the Security of Critical Infrastructure Act 2018 applies.
The rules set the figure. Subsection 6(1) of the Ransomware Payment Reporting Rules says the amount of turnover threshold for a business for the previous financial year is $3 million. Subsection 6(2) gives a formula for a business carried on for only part of the previous financial year: $3 million multiplied by the number of days in the part, divided by the number of days in the previous financial year.
The Department's own documents word the comparison in more than one way. Its factsheet describes, in one place, an annual turnover of $3 million or more within the last financial year and, in another, an annual turnover for the previous financial year that exceeds that figure; its how-to guide describes a turnover that is equal to or exceeds $3 million.
The Act's word, in subparagraph 26(2)(a)(i), is exceeds, and the simplified outline in section 5 of the rules uses the same word.
This page quotes the Act. If your turnover sits near the figure, or your business started part way through the year, put the question to your accountant and lawyer before you need the answer.
- The test is applied at the time the payment is made, using the previous financial year's turnover, so the answer can change from one year to the next.
- Subsection 85(2) says an obligation the Act purports to impose on an entity that is not a legal person is imposed on each person who is an accountable person for the entity at the time the obligation arises or is in operation, and subsection 85(4) says who that is for a partnership, a trust and an unincorporated association.
- Whether the business is a reporting business entity, and whether an incident is a cyber security incident, are questions for the business and its lawyer. This page does not answer them for any reader.
The Cyber Security Act ransomware payment report: what starts the clock and what it holds
Subsection 27(1) is the duty.
The reporting business entity must give the designated Commonwealth body a report, a ransomware payment report, that complies with section 27 within 72 hours of making the ransomware payment or becoming aware that the ransomware payment has been made, whichever is applicable. The clock starts at the payment or at awareness of it.
It does not start when the incident is noticed or when a demand arrives, and the Department's factsheet says entities are not required to report where a ransom or extortion demand was made but no payment was provided.
Section 8 defines the designated Commonwealth body as a Department, or a body established by a law of the Commonwealth, specified in the rules or, if no rules are made for that purpose, the Department and the Australian Signals Directorate (ASD).
The Ransomware Payment Reporting Rules as made specify none. The Department's factsheet says a reporting business entity has an obligation to make a report using the reporting form on ASD's website, and the Australian Cyber Security Centre's report page lists reporting a ransomware or cyber extortion payment to the Department of Home Affairs among its options.
The Department's how-to guide says the form is reached from the ReportCyber landing page on cyber.gov.au by reporting on behalf of a business or organisation.
Subsection 27(2) lists what the report must contain, in accordance with any requirements the rules prescribe, and limits it to what the reporting business entity knows, or is able by reasonable search or enquiry to find out, at the time of making the report. Section 7 of the rules fills in each item:
- Contact and business details: the reporting business entity's if it made the payment, or the other entity's if another entity made it, in each case including the ABN (if any) and address (paragraphs 27(2)(a) and (b); rules subsections 7(2) and 7(3)).
- The cyber security incident and its impact (paragraph 27(2)(c); rules subsection 7(4)): when it occurred or is estimated to have occurred; when the entity became aware of it; its impact on the entity's infrastructure and on its customers; what variants (if any) of ransomware or other malware were used; what vulnerabilities (if any) in the entity's system were exploited; and information that could assist the response to, mitigation or resolution of the incident by a Commonwealth body or State body.
- The demand (paragraph 27(2)(d); rules subsection 7(5)): the amount or quantum demanded, or a description of a non-monetary benefit demanded, and the method of provision demanded.
- The payment (paragraph 27(2)(e); rules subsection 7(6)): the amount or quantum, or a description of a non-monetary benefit, and the method of provision.
- Communications with the extorting entity (paragraph 27(2)(f); rules subsection 7(7)): the nature and timing of any communications, a brief description of them (if any), and a brief description of any pre-payment negotiations about the demand or the payment.
Form, extra information and the penalty
Subsection 27(3) says the report may include other information relating to the incident. Subsection 27(4) says it must be given in the form approved by the Secretary, if any, and in the manner prescribed by the rules, if any. Subsection 27(5) makes a contravention of subsection 27(1) a civil penalty of 60 penalty units.
Subsection 28(1) says an entity is not liable to an action or other proceeding for damages for an act done or omitted in good faith in compliance with section 27.
The note to subsection 7(1) of the rules ties the content to the clock: information is only required to the extent the entity knows or is able, by reasonable search or enquiry, to find out within the 72 hour time period.
The Department's how-to guide says you may select Unknown on the form if you do not know which malware was used or which vulnerabilities were exploited at the time you make your report.
Its factsheet says a unique reference identification number is generated once the report is submitted, and that a copy of the report will not be provided. Keep your own copy of what you enter.
What this page does not cover
Part 3 deals with reporting a payment once one has been made. This page gives no view on whether a payment should be made in any incident. That decision, and the advice behind it, belongs to the business, its lawyer and whoever else it has engaged, such as an incident response provider and, where it holds a policy, its insurer.
How information in a ransomware payment report may be used
Division 3 of Part 3 limits what happens to a report.
Under subsection 29(1), a designated Commonwealth body may make a record of, use or disclose information in a ransomware payment report only for the purposes listed in paragraphs 29(1)(a) to (i). They include assisting the reporting business entity, and other entities acting on its behalf, to respond to, mitigate or resolve the incident; performing functions or exercising powers under Part 3, or Part 6 as it applies to Part 3; the functions of the National Cyber Security Coordinator under Part 4; informing and advising Ministers about a cyber security incident; and the functions of an intelligence agency.
Subsection 29(2) adds a restriction. The body must not make a record of, use or disclose the information to investigate or enforce, or assist in investigating or enforcing, a contravention by the reporting business entity of a Commonwealth, State or Territory law, other than a contravention of Part 3 or of a law that imposes a penalty or sanction for a criminal offence.
Subsection 29(3) says subsection 29(1) does not authorise recording, use or disclosure to the extent the Privacy Act 1988 prohibits or restricts it, and subsection 29(4) says subsection 29(1) does not prohibit recording, use or disclosure of information already lawfully made available to the public, or of information given to the body by or on behalf of the entity to comply with a requirement the subsection lists, among them a requirement in Part 2B of the Security of Critical Infrastructure Act 2018.
Section 30 places the same purposes and the same restriction on another entity or body that obtains the information under subsection 29(1) or section 30, with exceptions in subsection 30(5).
Sections 31 and 32 deal with proceedings. Under subsection 31(1), the fact that the entity provided information in a report does not otherwise affect a claim of legal professional privilege that anyone may make over it, except in the proceedings subsection 31(2) lists, among them a coronial inquiry or a Royal Commission.
Under section 32, information in a report that a Commonwealth body or State body obtained under section 27, subsection 29(1) or section 30, and holds, is not admissible in evidence against the reporting business entity in the proceedings subsection 32(2) lists, with exceptions that include proceedings for false or misleading information or obstruction offences that relate to the Act, civil proceedings for a civil penalty provision of Part 3, and the proceedings subsection 32(3) names.
Sections 30 and 32 are written about information obtained through the report, and the notes to subsections 30(1) and 32(1) say each section does not apply to information to the extent it has been otherwise obtained. Ask your lawyer how that bears on copies your business shares with an insurer, a responder or a customer, and how any of this applies to a particular report. Row R12 of the evidence pack records who holds the report and who it has gone to.
Other reporting clocks that can run at the same time
A single incident can bring more than one reporting duty, each with its own trigger and its own deadline.
The asset on this page lays them side by side because the triggers differ: the Part 3 clock starts at a payment or at awareness of one, while the SOCI Act clocks start when the responsible entity becomes aware of a cyber security incident and of the impact on the asset that section 30BC or 30BD names, and the Privacy Act assessment clock starts when an entity becomes aware that there are reasonable grounds to suspect that there may have been an eligible data breach.
Each applies only if its own conditions are met, and whether one reaches your business is a question for your own lawyer or privacy adviser, so the asset starts with rows that record their answers.
The Privacy Act assessment
Under section 26WH of the Privacy Act 1988, as compiled on 4 June 2026, an entity that is aware that there are reasonable grounds to suspect that there may have been an eligible data breach of the entity, and is not aware that there are reasonable grounds to believe the relevant circumstances amount to one, must carry out a reasonable and expeditious assessment and take all reasonable steps to ensure it is completed within 30 days after it becomes aware of those grounds to suspect; the notifiable data breaches guide covers that assessment and what can follow it.
The SOCI Act incident reports
Where Part 2B of the Security of Critical Infrastructure Act 2018, as compiled on 4 June 2026, applies to a critical infrastructure asset, sections 30BC and 30BD require its responsible entity to give the relevant Commonwealth body a report as soon as practicable, and in any event within 12 hours after becoming aware of a cyber security incident that has occurred or is occurring and has had, or is having, a significant impact (whether direct or indirect) on the availability of the asset, or within 72 hours after becoming aware of one that has occurred, is occurring or is imminent and has had, is having, or is likely to have, a relevant impact on the asset; the SOCI Act guide covers which assets Part 2B applies to and how those reports work.
Under paragraph 26(2)(b) of the Cyber Security Act, an entity that is the responsible entity for such an asset at the time a ransomware payment is made is a reporting business entity. That paragraph carries no turnover test.
Section 44 of the Cyber Security Act says information given voluntarily to the National Cyber Security Coordinator under Part 4 does not affect any other requirement to provide it under that Act or another law of the Commonwealth, and its note gives Part 3 and Part 2B of the SOCI Act among its examples.
The Department's factsheet makes the point for Part 3: voluntarily providing information to the Coordinator does not meet the requirement under section 27.
Smart device standards, the Coordinator and the Review Board
Part 2 is about products, not websites.
Sections 15 and 16 bind an entity that manufactures, or supplies in Australia, a relevant connectable product in a class the rules cover, where it is aware, or could reasonably be expected to be aware, that the product will be acquired in Australia in the specified circumstances, and subsection 15(5) sets an exception to section 15.
Subsection 8(1) of the Smart Devices Rules sets the class: relevant connectable products intended by the manufacturer to be used, or of a kind likely to be used, for personal, domestic or household use or consumption, other than desktop computers and laptops, tablet computers, smartphones, and therapeutic goods, road vehicles and road vehicle components within the meaning of the Acts the rules name.
Subsection 8(2) says the specified circumstances are that the products will be acquired in Australia by a consumer.
Schedule 1 of those rules sets requirements on passwords (clause 2), on publishing at least one point of contact for reports of security issues and when a reporter will receive an acknowledgement and status updates (clause 3), and on publishing a defined support period for security updates (clause 4).
Subclause 4(7) mentions a website: if the manufacturer offers to supply the product on its own website, or another website under its control, it must ensure the support period information is prominently published with the other information on the website intended to inform consumers' decisions to acquire the product, and published alongside, or otherwise given equal prominence to, each publication of the product's main characteristics.
Paragraph 3(1)(d) of Schedule 1 also reaches software used for, or in connection with, any of the manufacturer's intended purposes of the product, and paragraph 4(1)(d) reaches such software where it was developed by, or on behalf of, any manufacturer and is capable of receiving security updates; in each case the duty to publish falls on the manufacturer of the product.
The standard itself is prescribed for the class of products in subsection 8(1), and nothing in the rules sets a security standard for websites or web applications as such.
A business that sells such products, including through an online store, should ask its lawyer whether it is a supplier for Part 2.
Sharing under Part 4 is voluntary. Subsection 35(2) says an impacted entity, as subsection 35(1) describes it, or another entity acting on its behalf, may provide information about an incident to the National Cyber Security Coordinator if it is, or could reasonably be expected to be, a significant cyber security incident, and the note to subsection 35(3) says there is no obligation to provide information in response to a request.
Part 5 comes after the event. Subsection 46(2) says a review may only be conducted after the incident and the immediate response have ended, if the Board is satisfied the criteria in subsection 46(3) are met, and if the Minister has approved the terms of reference.
The Chair may request information or documents under section 48, and the first note to that section says there is no requirement to comply. Where the Board reasonably believes that an entity involved in the incident has a document relevant to the review, and the Chair has asked for it under section 48, section 49 lets the Chair require that entity, unless it is a Commonwealth body or a State body or an officer or employee of one, to produce it, or copies of it, within a period of not less than 14 days, and section 50 makes failing to comply a civil penalty of 60 penalty units, subject to the exceptions in subsection 50(2).
Where testing sits around a ransomware payment, and where it does not
The Act does not create a general website testing requirement.
Its text as made does not use the words penetration test, and it uses the word website in section 20 and paragraph 87(3)(a), each time about publishing on the Department's website. The words testing and tested appear in section 23, under which the Secretary may engage an appropriately qualified and experienced expert to examine a relevant connectable product.
Part 3 is triggered by a payment, Part 2 by making or supplying a product, Part 4 by a choice to share and Part 5 by a review. None of them asks a business to test its website or application.
A test still has a narrow place in the records around an incident. Paragraph 7(4)(f) of the rules asks what vulnerabilities, if any, in the entity's system were exploited. Working that out is incident response and forensic work.
A test report from before the incident cannot answer it, but it does list the findings recorded on the build tested at that time, which a responder can compare with the way in they identify. After the incident, a test of the cleaned site or application is a separate piece of work: its report shows how the controls behaved on that build with those accounts, and section 27 does not ask for it.
- A test can supply: a dated report on one website or application, with its scope as tested, findings, negative results for what was checked and, after the retest, a status for each finding.
- A test cannot supply: whether the business is a reporting business entity, what was exploited in this incident, the content of a ransomware payment report, a Privacy Act assessment or a SOCI Act report, a view on any payment, or a statement that the business meets the Act.
- Recovery testing and reporting stay separate. Do not hold a report back for a test, because the Part 3 clock runs from the payment or from becoming aware of it.
How to use the reporting timeline and evidence pack
The table on this page has sixteen rows.
Rows R1 to R4 are filled in before any incident and reviewed at the points their "When it falls" column gives. Rows R5 to R12 follow an incident from the first sign to the time after the report, with the Part 3 clock starting at R9.
Row R13 records recovery and any test after the cleanup. Rows R14 to R16 cover Parts 2, 4 and 5 of the Act. No row sends test requests to any system.
- Copy the table into a document your decision owners can reach when your usual systems may be down, such as a printed copy kept with your incident contact sheet.
- Fill R1 to R4 now. A blank R1 on the day of a payment leaves 72 hours to work out whether the duty applies at all.
- In R9, write the deadline as a date and time, 72 hours after the payment or after the moment the business became aware of it, whichever applies.
- Keep R10 honest: record what is known, who said it and when, and mark the rest unknown. The note to subsection 7(1) of the rules limits the content to what can be found out by reasonable search or enquiry within the 72 hours.
- File test reports in R4 and R13; R7 and R10 refer back to them. Section 27 and the rules do not ask for a test report.
- The hacked website guide sets out the first hour after a website is compromised, including what evidence to keep; R5 assumes that work is under way.
- Where the business holds cyber insurance, check the policy's terms on telling the insurer and on who appoints a responder before anyone is engaged, and note the answer in R3.
Who decides, and who to ask
The Act puts each duty on a named party.
The ransomware payment report is the reporting business entity's, the smart device duties are the manufacturer's and the supplier's, and a notice to produce under section 49 is answered by the entity that receives it. The Department's factsheet says the Department of Home Affairs administers the Act, including monitoring compliance with the obligation to report, and that ASD may receive ransomware payment reports but is not a regulator and will not monitor compliance.
Inside the business, the people named in row R3 decide, with advice. Whether the business is a reporting business entity, whether an incident is a cyber security incident, how to respond to a demand, and how the protections in sections 29 to 32 apply are questions for your lawyer. Whether a privacy breach is notifiable is a question for your privacy adviser. A tester decides none of them.
Cyber Security Act 2024 compliance and testing: where Clever Ops fits, and where it stops
The services Clever Ops sells cover what a customer reaches through a browser or an API: the website security check from outside, the WordPress security audit, the web application and API penetration test for custom applications with customer or staff logins, the vibe-coded app security check, and the AI chatbot and agent security test.
Against this Act, that work can fill two rows of the evidence pack. Before an incident, R4 can hold a dated report on one website or application. Once an incident response specialist has finished the cleanup, an audit can check the web application before the business relies on it again, and its record goes in R13.
One consolidated retest comes with every test, and afterwards each finding carries one of four statuses: fixed, partially fixed, still reproducible or not retested.
Incident response, forensics, malware cleanup and round-the-clock monitoring sit outside what Clever Ops sells, so a site that is compromised now goes to an incident response specialist first. How to respond to a ransomware demand, and how the Act applies, are questions for the business and its lawyer, and the ransomware payment report is the reporting business entity's to give.
Clever Ops has no security certification or accreditation, so what it hands over is a record of what was tested, for the business and its advisers to weigh, rather than a certificate or a view on compliance.
Clever Ops is not CREST accredited: if a tender, panel or contract makes CREST accreditation a requirement, Clever Ops passes that work to an accredited firm.
Where Clever Ops has built or hosts the system, its work is labelled a security review instead of an independent test, since it would be checking its own work, and the report names both the builder and the host.
Frequently asked questions
No provision of the Act as made asks for one. Its text does not use the words penetration test, and where it speaks of testing, in section 23, it is about an expert the Secretary may engage to examine a relevant connectable product under Part 2, the Act's smart device Part. The ransomware payment duty in section 27 is triggered by a payment, not by a test. A test report can still sit in your records as dated evidence about one website or application, as rows R4 and R13 of the evidence pack show, but it does not meet any duty in the Act.
A reporting business entity, as subsection 26(2) defines it: at the time the payment is made, either an entity carrying on a business in Australia with an annual turnover for the previous financial year that exceeds the turnover threshold, that is not a Commonwealth or State body and not a responsible entity for a critical infrastructure asset, or a responsible entity for a critical infrastructure asset to which Part 2B of the Security of Critical Infrastructure Act 2018 applies. Subsection 6(1) of the Ransomware Payment Reporting Rules sets the threshold at $3 million, with a part-year formula in subsection 6(2). Whether your business meets the test is a question for your accountant and lawyer.
Subsection 27(1) runs the 72 hours from making the ransomware payment or becoming aware that it has been made, whichever is applicable. Paragraph 26(1)(e) covers a payment the reporting business entity provides itself or is aware another entity has provided on its behalf, and under subsection 7(3) of the rules that other entity's contact and business details in the report must include its ABN (if any) and address. The Department's factsheet says no report is required where a demand was made but no payment was provided.
Sections 29 to 32 limit it. A designated Commonwealth body may make a record of, use or disclose the information only for the purposes subsection 29(1) lists, and must not do so to investigate or enforce a contravention by the reporting business entity of a Commonwealth, State or Territory law other than Part 3 or a law that imposes a penalty or sanction for a criminal offence. Subsection 29(4) leaves some information outside the first of those limits, such as information already lawfully made available to the public. Section 32 makes information that a Commonwealth or State body obtained through the report inadmissible against the entity in the proceedings it lists, with exceptions that include proceedings for false or misleading information that relates to the Act and civil penalty proceedings under Part 3. How those sections apply to your report is a question for your lawyer.
The Smart Devices Rules set a standard for a class of products, which section 8 calls consumer grade relevant connectable products: those intended by the manufacturer to be used, or of a kind likely to be used, for personal, domestic or household use or consumption, other than the products subsection 8(1) excludes, that will be acquired in Australia by a consumer. The duties fall on manufacturers and suppliers of those products. Subclause 4(7) of Schedule 1 mentions a website: it applies where a manufacturer offers to supply the product on its own website, or another website under its control, and concerns how the defined support period is published there. Nothing in the rules sets a security standard for websites or web applications as such.
No test does that. The duties the Act places on businesses include a report after a ransomware payment, product standards for manufacturers and suppliers, and producing documents when the Chair of the Review Board requires them under section 49, and a test meets none of them. A Clever Ops report records what was tested on one website or application, what was found and what the retest showed. Whether the business has met the Act is for the business and its lawyer, and the Department of Home Affairs administers the Act.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.