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.

Use this page to separate product scope from incident and payment scope before assigning controls, evidence, or reporting work. This guidance is practical, source-linked, and should be validated against current legal and policy requirements before implementation.

Author
Sorena AI
Published
May 9, 2026
Updated
May 9, 2026
Sections
7

Structured answer sets in this page tree.

Primary sources
5

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated May 9, 2026
Overview

Australia's Cyber Security Act 2024 should not be scoped as a single generic cyber checklist. For implementation teams, the first question is which statutory pathway applies: a consumer-grade relevant connectable product, a manufacturer or supplier obligation, a ransomware payment report by a reporting business entity, or a SOCI Act critical-infrastructure overlap.

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 consumer-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 relevant connectable product 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 reporting business entity and whether a ransomware payment was made by it or on its behalf.
  • SOCI overlap pathway: decide whether the organisation is a responsible entity 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 relevant connectable product 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 consumer-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 acquisition circumstance is also important: the products must be acquired in Australia by a consumer. The Rules define consumer by reference to section 3 of the Australian Consumer Law.

  • 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 consumer.
  • 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.
Section 4

What do manufacturer and supplier mean for scope?

The Act uses Australian Consumer 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 suppliers must supply the product with a compliant statement of compliance.

  • 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 consumer 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 responsible entity 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.

  • 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 responsible entity for a critical infrastructure asset.
  • Critical-infrastructure limb: responsible entity for a critical infrastructure asset to which SOCI Act Part 2B applies.
  • Payment trigger: the reporting business entity 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 reporting business entity, 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 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 responsible entity, and it uses SOCI Act Part 2B status in the reporting-business-entity definition.

The practical result is that 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 relevant connectable product, consumer-grade class, and Australian consumer acquisition.
Primary sources

References and citations

legislation.gov.au
Referenced sections
  • Sets the additional information categories that a ransomware payment report must contain to the extent known or reasonably findable within 72 hours.
"Information is only required to be given"
legislation.gov.au
Referenced sections
  • Cross-references SOCI Act critical infrastructure asset and responsible entity concepts and states that Part 3 reporting does not displace other reporting requirements.
"does not affect any other requirement"
legislation.gov.au
Referenced sections
  • 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.au
Referenced sections
  • Primary SOCI source for critical infrastructure asset, responsible entity, and Part 2B incident-notification concepts referenced by the Cyber Security Act.
"Part 2B--Notification of cyber security incidents"
Related guides

Explore more topics

Australia Cyber Security Act and SOCI Act overlap
How the Australia Cyber Security Act overlaps with the Security of Critical Infrastructure Act for responsible entities, ransomware payment reporting, smart devices, and evidence records.
Australia Cyber Security Act Applicability Test
Decide whether the Australia Cyber Security Act 2024 applies to a smart-device product, supplier, manufacturer, or ransomware payment reporting scenario.
Australia Cyber Security Act Compliance Checklist
Concrete checklist items for Australian Cyber Security Act smart-device and ransomware duties, with SOCI and APRA CPS 234 evidence checks.
Australia Cyber Security Act Compliance Guide
A source-linked compliance guide for Australia Cyber Security Act smart-device statements, ransomware payment reporting, incident coordination, and review-board readiness.
Australia Cyber Security Act Deadlines and Compliance Calendar
Calendar of grounded Australia Cyber Security Act milestones for ransomware reporting, smart-device security standards, statements of compliance, 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
Grounded guide to Australia Cyber Security Act civil penalties, smart-device enforcement notices, ransomware reporting exposure, Board notice failures, and evidence records.
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 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
Grounded template fields for Australia Cyber Security Act smart-device scope, statements of compliance, ransomware reports, notices, SOCI overlap, and records.
Australia Cyber Security Act Timeline And Commencement Guide
Australia Cyber Security Act guidance for Timeline And Commencement, with practical decisions, evidence, edge cases, and external source citations.
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 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.
Australia Smart Device Statement of Compliance Evidence Workflow
Evidence workflow for preparing, supplying, and retaining statements of compliance under Australia's Cyber Security Act 2024 and Smart Devices Rules.
CSA 2024 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.
CSA 2024 Ransomware Threshold & Report FAQ
FAQ answer on Australia's Cyber Security Act ransomware payment reporting scope, $3 million turnover threshold, 72-hour trigger, report fields, and evidence.
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.
CSA 2024 Smart Device Statement of Compliance
What a smart-device statement of compliance must contain under Australia's Cyber Security Act 2024 and Smart Device Rules, who prepares and supplies it, how long to retain it, and how to prepare for examination.
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.
Cyber Security Act 2024 Statements of Compliance FAQ
FAQ answer on Australian Cyber Security Act 2024 statements of compliance for smart devices, including scope, actors, required contents, retention, evidence, and citations.
Cyber Security Act vs EU CRA: scope and obligations comparison
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.
Cyber Security Act vs UK PSTI Act: device security obligations compared
Compare Australia's Cyber Security Act 2024 smart-device, ransomware, and SOCI-adjacent obligations with the UK's PSTI connected-product regime.
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 grounded 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
Direct FAQ answer on Cyber Security Act 2024 smart-device duties for manufacturers, importers, and suppliers, including scope, statement records, exceptions, and citations.
Smart Device Applicability: CSA 2024
A source-linked workflow for deciding whether a connected product is covered by Australia's Cyber Security Act 2024 smart-device standard and what evidence to keep.
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 source-linked scope checks.
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.