Artifact GuideAustraliaScope and Definitions

Australia Cyber Security Act 2024 Scope and definitions

The Act covers more than one workflow: smart-device security standards for relevant connectable products, ransomware payment reporting for reporting business entities, voluntary incident coordination, and Cyber Incident Review Board processes.

Separate product scope from incident, payment, review-board, and SOCI scope before assigning a control, reporting clock, or evidence owner.

Author
Sorena AI
Published
May 9, 2026
Updated
Oct 15, 2026
Overview

Australia's Cyber Security Act 2024 has separate statutory pathways. For implementation teams, the first question is which pathway applies: a , a manufacturer or supplier obligation, a ransomware payment report by a , or a SOCI Act critical-infrastructure overlap. The Federal Register displays 29 May 2025 for Parts 3 and 5, while Home Affairs guidance says the ransomware and review-board regimes started on 30 May 2025; obtain case-specific advice for an event on 29 May. Part 2 commenced on 29 November 2025, and the Smart Devices Rules' Part 2 and Schedule 1 requirements commenced on 4 March 2026.

Section 1

What does the Cyber Security Act 2024 cover?

The Act creates several separate cyber security regimes. Part 2 deals with security standards for smart devices. Part 3 deals with ransomware payment reporting. Part 4 deals with voluntary information sharing with the National Cyber Security Coordinator for significant cyber security incidents. Part 5 deals with the Cyber Incident Review Board.

A scope decision should therefore name the pathway before naming the control. A product launch may require relevant-connectable-product and -grade analysis. A cyber extortion event may require reporting-business-entity and ransomware-payment analysis. A critical infrastructure incident may also need a separate SOCI Act check.

  • Product pathway: decide whether the item is a and whether the Smart Devices Rules prescribe a security standard for it.
  • Supply pathway: decide whether the organisation is a manufacturer, supplier, or both for the covered product.
  • Ransomware pathway: decide whether the affected organisation is a and whether a ransomware payment was made by it or on its behalf.
  • SOCI overlap pathway: decide whether the organisation is a for a critical infrastructure asset to which SOCI Act Part 2B applies.
Section 2

How should teams define a relevant connectable product?

Under the Act, a is an internet-connectable product or a network-connectable product that has not been exempted under the rules. An internet-connectable product can connect to the internet using an internet protocol suite communication protocol to send and receive data.

A network-connectable product is not internet-connectable, but can send and receive data by electrical or electromagnetic transmission and meets the Act's direct-connection conditions. That means product teams should document actual connectivity, companion devices, gateways, communication protocols, and whether the product connects directly or indirectly to internet-capable equipment.

  • Record the product, model or batch, connectivity hardware, firmware, software, protocol, companion app, gateway, and whether data can be sent and received.
  • Do not scope only by marketing labels such as smart, IoT, connected, wireless, or app-enabled; tie the conclusion to the Act's internet-connectable or network-connectable tests.
  • Keep exemption analysis separate from connectivity analysis because the Act first asks whether the product is connectable and then whether it is exempted by rules.
Section 3

Which consumer-grade smart devices are currently in the Smart Devices Rules scope?

The Smart Devices Rules currently prescribe a security standard for -grade relevant connectable products. The class is 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.

The specified circumstance is that the products will be acquired in Australia by a . The Rules adopt section 3 of the Australian Consumer Law, which can cover goods priced at no more than the prescribed $100,000 amount or goods ordinarily acquired for personal, domestic or household use. It excludes acquisitions for resale and specified production, manufacture, repair, or treatment uses.

  • In-scope class: relevant connectable products intended or likely for personal, domestic, or household use or consumption.
  • Specified circumstance: the products will be acquired in Australia by a .
  • Express exclusions: desktop computers or laptops, tablet computers, smartphones, therapeutic goods, road vehicles, and road vehicle components.
  • Useful evidence: manufacturer's intended purpose, label, instructions for use, promotional or sales materials, likely household use, Australian acquisition channel, and exclusion checks.
  • -test evidence: price, ordinary use, buyer purpose, and any resale or production-use exclusion; a business buyer is not automatically outside the test.
Section 4

What do manufacturer and supplier mean for scope?

The Act uses Australian Law meanings for manufacturer and supply, with supplier and supplied carrying corresponding meanings. The Smart Devices Rules then apply obligations to covered products through those roles.

For covered products, manufacturers must manufacture in compliance with the applicable security standard when they are aware, or could reasonably be expected to be aware, that the product will be acquired in Australia in the specified circumstances. Suppliers must not supply a non-compliant product in Australia when they have the same awareness, and they must meet the Act's statement-of-compliance supply duty. The official explanatory statement says this does not require a physical statement at the point of sale; the statement is a regulatory record that may also be provided or published.

  • Manufacturer scope evidence: product design and production role, manufacturer name and address, authorised representative details, product type, and batch identifier.
  • Supplier scope evidence: Australian supply channel, awareness of Australian acquisition, statement-of-compliance availability, and non-compliance escalation route.
  • Statement scope evidence: product type and batch identifier, manufacturer details, compliance declaration, defined support period, signatory details, place and date of issue, and five-year retention owner.
Section 5

Who is a reporting business entity for ransomware payment reporting?

The ransomware reporting pathway starts only after the entity is inside the Act's reporting-business-entity definition and the incident and payment trigger is met. For non-government businesses, the Act looks to a business carrying on in Australia with annual turnover for the previous financial year above the prescribed threshold, excluding Commonwealth or State bodies and excluding responsible entities for critical infrastructure assets from that limb.

A separate limb captures a for a critical infrastructure asset to which SOCI Act Part 2B applies. The Ransomware Payment Reporting Rules prescribe a $3 million turnover threshold, with a pro-rated formula where the business operated for only part of the previous financial year. Section 26 says turnover must exceed the threshold. The current cyber.gov.au form instead says "equal to or exceeds $3 million," so an entity at exactly $3 million should confirm the filing position promptly.

  • Business limb: carrying on a business in Australia, annual turnover for the previous financial year exceeds the prescribed threshold, and the entity is not a Commonwealth body, State body, or for a critical infrastructure asset.
  • Critical-infrastructure limb: for a critical infrastructure asset to which SOCI Act Part 2B applies.
  • Payment trigger: the provides, or knows another entity provided on its behalf, a payment or benefit directly related to the extorting entity's demand.
  • Report clock: the report is due within 72 hours of making the payment or becoming aware the payment was made, whichever is applicable.
Section 6

What information belongs in a ransomware payment scope record?

A ransomware payment scope record should be narrow and factual. It should show why the entity is or is not a , when the payment was made or discovered, what information was known or reasonably findable within the 72-hour reporting period, and who approved the report decision.

The Rules require specific report content: contact and business details including Australian Business Number (ABN), if any, and address, incident timing and awareness, impact on infrastructure and customers, ransomware or malware variants if any, exploited vulnerabilities if any, demand details, payment details, communications, and any pre-payment negotiations.

  • Entity evidence: Australian business activity, previous-financial-year turnover threshold analysis, Commonwealth or State body exclusion, and SOCI responsible-entity analysis.
  • Incident evidence: occurrence or estimated occurrence time, awareness time, infrastructure impact, customer impact, malware variant, exploited vulnerabilities, and response-useful information.
  • Demand and payment evidence: amount or non-monetary benefit demanded, method demanded, amount or non-monetary benefit provided, method of provision, communications, and pre-payment negotiations.
Section 7

How does SOCI Act overlap change the scope answer?

The Cyber Security Act does not supersede the Security of Critical Infrastructure Act 2018. It imports SOCI Act concepts for critical infrastructure asset and , and it uses SOCI Act Part 2B status in the reporting-business-entity definition.

SOCI status can bring an organisation into the ransomware payment reporting regime even if the ordinary business-turnover limb is not the right path. The same event may also require separate reporting or information provision under SOCI Act Part 2B or another Commonwealth law; the Act states that a Part 3 report does not affect other information-provision requirements.

  • Keep SOCI evidence separate from product evidence: asset classification, responsible-entity reasoning, and whether Part 2B applies.
  • Keep Cyber Security Act ransomware evidence separate from SOCI incident-notification evidence so each report has its own trigger, clock, content, and submission proof.
  • Do not treat critical-infrastructure status as proof that smart-device standards apply; smart-device scope still depends on , -grade class, and Australian consumer acquisition.
Primary sources

References and citations

legislation.gov.au7 citations
Referenced sections
  • Primary Act source for Cyber Security Act scope, relevant connectable product definitions, manufacturer and supplier duties, ransomware payment reporting, and SOCI-linked definitions.
  • Primary Act source for the separate smart-device, ransomware reporting, incident coordination, and Cyber Incident Review Board pathways.
  • Defines relevant connectable product, internet-connectable product, and network-connectable product for smart-device scope decisions.
Show 4 more
  • Supports manufacturer and supplier meanings and the Act's high-level obligations for covered relevant connectable products.
  • Defines reporting business entity, ransomware payment, and the 72-hour report trigger in Part 3.
  • Supports the statutory report categories: reporting entity details, incident, demand, payment, and communications with the extorting entity.
  • Cross-references SOCI Act critical infrastructure asset and responsible entity concepts and states that Part 3 reporting does not displace other reporting requirements.
"relevant connectable product"
More quoted passages
"Security standards for smart devices"
"is an internet-connectable product or a network-connectable product"
"has the same meaning as in the Australian Consumer Law"
"within 72 hours of making the ransomware payment"
"the demand made by the extorting entity"
"does not affect any other requirement"
legislation.gov.au4 citations
Referenced sections
  • Primary rules source for the ransomware payment reporting turnover threshold and required report information.
  • Primary rules source for ransomware payment reporting threshold and report-content requirements.
  • Prescribes the $3 million turnover threshold and report-content requirements for ransomware payment reports.
Show 1 more
  • Sets the additional information categories that a ransomware payment report must contain to the extent known or reasonably findable within 72 hours.
"the amount of turnover threshold"
More quoted passages
"Ransomware payment reporting obligations"
"Information is only required to be given"
legislation.gov.au4 citations
Referenced sections
  • Primary rules source for consumer-grade relevant connectable products, Australian consumer acquisition, excluded product categories, statement contents, and statement retention.
  • Primary rules source for the current prescribed smart-device security standard and its consumer-grade product scope.
  • Shows that expressions including manufacturer, supplier, and relevant connectable product are taken from the Act for the Smart Devices Rules.
Show 1 more
  • Supports the consumer-grade product class, Australian consumer acquisition circumstance, consumer definition, and six product exclusions.
"Security standards for consumer grade relevant connectable products"
More quoted passages
"consumer grade relevant connectable products"
"relevant connectable product"
"personal, domestic or household use or consumption"
legislation.gov.au2 citations
Referenced sections
  • Explains the policy scope for consumer-grade smart devices and gives official product examples discussed for the Rules.
  • Explains that the Rules apply to everyday consumer products such as smart TVs, smart watches, home assistants, baby monitors, and consumer energy resources.
"smart TVs, smart watches, home assistants, baby monitors"
legislation.gov.au2 citations
Referenced sections
  • Primary SOCI source for critical infrastructure asset, responsible entity, and Part 2B concepts referenced by the Cyber Security Act.
  • Primary SOCI source for critical infrastructure asset, responsible entity, and Part 2B incident-notification concepts referenced by the Cyber Security Act.
"Notification of cyber security incidents"
legislation.gov.au
Referenced sections
  • Clarifies the regulatory purpose of the statement and that it need not be physically provided at the point of sale.
"Statements of compliance are not required to be provided with the product at point of sale"
Show all related guides (29)

Australia Cyber Security Act Deadlines and Calendar

Cyber Security Act 2024 dates and event-driven deadlines for ransomware payment reports, smart-device duties, records, notices, and statutory review.

Australia Cyber Security Act FAQ

Answers to Australia Cyber Security Act questions on smart device scope, statements of compliance, ransomware reports, enforcement notices, and incident review.

Australia Cyber Security Act penalties and fines

Cyber Security Act 2024 civil penalties explained by section, including ransomware reports, protected information, CIRB notices, and smart-device enforcement.

Australia Cyber Security Act Requirements

Australia Cyber Security Act requirements for smart-device security standards, statements of compliance, ransomware payment reports, notices, and evidence records.

Australia Cyber Security Act Statement of Compliance Evidence

Evidence guide for Australia Cyber Security Act smart-device statements of compliance: required fields, manufacturer and supplier records, five-year retention, and examination readiness.

Australia Cyber Security Act templates

Source-backed field lists for Australia Cyber Security Act smart-device scope, statements of compliance, ransomware reports, notices, SOCI overlap, and records.

Australia Cyber Security Act vs EU Cyber Resilience Act

Compare Australia's Cyber Security Act 2024 with the EU Cyber Resilience Act across smart-device duties, ransomware reporting, product-with-digital-elements scope, actors, records, and enforcement routes.

Australia Cyber Security Act vs UK PSTI Act Guide

Compare Australia's Cyber Security Act 2024 smart-device, ransomware, and SOCI-adjacent obligations with the UK's PSTI connected-product regime.

Australia ransomware payment reporting 72-hour duty

Explain when Australia's Cyber Security Act 2024 requires a ransomware payment report, when the 72-hour clock starts, and what information the report must contain.

Australia Ransomware Payment Reporting Workflow

Operational workflow for Australia Cyber Security Act 2024 ransomware payment reports: scope, 72-hour trigger, report fields, owners, evidence, and cited Act and Rules sources.

Australia Smart Device Applicability Workflow

Decide whether Australia's mandatory smart-device security standard applies, including commencement, connectivity, consumer use, exclusions, roles, and evidence.

Australia Smart Device Compliance Statement

What a smart-device statement of compliance must contain under Australia's Cyber Security Act 2024 and Smart Devices Rules, who prepares and supplies it, how long to retain it, and how to prepare for examination.

Australia Smart Device Security Standards under the Cyber Security Act

Plain-English guide to Australia's Cyber Security (Security Standards for Smart Devices) Rules 2025: scope, passwords, vulnerability reporting, support periods, statements of compliance, and evidence records.

CSA 2024 Smart Device Applicability Test

Check whether a smart device is a consumer-grade relevant connectable product under Australia's Cyber Security Act and Smart Devices Rules.

Cyber Security Act 2024 Smart Device Compliance Checklist

Checklist for Australia Cyber Security Act 2024 smart-device scope, password controls, vulnerability reporting, security-update support periods, statements of compliance, retention, and evidence.

SOCI overlap triage workflow for Australia Cyber Security Act

Triage SOCI Act overlap with Australia Cyber Security Act ransomware reporting and smart-device standards using separate owners, evidence, and cited scope checks.

Australia Cyber Security Act recordkeeping FAQ

What records to keep for Cyber Security Act 2024 smart-device statements, ransomware payment reports, and supported SOCI or APRA overlap checks.

Australia Ransomware Payment Reporting: Threshold and Report Content

FAQ answer on Australia's Cyber Security Act ransomware payment reporting scope, $3 million turnover threshold, 72-hour trigger, report fields, and evidence.

Cyber Security Act 2024 Statements of Compliance FAQ

Australian smart-device statements of compliance: covered products, responsible actors, required contents, supporting evidence, and five-year retention.

How do notices and recalls work under the Australia Cyber Security Act?

FAQ on Australia Cyber Security Act compliance notices, stop notices, recall notices, public notifications, owners, evidence fields, and cited timing.

How does the Australia Cyber Security Act overlap with the SOCI Act?

FAQ on when Australia Cyber Security Act ransomware reporting overlaps with SOCI critical infrastructure assets, responsible entities, and smart-device duties.

Manufacturer, Importer, and Supplier Duties under Australia's Cyber Security Act 2024

Cyber Security Act 2024 smart-device duties for manufacturers, importers, and suppliers, including role tests, scope, statements, and records.

Which smart devices are in scope under Australia's Cyber Security Act 2024?

FAQ on Cyber Security Act 2024 smart-device scope: relevant connectable products, consumer-grade criteria, exclusions, Australian consumer acquisition, and records to keep.