Artifact GuideAustraliaSmart Device Statement of Compliance

Australia Cyber Security Act Smart Device Statement of Compliance

For covered consumer-grade smart devices, the statement of compliance is the product-level record that connects the manufacturer, the product batch, the declared security-standard compliance position, and the support-period claim.

This page explains the statement requirements in force from 4 March 2026, the five-year retention duty, and the records needed if the Secretary requests the product, statement, or both for independent examination.

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

Structured answer sets in this page tree.

Primary sources
4

Cited legal and guidance references.

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

Australia's Cyber Security Act 2024 and the Cyber Security (Security Standards for Smart Devices) Rules 2025 require a for covered when the statutory awareness and acquisition conditions are met. The statement requirements commenced on 4 March 2026. The provides the statement for Australian supply, the supplies the product with it, and each retains a copy for the five-year period set by the Rules.

Section 1

When a smart-device statement of compliance is needed

The statement duty sits in Part 2 of the Cyber Security Act 2024. Part 2 applies to a manufactured on or after 29 November 2025, or supplied other than as second-hand goods on or after that date. The prescribed smart-device standard and statement requirements commenced on 4 March 2026.

The Smart Devices Rules prescribe a security standard for : products intended by the to be used, or of a kind likely to be used, for personal, domestic, or household use or consumption, excluding listed product categories such as desktop and laptop computers, tablets, smartphones, therapeutic goods, road vehicles, and road vehicle components. The official explanatory statement gives smart TVs, smart watches, home assistants, baby monitors, and energy resources as examples. Those examples explain the class but do not replace the Rules' product-specific connectivity, intended-use, acquisition, awareness, date, and exclusion tests.

The Rules use the Australian Law acquisition test. A consumer can be an individual or business where the goods cost no more than the current $100,000 threshold or are ordinarily acquired for personal, domestic, or household use, subject to the separate vehicle-or-trailer limb and exclusions for acquisitions such as resupply or use up or transformation in production, manufacture, repair, or treatment.

For an in-scope product, the must provide a statement for supply in Australia if it is aware, or could reasonably be expected to be aware, that the product will be acquired in Australia by a . A must supply the product with the statement when the same awareness condition is met.

  • Confirm that the product is a and is within the -grade class covered by the Smart Devices Rules.
  • Record whether any listed exclusion applies before treating the product as covered.
  • Identify the because the statement must be prepared by, or on behalf of, the manufacturer.
  • Identify each Australian path because the Act also places a supply-with-statement duty on suppliers.
Section 2

Required fields in the statement of compliance

The Smart Devices Rules specify mandatory statement fields for .

The statement must identify the product and batch and give the name and address of the and relevant authorised representatives. It must declare that it was prepared by or on behalf of the manufacturer and include the manufacturer's opinion that the product was manufactured in compliance with the security standard and that the manufacturer complied with the standard's other obligations.

The statement must also include the product's at the date of issue, plus the signature, name, and function of the 's signatory and the place and date of issue. The Rules prescribe the information, not an official government certificate, fixed layout, or mandatory wording beyond the required declarations.

Section 9 requires one 's name and address, plus each other authorised representative in Australia if any. It does not define authorised representative or prescribe an appointment form. Record the appointment basis and seek case-specific advice if the has no representative rather than treating the field as optional.

  • Product type and batch identifier.
  • name and address.
  • Name and address of an , plus the name and address of each other authorised representative in Australia, if any.
  • Declaration that the statement was prepared by, or on behalf of, the .
  • Declaration of the 's opinion on product compliance with the security-standard requirements and other obligations.
  • for the product at the date the statement is issued.
  • Signature, name, and function of the 's signatory.
  • Place and date of issue.
Section 3

Recordkeeping and five-year retention

The Act requires both the and , where the statement duty applies to them, to retain a copy of the statement for the period specified in the rules. For statements of compliance with the -grade smart-device security standard, the Smart Devices Rules set that period at five years.

Section 10 of the Rules specifies a five-year period but does not state how to calculate its start date. Record a conservative retention start and end date with counsel rather than implying that the Rules prescribe a particular starting event.

Tie the record to the exact product type and batch identifier used in the statement. Keep it with evidence for the 's security-standard position, publication, security-issue reporting process, and supply-chain handoff so a reviewer can connect the signed statement to the product supplied in Australia.

The Act says the must supply the product with the statement, but neither the Act nor the Rules prescribe a delivery medium. The explanatory statement says a physical statement is not required at the point of sale and that entities may provide or publish it. Record the delivery method used for each supply channel; public availability alone should not be treated as conclusive proof of the supplier's duty without case-specific analysis.

  • Keep the issued statement and any replacement or corrected statement for the applicable five-year period, with the retention calculation recorded.
  • Store the statement against the product type, batch identifier, , signatory, issue date, and Australian path.
  • Retain evidence supporting the statement's declared support period and the 's compliance opinion.
  • Make records show that the product was supplied in Australia with the statement, not merely that a statement existed internally.
  • Keep supporting technical and publication evidence separate from the issued statement while linking both to the same product type and batch; the Rules require the statement itself, while the larger evidence pack is an operational record supporting the 's opinion.
Section 4

Examination readiness

The Cyber Security Act 2024 allows the to engage an appropriately qualified and experienced expert to conduct an independent examination of a product where an entity must comply with section 15 or 16 obligations. The examination can assess whether the product complies with the security standard, whether the statement complies with section 16 requirements, or both.

For examination readiness, keep the statement retrievable together with the product identifier, details, Australian details, support-period publication evidence, and the technical evidence that supports password, security-issue reporting, and security-update support-period controls.

If a written request is made for examination, the Act says the notice may request the product, the , or both, and must specify matters such as the product, the if known, the period for providing the item, the period of retention for testing, the security-standard requirements to be tested, the testing or analysis to be done, and what may happen if the entity does not comply.

  • Maintain a retrieval path from the Australian-supplied product to the exact statement version that accompanied it.
  • Keep product samples, packaging references, firmware and software evidence, and support-period publication screenshots linked to the statement record.
  • Prepare a response owner for notices so product, legal, security, and supply-chain teams can provide the product or statement within the specified period.
  • Treat the statement as evidence that may be tested against the statutory requirements.
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 acquisition exclusions.
legislation.gov.au
Referenced sections
  • Provides the security-standard controls that statement records should be able to support: passwords, security-issue reporting, and defined support periods for security updates.
"Requirements relating to defined support periods and security updates"
legislation.gov.au
Referenced sections
  • Provides the examination power for products and statements of compliance, including written requests for the product, statement, or both.
"Examination to assess compliance with security standard and statement of compliance"
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 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.