Cyber security regulation: the Cyber Security Act 2024

Which incidents the Act reaches

Parts 3 and 4 apply to a cyber security incident. Section 9(1) borrows this meaning from the Security of Critical Infrastructure Act 2018.

Section 9(2) narrows this. The incident must have a constitutional connection, such as a critical infrastructure asset, a constitutional corporation’s activities, or use of a telecommunications service like the internet. It can also involve impairing a computer’s connection to such a service, or serious prejudice to Australia’s social or economic stability, defence or national security.

Where the facts are unclear, ss 26(4) and 35(4) let this connection be presumed on the probabilities. But s 26(5) removes Part 3 civil penalty liability if the connection did not actually exist.

A significant cyber security incident is a narrower, more serious category. Under s 34, it is one carrying a material risk of serious prejudice to stability, defence or national security. It also includes one that is, or could reasonably be expected to be, of serious concern to the Australian people.

Ransomware payment reporting

Part 3 covers ransomware payment reporting. It applies when a cyber security incident affects, or could reasonably affect, a reporting business entity. It also requires that an extorting entity (someone making the ransom demand) demands payment, and the entity pays or knows a payment was made on its behalf (s 26(1)).

A reporting business entity is an Australian business with turnover above $3 million last financial year (s 6 of the Ransomware Payment Reporting Rules). This excludes Commonwealth or State bodies, critical infrastructure responsible entities, and responsible entities under Part 2B of the Security of Critical Infrastructure Act (s 26(2)).

The entity must report to the designated Commonwealth body within 72 hours of paying, or of learning that payment was made (s 27(1)). The designated body is usually the Department and the Australian Signals Directorate, unless the rules name another body (s 8).

The report must cover the incident, the demand, the payment, and communications with the extorting entity. This applies only so far as the entity knows or can find out through reasonable search or enquiry (s 27(2); rules s 7).

Failing to report can attract a civil penalty of 60 penalty units (s 27(5)). Entities that comply in good faith face no liability in damages (s 28).

What reported information can and cannot be used for

Two rules protect entities that report ransomware payments, so they feel safe reporting.

The first rule limits use. Information in a ransomware payment report can only be used for listed purposes, like helping the entity respond (s 29(1)). It cannot be used to investigate or enforce the entity’s breaches of other laws, except breaches of Part 3 or criminal offence laws (s 29(2)).

The second rule limits admissibility, meaning whether the information can be used as evidence. It cannot be used against the entity in criminal proceedings, civil penalty proceedings outside Part 3, other proceedings for breaking a law (including common law), or tribunal proceedings (s 32(2)). There is an exception for two Criminal Code offences: giving false or misleading information, and obstruction.

So criminal offences are excluded from the use restriction, but not from the admissibility rule. The two protections don’t line up exactly.

The admissibility protection also has its own exceptions. It does not apply to a coronial inquiry, a Royal Commission, or certain federal court proceedings seeking mandamus, prohibition or an injunction against a Commonwealth officer (s 32(3)).

Neither protection lets anyone do something the Privacy Act 1988 (Cth) forbids (s 29(3)). Reporting also does not, by itself, affect a claim of legal professional privilege (s 31), which protects confidential legal advice from disclosure.

Information shared under Part 4 gets similar protections, but the exceptions there refer to Part 4 instead of Part 3 (ss 38, 42).

The Cyber Incident Review Board

The Cyber Incident Review Board has a Chair and two to six standing members (s 61). It reviews incidents after they finish and suggests ways to prevent, detect, respond to, or reduce similar ones (s 62).

A review only starts after a referral, from the Minister, the Coordinator, an affected entity, or a Board member. The incident must also meet a test in s 46(3), like serious harm to national security or unusual methods used.

The incident and the immediate response must also be over, and the Minister must approve the review’s terms of reference (s 46).

The Chair can make a private entity hand over documents, but only after first asking for them. Refusing risks a civil penalty of 60 penalty units (ss 48–50). A civil penalty is a fine for breaking the law, not a criminal charge.

The Board does not decide who is at fault. Its final report cannot blame anyone, help prove liability, name a person without their consent, or let people assume guilt just because a review happened (s 52(4)).

Enforcement

Civil penalty provisions under the Act are enforced using the Regulatory Powers (Standard Provisions) Act 2014 (Cth). This means courts can issue civil penalty orders (fines), injunctions (court orders stopping conduct), enforceable undertakings (formal promises to comply), and use monitoring, investigation and infringement notices (ss 79–82).

These matters can be heard in the Federal Court, the Federal Circuit and Family Court of Australia (Division 2), or a State or Territory court with jurisdiction.

The Crown itself cannot be made to pay a pecuniary penalty. However, a Crown authority can be penalised (s 79(8)–(9)).

The rules made under the Act cannot create a new offence or civil penalty (s 87(2)(a)).

Applying this in a problem question

First, work out which regime applies. It could be a product issue (Part 2), a ransomware payment (Part 3), voluntary information sharing (Part 4), or a Board review (Part 5).

For Parts 3 and 4, you must first show a cyber security incident under s 9(2). Only use the presumptions in ss 26(4) and 35(4) if the facts are unclear.

For a product question, check it is a relevant connectable product used by consumers. Then test whether the manufacturer or supplier had awareness under s 15.

For a payment question, prove each element of s 26(1). Apply the $3 million threshold. Count the 72-hour period from the payment, or from when the person became aware of it.

Apply the use restriction and the admissibility rule as separate tests. Each has its own exceptions, so check both carefully.

Finally, state the outcome. This is either the notice sequence under Part 2, or a remedy available under the Regulatory Powers Act.

A Quick Read uses simpler language and may leave out detail, including whole topics, to stay short. The full article is the complete statement.

Read the full article →

Pop quiz

5 quick questions on this article, the authorities it cites and the articles it links to.

  • About 3 minutes, and no time limit.
  • You can only go forwards: each answer locks when you submit it.
  • After each question you see the right answer, why, and where to read more.
  • Free, and no account needed. Log in or create a free account to keep your scores.