Engineer working on a laptop connected to a device test rig, surrounded by wiring harnesses and test hardware

Firmware vulnerabilities & fixes

OWASP ISVS: the IoT Security Verification Standard, explained

Last updated:

OWASP's IoT Security Verification Standard (ISVS), currently release candidate v1.0.0-RC2, is an Incubator Project framework of numbered security requirements organised into five categories — ecosystem design, user-space application, software platform, communication protocol and hardware — each assessed across three cumulative verification levels (L1 through L3), for teams building or assessing connected devices. Its own README describes it as "a community effort to establish an open standard of security requirements for Internet of Things (IoT) ecosystems," usable "at many stages during the Development Life Cycle including design, development, and testing." Led by project leaders Cédric Bassem and Aaron Guzman, and licensed under CC BY-SA 4.0, ISVS began life as an appendix to OWASP's own Application Security Verification Standard before growing into an independent project. As of November 2026, the project's GitHub repository carries an explicit banner reading: "This is a release candidate under community review and may change before the final release."

Key takeaways

  • ISVS stacks its requirements the way a device is built.
  • Each level adds depth to the one below.
  • Every row starts with "Verify that…", so each one can be tested.
  • A new Incident Response subsection (V1.5), covering credential-compromise handling and device-validation procedures.

What are ISVS's five requirement categories?

ISVS stacks its requirements the way a device is built. The Using the ISVS chapter puts the hardware platform (V5) at the bottom, the software platform (V3) and communication (V4) on top of it, user-space applications (V2) above those, and the ecosystem requirements (V1) as "the glue between the connected device and the surrounding ecosystem."

Parsing the requirement tables in the master-branch source files on 11 November 2026 (last commit 29 June 2026) gives these counts:

Category Requirements Subsections
V1: IoT Ecosystem Requirements 44 Application and Ecosystem Design (6) · Supply Chain (9) · Secure Development (15) · Logging (7) · Incident Response (3) · End-of-Life and Update Support Policy (4)
V2: User Space Application Requirements 29 Identification & Authentication (13) · Authorization (4) · Data Protection (4) · Cryptography (8)
V3: Software Platform Requirements 44 Bootloader (9) · OS Configuration, including Linux (16) · Software Updates (13) · Security Chip Integrations (4) · Kernel Space Application Requirements (2)
V4: Communication Requirements 39 General (8) · Machine-to-Machine (3) · Bluetooth (10) · Wi-Fi (5) · Zigbee (8) · LoRaWAN (5)
V5: Hardware Platform Requirements 13 Design (13)

Source: ISVS master branch, files V1–V5 in the en/ directory, parsed 11 November 2026.

That is 169 requirement rows. Published figures disagree: the release notes give "165 security requirements" as a headline, while their own per-chapter figures (40, 34, 49, 46 and 13) add up to 182. An earlier edition of this page gave 181; that total added the V3 and V4 subsection counts wrongly. Cite a requirement by ID and by the commit or release you read, never by its position in a count.

Which verification level fits your device?

Each level adds depth to the one below. The Using the ISVS chapter defines them by the attacker and the damage a compromise would cause, and gives device examples for each:

Level Protects against ISVS's own example devices Rows that apply (of 169)
L1 Software-only attacks, with no physical access to the device A smart light bulb built from off-the-shelf parts, storing no personal data 79
L2 Attacks that also target the hardware Smart locks, alarm systems, smart cameras, medical devices that send readings to a physician 143
L3 Determined attackers, with reverse engineering and physical tampering in scope Hardware crypto wallets, smart meters, connected vehicles, medical implants 168

Source: ISVS Using_ISVS.md (definitions, examples); level counts parsed from the V1–V5 tables on 11 November 2026.

The jump from L1 to L2 is the big one: 64 more rows, mostly secure boot, debug-port lockdown, logging and hardware key storage. Only one row, 4.3.7 (Bluetooth 4.2 or higher with LE Secure Connections), stops at L2, because 4.3.8 replaces it at L3 with Bluetooth 5.3 or higher and a 128-bit minimum key size. The standard also allows mixed results: a device "might meet Level 3 requirements for cryptography but only Level 1 for communication protocols," and should then report the level per category.

What do ISVS requirements look like in practice?

Every row starts with "Verify that…", so each one can be tested. A few rows that firmware teams meet first:

ID Requirement (shortened) L1 L2 L3
1.1.5 A responsible disclosure policy exists and is easy to find on the company website ✓ ✓ ✓
1.2.1 Each application, including firmware, keeps an SBOM listing third-party components, versions and published vulnerabilities ✓ ✓ ✓
1.2.4 Debug interfaces such as JTAG and SWD are disabled or protected before shipping ✓ ✓
1.6.1 A minimum security-update support period, with its end date, is defined and published ✓ ✓ ✓
3.1.4 The first-stage bootloader is verified by a trusted component whose ROM configuration cannot be altered ✓ ✓
3.4.3 Updates are cryptographically signed and verified before execution ✓ ✓ ✓
3.4.6 The device cannot be downgraded to known vulnerable versions (anti-rollback) ✓
5.1.5 The platform's security configuration can be locked, for example with OTP fuses ✓ ✓

Source: ISVS V1, V3 and V5 requirement tables, master branch, read 11 November 2026.

Note that 1.2.1 applies at every level: even an L1 light bulb is expected to have a firmware SBOM. Our firmware SBOM guide covers how to produce one from a binary image, and the secure boot guide covers the 3.1.x chain.

What did RC2 add, including post-quantum cryptography?

The project's release notes describe these additions over the earlier candidate:

  • A new Incident Response subsection (V1.5), covering credential-compromise handling and device-validation procedures.
  • Added anti-brute-force and periodic-reauthentication requirements inside V2.1 (Identification & Authentication).
  • Stronger wireless requirements: Bluetooth raised to "5.3+ at L3 with mandatory 128-bit encryption and encrypted advertising," and WPA3 required for Level-3 Wi-Fi.
  • Seven new Level-3 post-quantum cryptography (PQC) requirements (2.4.7–2.4.8, 3.1.9, 3.4.13, 4.1.7–4.1.8 and 5.1.13), targeting ML-KEM, ML-DSA and SLH-DSA as standardised in NIST's FIPS 203 and its sibling standards, and aimed, per the release notes, at "devices designed in 2025 with 2027+ deployment timelines." See our FIPS 203, 204 and 205 guide.
  • Documentation on non-conformities and risk-based decisions, plus corrected numbering where two requirement IDs had been skipped.

The same notes defer a V3 platform-requirements refresh, an overview-figure redesign, and new attack-scenario documentation to the 1.1 release.

How does ISVS map to the CRA, RED and ETSI EN 303 645?

ISVS ships an Appendix B compliance mapping to four frameworks: the EU Cyber Resilience Act, the Radio Equipment Directive's Delegated Regulation 2022/30 (with EN 18031-1/-2/-3), NIST SP 800-213A and ETSI EN 303 645 v2.1.1. Some of its reverse-lookup rows:

Framework clause ISVS rows the appendix maps to it
CRA Annex I Part II: SBOM 1.2.1
CRA Annex I Part II: coordinated vulnerability disclosure 1.1.5, 1.1.6
CRA Annex I Part I 2(c): security updates 1.2.9, 3.4.1–3.4.2, 3.4.3 (partial), 3.4.4–3.4.7, 3.4.10 (partial), 3.4.12
RED 3.3(d) / EN 18031-1: secure boot and bootloader integrity 1.2.6 (partial), 1.2.7, 3.1.1–3.1.5, 3.4.3 (partial), 3.4.8, 5.1.2

The appendix states plainly that it "is informative only," that meeting ISVS "does not constitute legal compliance," and that it covers the v1.0 requirement set without the newer V1.5 and PQC rows. Treat it as a cross-reference for your technical file, then read the clause itself: our CRA Annex I, EN 18031 and ETSI EN 303 645 guides cover each.

How does ISVS fit with ISTG and FSTM?

OWASP maintains three complementary IoT and firmware projects rather than one all-in-one standard. Our OWASP Firmware Security Testing Methodology guide quotes FSTM's own framing directly: "the OWASP IoT Security Verification Standard (ISVS) defines WHAT security controls must be implemented, while FSTM defines HOW to test firmware components," while the separate IoT Security Testing Guide (ISTG) "provides additional test cases for hardware interfaces, wireless protocols, network services, and user interfaces." Use ISVS as the control checklist, ISTG for the device's wider attack surface and FSTM for the firmware image itself. See also our OWASP IoT Top 10 guide for the companion risk list.

What happens when a requirement cannot be met?

The standard expects gaps and asks for a recorded decision instead of silence. Its non-conformity section sets four steps:

  1. Assess the riskof leaving the control out: data sensitivity, device function, likelihood of exploitation, business and safety impact.
  2. Document the decision: the requirement ID, the reason, the assessed risk, any compensating control and who approved it.
  3. Add compensating controlswhere the original requirement cannot be met in full.
  4. Review it againwhen the threat landscape, the deployment context or the cost of a fix changes, or a new vulnerability appears.

The same chapter suggests putting ISVS rows into the development backlog as tickets, so gaps stay visible as debt.

Worked example: how would a smart lock be scoped to Level 2?

Synthetic example for illustration; the product and team are invented.

A team ships a Wi-Fi and Bluetooth smart lock running embedded Linux on a SoC with a secure-boot ROM.

  1. Pick the levelISVS lists smart locks as an L2 example, and the lock's keys and access logs are sensitive, so the target is L2. The 143 L2 rows are the starting list.
  2. Remove what does not applyNo Zigbee or LoRaWAN radio, so those 13 V4 rows are marked not applicable, with the reason recorded.
  3. Map rows to evidence1.2.1 gets the firmware SBOM for the release build; 3.1.4–3.1.5 get the secure-boot chain description and a test showing an unsigned image is refused; 1.2.4 and 5.1.5 get the fuse map and a JTAG probe test on a production unit.
  4. Record a non-conformityThe SoC has no hardware key store, so 2.4.4 fails. The team documents the gap, keeps keys in a TrustZone-isolated service as a compensating control, and schedules a SoC change for the next hardware revision.
  5. Report per categoryThe final statement lists L2 for V1, V2 (with the 2.4.4 exception), V3 and V5, and L2 for V4 Wi-Fi and Bluetooth only, with the commit of ISVS used.

What are the common pitfalls?

  • Quoting a single total. 165, 169 and 182 all appear in the project's own files; quote IDs and the version read.
  • Claiming "ISVS certified." ISVS has no certification scheme; it is a requirements catalogue you verify against.
  • Choosing L3 by default. L3 adds anti-tampering rows that cost real hardware money; ISVS itself recommends tailoring to a risk assessment.
  • Treating 1.2.1 as a one-off. The SBOM must list published vulnerabilities, so it needs refreshing for each release.
  • Using Appendix B as a compliance claim. It is informative and excludes the newest rows.

Where should a device team start?

  1. Treat ISVS as pre-finalWith the project's own banner calling it a release candidate, pin the commit or release you cite.
  2. Pick the level from the threat model, using ISVS's own device examples, and report per category if results differ.
  3. Start with V1 and V3Supply chain, secure development, bootloader integrity and updates underpin the V2 and V4 rows.
  4. Flag the PQC rows early for long-lifecycle devicesIf the product will be in service past 2030, scope ML-KEM and ML-DSA into the crypto design now.
  5. Use ISVS, ISTG and FSTM together: what to verify, how to test the device, and how to test the firmware.

For the V1.2 supply-chain rows, SoftWSP's firmware security service extracts an SBOM from the firmware image as CycloneDX 1.6 JSON and matches its components against NVD, CISA KEV, FIRST EPSS and CISA's CSAF ICS advisories. An AI-drafted report cites the record behind each finding, and an engineer reviews it. It does not test bootloader, hardware or radio requirements, and it does not award an ISVS level.

This guide summarises the public OWASP ISVS project files on GitHub (README, release notes, Using the ISVS, V1–V5 and Appendix B, read 11 November 2026) and the related FSTM and IoT Top 10 publications. ISVS is a release candidate as of November 2026; this summary is not a substitute for the project's own current text and is not compliance or legal advice.

Put this guide to work

Frequently asked questions

What is OWASP ISVS?

The IoT Security Verification Standard (ISVS) is an OWASP Incubator Project, described in its own README as "a community effort to establish an open standard of security requirements for Internet of Things (IoT) ecosystems," usable "at many stages during the Development Life Cycle including design, development, and testing." It is led by project leaders **Cédric Bassem** and **Aaron Guzman**, licensed under **Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)**, and originated as an appendix inside OWASP's own [Application Security Verification Standard](/guides/owasp-asvs/) before splitting into its own project. As of November 2026, the project's GitHub repository flags its latest published text as **release candidate `1.0.0-RC2`**, with an explicit banner stating "This is a release candidate under community review and may change before the final release" — treat ISVS as pre-final and re-check the project's own release page before citing a specific requirement ID as stable.

What are ISVS's five requirement categories, and how many requirements does each have?

Reading the current master-branch source files directly, this guide counted: **V1 IoT Ecosystem Requirements** — 44 requirements across six subsections (Application and Ecosystem Design, Supply Chain, Secure Development, Logging, Incident Response, End-of-Life and Update Support Policy); **V2 User Space Application Requirements** — 29, across Identification & Authentication, Authorization, Data Protection and Cryptography; **V3 Software Platform Requirements** — 44, across Bootloader, OS Configuration including Linux, Software Updates, Security Chip Integrations and Kernel Space Application Requirements; **V4 Communication Requirements** — 39, across General, Machine-to-Machine, Bluetooth, Wi-Fi, Zigbee and LoRaWAN; and **V5 Hardware Platform Requirements** — 13, all under a single Design subsection. That totals 169 requirement rows in the version of the source this guide read (an earlier edition of this answer said 181 after adding the V2, V3 and V4 subsection counts wrongly). The project's own files disagree with each other: the release notes give "165 security requirements" as a headline, while their per-chapter figures add up to 182, because ISVS is a continuously edited community document. Cite a requirement by its ID and the release or commit you read, rather than by a total.

What are ISVS's three verification levels?

Following the same L1/L2/L3 pattern as OWASP's other verification standards, ISVS organises requirements by assurance level: **Level 1** targets baseline, software-only-attack resistance; **Level 2** adds requirements relevant once hardware-involved attacks and more sensitive data are in scope; and **Level 3** is aimed at critical systems, adding defense-in-depth and anti-tampering requirements — each higher level builds on, rather than replaces, the one below. The project's RC2-era release notes describe several Level-3-only additions along this pattern, including upgrading Bluetooth to "5.3+ at L3 with mandatory 128-bit encryption and encrypted advertising" and mandating WPA3 for Level-3 Wi-Fi.

What's new in the RC2 update, and how does ISVS relate to OWASP's ISTG and FSTM?

The project's own release notes for this update describe a new **Incident Response** subsection (V1.5) covering credential compromise and device validation, added anti-brute-force and periodic-reauthentication requirements in V2.1, and — notably — **seven new Level-3 post-quantum cryptography requirements** targeting algorithms including ML-KEM, ML-DSA and SLH-DSA, aimed at "devices designed in 2025 with 2027+ deployment timelines" and aligned to NIST's post-quantum standards. On scope: our [OWASP Firmware Security Testing Methodology guide](/guides/owasp-firmware-security-testing-methodology/) quotes FSTM's own framing of the three projects together — "the OWASP IoT Security Verification Standard (ISVS) defines WHAT security controls must be implemented, while FSTM defines HOW to test firmware components" — with the separate IoT Security Testing Guide (ISTG) covering "hardware interfaces, wireless protocols, network services, and user interfaces." OWASP's recommendation is to use ISVS as the requirements checklist, ISTG for the device's broader test surface, and FSTM for the firmware image itself.

Sources

  1. OWASP: IoT Security Verification Standard — official project page
  2. GitHub: OWASP/IoT-Security-Verification-Standard-ISVS — project README (version banner, licence, mission statement)
  3. GitHub: OWASP/IoT-Security-Verification-Standard-ISVS — the release notes (RC2 changes: incident response, PQC requirements, wireless updates)
  4. GitHub: OWASP/IoT-Security-Verification-Standard-ISVS — releases page (1.0RC pre-release tag)
  5. GitHub: OWASP/IoT-Security-Verification-Standard-ISVS — V1 through V5 requirement source files (en/ directory, master branch)
  6. Creative Commons: Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) licence text
  7. GitHub: OWASP/IoT-Security-Verification-Standard-ISVS — Using the ISVS (security model, verification levels, non-conformities)
  8. GitHub: OWASP/IoT-Security-Verification-Standard-ISVS — V1 IoT Ecosystem Requirements
  9. GitHub: OWASP/IoT-Security-Verification-Standard-ISVS — V3 Software Platform Requirements
  10. GitHub: OWASP/IoT-Security-Verification-Standard-ISVS — V5 Hardware Platform Requirements
  11. GitHub: OWASP/IoT-Security-Verification-Standard-ISVS — Appendix B: Compliance Mapping (CRA, RED, NIST SP 800-213A, ETSI EN 303 645)
  12. NIST: FIPS 203, Module-Lattice-Based Key-Encapsulation Mechanism Standard (ML-KEM)
Was this guide helpful?

In this cluster