- Supports Board review procedures, including prioritisation, terms of reference, timing, and notification of reviews.
"Terms of reference for reviews"
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.
Structured answer sets in this page tree.
Cited legal and guidance references.
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.
These focused FAQ modules break this artifact into narrower answer sets so teams can move straight to the right source-backed guidance.
What records to keep for Cyber Security Act 2024 smart-device statements, ransomware payment reports, and supported SOCI or APRA overlap checks.
FAQ answer on Australia's Cyber Security Act ransomware payment reporting scope, $3 million turnover threshold, 72-hour trigger, report fields, and evidence.
FAQ answer on Australian Cyber Security Act 2024 statements of compliance for smart devices, including scope, actors, required contents, retention, evidence, and citations.
FAQ on Australia Cyber Security Act compliance notices, stop notices, recall notices, public notifications, owners, evidence fields, and grounded timing.
FAQ on when Australia Cyber Security Act ransomware reporting overlaps with SOCI critical infrastructure assets, responsible entities, and smart-device duties.
Direct FAQ answer on Cyber Security Act 2024 smart-device duties for manufacturers, importers, and suppliers, including scope, statement records, exceptions, and citations.
FAQ on Cyber Security Act 2024 smart-device scope: relevant connectable products, consumer-grade criteria, exclusions, Australian consumer acquisition, and records to keep.
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.
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.
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.
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.
Use these FAQ answers to assign smart-device scope checks, statement-of-compliance evidence, ransomware reporting intake, and incident-review response tasks inside Sorena.
Turn FAQ answers into scoped questions, evidence fields, and review tasks.
Use Research Copilot to answer follow-up questions with cited source material.
Review product scope, incident triggers, evidence, owners, and next compliance actions with Sorena.
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.
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.
"Terms of reference for reviews"
"the amount of turnover threshold"
"actions consumers are recommended to consider taking"
"National Cyber Security Coordinator"
"Security of Critical Infrastructure Act 2018"