FAQAustraliaNotices and recalls

Australia Cyber Security Act notices and recalls

The Australia Cyber Security Act uses compliance notices, stop notices, and recall notices to enforce smart-device obligations under sections 15 and 16.

The pre-notice representation period, the final notice's action period, , escalation, and public-notification power are separate parts of the response.

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

Notices and recalls under the Australia Cyber Security Act enforce section 15 and 16 smart-device duties. Those duties include manufacturer compliance and publication obligations, supplier non-supply obligations, and manufacturer and supplier statement-of-compliance duties.

Search this module

Find a question or answer quickly

5 of 5 questions
Question 1

What triggers Australia Cyber Security Act compliance, stop, and recall notices?

A can be issued by the when an entity that must comply with section 15 or 16 is not complying, or when information suggests possible non-compliance. A response record should start with the product, the relevant connectable product class, the security-standard requirement, the manufacturer or supplier role, and the specific section 15 or 16 obligation at issue.

A is the next escalation. It depends on a prior and the being reasonably satisfied that the compliance notice was not met or that attempted remediation was inadequate.

A is a further escalation after a . It can be issued where the stop notice was not met or remediation remains inadequate for the same section 15 or 16 non-compliance.

  • Responsible actor: the entity that must comply with the section 15 or 16 obligation, usually the manufacturer or supplier for the affected smart device.
  • Trigger evidence: the non-compliance or possible non-compliance, the applicable security-standard requirement, and any compliance-notice or stop-notice history.
  • Pre-notice timing: before giving a compliance, stop, or , the must notify the entity of the intention to issue it and allow at least 10 days for representations. The final notice must specify a separate reasonable period for compliance.
Question 2

Can an entity seek review or variation of a notice?

Yes. An entity may apply in writing to the for of a decision to give or vary a compliance, stop, or . The application must be made within 30 days after the notice is given. Within 30 days after receiving the application, the decision-maker must review the decision and affirm, vary, or revoke it, then provide written reasons as soon as practicable.

The may also vary a notice to correct an error, defect, or ambiguity, or to address the non-compliance adequately. Before a variation, the entity must receive at least 10 days to make representations. The Secretary may revoke a notice if no longer satisfied that the grounds for issuing it were met. Once a notice for a particular non-compliance or possible non-compliance is revoked under section 21, no further Part 2 notices may be issued for that same non-compliance.

  • Record the date the notice was given and calculate the 30-day internal-review application deadline from that date.
  • Keep the review application, supporting product and remediation evidence, review decision, and written reasons with the notice file.
  • Do not assume an internal-review application pauses the notice. The cited provisions create the review route but do not state that applying automatically stays the notice.
Question 3

What can an Australia Cyber Security Act recall notice require?

A must identify the entity, give brief details of the non-compliance, and specify the action the entity must take. The action can require the entity to stop the product being acquired in Australia, stop the product being supplied to suppliers for supply in Australia, or arrange return of the product to the entity or to the manufacturer.

The notice must also specify a reasonable period for the action. If the considers it appropriate, the notice can also specify a reasonable period for the entity to provide evidence that the action was taken. The notice must explain what may happen if the entity does not comply and how the entity may seek review.

  • Assign the recall response to a product owner who can stop Australian acquisition or supply, plus a manufacturer or supplier contact who can arrange product return.
  • Track the notice fields exactly: entity name, product details, non-compliance, required action, action period, evidence period if included, consequences, and review route.
  • Keep the recall scope tied to the particular instance of non-compliance because the Act allows only one to be given to an entity for that instance. Sections 17 and 18 contain corresponding one-notice limits for compliance and stop notices.
Question 4

What becomes public if an entity fails to comply with a recall notice?

If an entity fails to comply with a , the Minister may publish information on the Department's website or another way the Minister considers appropriate. The Act lists the identity of the entity, product details, non-compliance details, and risks posed by the product relating to the non-compliance.

The 2025 Smart Devices Rules add that the public notification may include details of the and actions consumers are recommended to consider, such as destroying the product or taking extra precautions when using it.

  • Publication-risk evidence: entity identity, affected product identifiers, non-compliance description, product risk explanation, recall-notice details, and recommended consumer actions.
  • Consumer messaging owner: product, legal, and security teams should reconcile recall wording against the 's notice and the Minister's possible public-notification fields.
  • Do not replace the notice's deadlines with the separate 10-day pre-notice representation period. The final notice specifies the reasonable action period and any evidence period.
Question 5

Can the Secretary request a product or statement for independent examination?

Yes. If an entity has a section 15 or 16 obligation for a relevant connectable product, the may engage an appropriately qualified and experienced expert to examine whether the product complies with the security standard, whether its statement of compliance meets section 16, or both.

For that examination, the may request the product, the statement, or both in writing. The request must identify the product, identify the manufacturer if known when the recipient is not the manufacturer, set a reasonable response period, describe the retention period and testing requirements for the product, explain the kind of testing or analysis, and explain possible consequences of non-compliance. The Commonwealth must pay reasonable compensation for complying with the request.

  • Keep a retrievable copy of the statement and a product or representative unit tied to the relevant type and batch.
  • Route the written request separately from a compliance, stop, or ; section 23 examination can assess compliance but is not another step in the three-notice escalation sequence.
  • Record the requested product, response deadline, expected retention period, tests described, item transfer, chain of custody, and compensation costs.
Primary sources

References and citations

legislation.gov.au6 citations
Referenced sections
  • Primary source for sections 17 to 20: compliance notices, stop notices, recall notices, representation periods, recall actions, and public notification after failure to comply.
  • Sections 17, 18, and 19 establish the compliance-notice, stop-notice, and recall-notice escalation path for section 15 or 16 smart-device obligations.
  • Sections 21 and 22 set the variation, revocation, representation, internal-review application, decision, and written-reasons rules.
Show 3 more
  • Section 19 lists the mandatory recall-notice contents, the available recall actions, evidence period language, review explanation, and one-notice-per-instance limit.
  • Section 20 identifies what the Minister may publish after failure to comply with a recall notice.
  • Section 23 authorises independent examination, lists the required contents of a written product or statement request, and provides reasonable compensation for compliance.
"Public notification of failure to comply with recall notice"
More quoted passages
"The Secretary may give an entity"
"within 30 days after the day on which the notice was given"
"arrange for the return"
"details of the product"
"independent examination of the product"
legislation.gov.au3 citations
Referenced sections
  • Primary source for the consumer-grade relevant connectable product security standard and the additional public-notification matters for recall-notice non-compliance.
  • Section 8 and the simplified outline identify the consumer-grade relevant connectable products covered by the security standard and the manufacturer and supplier obligations that enforcement notices can attach to.
  • Section 11 adds recall-notice details and recommended consumer actions to the matters that may be published after recall-notice non-compliance.
"Matters to be published with notification of failure to comply with recall notice"
More quoted passages
"Part 1 of Schedule 1 provides a security standard"
"actions consumers are recommended to consider"
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.