FAQAustraliaCyber Security Act

Australia Cyber Security Act FAQ

Direct answers on who is covered, what smart device controls are required, what goes into statements of compliance, and when ransomware payment reports are triggered.

Use these answers to route product, supplier, incident-response, and legal review questions against the Act and its 2025 rules.

Author
Sorena AI
Published
May 9, 2026
Updated
May 9, 2026
FAQ modules
7

Structured answer sets in this page tree.

Primary sources
5

Cited legal and guidance references.

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

The Cyber Security Act 2024 covers several different workflows: security standards for relevant connectable products, statements of compliance, ransomware payment reports, National Cyber Security Coordinator information sharing, and Cyber Incident Review Board reviews. This FAQ separates those workflows so teams can identify the rule, actor, trigger, required evidence, and official source.

Browse sub-FAQs

Choose the question set you need

These focused FAQ modules break this artifact into narrower answer sets so teams can move straight to the right source-backed guidance.

Browse all FAQ items22
Focused FAQ modules
7
Showing 7 of 7
FAQ module

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.

3 items
FAQ module

CSA 2024 Ransomware Threshold & Report FAQ

FAQ answer on Australia's Cyber Security Act ransomware payment reporting scope, $3 million turnover threshold, 72-hour trigger, report fields, and evidence.

3 items
FAQ module

Cyber Security Act 2024 Statements of Compliance FAQ

FAQ answer on Australian Cyber Security Act 2024 statements of compliance for smart devices, including scope, actors, required contents, retention, evidence, and citations.

4 items
FAQ module

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

3 items
FAQ module

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.

3 items
FAQ module

Manufacturer, Importer, and Supplier Duties under Australia's Cyber Security Act 2024

Direct FAQ answer on Cyber Security Act 2024 smart-device duties for manufacturers, importers, and suppliers, including scope, statement records, exceptions, and citations.

3 items
FAQ module

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.

3 items
Question 1

Which smart devices are covered by the Australia Cyber Security Act and Smart Devices Rules?

Part 2 of the Cyber Security Act applies to a relevant connectable product manufactured on or after Part 2 commences, or supplied in Australia on or after that commencement other than as second-hand goods. A relevant connectable product is an internet-connectable product or a network-connectable product unless exempted by rules.

The 2025 Smart Devices Rules currently prescribe the security standard for consumer grade relevant connectable products: products intended by the manufacturer to be used, or likely to be used, for personal, domestic, or household use or consumption, where the product will be acquired in Australia by a consumer.

  • Included product class: consumer grade relevant connectable products acquired in Australia by a consumer.
  • Excluded from that class under the Smart Devices Rules: desktop computers or laptops, tablet computers, smartphones, therapeutic goods, road vehicles, and road vehicle components.
  • Act scope evidence to keep: product connectivity analysis, intended use or likely consumer use, Australian acquisition pathway, manufacture or supply date, and any exemption relied on.
  • Supplier evidence to keep: whether the supplier knew, or could reasonably be expected to know, the product would be acquired in Australia in the specified circumstances.
Question 2

What must manufacturers and suppliers do for covered smart devices?

Manufacturers must manufacture covered relevant connectable products in compliance with the applicable security standard when they are aware, or could reasonably be expected to be aware, that the product will be acquired in Australia in the specified circumstances. Suppliers must not supply a non-compliant covered product in Australia on the same awareness basis.

For consumer grade relevant connectable products, the Smart Devices Rules require password controls, a published security-issue reporting route, and a published defined support period for security updates. Manufacturers must provide a statement of compliance for supply in Australia, and suppliers must supply the product with that statement.

  • Passwords must be user-defined or unique per product; unique per-product passwords must not be based on incremental counters, public information, serial numbers without accepted encryption or keyed hashing, or otherwise guessable in a way unacceptable under good industry practice.
  • Security issue reporting information must include at least one contact point and must say when reporters will receive acknowledgement and status updates until resolution.
  • The defined support period must be expressed as a period of time with an end date, must be published clearly and freely in English, and must not be shortened after publication.
  • Statements of compliance must be prepared by or on behalf of the manufacturer and include the product type and batch identifier, manufacturer and authorised representative details, compliance declarations, defined support period, signatory details, and place and date of issue.
Question 3

How long must Australia Cyber Security Act statements of compliance be kept?

For consumer grade relevant connectable products covered by the Smart Devices Rules, manufacturers and suppliers must retain a copy of the statement of compliance for 5 years. The Act places the retention duty on both the manufacturer that provides the statement and the supplier that supplies the product with it.

The retained record should prove the specific product and batch covered by the statement, who prepared it, who signed it, the declared compliance position, the defined support period at the issue date, and the place and date of issue.

  • Minimum record: final statement of compliance issued for the product and batch.
  • Product linkage: product type, batch identifier, model/version information, and Australian supply channel.
  • Authority linkage: manufacturer name and address, authorised representative details, signatory name, function, signature, and issue date.
  • Control linkage: evidence supporting the password, security-issue reporting, and support-period claims made in the statement.
Question 4

When does the Australia Cyber Security Act require a ransomware payment report?

A ransomware payment report is required when a reporting business entity is impacted by a cyber security incident and has provided, or knows another entity has provided on its behalf, a ransomware payment to an entity seeking to benefit from the incident. The report must be given within 72 hours of making the payment or becoming aware that the payment has been made, whichever applies.

The Ransomware Payment Reporting Rules say an entity will generally be a reporting business entity if it is a responsible entity for a critical infrastructure asset to which Part 2B of the Security of Critical Infrastructure Act 2018 applies, or if it carries on business in Australia and its annual turnover for the previous financial year exceeds $3 million. If the business operated for only part of the previous financial year, the threshold is prorated using the formula in the Rules.

  • Report content: reporting entity contact and business details, including ABN if any and address.
  • Payment by another entity: that other entity's contact and business details, including ABN if any and address.
  • Incident facts: when the incident occurred or is estimated to have occurred, when the reporting entity became aware, infrastructure and customer impact, ransomware or malware variants, exploited vulnerabilities, and information that could assist government response, mitigation, or resolution.
  • Extortion and payment facts: demand amount or non-monetary benefit, demanded method of provision, actual payment amount or non-monetary benefit, actual method of provision, communications timing, communication summary, and any pre-payment negotiations.
  • Search limit: the Rules only require information the reporting business entity knows or can find by reasonable search or enquiry within the 72-hour reporting period.
Question 5

What happens if a covered smart device does not comply?

For smart-device obligations under sections 15 and 16, the Secretary may issue a compliance notice when reasonably satisfied that an entity is not complying, or when aware of information suggesting possible non-compliance. Before giving a compliance notice, the Secretary must notify the entity and give a specified period of at least 10 days for representations.

If the entity has received a compliance notice and has not complied, or its rectification is inadequate, the Secretary may issue a stop notice. If the entity then has a stop notice and does not comply, or its rectification remains inadequate, the Secretary may issue a recall notice. If an entity fails to comply with a recall notice, the Minister may publish information about the failure.

  • Compliance notice evidence: alleged non-compliance, required corrective action, response period, representation record, and evidence requested by the Secretary.
  • Stop notice evidence: prior compliance notice, corrective actions taken, why those actions were accepted or considered inadequate, and supply-stop instructions.
  • Recall notice evidence: prior stop notice, affected product scope, consumer communication, recall execution, and remediation or disposal instructions.
  • Public notification evidence: recall notice details and any consumer actions recommended for publication, such as destroying the product or taking extra precautions.
Question 6

How do National Cyber Security Coordinator sharing and Cyber Incident Review Board reviews fit with incident response?

The Act allows an impacted entity to voluntarily provide information to the National Cyber Security Coordinator about a significant cyber security incident. The Coordinator's statutory role is to lead whole-of-government coordination and triage of action in response to significant cyber security incidents.

The Act also establishes the Cyber Incident Review Board. The Board causes reviews to be conducted for certain cyber security incidents and makes recommendations to government and industry about actions that could prevent, detect, respond to, or minimise the impact of similar incidents in the future. The Board Rules add procedures for review prioritisation, terms of reference, timing to avoid interfering with investigations, and notification of reviews.

  • Coordinator sharing evidence: incident summary, why the incident is significant, information voluntarily provided, recipient, date, and permitted cyber security purpose.
  • Board review evidence: referral or review notice, terms of reference, requested or required documents, privilege review, redaction issues, and response owner.
  • Disclosure control: keep information-use restrictions with any incident package because Parts 3, 4, and 5 include limits on use, disclosure, secondary use, and admissibility.
  • Overlap check: keep SOCI, privacy breach, APRA, law-enforcement, and customer-notice workflows separate so a voluntary Coordinator update or Board request does not supersede another mandatory report.
Primary sources

References and citations

legislation.gov.au
Referenced sections
  • Supports voluntary information sharing with the National Cyber Security Coordinator, the Coordinator's role, and the establishment and functions of the Cyber Incident Review Board.
"National Cyber Security Coordinator"
legislation.gov.au
Referenced sections
  • Supports the SOCI Act reference used by the Ransomware Payment Reporting Rules for responsible entities and Part 2B critical infrastructure assets.
"Security of Critical Infrastructure Act 2018"
Related guides

Explore more topics

Australia Cyber Security Act 2024 scope and definitions
Grounded 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 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 source-linked 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 Compliance Calendar
Calendar of grounded Australia Cyber Security Act milestones for ransomware reporting, smart-device security standards, statements of compliance, and statutory review.
Australia Cyber Security Act penalties and fines
Grounded guide to Australia Cyber Security Act civil penalties, smart-device enforcement notices, ransomware reporting exposure, Board notice failures, and evidence records.
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
Grounded template fields for Australia Cyber Security Act smart-device scope, statements of compliance, ransomware reports, notices, SOCI overlap, and records.
Australia Cyber Security Act Timeline And Commencement Guide
Australia Cyber Security Act guidance for Timeline And Commencement, with practical decisions, evidence, edge cases, and external source citations.
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 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.
Australia Smart Device Statement of Compliance Evidence Workflow
Evidence workflow for preparing, supplying, and retaining statements of compliance under Australia's Cyber Security Act 2024 and Smart Devices Rules.
CSA 2024 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.
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.
CSA 2024 Smart Device Statement of Compliance
What a smart-device statement of compliance must contain under Australia's Cyber Security Act 2024 and Smart Device Rules, who prepares and supplies it, how long to retain it, and how to prepare for examination.
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 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.
Smart Device Applicability: CSA 2024
A source-linked workflow for deciding whether a connected product is covered by Australia's Cyber Security Act 2024 smart-device standard and what evidence to keep.
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 source-linked scope checks.