Product team testing a smart-speaker-style device with microphones in an anechoic chamber

Cyber Resilience Act

Australia's smart device cyber security standards (Rules 2025), explained

Last updated:

Australia's Cyber Security (Security Standards for Smart Devices) Rules 2025 became mandatory on 4 March 2026, making it the country's first binding baseline for consumer connected-device security. Made under Part 2 of the Cyber Security Act 2024 (Royal Assent 29 November 2024) and registered on the Federal Register of Legislation on 4 March 2025 as F2025L00276, the Rules move beyond Australia's earlier 2020 voluntary code of practice to an enforceable requirement covering three familiar baseline provisions — no default passwords, a vulnerability-reporting channel, and published update-support periods — for most consumer smart devices manufactured from the commencement date.

Key takeaways

  • Australia's Cyber Security (Security Standards for Smart Devices) Rules 2025 became mandatory on 4 March 2026, making it the country's first binding baseline for consumer connected-device security.
  • Two Parts and a Schedule.
  • Consumer-grade connectable products, minus six named exclusions.
  • The FAQ adds two practical points: a support period needs a date such as "no earlier than 30 June 2027", not "five years"; and a first-party companion app needs its own published period.

What do the Rules contain, section by section?

Two Parts and a Schedule. The registered text was made on 27 February 2025 and is short; this is the map a compliance file needs:

Provision Heading What it does
s2 Commencement Part 1 started on registration (4 March 2025); Part 2 and Schedule 1 started 12 months later (4 March 2026)
s6 Meaning of consumer Uses section 3 of the Australian Consumer Law
s8 Security standards for consumer grade relevant connectable products Sets the product class, the exclusions, and the "acquired in Australia by a consumer" condition
s9 Requirements for statement of compliance Lists what the statement must contain
s10 Retention period for statement of compliance 5 years, for manufacturers and suppliers
s11 Matters to be published with notification of failure to comply with recall notice What the Minister may publish about a failed recall
Sch 1, cl 2 Requirements in relation to passwords No universal default passwords
Sch 1, cl 3 Requirements relating to reports of security issues Published reporting route
Sch 1, cl 4 Requirements relating to defined support periods and security updates Published support period with an end date

The obligations themselves sit in the parent Cyber Security Act 2024, Part 2: section 15 (manufacture and supply in compliance with the standard), section 16 (statement of compliance) and sections 17 to 20 (enforcement).

Who do the Rules cover, and who's carved out?

Consumer-grade connectable products, minus six named exclusions. Section 8 covers products that "are intended by the manufacturer to be used, or are of a kind likely to be used, for personal, domestic or household use or consumption" and that "will be acquired in Australia by a consumer". The Department of Home Affairs factsheet gives smart TVs, smart watches, home assistants, baby monitors and consumer energy resources as examples. Section 8(1)(b) excludes:

  • a desktop computer or a laptop;
  • a tablet computer;
  • a smartphone;
  • therapeutic goods within the meaning of the Therapeutic Goods Act 1989;
  • a road vehicle, and a road vehicle component, within the meaning of the Road Vehicle Standards Act 2018.

Three scope details catch device makers out. The Department's FAQ (version of 4 March 2026) says the standards "apply to whole classes of smart devices, not individual cases of acquisition", so a product sold mostly to businesses is still in scope if a consumer could buy it. Aftermarket car audio and navigation units "are not currently considered road vehicle components", so they are likely to be in scope. And the Explanatory Statement treats smart meters as out of scope, because they are supplied and installed by electricity retailers rather than bought by consumers.

Timing follows the manufacture date: the Department states that "Products manufactured before 4 March 2026 are not required to comply with the security standards", and the supplier's duty applies only to products that had to comply when made.

What do the three requirements actually say?

Each clause is more detailed than the one-line summaries suggest:

Clause Core rule Detail that often gets missed
2 Passwords Passwords "must be: (a) unique per product … or (b) defined by the user of the product", in any state other than factory default Unique passwords must not be "based on incremental counters", based on public information, or derived from serial numbers unless done with an accepted encryption or keyed hashing method. Cryptographic keys, non-IP pairing PINs and API keys are not "passwords"
3 Security issues Publish "at least one point of contact" for reports, and when a reporter will receive "an acknowledgement of the receipt of the report" and "status updates until the resolution" The information must be in English, free, available without a request, and must not require personal information. No number of days is fixed
4 Support period Publish the defined support period, "expressed as a period of time with an end date" "The manufacturer must not shorten the defined support period after it is published." Extensions are allowed and must be published "as soon as is practicable". A manufacturer selling on its own website must show the period alongside the product's main characteristics

The FAQ adds two practical points: a support period needs a date such as "no earlier than 30 June 2027", not "five years"; and a first-party companion app needs its own published period.

How closely do they follow ETSI EN 303 645 and the UK PSTI regime?

Very closely. The Department's factsheet says the standards "closely follow the first three principles of the ETSI EN 303 645 standard and the United Kingdom's Product Security and Telecommunications Infrastructure (Security Requirements for Relevant Connectable Products) Regulations 2023". Those are the same three provisions behind the UK's PSTI regime and the US Cyber Trust Mark work, and the core of Singapore's CLS(IoT) Tier 1: see our ETSI EN 303 645 guide for provisions 5.1-1, 5.2-1 and 5.3-13 in their original form.

The overlap is useful in practice. FAQ question 16 says a manufacturer supplying the UK market "can use the same statement of compliance provided in accordance with the UK Regulations" in Australia, "as long as that statement of compliance meets all requirements set out in the Act and section 9 of Australia's Rules". Check the Australian-specific fields before reusing one: an Australian authorised representative, if there is one, and the batch identifier. Australia's earlier 2020 voluntary Code of Practice had 13 principles and asked industry to "prioritise the top three principles"; the Rules make those three mandatory.

What goes into the statement of compliance?

Seven items, under section 9(3) of the Rules:

  1. the product type and batch identifier;
  2. the name and address of the manufacturer, an authorised representative, and any other authorised representatives in Australia;
  3. a declaration that the statement was prepared by or on behalf of the manufacturer;
  4. a declaration that, in the manufacturer's opinion, the product complies and the manufacturer has met its other obligations;
  5. the defined support period at the date the statement is issued;
  6. the signature, name and function of the signatory;
  7. the place and date of issue.

The Department publishes an example template. The FAQ says the batch identifier "must identify the specific group of products manufactured or processed together", and wildcards are allowed. Section 10 sets the retention period at 5 years for both manufacturers and suppliers. The Explanatory Statement adds that statements "are not required to be provided with the product at point of sale": they are for the regulator.

Compliance duties and enforcement: how does it work?

Through notices that escalate in order. The Technology Assessment and Regulation Office in the Department of Home Affairs regulates the scheme for the Secretary, and the Department's page says it will "take an uplift-focused approach to regulation". Under the Act:

  1. Compliance notice (s17): the Secretary must first notify the entity and give it "a specified period (which must not be shorter than 10 days) to make representations".
  2. Stop notice (s18): only after a compliance notice has been given for the same non-compliance.
  3. Recall notice (s19): only after a stop notice.
  4. Public notification (s20): if an entity fails to comply with a recall notice, the Minister may publish details on the Department's website; section 11 of the Rules adds the recall details and consumer advice, such as destroying the product.

Section 22 gives internal review of a notice decision, and section 23 lets the Secretary require an examination of a product and its statement of compliance.

What's next for smart device security in Australia?

A voluntary label is next. The Explanatory Statement's impact analysis found that "the combination of a mandatory product standard and a voluntary labelling scheme for smart devices" was the best option. The Labelling Scheme for Smart Devices grant gives "an Internet of things (IoT) peak body with $1.7 million in funding" to "co-design and implement a voluntary labelling scheme", and its guidelines say the project must be completed "by 31 March 2027". GrantConnect lists IoT Alliance Australia as the recipient. Treat the current three-requirement baseline as a floor, and watch the Department's page for changes.

Worked example: how would a smart plug maker prepare?

Synthetic example, for illustration only: the company, product and dates are invented.

A maker of a Wi-Fi smart plug ("Plug P1", firmware 2.x, companion app) already sells in the UK and plans Australian retail from mid-2026:

  1. Confirm scopeThe plug is sold in retail stores for homes, so it is in scope. It is not on the section 8 exclusion list.
  2. Check manufacture datesUnits built in January 2026 can be sold without the new statement; units from the April 2026 production run must comply.
  3. Passwords (cl 2)The device's local web interface used a password derived from the MAC address. That derivation breaks cl 2(3)(c), so the team moves to a random per-unit password printed on the label.
  4. Reporting route (cl 3)The UK disclosure page already gives a contact address and says reports are acknowledged within 5 working days with monthly status updates. The team confirms the page needs no account or personal details, and adds a security.txt file that points researchers to it (see also our disclosure policy template).
  5. Support period (cl 4)The team publishes "Security updates for Plug P1 until at least 30 June 2030" on every product and comparison page, plus a separate date for the app.
  6. Statement of complianceIt reuses the UK statement, adds the Australian batch identifier and authorised representative, and stores it in a 5-year retention system that its Australian distributor can also access.
  7. Evidence fileIt keeps the firmware scan, password-generation design and published pages with the statement, ready for a section 23 examination.

What are the common pitfalls?

  • Reading the 4 March 2026 date as a sale date. The Department ties the obligation to the manufacture date.
  • Deriving "unique" passwords from serial numbers or MAC addresses without an accepted keyed method, which clause 2(3) rules out.
  • Publishing a duration instead of an end date for the support period, or hiding it on a regulatory page that the FAQ says should not be the only place.
  • Forgetting the app. A companion app that gets security updates needs its own published support period.
  • Shortening a support period after a component reaches end of life upstream: clause 4(4) forbids it, so pick a date the product team can keep.
  • Assuming a B2B channel takes the product out of scope, when a consumer could still buy it.

Where should a manufacturer start?

  1. Check the manufacture date, not the sale dateConfirm your own supply chain's manufacture dates before assuming stock is outside the Rules.
  2. Reuse ETSI EN 303 645 / PSTI / Cyber Trust Mark workUnique credentials, a disclosure channel and a published support window are the same engineering evidence, but the statement of compliance is a separate document. For EU sales, the Cyber Resilience Act goes much further than these three requirements.
  3. Draft the statement of compliance and retention process before the first covered unit ships
  4. Publish the support-period end date deliberately, because it cannot be shortened once published.
  5. Track the Department's page directlyThe FAQ has already been reissued once (December 2025, then March 2026).

Does AI write the statement of compliance for you?

No: the Rules require a manufacturer's own statement of compliance, and that stays a human, signed document. Where SoftWSP helps is upstream of it. Its platform extracts a firmware SBOM as a CycloneDX 1.6 document and matches the components against NVD, CISA KEV, FIRST EPSS and CISA CSAF ICS advisories. AI then drafts a report in which every finding cites its component and advisory record, and an engineer reviews it. That evidence supports decisions behind clause 4 (which components need updates during the support period) and helps find hard-coded credentials an engineer then confirms. AI doesn't test whether a password is unique on the production line, publish a disclosure policy or decide what counts as a reportable issue.

SoftWSP's device and firmware assessments can document the firmware evidence Australia's Rules, the UK's PSTI and the US Cyber Trust Mark all draw on: see Device & Firmware Security.

This guide summarizes the registered text of the Cyber Security (Security Standards for Smart Devices) Rules 2025, the Cyber Security Act 2024 and Department of Home Affairs guidance current as of this guide's last-updated date; it is not a substitute for the Rules' full text or for compliance or legal advice.

Put this guide to work

Frequently asked questions

What is the Cyber Security (Security Standards for Smart Devices) Rules 2025?

It is a legislative instrument made by the Australian Government under Part 2 of the Cyber Security Act 2024 (Cth) — the Act itself received Royal Assent on 29 November 2024. The Rules were registered on the Federal Register of Legislation on 4 March 2025 under reference F2025L00276, and, per that registered text, are structured as Part 1 (Preliminary: name, commencement, authority and definitions), Part 2 (Security Standards: a simplified outline, the meaning of "consumer," the security-standard obligation itself, statement-of-compliance requirements, a retention period, and recall-notice notification), and a Schedule setting out the three substantive technical requirements. They commenced on 4 March 2026, a date fixed by the instrument's own commencement provision rather than chosen informally.

What counts as a "relevant connectable product" under the Rules?

Industry guidance summarizing the Rules (the instrument's own definitions sit in Part 1, section 4) describes a relevant connectable product as a consumer-grade device that can connect, directly or indirectly, to the internet and is intended for personal, domestic or household use — smart TVs, IP cameras, smart speakers and home assistants, connected baby monitors, smart watches, home routers and similar connected appliances. Several categories are carved out: desktop computers and laptops, tablets, smartphones, therapeutic goods (regulated separately as medical devices), and road vehicles and road vehicle components. The Rules apply to covered products manufactured on or after 4 March 2026; stock manufactured before that date is not required to comply, because the standard was not in force when it was made.

What are the three security requirements, and do they track a specific international standard?

Per the Rules' Schedule (clauses 2 to 4, as reflected in the registered legislative text) and consistent secondary legal analysis, the three requirements are: (1) no universal default passwords — each device must ship with a unique per-device password or require the user to set one, rather than shipping a shared default; (2) a published mechanism for reporting security issues, with a public contact point and stated acknowledgement/update timelines; and (3) published transparency about the minimum period during which security updates will be provided, including a specified end date that, once published, cannot be shortened. Law-firm analysis of the Rules (AO Shearman) describes the first three as derived from the European Telecommunications Standards Institute's EN 303 645 baseline, while other coverage of the reform describes the regime as deliberately aligned with the UK's Product Security and Telecommunications Infrastructure (PSTI) Act regime, which rests on the same three ETSI EN 303 645 provisions — see our [ETSI EN 303 645](/guides/etsi-en-303-645-consumer-iot-security/) and [PSTI / US Cyber Trust Mark](/guides/psti-cyber-trust-mark/) guides for that baseline in its EU/UK/US form.

What must a manufacturer or supplier actually do to comply, and what happens if they don't?

The registered Rules require a manufacturer to prepare a statement of compliance for a covered product and a supplier to ensure the product is supplied together with that statement; secondary legal summaries of the retention provision (Part 2) describe a duty to keep that documentation for five years. The Department of Home Affairs administers the regime on the Secretary's behalf under the Cyber Security Act 2024, with compliance tools described in law-firm coverage of the reform (Minter Ellison, AO Shearman) including compliance notices, stop notices and recall notices for non-compliant products; confirm current enforcement detail directly with the Department before relying on it for a compliance decision.

Sources

  1. Federal Register of Legislation: Cyber Security (Security Standards for Smart Devices) Rules 2025 (F2025L00276) — registered legislative text, Parts 1-2 and Schedule structure
  2. Federal Register of Legislation: Cyber Security (Security Standards for Smart Devices) Rules 2025 — as-made PDF
  3. Department of Home Affairs: Security Standards for Smart Devices
  4. Minter Ellison: Cyber security standards for consumer smart devices — Australia's new mandatory IoT security requirements
  5. AO Shearman: Australia — new security standards for smart devices
  6. Federal Register of Legislation: Cyber Security Act 2024 (C2024A00098), as made — Part 2, sections 13-24
  7. Federal Register of Legislation: Explanatory Statement to F2025L00276 (PDF)
  8. Department of Home Affairs: Factsheet — Security standards for smart devices (PDF)
  9. Department of Home Affairs: Frequently asked questions — Security standards for smart devices, version of 4 March 2026 (PDF)
  10. Department of Home Affairs: Example statement of compliance template (PDF)
  11. Department of Home Affairs: Code of Practice — Securing the Internet of Things for Consumers (2020, PDF)
  12. business.gov.au: Labelling Scheme for Smart Devices grant
  13. GrantConnect: GA480666, Labelling Scheme for Smart Devices — IoT Alliance Australia
Was this guide helpful?

In this cluster

Australia's smart device cyber security standards (Rules 2025), explained