FAQAustraliaStatements of Compliance

Cyber Security Act 2024 Statements of Compliance FAQ

A is the product-specific record the prepares for a covered smart device. Section 16 gives the a corresponding duty when the product is supplied in Australia.

The statement requirements have applied since 4 March 2026. Scope, required contents, the five-year retention duty, and supporting records are addressed below.

Author
Sorena AI
Published
May 9, 2026
Updated
Jul 24, 2026
Overview

Section 16 of the Cyber Security Act 2024 places statements of compliance in the smart-device security-standard regime. They are product-specific statutory statements. General cyber policy records do not satisfy the statement requirements. The current requirements apply to the consumer-grade class prescribed by the Smart Devices Rules, whose operative provisions commenced on 4 March 2026.

Search this module

Find a question or answer quickly

4 of 4 questions
Question 1

What should teams do about statements of compliance under the Cyber Security Act 2024?

For covered smart devices, the must provide a for supply in Australia, and the must supply the product in Australia with that statement. Both manufacturer and supplier must retain a copy for the period set by the rules.

Start by confirming scope. The current Smart Devices Rules prescribe a security standard for intended or likely to be used for personal, domestic, or household use or consumption, where the products will be acquired in Australia by a consumer. The rules exclude desktop and laptop computers, tablet computers, smartphones, therapeutic goods, road vehicles, and road vehicle components.

The statement must be prepared by, or on behalf of, the . The Act requires the to supply the covered product in Australia with a compliant statement when the statutory conditions are met. The official Explanatory Statement says the statement is not required to be provided with the product at the point of sale. Neither the Act nor the Rules prescribes a regulator-issued certificate, third-party approval, or mandatory statement template. The required contents still need to appear in the statement.

  • Classify the product against the consumer-grade relevant connectable product scope and listed exclusions before drafting the statement.
  • Map the actor role: prepares or authorises the statement; supplies the product with the statement and retains its copy.
  • Tie the statement to the security-standard evidence for passwords, vulnerability-reporting information, and published defined support periods where those Schedule 1 duties apply.
  • Keep the statement available for regulator review because the Secretary may request the product, the , or both for an independent examination.
Question 2

What must an Australian smart-device statement of compliance contain?

For statements of compliance with the security standard in Part 1 of Schedule 1 to the Smart Devices Rules, the statement must be prepared by, or on behalf of, the product . It must identify the product and responsible parties, record manufacturer declarations, name the , and include execution details.

Use the required legal contents in the issued statement rather than a generic security attestation. The declaration records the 's opinion; it does not replace the product and publication evidence supporting that opinion.

  • Product type and batch identifier.
  • Name and address of the , an of the manufacturer, and each other authorised representative, if any, that is in Australia. The Rules do not define a special statement-only meaning for authorised representative.
  • Declaration that the statement was prepared by, or on behalf of, the .
  • opinion that the product was manufactured in compliance with the security-standard requirements and that the manufacturer complied with other security-standard obligations for the product.
  • for the product at the date the statement is issued.
  • Signature, name, and function of the signatory, plus place and date of issue.
Question 3

What evidence and retention should teams keep for statements of compliance?

Manufacturers and suppliers must each retain a copy of the statement for the five-year period prescribed for the consumer-grade relevant connectable product security standard. The Act and Rules state the period but do not state in these provisions that every supporting engineering or supply record has the same prescribed retention period. The retention file should connect the signed statement to the product batch, the role, the handoff, and the underlying security-standard controls.

Evidence should be practical and product-specific: retain the issued statement, the product classification decision, supporting test or engineering records, the published vulnerability-reporting and support-period materials, distribution proof, and any notices or regulator correspondence about examination requests.

  • Retain the issued statement version, date and place of issue, signatory details, product type, and batch identifier for five years.
  • Keep scope evidence showing why the product is covered or excluded, including consumer-grade use analysis and any exclusion relied on.
  • Keep control evidence for passwords, security-issue reporting, and defined support periods where those Schedule 1 requirements apply.
  • Keep evidence showing the method used to meet the Act's statement supply duty in Australia, plus records of any corrections or replacement statements.
  • Keep examination-readiness records so the product, statement, or both can be produced if requested in writing by the Secretary.
Question 4

Which mistakes create risk for statements of compliance?

A broad cyber compliance memo cannot replace the product-specific statutory statement tied to the smart-device security standard. Suppliers also need their own retained copy and evidence of the method used to meet the Act's statement supply duty for products supplied in Australia.

  • Using the statement for products outside the current covered class without recording the scope analysis.
  • Omitting the , signatory function, batch identifier, or authorised-representative details required by the rules.
  • Keeping only engineering test evidence and not the actual issued statement.
  • Treating the five-year retention period as a -only obligation when section 16 also gives suppliers a copy-retention duty.
  • Publishing or supplying product information that conflicts with the support period recorded in the statement.
Primary sources

References and citations

legislation.gov.au5 citations
Referenced sections
  • Rules source for the covered consumer-grade relevant connectable product class, exclusions, required statement contents, and five-year retention period.
  • Section 8 defines the current covered class as consumer-grade relevant connectable products and lists exclusions.
  • Section 9 lists the required statement contents; Schedule 1 defines the support period recorded in the statement.
Show 2 more
  • Section 10 sets the retention period for covered statements of compliance at five years.
  • Schedule 1 requires the defined support period to be published and prevents shortening after publication.
"Requirements for statement of compliance"
More quoted passages
"intended by the manufacturer to be used"
"The statement must include the following information"
"the period is 5 years"
"must not shorten the defined support period"
legislation.gov.au4 citations
Referenced sections
  • Primary Act source for section 16 duties to provide, supply, retain, and meet rule-based requirements for statements of compliance, and section 23 independent examination powers involving products and statements.
  • Section 16 establishes manufacturer and supplier statement-of-compliance duties for relevant connectable products supplied in Australia.
  • Section 23 supports keeping examination-ready product and statement records because the Secretary may request them for an independent examination.
Show 1 more
  • Section 16 assigns statement supply and copy-retention duties to both manufacturers and suppliers.
"must meet the requirements provided by the rules"
More quoted passages
"must supply the product with a statement of compliance"
"the product, or the statement of compliance"
"must retain a copy of the statement"
legislation.gov.au
Referenced sections
  • Clarifies that statements of compliance are not required to be 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"
Show all related guides (29)

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

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 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 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.

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.