Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
The OWASP IoT Top 10 ranks the most frequently encountered weaknesses in connected devices, from hardcoded passwords and insecure network services to missing update mechanisms and poor physical hardening.

What Is the OWASP IoT Top 10?
The OWASP IoT Top 10 is a community-produced list of the weaknesses that appear most often in connected devices. It exists for the same reason as the better-known web application list: to give developers, buyers, and testers a shared vocabulary and a defensible place to start. The current edition dates from 2018 and remains the reference most assessment reports cite, alongside the deeper OWASP IoT Security Testing Guide and the Firmware Security Testing Methodology.
| Rank | Weakness | What It Means |
|---|---|---|
| I1 | Weak, guessable, or hardcoded passwords | Credentials that are public, shared across a product line, or compiled into firmware and unchangeable. |
| I2 | Insecure network services | Unnecessary listening ports, debug daemons, Telnet, and services exposed to the internet by default. |
| I3 | Insecure ecosystem interfaces | Weak authentication or authorisation in the web, API, cloud, or mobile components around the device. |
| I4 | Lack of secure update mechanism | No signature validation, no anti-rollback, no delivery integrity, or no update capability at all. |
| I5 | Use of insecure or outdated components | Vulnerable third-party libraries, unsupported kernels, and software supply chain risk. |
| I6 | Insufficient privacy protection | Personal data stored or transmitted without the handling the law and the user expect. |
| I7 | Insecure data transfer and storage | Missing encryption or access control for data at rest, in transit, and during processing. |
| I8 | Lack of device management | No inventory, monitoring, update control, or decommissioning across deployed devices. |
| I9 | Insecure default settings | Shipping with permissive configuration and no way for the operator to tighten it. |
| I10 | Lack of physical hardening | Exposed debug ports, readable memory, and no tamper resistance. |
Three observations are worth more than the ranking itself.
First, I1 is at the top because it is the cheapest to exploit and the most consequential. Mirai needed nothing more — see default passwords.
Second, I3 is where most real findings land in professional assessments. The hardware may be competent while the cloud API accepts any authenticated session and trusts a device identifier supplied by the caller, so changing a serial number in a request reaches another customer’s equipment. Testing only the device misses this entirely.
Third, I10 is unique to this list. Web applications do not sit in an attacker’s hands; a thermostat does. Exposed JTAG and UART pads and readable flash turn a single purchase into fleet-wide key recovery.
As a scoping tool, the list maps cleanly onto the five surfaces a credible IoT test has to cover: the hardware, the firmware, the radio and network interfaces, the mobile or web application, and the cloud back end. Running through all ten entries forces the conversation about which of those are in scope and why. OWASP’s Firmware Security Testing Methodology then gives a repeatable nine-stage process for the firmware part, which keeps reporting consistent between testers.
As a procurement tool it is blunter but effective. Asking a supplier to state how their product addresses each of the ten, with evidence, separates vendors who have considered the question from those who have not.
The Top 10 describes what goes wrong; it does not tell a manufacturer what to build. For that, ETSI EN 303 645 gives 13 outcome-based provisions and, through the UK’s Product Security and Telecommunications Infrastructure Act 2022, three of them carry legal force for consumer products sold in Britain. NIST IR 8259 sets out the capabilities a manufacturer should provide, and IEC 62443-4-2 covers component requirements in industrial contexts. The pragmatic combination is EN 303 645 as the design baseline and the OWASP list as the testing checklist.
Treat it as a floor rather than a ceiling. A device can avoid all ten named weaknesses and still fail against a determined attacker with physical access, which is why assessment against the list should be paired with real testing rather than a questionnaire.
At Privia Security, our IoT Penetration Test Services map findings to these categories so that results can be compared across product lines and across years.
The list dates from 2018 and OWASP has not published a replacement, which leads some people to dismiss it. The weaknesses themselves have not changed much, and assessment reports still use its categories as a common language. Pair it with the OWASP IoT Security Testing Guide and the Firmware Security Testing Methodology, which are maintained more actively and go considerably deeper.
The web list covers vulnerability classes in application code, such as injection and broken access control. The IoT list spans a whole product ecosystem: hardware, firmware, network services, cloud interfaces, privacy, and physical hardening. Several entries, including missing update mechanisms and lack of physical hardening, have no equivalent in web application testing.
Not directly. It is an awareness and testing aid with no conformity scheme, no test specification, and no certification route. For compliance in the UK, use ETSI EN 303 645 with its companion test specification TS 103 701, which is what the PSTI regime draws on. The OWASP list is the checklist your testers work through, not the certificate your customer asks for.
Weak, guessable, or hardcoded passwords, by a wide margin, because exploitation requires no skill and scales automatically across the internet. Insecure ecosystem interfaces cause the most serious single incidents, since one authorisation flaw in a cloud API can expose every customer at once rather than one device at a time.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.