Start hereClassify products and the organisations supplying them
~35 days leftOpen step
Guide library
Regulation Asia–Pacific

Australia smart device security

Australian smart device security standards and statement of compliance

Check which connected consumer products are covered, show how their security features meet the rules, and supply the manufacturer’s statement of compliance.

Issuing authority
Australian Department of Home Affairs
Timing
Apply the rules before supply. Manufacturers and suppliers retain copies of the statement for five years. Maintain the published support period, including its end date, and publish extensions as soon as practicable.
Reviewed
Inside this guide
4 steps · 4 templates

Who it applies to

Manufacturers and Australian suppliers of covered consumer-grade relevant connectable products made on or after 4 March 2026. Review product and consumer definitions and the exclusions in Rule 8.

What you’ll produce

A model and batch scope record, evidence covering the three security requirements, a signed statement and a supplier handoff that reaches the purchaser.

The date of manufacture drives the transition. Use batch evidence when older and newer stock share a model name. Check both the device and in-scope software, including companion software where applicable.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

What applies to each entity, product and activity?
Have Legal or Regulatory confirm scope and applicable deadlines for each entity, activity and jurisdiction. Assign owners for incident reporting, filings and lifecycle changes where required.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.

How to spend the first week

  1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
  2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts.
  3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.

What to review each week

Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

Australia smart device security kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Classify products and the organisations supplying them · Product compliance + importer + Legal [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts.
3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • Can the supplier match an actual retail unit to the statement and manufacture date?
  • Can someone find the update end dates and report a product security issue without an account?

Worked scenario

A Melbourne importer receives two similar batches of a connected irrigation controller. Compliance records their manufacture dates and matches the covered batch to the manufacturer’s signed statement before releasing stock.

What to read next

FROM THE SOURCE

Cases and numbers

Rules commenced · 4 March 2026

5 yearsRequired retention period for statements of compliance

Two batches of the same model can have different obligations

Home Affairs says the requirements apply to covered products made on or after 4 March 2026. It also expects the available batch identifier on the statement to let suppliers and purchasers identify which products it covers.

What to check Keep the production date, product type, batch, statement version and supply channel in a single record.

Home Affairs smart device security FAQs (opens in a new tab)

Schedule 1 · support disclosures

Publish an end date customers can find before purchase

The rules require defined support periods for the covered updateable components. They prohibit shortening a published period and require publication of extensions as soon as practicable.

What to check Confirm the dates with the teams responsible for firmware and companion software before the statement is signed.

Schedule 1, clause 4 (opens in a new tab)
DATES AND TRIGGERS

Official milestones

See the deadline calendar
The whole journeyabout 35 days across 4 steps
  1. 01Classify products and the organisations supplying them, Product compliance + importer + Legal, about 7 days
  2. 02Verify passwords, reporting and support disclosures, Product security + firmware + customer support, about 14 days
  3. 03Prepare and supply the statement of compliance, Manufacturer signer + Regulatory Affairs + Distribution, about 7 days
  4. 04Keep statements and manage changes, Supplier operations + Product Security + Records, about 7 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 4 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Classify products and the organisations supplying themProduct compliance + importer + LegalBefore purchase or Australian releaseSet a start dateAustralian smart device scope and batch recordOpen
Verify passwords, reporting and support disclosuresProduct security + firmware + customer supportBefore approving the model for supplySet a start dateAustralian smart device security evidenceOpen
Prepare and supply the statement of complianceManufacturer signer + Regulatory Affairs + DistributionBefore releasing each covered product or batchSet a start dateAustralian smart device statement of complianceOpen
Keep statements and manage changesSupplier operations + Product Security + RecordsThroughout supply and supportSet a start dateAustralian smart device supplier release and retention logOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Classify products and the organisations supplying them

    Who Product compliance + importer + Legal When Before purchase or Australian release

    Record connectivity, sales channels and intended use. Check the Act and Rule 8 exclusions. Identify the manufacturer, Australian suppliers, product type and batch manufacture date. Obtain clear dated evidence for batches made before commencement.

    What to produce

    Australian smart device scope and batch recordSpreadsheet

    Gather first

    • Product label and specifications
    • Connectivity and intended use
    • Date-of-manufacture evidence
    • Sales channels
    • Act and Rule 8

    How to prepare it

    1. List each product type, model and batch. Record how it connects, who buys it, its intended use and who manufactures and supplies it in Australia.
    2. Check the relevant connectable product and consumer definitions and any exclusion. Keep dated evidence of manufacture for pre-commencement stock.
    3. Assign each batch an approval decision and record which statement is needed. Ask a warehouse colleague to match a carton to the record without relying on the retail model name alone.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional example
    Mallee Water Controller batch MAR-26-42, manufactured 12 March 2026, has app-controlled residential irrigation and is offered through Australian retailers.
    Older batch verification
    Batch FEB-26-11 was made on 20 February 2026. Compliance records the supplier’s production log and keeps the batches separate in inventory.

    Check before handing it over

    Every batch has a dated scope decision that a second person can verify against its label and supporting records.

    Give warehouse and supply teams the batch list, release flags and the approved document locator.

  2. 02

    Verify passwords, reporting and support disclosures

    Who Product security + firmware + customer support When Before approving the model for supply

    Test relevant passwords against Schedule 1, including the user-defined or unique-per-product route and limits on generation. Publish an English reporting contact and explain when reports will be acknowledged and updated. Publish clear support end dates for the covered updateable components.

    What to produce

    Australian smart device security evidenceSpreadsheet

    Gather first

    • Production model and firmware
    • Setup and reset documentation
    • Software component list
    • Published reporting and support pages
    • Schedule 1

    How to prepare it

    1. Verify the applicable password flow on production-representative devices and software. Record the unique or user-defined route and review the method against the generation restrictions.
    2. Review the published public reporting contact and promised timing for acknowledgement and status updates. Confirm that English guidance is free and available without sign-in or requesting personal information to display it.
    3. Record each updateable component in scope and its defined support end date. Test the manufacturer-controlled product pages and record where the support information appears.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional test entry
    On two initial production samples, setup requires a user-defined password. A second reviewer repeats the check after reset and signs the evidence record.
    Publication evidence
    The manufacturer saves dated copies of its reporting instructions, firmware support end date and separate companion app support end date.

    Check before handing it over

    A reviewer can verify each of the three Schedule 1 requirements against the actual device and public information.

    Give the manufacturer signer the reviewed evidence and give Support the reporting and update commitments.

  3. 03

    Prepare and supply the statement of compliance

    Who Manufacturer signer + Regulatory Affairs + Distribution When Before releasing each covered product or batch

    Use Rule 9 and the Home Affairs example. Record product and batch identity, applicable name and address information, required declarations, defined support period, signature, role, place and date. Verify the retailer can identify and supply the applicable statement with the product.

    What to produce

    Australian smart device statement of complianceMemo

    Gather first

    • Rule 9 and Home Affairs example
    • Approved security evidence
    • Product type and batch
    • Manufacturer and representative details
    • Defined support period

    How to prepare it

    1. Have the manufacturer or its delegate prepare the statement for the exact product. Check name and address fields for the manufacturer, its authorised representative and any other Australian authorised representatives as applicable.
    2. Include the required declarations about preparation and the manufacturer’s opinion on compliance. Set out the defined support period as it stands on issue and check that it matches the published dates.
    3. Have the manufacturer signatory add name, function, signature, issue place and date. Give the signed copy and batch mapping to all relevant suppliers.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional product and batch
    Mallee Water Controller, MAR-26-42. Enter the manufacturer’s legal name, postal address and applicable representative details from controlled records.
    Fictional support schedule
    Controller updates through 30 June 2030 and companion app updates through 30 June 2031. Confirm the dates across the published pages before signature.
    Signature block
    Manufacturer signatory name and function, signature, Melbourne as fictional issue place, and actual issue date.

    Check before handing it over

    The document contains the Rule 9 fields and can be matched to the correct batch, support disclosures and approved technical evidence.

    Send the signed copy to distribution and verify the version referenced in each supply channel.

  4. 04

    Keep statements and manage changes

    Who Supplier operations + Product Security + Records When Throughout supply and support

    Keep the signed statement retrievable for five years. Recheck supply when model, batch, support period or configuration changes. Keep published promises aligned with signed statements, publish extensions promptly and assign a response owner for regulatory notices.

    What to produce

    Australian smart device supplier release and retention logChecklist

    Gather first

    • Signed statement
    • Batch list and shipment records
    • Sales channel instructions
    • Retention policy
    • Published support end dates

    How to prepare it

    1. At receiving, map the signed statement to the lot and check that it matches the product and batch. Hold covered units with missing or inconsistent paperwork.
    2. Test how a customer receives the statement at supply. Confirm the printed, digital or other means reaches the purchaser and is tied to the correct product.
    3. Keep the signed copy retrievable for five years. Assign a custodian, record changes and revalidate the handoff when statements or support periods change.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional shipment
    The retailer checks MAR-26-42 against the signed statement and confirms the relevant document is included with orders.
    Retrieval drill
    A substitute records owner can find the signed copy from a carton label and provide the version given to customers.

    Check before handing it over

    The supplier can trace a retail unit to the statement it supplied and retrieve the retained version.

    Give the distribution owner a dated release decision and a way to stop dispatch if the evidence changes.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes