IoT cybersecurity depends on more than protecting a network perimeter. Connected devices, their software, mobile applications and cloud services can all affect the security of an IoT solution. For industrial automation teams evaluating connected products, the Australian Governmentâs voluntary Code of Practice: Securing the Internet of Things for Consumers offers a useful set of principles to consider across a deviceâs lifecycle. The code focuses on consumer IoT, so it is not an industrial security standard. However, its emphasis on secure design, maintenance and clear responsibilities raises questions relevant to manufacturers, system integrators and operators working with connected technology.
What the IoT cybersecurity code covers
The code sets out 13 principles for improving the security of internet-connected devices and associated services. It is voluntary, and an organization may follow all or some of its principles. If it claims partial compliance, the code says it should identify which principles it follows.
The principles address both technical controls and the processes around them. They cover passwords, vulnerability reporting, software updates, credential storage, personal data, exposed functionality, communications, software integrity, outages, telemetry, data deletion, installation and input validation. The code assigns responsibility across device manufacturers, IoT service providers, mobile application developers and retailers, reflecting the fact that security can depend on multiple parties.
Start with the three priorities
The Australian Government recommends prioritizing three principles for the greatest short-term security benefits: avoiding duplicated or weak default passwords, implementing a vulnerability disclosure policy, and keeping software securely updated. These priorities provide a practical starting point for product teams and for organizations assessing connected devices.
Use unique credentials and protect access
Devices and associated cloud accounts should not rely on a common factory password that can be reused across multiple units. The code calls for passwords that are unique, unpredictable, complex and difficult to guess. It also addresses web services, recommending multifactor authentication and password-reset processes that appropriately verify the user.
Credential protection continues beyond login. The code says credentials should be stored securely and should not be hard-coded into device software or hardware, where they may be discovered through reverse engineering. For an engineering or operations team, these requirements are useful prompts when reviewing how devices are commissioned, administered and supported.
Make vulnerability reporting actionable
A vulnerability disclosure policy gives security researchers and others a public point of contact for reporting issues. The code expects reported vulnerabilities to be addressed in a timely manner. It also notes that a bug bounty program can encourage and reward reporting, supporting coordinated disclosure and remediation.
For organizations that develop or supply connected products, a published reporting route is only one part of the process. The principle also highlights the need to act on disclosures. When assessing a vendor, teams can ask how vulnerabilities are reported, triaged and communicated, without assuming that a policy alone guarantees a particular response time or outcome.
Plan secure updates and end of life
Updates should be securely delivered, verified as coming from a trusted source and made available in a timely way. The code recommends that updates be easy to apply and automatic by default, while also protecting user-configured preferences and making the need for an update clear. It specifically includes firmware, third-party and open-source software, and associated web services.
Update planning should include the productâs end of life. The code calls for consumers to be told the minimum period during which updates will be provided, the reasons for that timeframe, and how they will be warned when support ends. For constrained devices that cannot be physically updated, it recommends that the product be isolatable and replaceable. These provisions make update support and lifecycle expectations important topics when specifying connected equipment.
Apply the wider principles across the device lifecycle
The remaining principles broaden the discussion from account security and patching to the way devices are designed, deployed and operated:
- Limit exposure: Follow least privilege, disable unused functions, close unnecessary ports and restrict management interfaces to the local network unless remote access is required. The code also recommends secure development processes and penetration testing.
- Protect data and communications: Collect personal data only when needed, use privacy-protective defaults, and apply appropriate encryption to data at rest and in transit. Remote management and control communications should also be protected, with remote access logged.
- Verify software integrity: Secure boot mechanisms should verify device software. If an unauthorized change is detected, the device should alert the consumer or administrator and limit network connectivity to what is needed to provide that alert.
- Design for outages: Where appropriate, devices should remain locally functional during network loss without compromising security or safety, recover cleanly after power is restored and reconnect in an orderly way. Users should be told which features depend on an associated service.
- Support operation and retirement: Monitor collected telemetry for security anomalies, provide clear setup and maintenance guidance, validate input from interfaces and APIs, and make it straightforward to remove personal data when a device changes ownership or is disposed of.
Turn principles into procurement and engineering questions
The code is aimed at consumer-grade IoT, but its principles can help structure conversations about connected products in industrial environments. They are not a substitute for requirements specific to an industrial system, nor do they establish that a product is secure simply because a supplier references them. Instead, teams can use them to make requirements and responsibilities more explicit.
During procurement or design reviews, ask who provides updates and for how long, how credentials are provisioned and stored, where vulnerabilities can be reported, and how remote access is protected and logged. Consider what continues to function if cloud or network services are unavailable, how devices are isolated or replaced if they can no longer be updated, and how data is removed at end of life. These questions connect product security claims to operational arrangements.
Conclusion
The Australian code presents IoT cybersecurity as a lifecycle responsibility shared among the organizations that build, provide and sell connected products. Its three stated short-term prioritiesâunique passwords, vulnerability disclosure and secure updatesâoffer a clear starting point. The broader principles add practical considerations for access, communications, resilience, data handling and retirement. For industrial automation decision-makers, using this framework as a basis for supplier discussions and design reviews can help clarify security expectations while keeping the needs of the specific application in view.
Access Official Technical PDF