Applicability TestAustraliaCyber Security Act 2024

Australia Cyber Security Act Applicability Test

Decide whether the Cyber Security Act 2024 applies because of a consumer-grade relevant connectable product, a statement-of-compliance duty, or a ransomware payment report.

The test separates product scope, actor role, statutory exclusions, ransomware payment thresholds, and SOCI overlap so teams can record a traceable in-scope or out-of-scope decision.

Author
Sorena AI
Published
May 9, 2026
Updated
Jul 24, 2026
Sections
6

Structured answer sets in this page tree.

Primary sources
9

Cited legal and guidance references.

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

Run two separate applicability tracks under the Australian Cyber Security Act 2024: Part 2 smart-device product duties and Part 3 ransomware payment reporting. If neither track is satisfied, record the reason and check whether another regime, such as SOCI, privacy breach notification, APRA CPS 234, or contract obligations, applies instead.

Section 1

Step 1: test whether the product is a relevant connectable product

Start the assessment with the product. Part 2 commenced on 29 November 2025 and applies to a manufactured on or after that date, or supplied in Australia other than as second-hand goods on or after that date. The current Smart Devices Rules' security standard and statement requirements commenced later, on 4 March 2026.

A product is a if it is an internet-connectable product or a network-connectable product and is not exempted under the rules. The Act defines an internet-connectable product as one capable of connecting to the internet using a protocol in the internet protocol suite to send and receive data. A network-connectable product can send and receive data by electrical or electromagnetic transmission, is not internet-connectable, and meets the Act's direct-connection tests.

  • In scope for the product track: internet-connectable products and products that meet the Act's specific network-connectable tests, unless an exemption applies.
  • Out of scope for this product track: products that are not internet-connectable or network-connectable under the Act, products exempted by rules, and second-hand goods supply where neither paragraph 13(1)(a) nor paragraph 13(1)(b) applies.
  • Do not treat every second-hand supply as outside Part 2. Paragraph 13(1)(b) excludes second-hand goods from its supply trigger, but paragraph 13(1)(a) can still apply if the product was manufactured on or after 29 November 2025.
  • Evidence to keep: product connectivity specification, supported protocols, companion-app or gateway architecture, manufacture date, supply path into Australia, and whether the item is new or second hand.
  • Decision output: , exempt product, or no Part 2 product trigger.
Section 2

Step 2: test the consumer-grade smart-device class and exclusions

The current smart-device security standard does not cover every . The Cyber Security (Security Standards for Smart Devices) Rules 2025 prescribe the security standard for -grade relevant connectable products: 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 acquisition in Australia by a . Under the Australian Consumer Law test incorporated by the Rules, that can include goods priced at no more than the prescribed $100,000 amount or goods ordinarily acquired for personal, domestic or household use, including some business purchases. Goods acquired for resale or for specified use-up or transformation in production, manufacture, repair, or treatment are excluded from that consumer test. The Rules also carve out six product groups from the smart-device class: desktop computers or laptops, tablet computers, smartphones, therapeutic goods, road vehicles, and road vehicle components.

  • In scope for the current smart-device standard: a intended or likely for personal, domestic, or household use or consumption, acquired in Australia by a , and not in an excluded product group.
  • Excluded from the current smart-device standard: desktop computers, laptops, tablet computers, smartphones, therapeutic goods, road vehicles, and road vehicle components.
  • Do not decide on marketing labels alone: record the manufacturer's intended purpose, labels, instructions, promotional material, customer segment, and likely household or use.
  • For the acquisition branch, record price, whether the goods are ordinarily acquired for personal, domestic or household use, and whether the buyer acquires them for resale or specified production, manufacture, repair, or treatment use.
  • Decision output: , excluded product, or with no currently prescribed standard identified.
Section 3

Step 3: map the product role to manufacturer and supplier duties

If a security standard applies, the Act splits duties by role. A manufacturer must manufacture the product in compliance with the security standard when it is aware, or could reasonably be expected to be aware, that the product will be acquired in Australia in the specified circumstances. The manufacturer must also meet other obligations in the standard, such as publishing product security information.

A supplier must not supply a non-compliant product in Australia if it is aware, or could reasonably be expected to be aware, that the product will be acquired in Australia in the specified circumstances. A supplier must also meet the Act's duty to supply the product with a that meets the Rules. The official explanatory statement clarifies that the statement need not be physically provided at the point of sale; it is a regulatory record that an entity may also provide or publish.

  • Manufacturer duty check: was the entity the manufacturer, and did it know, or should it reasonably have known, the product would be acquired in Australia by a ?
  • Supplier duty check: is the entity supplying the product in Australia, and does it know, or should it reasonably have known, the product would be acquired in Australia by a ?
  • Statement check: for in-scope -grade relevant connectable products, the statement must be prepared by or on behalf of the manufacturer and include product type, batch identifier, manufacturer and authorised representative details, declarations of compliance, the defined support period, signatory details, and place and date of issue.
  • Retention check: manufacturers and suppliers must retain statements of compliance for the five-year period specified in the Smart Devices Rules.
Section 4

Step 4: test whether the smart-device security controls are triggered

For in-scope -grade relevant connectable products, the Rules make the applicability decision operational: the product must meet password requirements, the manufacturer must publish a way to report security issues, and the manufacturer must publish the defined support period for security updates.

The defined support period must be expressed as a period of time with an end date. Once published, the manufacturer must not shorten it; if the period is extended, the new period must be published as soon as practicable.

  • Password control: passwords must be unique per product or defined by the user; unique per product passwords must not be based on incremental counters, public information, guessable serial-number derivations unless protected by accepted encryption or keyed hashing, or otherwise unacceptable guessable methods.
  • Security issue reporting control: the manufacturer must publish at least one contact point and say when reporters will receive acknowledgement and status updates until resolution.
  • Publication quality control: required security issue and support-period information must be accessible, clear, transparent, in English, free of charge, available without prior request, and available without requesting personal information.
  • Website prominence control: if the manufacturer offers the product on its own website, support-period information must be prominent with acquisition-decision information and given equal prominence where main product characteristics are published.
Section 5

Step 5: test ransomware payment reporting separately

A ransomware payment scenario is a separate applicability track. Part 3 applies when an incident has occurred, is occurring, or is imminent; the incident is a cyber security incident; it has, is having, or could reasonably be expected to have a direct or indirect impact on a ; an extorting entity makes a demand to benefit from the incident or impact; and the reporting business entity provides, or becomes aware that another entity has provided on its behalf, a payment or benefit directly related to the demand.

The entity must also be a at the time the ransomware payment is made. That means either a responsible entity for a critical infrastructure asset to which Part 2B of the Security of Critical Infrastructure Act 2018 applies, or an entity carrying on business in Australia with annual turnover for the previous financial year exceeding the threshold and that is not a Commonwealth body, State body, or responsible entity for a critical infrastructure asset.

  • Turnover threshold: the Ransomware Payment Reporting Rules set the previous-financial-year turnover threshold at $3 million.
  • Threshold wording conflict: section 26 requires turnover to exceed the threshold, but the current cyber.gov.au form describes its business option as "equal to or exceeds $3 million." An entity at exactly $3 million should confirm the filing position promptly rather than treating the form label as an amendment to the Act.
  • Part-year threshold: if the business operated for only part of the previous financial year, apply the Rules formula: $3 million multiplied by the number of days in that part divided by the number of days in the previous financial year.
  • Reporting clock: the report must be given within 72 hours of making the ransomware payment or becoming aware that the ransomware payment has been made.
  • Report content: collect the reporting entity's ABN if any and address, any other paying entity's ABN if any and address, incident timing and awareness timing, infrastructure and customer impact, ransomware or malware variants, exploited vulnerabilities, demand amount or non-monetary benefit, payment amount or benefit, method of provision, and communications with the extorting entity.
Section 6

Step 6: record the decision and unresolved gaps

The decision record should be short but specific enough to re-run later. Use separate rows for product duties and ransomware reporting because the actor, trigger, threshold, evidence, and deadline are different.

Mark a decision as unresolved if the facts needed for a legal threshold are missing. Common unresolved facts include whether a product is second hand, whether it is likely to be used for personal, domestic, or household use, whether a product is an excluded tablet, smartphone, therapeutic good, road vehicle, or vehicle component, whether the supplier knew or should have known the Australian acquisition circumstance, whether turnover exceeds the threshold, or whether the entity is a responsible entity for a Part 2B SOCI critical infrastructure asset.

  • Product record fields: product name, model or batch, connectivity route, manufacturer, supplier, acquisition circumstance, -grade analysis, exclusion check, security-standard conclusion, statement-of-compliance status, and five-year retention owner.
  • Ransomware record fields: incident date or estimate, awareness date, affected entity, payer if different, turnover threshold evidence, SOCI responsible-entity analysis, demand details, payment details, 72-hour deadline, report status, and unresolved unknowns.
  • Escalation rule: ask for legal review before shipment, supply, payment approval, or report closure when an exclusion, SOCI status, turnover calculation, or role allocation cannot be supported by evidence.
  • Out-of-scope: a no-trigger decision under this page does not clear privacy breach notification, SOCI cyber incident reporting, APRA prudential obligations, sanctions, criminal law, insurance, or customer-contract reporting duties.
Primary sources

References and citations

legislation.gov.au
Referenced sections
  • Supplies the goods-acquisition consumer test incorporated by section 6 of the Smart Devices Rules, including the price and ordinary-use limbs and the resale and production-use exclusions.
legislation.gov.au
Referenced sections
  • Supports ransomware-reporting threshold, timing, and report-content fields in the decision record.
"Information is only required to be given to the extent that the reporting business entity knows"
legislation.gov.au
Referenced sections
  • Supports keeping separate records for Part 2 product duties and Part 3 ransomware reporting because the Act sets different triggers and obligations.
"This Act also provides an obligation to report payments or benefits"
legislation.gov.au
Referenced sections
  • Explains that examples of consumer-grade products include smart TVs, smart watches, home assistants, baby monitors, and consumer energy resources.
"smart TVs, smart watches, home assistants, baby monitors, and consumer energy resources"
legislation.gov.au
Referenced sections
  • Clarifies that a statement is a regulatory record and need not be physically provided with the product at the point of sale.
"Statements of compliance are not required to be provided with the product at point of sale"
Related guides

Explore more topics

Australia Compliance Statement Evidence Workflow
Evidence workflow for preparing, supplying, and retaining statements of compliance under Australia's Cyber Security Act 2024 and Smart Devices Rules.
Australia Cyber Security Act 2024 scope and definitions
Official source scope guide for Australia's Cyber Security Act 2024: relevant connectable products, consumer-grade smart devices, reporting business entities, ransomware payment reports, and SOCI overlap.
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 Commencement Timeline
Cyber Security Act 2024 commencement timeline for ransomware reporting, CIRB reviews, smart-device duties, statement retention, and statutory review.
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 cited 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 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 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
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 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.
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.
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.
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 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.
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.
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.