Industrial IoT security depends on more than protecting a connected device. A sensor, gateway, or controller may rely on network services, cloud platforms, mobile applications, software components, and operational processes. Weakness in any of these areas can create a route to unauthorized access or disrupt the confidentiality, integrity, or availability of information and services. The 2018 OWASP IoT Top 10 offers a concise framework for reviewing these IoT security risks across the device lifecycle.
OWASP designed the list as a shared reference for developers, manufacturers, enterprises, and consumers, rather than separate guidance for different audiences. For industrial automation teams, its value is in prompting a system-level review: security must account for devices, interfaces, data flows, configuration, and support after deployment.
Ten IoT security risks to assess
1. Weak, guessable, or hardcoded passwords
Easy-to-brute-force, publicly available, or unchangeable credentials can provide unauthorized access. The risk also includes backdoors in firmware or client software. In an industrial environment, teams should identify how devices are authenticated and whether credentials can be changed and managed securely.
2. Insecure network services
Unnecessary or poorly secured services on a device can expose information or enable unauthorized remote control, particularly when reachable from the internet. Review which services are enabled, why they are needed, and whether access is appropriately restricted.
3. Insecure ecosystem interfaces
A device’s security can be undermined by interfaces beyond the device itself, including web applications, backend APIs, cloud services, and mobile applications. OWASP highlights missing or weak authentication and authorization, inadequate encryption, and insufficient input and output filtering as common concerns. Assess these interfaces as part of the connected system, not as separate from the device.
4. Lack of a secure update mechanism
Updates are a security control only when they can be delivered and applied securely. Risks include missing firmware validation, unencrypted delivery, no anti-rollback protection, and inadequate notification of security changes resulting from updates. Teams should understand how updates are authenticated, delivered, installed, and communicated.
5. Insecure or outdated components
Deprecated or vulnerable software libraries and components can expose a device to compromise. The concern also includes insecure customization of operating system platforms and third-party hardware or software from a compromised supply chain. Component selection and maintenance therefore belong in the security review, not only initial product development.
6. Insufficient privacy protection
Personal information stored on a device or elsewhere in its ecosystem may be used insecurely, improperly, or without permission. While industrial systems may focus on operational data, teams should also identify personal information in connected services and consider how it is stored and used.
7. Insecure data transfer and storage
Sensitive data may be exposed when encryption or access controls are missing. OWASP’s concern covers data at rest, in transit, and during processing throughout the ecosystem. Mapping where information moves and resides helps teams identify where protections need review.
8. Lack of device management
Security responsibilities continue after deployment. The list identifies gaps in asset management, update management, secure decommissioning, monitoring, and response capabilities. Without a way to track and support devices in production, organizations may struggle to maintain security over time or respond to changes and incidents.
9. Insecure default settings
Devices may ship with settings that are not secure, or may restrict operators from making configurations more secure. Review initial configurations before deployment and establish how configuration changes are controlled and maintained.
10. Lack of physical hardening
Insufficient physical protections can allow an attacker to obtain sensitive information or take local control of a device. Physical access can also support a later remote attack. Consider physical exposure alongside network and software risks when assessing where equipment is installed and how it is protected.
Use the list across the device lifecycle
The ten categories are most useful when treated as connected review areas rather than isolated checklist items. For example, a device with strong credentials may still be exposed through an insecure API, an unnecessary network service, or an outdated component. Likewise, secure initial configuration does not replace ongoing asset, update, and monitoring processes.
Industrial teams can use the framework to structure questions for design reviews, procurement discussions, deployment planning, and operational support. A practical review can ask:
- Are credentials, network services, and interfaces understood and appropriately secured?
- How are software components maintained, and how are updates validated and delivered?
- Where is sensitive data stored, transferred, or processed, and what protections apply?
- How are deployed devices tracked, monitored, updated, and securely decommissioned?
- Do default configurations and physical protections suit the deployment environment?
These questions do not replace system-specific risk assessment. They help teams identify areas that require closer examination across connected products and the services that support them.
A shared framework, developed through review
The OWASP project began in 2014 to help people make better decisions about creating and using IoT systems. For the 2018 update, contributors reviewed the earlier project, collected vulnerability information, examined related IoT security initiatives, and sought community feedback before releasing the list in December 2018. The project’s stated aim was simplicity: one prioritized set of issues relevant to manufacturers, enterprises, and consumers.
The project also described possible future work, including mapping the list to other security projects, adding use and abuse cases, and exploring areas such as embedded security and ICS/SCADA. These plans underline the value of adapting broad IoT guidance to the systems and responsibilities of each organization; they should not be mistaken for additional items in the 2018 list.
Conclusion
For industrial automation organizations, the OWASP IoT Top 10 is a useful starting point for examining security across connected devices and their surrounding ecosystem. Its practical message is to look beyond the device itself: credentials, services, interfaces, components, data handling, configuration, physical access, and ongoing management all matter. Applying these categories throughout design, deployment, and operations can help teams make security gaps visible and assign them for further assessment.
Access Official Technical PDF