Artifact GuideAPAC

Australia Cyber Security Act 2024 Smart Device Compliance Checklist

A comprehensive, release-ready Australia Cyber Security Act 2024 smart device compliance checklist for manufacturers and suppliers of connectable products sold in Australia. Covers every requirement in Schedule 1 of the Cyber Security (Security Standards for Smart Devices) Rules 2025: password security under Clause 2, vulnerability disclosure under Clause 3, defined support period under Clause 4, statement of compliance under Section 9, recordkeeping under Section 10, and excluded products under Section 8.

Built for product security engineers, compliance officers, product managers, legal counsel, and supply chain teams preparing smart devices for the Australian market. Part 2 and Schedule 1 of the Rules commenced on 4 March 2026, meaning every consumer grade connectable product supplied in Australia after that date must pass this Australia Cyber Security Act 2024 smart device compliance checklist.

Author
Sorena AI
Published
Mar 4, 2026
Updated
Mar 4, 2026
Sections
11

Structured answer sets in this page tree.

Primary sources
3

Cited legal and guidance references.

Publication metadata
Sorena AI
Published Mar 4, 2026
Updated Mar 4, 2026
Overview

This Australia Cyber Security Act 2024 smart device compliance checklist translates the three mandatory security standards in Schedule 1 of the Smart Device Rules 2025, together with the statement of compliance and recordkeeping obligations in Part 2 of those Rules, into a practical, section by section release gate. Every checklist item maps directly to a clause in the Rules or a section of the Cyber Security Act 2024. Use this Australia Cyber Security Act 2024 smart device compliance checklist before manufacturing, before first supply, and at every product revision to confirm that your product meets the password security, vulnerability disclosure, and defined support period requirements. A product that passes every item on this checklist is ready for the Australian market. A product that fails any item should not be supplied until the gap is closed. The Rules closely follow the UK Product Security and Telecommunications Infrastructure (PSTI) Regulations 2023, so manufacturers already compliant with the UK PSTI framework can map their existing compliance evidence to this Australia Cyber Security Act 2024 smart device compliance checklist, provided all requirements set out in the Australian Rules are met.

Section 1

How to use this Australia Cyber Security Act 2024 smart device compliance checklist

This Australia Cyber Security Act 2024 smart device compliance checklist is designed as a pre-supply release gate. Run through every section before a product enters the Australian distribution channel. Each checklist item corresponds to a specific clause in Schedule 1 of the Cyber Security (Security Standards for Smart Devices) Rules 2025 or a section in the Cyber Security Act 2024. The references are included so your legal and product teams can trace each requirement back to the official text.

The Australia Cyber Security Act 2024 smart device compliance checklist is organized into eleven sections that mirror the structure of the Rules. Start with scope verification to confirm the product is covered. Then confirm the product does not fall into the excluded products list under Section 8. Move through each technical control: password security under Clause 2, vulnerability disclosure under Clause 3, and defined support period under Clause 4. After the technical controls, verify security update delivery capability, confirm public information accessibility, prepare the statement of compliance under Section 9, lock the evidence pack under Section 10, and complete supply chain readiness checks.

If any item on this Australia Cyber Security Act 2024 smart device compliance checklist cannot be confirmed, stop the release process. Under Section 15 of the Act, manufacturers must manufacture in-scope products in compliance with the security standard if they are aware, or could reasonably be expected to be aware, that the product will be acquired in Australia. Under Section 16, suppliers must not supply a product in Australia if the product does not comply with the applicable security standard and the supplier is aware, or could reasonably be expected to be aware, of the non-compliance. Enforcement escalates from compliance notice (Section 17) to stop notice (Section 18) to recall notice (Section 19), with the Minister able to publish the failure publicly under Section 20.

Each section of this Australia Cyber Security Act 2024 smart device compliance checklist includes practical testing criteria that describe how to verify each requirement. These testing criteria are not mandated by the Rules themselves, but they represent the evidence you would need to demonstrate compliance if the Secretary issues a compliance notice and you must respond within the minimum 10 day representation period provided under Section 17(3)(b) of the Act.

Recommended next step

Turn Australia Cyber Security Act 2024 Smart Device Compliance Checklist into an operational assessment

Assessment Autopilot can take Australia Cyber Security Act 2024 Smart Device Compliance Checklist from turning this checklist into an operational workflow to a reusable workflow inside Sorena. Teams working on Australia Cyber Security Act 2024 can keep owners, evidence, and next steps aligned without copying this guide into separate documents.

Section 2

Product scope verification checklist for Australia Cyber Security Act 2024 smart devices

The first step in the Australia Cyber Security Act 2024 smart device compliance checklist is to confirm whether the product falls within the scope of the Cyber Security (Security Standards for Smart Devices) Rules 2025. Section 8 of the Rules defines the class of products covered: all relevant connectable products that are intended by the manufacturer to be used, or are of a kind likely to be used, for personal, domestic or household use or consumption. The specified circumstance is that the products will be acquired in Australia by a consumer as defined under Section 3 of the Australian Consumer Law.

Under Section 13 of the Cyber Security Act 2024, a relevant connectable product is a product that is an internet-connectable product or a network-connectable product and is not exempted under the Rules. An internet-connectable product can connect to the internet using a communication protocol that forms part of the internet protocol suite to send and receive data. A network-connectable product can send and receive data by electrical or electromagnetic energy and meets the conditions in Section 13(6) or 13(7) of the Act for indirect internet connectivity. This broad definition means that products communicating over Bluetooth, Zigbee, Z-Wave, or similar protocols to an internet-connected hub are still classified as relevant connectable products.

The scope determination also depends on the Australian Consumer Law definition of consumer. Under Section 3 of the ACL, a person acquires goods as a consumer if the goods cost less than the prescribed threshold (currently $100,000 including GST), or the goods are of a kind ordinarily acquired for personal, domestic or household use and consumption regardless of cost, or the goods are a vehicle or trailer used primarily for transporting goods on public roads. Products that are not ordinarily acquired by consumers, such as smart meters installed by electricity retailers, fall outside the scope of this Australia Cyber Security Act 2024 smart device compliance checklist.

Practical testing criteria for scope verification: Document the product's communication protocols and confirm whether it connects directly or indirectly to the internet. Record the manufacturer's intended use as stated on the label, in instructions, and in promotional materials. Confirm whether the product is of a kind ordinarily acquired by consumers. Check the price against the ACL threshold. Record the date of manufacture or first supply to confirm it falls on or after 4 March 2026. File the scope decision with a signature from the product compliance owner.

  • The product can connect directly or indirectly to the internet, making it a relevant connectable product under Section 13 of the Cyber Security Act 2024. Test by listing every communication protocol the product supports and confirming at least one provides a path to the internet.
  • The product is intended by the manufacturer for personal, domestic, or household use or consumption, or is of a kind likely to be used for those purposes, as required by Section 8(1)(a) of the Smart Device Rules 2025. Verify by reviewing the manufacturer's label, instructions for use, and all promotional or sales materials.
  • The product will be acquired in Australia by a consumer as defined under Section 3 of the Australian Consumer Law. Confirm price is below the $100,000 GST-inclusive threshold or that the product is of a kind ordinarily acquired for personal, domestic, or household use.
  • The product was manufactured on or after the commencement of Part 2 of the Cyber Security Act 2024, or will be supplied (other than as second hand goods) on or after that commencement date, as required by Section 13(1) of the Act
  • The legal entity (manufacturer or supplier), product model, product version, firmware version, and batch identifier are clearly documented for this Australia Cyber Security Act 2024 smart device compliance checklist review
  • A scope decision document has been prepared and signed by the compliance owner, explaining why the product is within the covered class under Section 8 of the Smart Device Rules 2025
Section 3

Excluded products checklist under Section 8 of the Smart Device Rules 2025

Section 8(1)(b) of the Cyber Security (Security Standards for Smart Devices) Rules 2025 lists six categories of products that are explicitly excluded from the consumer grade class even if they are relevant connectable products intended for personal, domestic, or household use. These exclusions exist because the excluded products are covered by other regulatory frameworks or have component supply chains too complex for the current standard. If your product falls into one of the excluded categories, the Australia Cyber Security Act 2024 smart device compliance checklist does not apply to that product. However, you must document your exclusion decision and retain it for at least five years alongside any related product records.

The six excluded categories are: desktop computers and laptops; tablet computers; smartphones; therapeutic goods within the meaning of the Therapeutic Goods Act 1989; road vehicles within the meaning of the Road Vehicle Standards Act 2018; and road vehicle components within the meaning of the Road Vehicle Standards Act 2018. The Explanatory Statement for the Rules explains the rationale for each exclusion. Desktop computers, tablets, and smartphones are excluded due to the difficulty manufacturers of these products would face in complying because of the complex nature of the supply chains of product components. Medical devices are excluded because they are more strictly regulated by the Therapeutic Goods Administration. Road vehicles and road vehicle components are excluded because they are covered by the Road Vehicle Standards Act 2018.

Practical testing criteria for exclusion verification: If you are claiming an exclusion, identify which of the six categories applies. Then confirm the product meets the legal definition of that excluded category under the relevant Act. For example, a product claimed as a therapeutic good must actually be registered or listed as a therapeutic good under the Therapeutic Goods Act 1989. A product claimed as a road vehicle component must meet the definition under the Road Vehicle Standards Act 2018. A borderline product that does not cleanly fit an exclusion category should be treated as within scope of this Australia Cyber Security Act 2024 smart device compliance checklist.

Edge cases to evaluate carefully: Consumer energy resources such as smart solar inverters and home battery systems are within scope of the Rules and are not excluded. Point of sale and contactless payment devices are within scope provided they cost less than the ACL threshold. Smart accessories for smartphones, such as Bluetooth earbuds, are within scope even though the smartphone itself is excluded, because the accessory is a separate relevant connectable product in its own right.

  • The product is not a desktop computer or a laptop, as excluded by Section 8(1)(b)(i) of the Smart Device Rules 2025
  • The product is not a tablet computer, as excluded by Section 8(1)(b)(ii) of the Smart Device Rules 2025
  • The product is not a smartphone, as excluded by Section 8(1)(b)(iii) of the Smart Device Rules 2025
  • The product is not a therapeutic good within the meaning of the Therapeutic Goods Act 1989, as excluded by Section 8(1)(b)(iv) of the Smart Device Rules 2025. If claiming this exclusion, record the ARTG registration or listing number.
  • The product is not a road vehicle within the meaning of the Road Vehicle Standards Act 2018, as excluded by Section 8(1)(b)(v) of the Smart Device Rules 2025
  • The product is not a road vehicle component within the meaning of the Road Vehicle Standards Act 2018, as excluded by Section 8(1)(b)(vi) of the Smart Device Rules 2025
  • If an exclusion is claimed, the exclusion decision has been documented with a reference to the specific legal definition under the relevant Act and retained in the evidence pack for at least five years
  • If no exclusion applies, the product is confirmed as within scope and the remainder of this Australia Cyber Security Act 2024 smart device compliance checklist must be completed in full
Section 4

Password security compliance checklist under Clause 2 of Schedule 1

Clause 2 of Schedule 1 of the Smart Device Rules 2025 sets out the password security requirements for the Australia Cyber Security Act 2024 smart device compliance checklist. These requirements apply to passwords used with the hardware of the product (when not in factory default state), pre-installed software, and any software that must be installed for the manufacturer's intended purposes. The password checklist items below cover both the unique per product model and the user-defined model. The definition of password in Clause 1 of Schedule 1 excludes cryptographic keys, personal identification numbers used for pairing in communication protocols that do not form part of the internet protocol suite, and application programming interface keys.

The Rules define 'unique per product' as unique for each individual product of a given product class or type. This means every single manufactured unit must have a different password. The Rules also define several prohibited derivation methods in Clause 2(3). Passwords must not be based on incremental counters (such as 'password1' and 'password2'). Passwords must not be based on or derived from publicly available information. Passwords must not be based on or derived from unique product identifiers such as serial numbers, unless the derivation uses an encryption method or keyed hashing algorithm accepted as good industry practice. Passwords must not be otherwise guessable in a manner unacceptable as part of good industry practice.

Good industry practice is defined in Clause 1 of Schedule 1 as the exercise of that degree of skill, diligence, prudence, and foresight which would reasonably and ordinarily be expected from a skilled and experienced cryptographer engaged in the same type of activity. This definition sets a high bar. A password generation scheme reviewed only by software developers, without input from a qualified cryptographer, may not meet this standard for this Australia Cyber Security Act 2024 smart device compliance checklist.

If your product ships with no password and requires the user to set one during initial setup, the user-defined model under Clause 2(2)(b) applies and the prohibited derivation restrictions in Clause 2(3) do not apply. However, you must verify that the product cannot be used in any meaningful way without the user first setting a password. A product that can be operated, configured, or accessed over a network without authentication fails this section of the Australia Cyber Security Act 2024 smart device compliance checklist.

Practical testing criteria for password security: Sample at least 20 units from different production batches. Extract the factory password from each unit and confirm every password is different. Verify no password follows an incremental counter pattern by checking for sequential characters across units. Confirm that no password can be derived from publicly visible information on the product packaging, label, or documentation. If passwords are derived from product identifiers, obtain the cryptographic design document and confirm a qualified cryptographer has reviewed the encryption method or keyed hashing algorithm. For the user-defined model, attempt to operate the product in a meaningful way without setting a password, including network access, configuration interfaces, and data retrieval.

  • Every password is either unique per product or defined by the user during setup, as required by Clause 2(2) of Schedule 1. Test by extracting default passwords from at least 20 units across multiple production batches and confirming every password is different.
  • No password is based on an incremental counter method, as prohibited by Clause 2(3)(a) of Schedule 1. Test by sorting all sampled passwords alphabetically and numerically and checking for sequential patterns such as 'password1', 'password2', or similar character rotation.
  • No password is based on or derived from publicly available information, as prohibited by Clause 2(3)(b) of Schedule 1. Test by cross-referencing each password against publicly visible information including MAC addresses, model numbers, packaging text, and any information available through unauthenticated network discovery.
  • No password is derived from unique product identifiers such as serial numbers, unless an encryption method or keyed hashing algorithm accepted as good industry practice is used, as required by Clause 2(3)(c) of Schedule 1. Test by collecting serial numbers from sampled units and confirming the password cannot be reconstructed from the serial number without knowledge of the secret key.
  • No password is otherwise guessable in a manner unacceptable as part of good industry practice, as required by Clause 2(3)(d) of Schedule 1. Test by running each sampled password against a common password dictionary and confirming no match is found.
  • The password generation process has been reviewed by a qualified cryptographer or security engineer against the good industry practice standard defined in Clause 1 of Schedule 1. Retain the cryptographic review report in the evidence pack.
  • Password compliance has been verified for all applicable components: hardware when not in factory default state, pre-installed software when not in factory default state, and software required for the manufacturer's intended purposes, as specified in Clause 2(1)(a), (b), and (c) of Schedule 1
  • If the user-defined password model is used, the product cannot be operated, configured, accessed over a network, or used to retrieve data in any meaningful way without the user first setting a password. Test by powering on the product and attempting all functional pathways before password creation.
Section 5

Vulnerability disclosure compliance checklist under Clause 3 of Schedule 1

Clause 3 of Schedule 1 of the Smart Device Rules 2025 requires manufacturers to publish specific information about how security issues can be reported. This section of the Australia Cyber Security Act 2024 smart device compliance checklist verifies that the vulnerability disclosure process meets every requirement in the Rules. The reporting requirements apply to security issues in the hardware, pre-installed software, software required for the manufacturer's intended purposes, and any software used for or in connection with those purposes. This last category, Clause 3(1)(d), is broader than the password requirements in Clause 2 because it includes companion applications, cloud services, and any other software used in connection with the product's intended purpose.

The published information must include at least one point of contact where a person can report security issues to the manufacturer. The manufacturer must also specify when a reporter will receive an acknowledgement of their report and when they will receive status updates until the security issue is resolved. This means you need a defined triage and response workflow, not just a contact email address. The word 'when' in Clause 3(2)(b) requires a stated timeframe, such as 'acknowledgement within 5 business days', not a vague commitment like 'as soon as possible'.

Clause 3(3) of the Rules adds four accessibility requirements that are frequently missed during compliance reviews for this Australia Cyber Security Act 2024 smart device compliance checklist. The vulnerability disclosure information must be available without prior request, in English, free of charge, and without requiring the reporter to provide personal information to access the contact details. A vulnerability reporting page that sits behind a login wall or requires registration fails this section of the checklist. However, as the Explanatory Statement clarifies, once a person submits a report, the manufacturer may request reasonable contact information such as an email address for the purpose of providing the acknowledgement and status updates required under Clause 3(2)(b).

Practical testing criteria for vulnerability disclosure: Open a browser in private or incognito mode (to simulate an anonymous visitor) and navigate to the manufacturer's vulnerability reporting page. Confirm the page loads without requiring login, registration, or submission of any personal information. Confirm the page is in English. Confirm no paywall or subscription is required. Confirm the page states at least one contact method (email address, web form, or phone number). Confirm the page states a specific timeframe for acknowledgement of receipt. Confirm the page states a specific timeframe or frequency for status updates until resolution. Then submit a test report and verify that the acknowledgement and status update process works within the published timeframes.

  • At least one point of contact for reporting security issues is published and accessible, as required by Clause 3(2)(a) of Schedule 1. Test by navigating to the published URL and confirming a contact method (email, web form, or phone number) is visible.
  • The published information states a specific timeframe for when reporters will receive an acknowledgement of their report, as required by Clause 3(2)(b)(i) of Schedule 1. Test by reading the published text and confirming a concrete period is stated (such as '5 business days'), not a vague commitment.
  • The published information states a specific timeframe or frequency for when reporters will receive status updates until the security issue is resolved, as required by Clause 3(2)(b)(ii) of Schedule 1. Test by confirming the published text includes an update interval or milestone schedule.
  • The vulnerability disclosure information is accessible, clear, and transparent, as required by Clause 3(3) of Schedule 1. Test by having a person unfamiliar with the product attempt to find and understand the reporting instructions without guidance.
  • The information is available without prior request from the person seeking it, as required by Clause 3(3)(a) of Schedule 1. Test by confirming the information is published on a web page that can be found through the manufacturer's website navigation or through a search engine query.
  • The information is published in English, as required by Clause 3(3)(b) of Schedule 1. Test by confirming all reporting instructions, timeframes, and contact details are displayed in English.
  • The information is available free of charge, as required by Clause 3(3)(c) of Schedule 1. Test by accessing the page without any payment, subscription, or premium membership.
  • The information can be accessed without providing personal information, as required by Clause 3(3)(d) of Schedule 1. Test by opening the page in a private browser session and confirming no login, registration, or personal data entry is required to view the contact details and reporting process.
  • An internal triage process exists that can receive, acknowledge, track, and resolve reported security issues within the published timeframes. Test by submitting a simulated security report and verifying the acknowledgement is received within the stated period.
  • The vulnerability disclosure process covers all four component categories listed in Clause 3(1): hardware, pre-installed software, software required for the manufacturer's intended purposes, and software used in connection with those purposes including companion applications and cloud services
Section 6

Defined support period compliance checklist under Clause 4 of Schedule 1

Clause 4 of Schedule 1 of the Smart Device Rules 2025 requires manufacturers to publish a defined support period for security updates. This is one of the most consequential items on the Australia Cyber Security Act 2024 smart device compliance checklist because the defined support period, once published, cannot be shortened under Clause 4(4). If the manufacturer extends the defined support period, Clause 4(5) requires the new period to be published as soon as is practicable.

The defined support period must be expressed as a period of time with an end date, as required by Clause 4(3). The Explanatory Statement provides an example: 'no later than 30 June 2027'. A vague statement like 'updates provided for the life of the product' or 'updates until further notice' does not satisfy this requirement. The end date must be a calendar date that a consumer can understand without technical knowledge.

Clause 4(1) lists four categories of components that require a published defined support period: hardware capable of receiving security updates; pre-installed software capable of receiving security updates; software that must be installed for the manufacturer's intended purposes and is capable of receiving security updates; and software developed by or on behalf of any manufacturer that is capable of receiving security updates and used for or in connection with the manufacturer's intended purposes. Each of these components may have a different support end date, and each must be published individually if they differ.

Clause 4(2) defines a security update as a software update that protects or enhances the security of the product, including a software update that addresses a security issue which has been discovered by or reported to the manufacturer. The manufacturer must provide available security updates to the product while it is within its defined support period, as far as practicable and in line with good industry practice.

The publication requirements for the defined support period are more demanding than most manufacturers expect when completing this Australia Cyber Security Act 2024 smart device compliance checklist. Clause 4(6) requires the information to be accessible, clear, and transparent. It must be in English. It must be free of charge. It must be available without prior request. It must be available without requiring personal information. And it must be understandable by a reader without prior technical knowledge. This last requirement, in Clause 4(6)(b)(v), is unique to the defined support period and does not appear in the vulnerability disclosure requirements.

Practical testing criteria for the defined support period: Read the published support period statement. Confirm it includes a calendar end date. Confirm the end date is in the future at the time of first supply. Confirm the statement is in plain language a non-technical person can understand. For each of the four component categories in Clause 4(1), confirm whether the component is capable of receiving security updates. If it is, confirm a defined support period is published for that component. If the support end dates differ by component, confirm each is published separately. Check that the published period has not been shortened from any previously published version.

  • The defined support period is published for all hardware capable of receiving security updates, as required by Clause 4(1)(a) of Schedule 1. Test by identifying every hardware component that can receive firmware updates and confirming a support end date is published for each.
  • The defined support period is published for all pre-installed software capable of receiving security updates, as required by Clause 4(1)(b) of Schedule 1. Test by listing all pre-installed software modules and confirming a support end date is published for each that is updateable.
  • The defined support period is published for all required software capable of receiving security updates, as required by Clause 4(1)(c) of Schedule 1. Test by identifying any software the user must install for the manufacturer's intended purposes and confirming a support end date is published.
  • The defined support period is published for all manufacturer-developed software used for the product's intended purposes that is capable of receiving security updates, as required by Clause 4(1)(d) of Schedule 1. This includes companion mobile applications and cloud services developed by or on behalf of the manufacturer.
  • The defined support period is expressed with a fixed calendar end date, not an open-ended or vague commitment, as required by Clause 4(3) of Schedule 1. Test by reading the published text and confirming a specific date appears (such as 'no later than 30 June 2029').
  • The manufacturer has confirmed the defined support period will not be shortened after publication, in compliance with Clause 4(4) of Schedule 1. If the period has been extended, confirm the new period was published as soon as practicable under Clause 4(5).
  • The published information is accessible, clear, transparent, in English, free of charge, and available without requiring personal information, as required by Clause 4(6)(a) and (b)(i) through (iv) of Schedule 1
  • The published information is understandable by a reader without prior technical knowledge, as required by Clause 4(6)(b)(v) of Schedule 1. Test by having a non-technical person read the statement and confirm they understand when security updates will stop being provided.
  • If the product is sold on the manufacturer's website, the defined support period is prominently published with information intended to inform consumer purchasing decisions, as required by Clause 4(7)(a) of Schedule 1. Test by visiting every product listing, product comparison, and product purchase page and confirming the support period is visible.
  • If the product is sold on the manufacturer's website, the defined support period is given equal prominence with the main product characteristics wherever those characteristics appear, as required by Clause 4(7)(b) of Schedule 1. Test by comparing the font size, placement, and visibility of the support period against the product's features, benefits, and specifications on each page.
Section 7

Security update delivery compliance checklist for Australia Cyber Security Act 2024 smart devices

While the Smart Device Rules 2025 focus on publishing the defined support period rather than prescribing a specific update mechanism, this section of the Australia Cyber Security Act 2024 smart device compliance checklist addresses the operational capability to deliver security updates throughout the published support period. Clause 4(2) of Schedule 1 defines a security update as a software update that protects or enhances the security of the product, including updates that address security issues discovered by or reported to the manufacturer.

Once you publish a defined support period, you are committing to provide security updates for the entire duration of that period. The Explanatory Statement confirms that the manufacturer must provide an available security update to a product, while the product is within its defined support period, as far as practicable and in line with good industry practice. A product that cannot reliably receive updates, or that has an update path vulnerable to tampering, undermines the entire compliance framework of this Australia Cyber Security Act 2024 smart device compliance checklist.

Test the update path end to end before the product is supplied in Australia. Confirm that updates can be delivered to the hardware, pre-installed software, and any required software components. Verify update integrity checks, rollback capabilities, and version traceability. These operational tests are not explicitly mandated by the Rules, but they provide the evidence that your defined support period commitment is credible and that you can meet the good industry practice standard referenced throughout Schedule 1.

Practical testing criteria for security update delivery: Push a test update to at least five units from different production batches. Verify the update installs successfully on each unit. Verify the update's digital signature or checksum is validated before installation. Attempt to push a tampered update file and confirm the device rejects it. Simulate an interrupted update (such as a power loss during installation) and confirm the device recovers to a functional state. Record the firmware version before and after each test to confirm version traceability.

  • Security updates can be delivered to every hardware component covered by the defined support period. Test by pushing a firmware update to the hardware and confirming successful installation on multiple units.
  • Security updates can be delivered to every pre-installed software component covered by the defined support period. Test by pushing a software update and confirming successful installation on multiple units.
  • Security updates can be delivered to every required software component covered by the defined support period, including companion applications and cloud service components
  • The update delivery mechanism includes integrity verification to prevent tampering during transit. Test by modifying a legitimate update file and confirming the device rejects the tampered file.
  • The update process supports version traceability so each installed update can be identified and audited. Test by querying the device firmware version after an update and confirming it matches the intended version.
  • The update process has been tested for recoverability in case an update fails or corrupts the device. Test by interrupting an update in progress (simulating power loss or network disconnection) and confirming the device returns to a working state.
  • A process exists to identify, prioritize, develop, test, and deploy security updates within the published support period. Document the process with roles, responsibilities, and target timeframes for each stage.
  • The update delivery infrastructure (servers, CDN, signing keys, and certificates) is confirmed to remain operational and maintained for the full duration of the published defined support period
Section 8

Website and public information compliance checklist for Australia Cyber Security Act 2024 smart devices

The Smart Device Rules 2025 treat public-facing information as part of the compliance obligation, not as a marketing activity. Both Clause 3 (vulnerability disclosure) and Clause 4 (defined support period) require information to be published in a way that meets specific accessibility standards. This section of the Australia Cyber Security Act 2024 smart device compliance checklist consolidates all the public information requirements into one verification pass.

The key accessibility requirements appear in both Clause 3(3) and Clause 4(6) of Schedule 1: information must be accessible, clear, and transparent. It must be in English. It must be free of charge. It must be available without prior request. It must be available without requiring the person to provide personal information. For defined support period information, Clause 4(6)(b)(v) adds that the information must be understandable by a reader without prior technical knowledge.

If the manufacturer sells the product on its own website, Clause 4(7) adds further requirements. The defined support period must appear alongside the main product characteristics and be given equal prominence. The Explanatory Statement explains that the defined support period must be published in any location on the website where either of two criteria are met: information intended to inform consumer acquisition decisions is published, or the main characteristics of the product are published. This may require the manufacturer to publish the defined support period in multiple locations on the website. The Explanatory Statement provides examples: product information pages, product purchase pages, and product comparison pages are likely to require the support period. Generic press releases, support articles, and accessory pages are not likely to require it.

Practical testing criteria for public information: Visit the manufacturer's website in a private browser session. Locate the vulnerability disclosure page and the defined support period page. Confirm both are accessible without login, registration, or payment. Confirm both are in English. Confirm the defined support period is understandable by a non-technical reader. Then visit every product listing, product comparison, and product purchase page on the website and confirm the defined support period is displayed with equal prominence to the main product characteristics.

  • The vulnerability disclosure contact and process information is published on a public web page accessible without authentication
  • The defined support period with its calendar end date is published on a public web page accessible without authentication
  • All published compliance information is in English and free of charge, meeting the requirements of Clause 3(3)(b), Clause 3(3)(c), Clause 4(6)(b)(ii), and Clause 4(6)(b)(iii) of Schedule 1
  • No login, registration, or personal information submission is required to view the compliance information, meeting the requirements of Clause 3(3)(d) and Clause 4(6)(b)(iv) of Schedule 1
  • The language used in defined support period information is understandable by a reader without technical knowledge, meeting the additional requirement of Clause 4(6)(b)(v) of Schedule 1
  • If the product is sold on the manufacturer's website, the defined support period appears on every page where information intended to inform consumer purchasing decisions is published, as required by Clause 4(7)(a) of Schedule 1
  • If the product is sold on the manufacturer's website, the defined support period is given equal prominence with the main product characteristics on every page where those characteristics appear, as required by Clause 4(7)(b) of Schedule 1. Check product information pages, product purchase pages, and product comparison pages.
  • The defined support period is not published only in the statement of compliance or only in a regulatory section of the website if product characteristics and purchasing information appear elsewhere, as emphasized in the Explanatory Statement
  • Packaging and point of sale materials, where applicable, reference the published compliance information or include equivalent details
Section 9

Statement of compliance preparation checklist under Section 9 of the Smart Device Rules 2025

Section 9 of the Smart Device Rules 2025 specifies the mandatory contents for the statement of compliance. Under Section 16 of the Cyber Security Act 2024, manufacturers must provide a statement of compliance for the supply of in-scope products in Australia, and suppliers must supply the product accompanied by a statement of compliance that meets the requirements in the Rules. The statement must be prepared by, or on behalf of, the manufacturer. Do not issue the statement as a paperwork exercise at the end of the process. The statement is the final output of the Australia Cyber Security Act 2024 smart device compliance checklist and should only be completed when every preceding section has been passed.

Section 9(3) of the Rules lists seven categories of required information. The statement must include: the product type and batch identifier; the name and address of the manufacturer, an authorised representative, and any other authorised representatives in Australia; a declaration that the statement was prepared by or on behalf of the manufacturer; a declaration that the product was manufactured in compliance with the security standard and that the manufacturer has complied with any other obligations; the defined support period at the date the statement is issued; the signature, name, and function of the signatory; and the place and date of issue.

The statement of compliance is not required to be physically included with the product at the point of sale. As the Explanatory Statement confirms, the statement is primarily for the regulator to verify that the responsible entity has met its obligations under the Act and Rules. However, manufacturers and suppliers may choose to provide or publish the statement with their product. If you already comply with the UK PSTI statement of compliance requirements, you can use the same information for Australia, provided all the requirements in Section 9 of the Smart Device Rules 2025 are met.

Practical testing criteria for statement of compliance: Prepare a draft statement and compare every field against the seven categories in Section 9(3). Verify the product type and batch identifier match the manufacturing records. Verify all names and addresses are current. Verify the defined support period in the statement matches the period published on the website. Have the signatory confirm they have the authority to sign on behalf of the manufacturer and document the approval chain. Record the place and date of issue. Then file the signed statement in the evidence pack before first supply in Australia.

  • The statement includes the product type and batch identifier, as required by Section 9(3)(a) of the Smart Device Rules. Test by cross-referencing the product type and batch identifier against manufacturing records to confirm accuracy.
  • The statement includes the name and address of the manufacturer, as required by Section 9(3)(b)(i) of the Smart Device Rules. Test by confirming the manufacturer's name and address match the current business registration.
  • The statement includes the name and address of an authorised representative of the manufacturer, as required by Section 9(3)(b)(ii) of the Smart Device Rules
  • The statement includes the name and address of each (if any) of the manufacturer's other authorised representatives in Australia, as required by Section 9(3)(b)(iii) of the Smart Device Rules
  • The statement includes a declaration that it has been prepared by, or on behalf of, the manufacturer, as required by Section 9(3)(c) of the Smart Device Rules
  • The statement includes a declaration that, in the opinion of the manufacturer, the product has been manufactured in compliance with the security standard and that the manufacturer has complied with any other obligations relating to the product in the security standard, as required by Section 9(3)(d) of the Smart Device Rules
  • The statement includes the defined support period for the product at the date the statement is issued, as required by Section 9(3)(e) of the Smart Device Rules. Test by confirming the period in the statement matches the period published on the website.
  • The statement includes the signature, name, and function of the signatory, as required by Section 9(3)(f) of the Smart Device Rules. Test by confirming the signatory has documented authority to sign on behalf of the manufacturer.
  • The statement includes the place and date of issue, as required by Section 9(3)(g) of the Smart Device Rules
  • The signatory has the authority to sign on behalf of the manufacturer, and the internal approval trail is documented and retained
  • If the same statement of compliance is used for both Australia and the UK PSTI regime, all seven categories in Section 9(3) of the Smart Device Rules have been verified independently for the Australian requirements
Section 10

Recordkeeping and evidence retention compliance checklist under Section 10

Section 10 of the Smart Device Rules 2025 specifies that statements of compliance must be retained for five years. This five year period applies to both manufacturers and suppliers. The period was reduced from the originally proposed ten years following stakeholder feedback during the public consultation, as noted in the Explanatory Statement. The Explanatory Statement states this reduction is consistent with the average lifespan of a relevant connectable product and reduces administrative burden on industry.

A compliance checklist is only as strong as the evidence behind it. Every item on this Australia Cyber Security Act 2024 smart device compliance checklist should be backed by documented evidence that can be produced if the Secretary issues a compliance notice under Section 17, a stop notice under Section 18, or a recall notice under Section 19 of the Cyber Security Act 2024. Build your evidence pack as you work through the checklist, not after the product has been released.

If the Secretary issues a compliance notice under Section 17 of the Act, the entity has a minimum of 10 days to make representations before the notice takes effect, as required by Section 17(3)(b). Having a complete evidence pack ready before this situation arises is the most effective way to respond quickly and demonstrate compliance. Under Section 23 of the Act, the Secretary may also request the manufacturer or supplier to provide the product, the statement of compliance, or both for the purposes of an independent audit to assess compliance.

Practical testing criteria for recordkeeping: Confirm that a document management system or repository is in place and that it supports retention for at least five years. Confirm that every category of evidence listed below has been uploaded or filed before first supply in Australia. Assign a retention start date equal to the date of first supply. Set a calendar reminder for the five year retention expiry. Confirm that records can be retrieved within 48 hours if the Secretary requests them.

  • A scope decision document exists that explains why this product is (or is not) within the covered class under Section 8 of the Smart Device Rules. The document includes references to the product's communication protocols, intended use, and consumer classification.
  • Password design documentation includes the generation method, whether the unique per product or user-defined model is used, the cryptographic review findings from a qualified cryptographer, and test results from batch sampling
  • Vulnerability disclosure process documentation includes the published contact method, published acknowledgement timeline, published update frequency, internal resolution tracking workflow, and internal triage procedures
  • Defined support period publication evidence includes timestamped screenshots or web archive captures of every page where the support period is displayed, taken at the time of first supply in Australia
  • Security update capability test results demonstrate that updates can be delivered, verified with integrity checks, and installed on every covered component across multiple production batches
  • The signed statement of compliance is stored with the evidence pack in a system that supports the five year retention requirement under Section 10 of the Smart Device Rules
  • Website publication evidence is captured at the time of first supply and updated whenever the published information changes. Each capture includes the page URL, date, and a full page screenshot or web archive file.
  • All evidence is organized by product model, batch identifier, date of first supply in Australia, and the date the statement of compliance was issued
  • A retention policy document is in place that assigns responsibility for maintaining the evidence pack, sets the five year retention period, and describes the retrieval process if the Secretary issues a compliance notice or requests an audit under Section 23 of the Cyber Security Act 2024
  • If the product is also sold in the UK under PSTI, the Australian evidence pack is maintained separately or contains clear mappings to Australian requirements to avoid confusion during a regulatory review
Section 11

Supply chain and distribution compliance checklist for Australia Cyber Security Act 2024 smart devices

The Cyber Security Act 2024 places obligations on both manufacturers and suppliers. Under Section 15, manufacturers must manufacture in-scope products in compliance with the security standard if they are aware, or could reasonably be expected to be aware, that the product will be acquired in Australia in the specified circumstances. Under Section 16, suppliers must not supply non-compliant products and must ensure every product is accompanied by a compliant statement of compliance. The term 'supply' has the same meaning as in the Australian Consumer Law, which means obligations extend across the entire distribution chain in Australia.

This section of the Australia Cyber Security Act 2024 smart device compliance checklist ensures that everyone in the supply chain understands their role. Distributors, importers, and retailers all qualify as suppliers under the Act if they supply the product in Australia. Each supplier must have access to the statement of compliance and must be able to confirm that the product they are supplying meets the security standard. Each supplier must also retain a copy of the statement of compliance for five years under Section 16(4) of the Act, as specified in Section 10 of the Rules. If a supplier becomes aware that a product is non-compliant, the supplier must stop supplying that product immediately.

Build compliance communication into your distribution agreements. Every entity that supplies the product in Australia should know where to find the statement of compliance, how to verify it, and what to do if they receive a compliance notice, stop notice, or recall notice from the Secretary. Under Section 20 of the Act, the Minister may publicly notify failure to comply with a recall notice, including the identity of the entity, product details, and recommended consumer actions. Under Section 11 of the Rules, the Minister may also publish details of the recall notice and recommend actions such as destroying the product or taking extra precautions when using the product.

Practical testing criteria for supply chain readiness: Contact each entity in the Australian distribution chain and confirm they have received a copy of the statement of compliance. Confirm each entity understands their obligation not to supply the product if they become aware of non-compliance. Confirm each entity has a process to escalate compliance concerns to the manufacturer. Confirm distribution agreements include clauses addressing obligations under the Cyber Security Act 2024 and Smart Device Rules 2025.

  • Every supplier in the Australian distribution chain has received and retained a copy of the current statement of compliance for the product, as required by Section 16(3) and 16(4) of the Cyber Security Act 2024
  • Distribution agreements include compliance obligations under the Cyber Security Act 2024 and Smart Device Rules 2025, specifying each party's responsibilities for the statement of compliance, recordkeeping, and enforcement notice response
  • Suppliers understand that they must not supply the product in Australia if they are aware, or could reasonably be expected to be aware, that the product does not comply with the security standard, as required by Section 15(3) of the Act
  • A process exists to notify all Australian suppliers immediately if a compliance issue is discovered after first supply, including a documented escalation path and contact list
  • Contact details for the manufacturer's compliance team are available to every entity in the Australian supply chain, enabling rapid communication if the Secretary issues a notice
  • Procedures are documented for responding to compliance notices (Section 17), stop notices (Section 18), and recall notices (Section 19) issued by the Secretary, including the minimum 10 day representation period and the internal review rights under Section 22 of the Act
  • The manufacturer has identified its authorised representative and any other authorised representatives in Australia, and their contact details are included in the statement of compliance as required by Section 9(3)(b) of the Smart Device Rules
  • Each supplier in the Australian distribution chain is retaining their copy of the statement of compliance for the full five year period specified in Section 10 of the Smart Device Rules
Primary sources

References and citations

legislation.gov.au
Referenced sections
  • Primary source for all three mandatory security standards (Schedule 1), statement of compliance requirements (Section 9), retention period (Section 10), product scope and exclusions (Section 8), and all checklist items on this page. Part 2 and Schedule 1 commenced 4 March 2026.
"Part 1 of Schedule 1 prescribes the security standard for the class of relevant connectable products that is all relevant connectable products that are intended by the manufacturer to be used, or are of a kind likely to be used, for personal, domestic or household use or consumption."
legislation.gov.au
Referenced sections
  • Primary source for manufacturer obligations (Section 15), supplier obligations (Section 16), enforcement notices (Sections 17-20), internal review rights (Section 22), independent audit powers (Section 23), and the definition of relevant connectable product (Section 13).
"An entity must not supply a product in Australia that was not manufactured in compliance with the requirements of the security standard for a class of relevant connectable product that will be acquired in Australia in specified circumstances."
legislation.gov.au
Referenced sections
  • Provides policy rationale for product scope, exclusion categories, password requirements, vulnerability disclosure, defined support period website placement requirements, alignment with UK PSTI regulations, and the reduction of the retention period from ten years to five years following stakeholder consultation.
"Products already compliant with the UK PSTI requirements can provide the same statement of compliance for the Australian market, as long as all the requirements set out in this section are met."
Related guides

Explore more topics

Australia Cyber Security Act 2024 Applicability Test | Who Must Comply
Complete Australia Cyber Security Act 2024 applicability test covering smart device security standards, ransomware payment reporting obligations.
Australia Cyber Security Act 2024 Compliance Checklist
Comprehensive Australia Cyber Security Act 2024 compliance checklist covering smart device security standards, ransomware payment reporting.
Australia Cyber Security Act 2024 Compliance Guide | Implementation Playbook
A detailed Australia Cyber Security Act 2024 compliance guide covering smart device security standards, statement of compliance requirements.
Australia Cyber Security Act 2024 Compliance Templates | Statement of Compliance, Ransomware Report, Evidence Pack, Vulnerability Disclosure, Support Period
Comprehensive Australia Cyber Security Act 2024 compliance templates with every required field.
Australia Cyber Security Act 2024 Deadlines and Compliance Calendar | Commencement Dates
Complete Australia Cyber Security Act 2024 deadlines and compliance calendar with all commencement dates: 30 November 2024 Royal Assent.
Australia Cyber Security Act 2024 FAQ | Frequently Asked Questions
Get detailed answers to frequently asked questions about the Australia Cyber Security Act 2024.
Australia Cyber Security Act 2024 Requirements | Smart Device and Ransomware Reporting Obligations
Complete guide to Australia Cyber Security Act 2024 requirements covering smart device password rules, vulnerability disclosure.
Australia Cyber Security Act 2024 Timeline and Commencement Dates | Full Schedule
Complete Australia Cyber Security Act 2024 timeline with every commencement date from Royal Assent on 29 November 2024.
Australia Cyber Security Act 2024 vs EU Cyber Resilience Act | Full CRA Comparison
Detailed comparison of the Australia Cyber Security Act 2024 and the EU Cyber Resilience Act covering scope, product categories, security requirements.
Australia Cyber Security Act 2024 vs UK PSTI Act | Product Security Comparison
Detailed product security comparison of the Australia Cyber Security Act 2024 and the UK PSTI Act covering scope, ETSI EN 303 645, password requirements.
Penalties and fines | Australia Cyber Security Act 2024 | 60 Penalty Units, Smart Device Enforcement, Ransomware Reporting
Australia Cyber Security Act 2024 penalties explained: 60 penalty units (AUD 19,800) per contravention for individuals.
Ransomware Payment Reporting in 72 Hours | Australia Cyber Security Act 2024
Complete guide to the 72 hour ransomware payment reporting obligation under Part 3 of the Australia Cyber Security Act 2024.
Scope and Definitions | Australia Cyber Security Act 2024
Complete guide to the Australia Cyber Security Act 2024 scope and definitions.
Smart device security standards | Australia Cyber Security Act 2024
Complete technical guide to the three Australia Cyber Security Act 2024 smart device security standards: password security under Clause 2.
Statement of Compliance and Recordkeeping | Australia Cyber Security Act 2024 | Section 9, Section 10, 5 Year Retention
Australia Cyber Security Act 2024 statement of compliance explained: all mandatory fields under Section 9(3) of the Smart Device Rules 2025.