Meet the IoT Code of Practice principles with less manual effort
The IoT Code of Practice is the Australian Government's voluntary Code of Practice: Securing the Internet of Things for Consumers, which sets 13 security principles for internet-connected consumer devices and their associated services.
- Issued by
- Department of Home Affairs, with the Australian Signals Directorate's Australian Cyber Security Centre
- Published
- 2020
- Status
- Voluntary; entities may comply with all or some principles and should state which
- Structure
- 13 principles, with principles 1 to 3 recommended as priorities
Is the IoT Code of Practice right for your organisation?
It was published in 2020 by the Department of Home Affairs in partnership with the Australian Signals Directorate's Australian Cyber Security Centre, and aligns with the UK's earlier code. The government recommends industry prioritises the first three principles: no default passwords, vulnerability disclosure and secure software updates.
The code is aimed at device manufacturers, IoT service providers, mobile application developers and retailers of consumer smart devices offered in Australia. It is voluntary, but its first three principles now underpin the mandatory Cyber Security (Security Standards for Smart Devices) Rules 2025, which apply to most consumer smart devices manufactured on or after 4 March 2026. Organisations that build or run connected products use it as a security baseline and to show customers and retailers they take device security seriously.
Adopting it is voluntary, though customers and auditors often expect it.
How OneClickComply helps with the IoT Code of Practice
OneClickComply maps the 13 principles to one set of controls, so the evidence you collect for ISO 27001, SOC 2 or other frameworks also counts towards the code. Automated evidence collection and continuous monitoring cover the cloud, identity and development tools behind your IoT services, while AutoComplete policies document your vulnerability disclosure, update and data protection commitments. Our in-house auditors and penetration testing support help you check device and backend security against the principles.
Requirements covered
13 principles, each naming the parties it primarily applies to, with principles 1 to 3 (passwords, vulnerability disclosure and software updates) flagged as the top priorities.
Manual IoT Code of Practice compliance vs OneClickComply
Doing it manually
- Interpreting 13 broad principles and working out which ones apply to your devices, cloud services and apps
- Writing vulnerability disclosure, update support period and data deletion policies from scratch
- Chasing screenshots to prove MFA, encryption and credential storage on backend services
- Losing track of security settings that drift between releases and infrastructure changes
- Repeating the same evidence work for ISO 27001, SOC 2 and customer security questionnaires
With OneClickComply
- Each principle is mapped to clear controls, so you can see what applies and what is missing
- AutoComplete generates audit-ready policies based on your real environment
- Evidence is collected automatically through API integrations and the Companion AI browser agent
- Continuous monitoring alerts you when backend controls drift out of line
- Evidence collected once counts towards every framework it applies to, including questionnaires
Everything you need for the IoT Code of Practice
Map all 13 IoT Code of Practice principles to controls you already run for other frameworks
Generate vulnerability disclosure, software update and end-of-life policies with AutoComplete
Collect evidence automatically from the cloud and identity tools behind your IoT services
Monitor MFA, credential storage and encryption settings continuously, with alerts on drift
Fix supported cloud and identity misconfigurations with OneClickFix, logged as evidence
Use penetration testing and Ask an Auditor to check backend and app security against the principles
Three steps to IoT Code of Practice compliance
Connect and scan
Connect your cloud, identity and SaaS tools. OneClickComply checks them against the IoT Code of Practice and shows which controls pass and which fail.
Fix and generate
OneClickFix fixes supported misconfigurations automatically, and AutoComplete drafts IoT Code of Practice policies from your real environment.
Monitor and evidence
Continuous monitoring flags drift as it happens, and our in-house audit team is on hand when you need expert guidance.
See how far your current setup is from the IoT Code of Practice.
Code of Practice: Securing the Internet of Things for Consumers requirements
All 13 principles of the Code of Practice: Securing the Internet of Things for Consumers, using their official titles.
| Reference | Requirement |
|---|---|
| Principle 1 | No duplicated default or weak passwords |
| Principle 2 | Implement a vulnerability disclosure policy |
| Principle 3 | Keep software securely updated |
| Principle 4 | Securely store credentials |
| Principle 5 | Ensure that personal data is protected |
| Principle 6 | Minimise exposed attack surfaces |
| Principle 7 | Ensure communication security |
| Principle 8 | Ensure software integrity |
| Principle 9 | Make systems resilient to outages |
| Principle 10 | Monitor system telemetry data |
| Principle 11 | Make it easy for consumers to delete personal data |
| Principle 12 | Make installation and maintenance of devices easy |
| Principle 13 | Validate input data |
Always check the official text of the IoT Code of Practice for the exact wording.
IoT Code of Practice questions, answered
Can't find what you need? Our in-house auditors can talk you through the IoT Code of Practice on a 30-minute call.
What is the Australian IoT Code of Practice?
The IoT Code of Practice, formally the Code of Practice: Securing the Internet of Things for Consumers, is voluntary Australian Government guidance published in 2020. Developed by the Department of Home Affairs with the Australian Cyber Security Centre, it sets 13 security principles that the government recommends as the minimum standard for consumer IoT devices, covering passwords, vulnerability disclosure, updates, data protection, communication security and resilience.
Is the IoT Code of Practice mandatory in Australia?
No, the code itself is voluntary, and organisations may comply with all or only some principles, stating which ones they meet. However, its three priority principles are now reflected in the mandatory Cyber Security (Security Standards for Smart Devices) Rules 2025, made under the Cyber Security Act 2024. Those Rules apply to most consumer smart devices manufactured on or after 4 March 2026.
Who does the IoT Code of Practice apply to?
The code is designed for an industry audience: device manufacturers, IoT service providers, mobile application developers and retailers of internet-connected consumer devices in Australia. Each principle states which of these parties it primarily applies to. For example, no default passwords mainly applies to manufacturers, while personal data protection applies to manufacturers, service providers, app developers and retailers.
What are the 13 principles of the IoT Code of Practice?
The 13 principles are: no duplicated default or weak passwords; implement a vulnerability disclosure policy; keep software securely updated; securely store credentials; ensure personal data is protected; minimise exposed attack surfaces; ensure communication security; ensure software integrity; make systems resilient to outages; monitor system telemetry data; make it easy to delete personal data; make installation and maintenance easy; and validate input data.
Which principles should organisations prioritise?
The Australian Government recommends prioritising the first three principles: no duplicated default or weak passwords, implementing a vulnerability disclosure policy, and keeping software securely updated. It considers action on these areas to bring the largest security benefit in the short term. These three areas also match the obligations in the mandatory smart device security standards that commenced on 4 March 2026.
How does the IoT Code of Practice relate to the UK code and ETSI EN 303 645?
The Australian code aligns with and builds on the UK Government's Code of Practice for Consumer IoT Security, and its 13 principles closely mirror the UK's 13 guidelines. The UK guidance also informed the European standard ETSI EN 303 645. Manufacturers already working to the UK code or ETSI EN 303 645 will find most of the Australian principles familiar.
How does the IoT Code of Practice relate to ISO 27001 and the Privacy Act?
The code focuses on device and service security, while ISO 27001 is a management system standard for information security across an organisation. Many backend controls overlap, such as access control, encryption, secure development and vulnerability management. Principle 5 also requires personal data to be handled in line with the Privacy Act 1988 and the Australian Privacy Principles, so privacy compliance supports the code.
Does OneClickComply support the IoT Code of Practice?
Yes. OneClickComply supports the IoT Code of Practice today, mapping its 13 principles to a shared control set so evidence also counts towards frameworks such as ISO 27001 and SOC 2. The platform automates evidence collection, generates policies and monitors backend controls. As the code is voluntary, there is no certification; OneClickComply helps you show which principles you meet.
Related frameworks
- Japan Act on the Protection of Personal Information (APPI)Law · Japan
- New Zealand Privacy Act 2020Law · New Zealand
- China Personal Information Protection Law (PIPL)Law · China
- India Digital Personal Data Protection Act 2023Law · India
- China Cybersecurity LawLaw · China
- APEC Privacy FrameworkFramework · Asia-Pacific
- South Korea Personal Information Protection Act (PIPA)Law · South Korea
- Philippines Data Privacy Act of 2012Law · Philippines
What powers IoT Code of Practice compliance
Start working towards the IoT Code of Practice
Automate controls, gather evidence continuously and stay audit-ready, all on one platform.