Artifact GuideAustraliaSmart Device Security Standards

Australia smart device security standards

Australia's Cyber Security (Security Standards for Smart Devices) Rules 2025 set mandatory baseline requirements for covered consumer-grade relevant connectable products.

For covered products, document password design, security-issue reporting contacts and response commitments, support-period publication, the statement of compliance, and the evidence behind each claim.

Author
Sorena AI
Published
May 9, 2026
Updated
Jul 25, 2026
Sections
5

Structured answer sets in this page tree.

Primary sources
5

Cited legal and guidance references.

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

The Cyber Security Act 2024 allows rules to set mandatory standards for relevant connectable products. Part 2 of the Act commenced on 29 November 2025, and the 2025 Smart Devices Rules' standard and statement requirements commenced on 4 March 2026. They apply to that will be acquired in Australia by a , unless an exclusion applies.

Section 1

What products are covered by Australia's smart-device security standard?

Start with product scope. The Rules cover relevant connectable products that are intended by the for personal, domestic or household use or consumption, or are of a kind likely to be used that way, where the product will be acquired in Australia by a .

The test comes from section 3 of the Australian Consumer Law. It can include a business buyer, including where the price does not exceed the current $100,000 threshold, unless a statutory exclusion such as acquisition for resupply or use up or transformation in production applies. Record the actual acquisition facts instead of treating retail and business labels as decisive.

Do not treat every connected product as covered. The Rules exclude desktop computers and laptops, tablet computers, smartphones, therapeutic goods, road vehicles, and road vehicle components.

Part 2 applies to a manufactured on or after 29 November 2025 or supplied in Australia, other than as second-hand goods, on or after that date. A second-hand supply can still involve a product captured by the separate manufacture trigger.

Section 15 also contains a narrow constitutional exception for requirements that do not relate to internet or like-service connection, use, or protection. It applies only where the entity is neither a constitutional corporation nor acting in interstate, Territory, or international trade or commerce. Do not assume a small or unincorporated is exempt without applying those conditions to the particular requirement.

  • Record the product type, intended purpose, Australian supply path, and why the buyer is treated as a for the Rules.
  • Check whether an exclusion applies before assigning , vulnerability-reporting, support-period, and statement-of-compliance work.
  • Keep product-family and batch decisions separate when different versions ship with different software, security updates, or default credential behavior.
  • For websites controlled by the , plan where support-period information will appear alongside product information that informs purchase decisions.
Section 2

What does the password requirement require?

For covered products with functionality, passwords used with covered hardware and software must either be unique per product or defined by the user. The rule applies to product hardware when not in the , pre-installed software when not in the factory default state, and software that must be installed for all -intended purposes that use covered hardware or software. The Rules' definition of password excludes cryptographic keys, personal identification numbers used for pairing over communication protocols outside the internet protocol suite, and application programming interface keys.

A unique-per-product cannot be a simple sequence, public-information derivative, or plain serial-number derivative. If it is based on a unique product identifier such as a serial number, the Rules require an encryption method or keyed hashing algorithm accepted as .

  • Evidence the credential model for covered hardware, pre-installed software, and software that must be installed on the product for all -intended purposes, and record why any cryptographic key, pairing personal identification number used outside the internet protocol suite, or application programming interface key is outside the Rules' definition.
  • Show whether each covered is user-defined or unique per product, including the state after the product leaves or is reset from its .
  • If serial numbers or other identifiers influence credential generation, retain the design evidence for encryption or keyed hashing and the good-industry-practice review.
  • Include the first boot experience, factory-reset behavior, and post-sale required software updates in the review.
Section 3

What vulnerability-reporting information must manufacturers publish?

Manufacturers of covered products must publish information on how a person can report for the product's hardware, pre-installed software, required software for intended purposes, and software used for or in connection with the 's intended purposes.

The publication must include at least one point of contact, plus when the reporter will receive acknowledgement of receipt and status updates until the reported are resolved. The information must be accessible, clear, transparent, in English, free of charge, available without a prior request, and available without requesting personal information just to access the reporting information.

  • Publish a security-issue reporting contact that works for researchers, customers, and other reporters.
  • State the acknowledgement and status-update process in the published reporting information.
  • Make the reporting instructions available without an account gate, form gate, paywall, prior request, or collection of personal information merely to see the instructions.
  • Keep evidence of the published page, contact routing, acknowledgement template, status-update workflow, and closure record for reported issues.
Section 4

How should support periods and security updates be published?

Manufacturers must publish the for security updates for covered product hardware and software that can receive security updates. The defined support period is the period, expressed as a period of time with an end date, during which security updates will be provided by or on behalf of the .

The publication must be accessible, clear, transparent, in English, free of charge, available without prior request or a request for personal information, and understandable without prior technical knowledge. Once published, the must not be shortened. If it is extended, the new support period must be published as soon as practicable. For -controlled websites that offer the product, the support-period information must be prominently published with purchase information and given equal prominence where the product's main characteristics are published.

  • Use a fixed end date for the support period, and align it with product pages, comparison pages, packaging copy, support pages, and statements of compliance.
  • Track which hardware, pre-installed software, required software, and -developed supporting software can receive security updates.
  • Do not bury the only in a regulatory document if product characteristics or acquisition information appears elsewhere on a controlled website.
  • Keep change control for support-period extensions and evidence that the updated period was published promptly.
Section 5

What must the statement of compliance and evidence file contain?

For covered products, the must be prepared by or on behalf of the . It must identify the product type and batch identifier, manufacturer and details, the compliance declarations, the at issue date, signatory details, and the place and date of issue.

The Rules set a five-year retention period for statements of compliance made for the -grade standard. Pair that retained statement with the technical and publication evidence that supports the 's declarations.

  • Keep the with the product type, batch identifier, details, details, compliance declarations, support period, signatory, place, and date of issue.
  • Pair the statement with engineering evidence for generation, vulnerability-reporting publication, support-period publication, and security-update handling.
  • For each , document how the Act's statement supply duty is met and retain the statement for the required period. A physical statement is not required at the point of sale.
  • Maintain batch-level traceability where similar products have different manufacturing dates, default software, or security-update status.
Primary sources

References and citations

accc.gov.au
Referenced sections
  • Current official explanation of the Australian Consumer Law acquisition test, including business purchases, the $100,000 threshold, and the resupply and production exclusions.
legislation.gov.au
Referenced sections
  • Part 2 establishes the manufacturer and supplier obligations to comply with security standards and provide or supply products with statements of compliance.
"Obligation to provide and supply products with a statement of compliance"
legislation.gov.au
Referenced sections
  • Supports the manufacture and non-second-hand supply commencement triggers, the connectivity test, and the limited constitutional exception in section 15.
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 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 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.
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.