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

Firmware vulnerabilities & fixes

MITRE EMB3D: the embedded device threat model, explained

Last updated:

MITRE EMB3D, now at version 2.0.2 (released 1 June 2026) after its first full public release in 2024, is a free, public threat model purpose-built for embedded devices — the microcontroller- and SoC-based hardware running firmware inside routers, PLCs, medical devices, vehicles, and the other categories SoftWSP guides already cover. Instead of listing generic attack techniques, EMB3D starts from what a specific device actually has (its properties) and derives from that which threats realistically apply and which technical mitigations close them — a structure MITRE built specifically because general-purpose frameworks like ATT&CK weren't designed around embedded hardware's constraints.

Key takeaways

  • Every entry has a stable ID, and the first digit of a property or threat ID tells you its category.
  • It tells you how much real-world evidence exists that attackers can do it.
  • EMB3D is explicitly designed to interoperate with, not replace, MITRE's other frameworks.
  • Worked example — synthetic device, real EMB3D v2.0.1 mappings.

Who built EMB3D, and why?

MITRE announced a pre-release review version of EMB3D on 13 December 2023 jointly with Red Balloon Security and Narf Industries, naming Niyo "Little Thunder" Pearson (then of ONE Gas) as a contributing collaborator, and invited device vendors, asset owners, academics and researchers to review the draft ahead of a full public launch. MITRE's own About page for the project adds that a set of pilot organizations spanning energy, water, manufacturing, robotics, aerospace, health and automotive sectors, plus independent researchers and threat-tool vendors, contributed to shaping the content. MITRE's news release frames the motivation as the rising number of CISA ICS advisories affecting embedded devices across critical infrastructure, and the lack, until EMB3D, of a common framework connecting device characteristics directly to attacker-relevant threats and vendor-actionable mitigations.

How is EMB3D structured?

Per MITRE's EMB3D white paper, the model is organized into three linked knowledge bases:

Part What it contains Organized by
Device Properties A device's hardware and software features and capabilities — what it has, not what's wrong with it Four top-level categories: Hardware, System Software, Application Software, Networking, each broken into sub-properties
Threats Attacker goals/impacts achievable against a device that has a given property, including the attacker actions required and the CWEs/CVEs that enable the threat Threat IDs (TIDs) mapped back to the specific properties that expose a device to them
Mitigations Technical mechanisms/technologies a vendor can build into the device to defend against a threat, plus known limitations of each Maturity tiers — Foundational (the largest group, 48 entries in the site's mitigation index), Intermediate (31), and Leading (10, the newest and least-established techniques)

The site's own "Getting Started" guidance describes the intended workflow end to end: identify which Device Properties apply to the device under review (from documentation or device knowledge), select them in the Properties Mapper tool to generate the resulting Threat list, then check which Mitigations are already implemented to see what residual threat exposure remains — turning EMB3D into a working threat-modeling and gap-analysis tool rather than just a reference document.

The white paper adds a rule for using the tiers: product teams "should initially prioritize the adoption of Foundational mitigations" before moving up, and a higher-tier mitigation either complements the Foundational one (deploy both) or replaces it, depending on the threat.

How do PID, TID and MID identifiers fit together?

Every entry has a stable ID, and the first digit of a property or threat ID tells you its category. Counts below are from the EMB3D STIX 2.1 data file for v2.0.1 (v2.0.2 changed no model content) and match the site's Properties List and threat index.

Category Property IDs Properties Threat IDs Threats
Hardware PID-1x 10 TID-1xx 16
System Software PID-2x 25 TID-2xx 26
Application Software PID-3x 18 TID-3xx 30
Networking PID-4x 6 TID-4xx 9
Total 59 81

Sub-properties extend the parent's number: PID-27 "Device includes support for firmware/software updates" has children such as PID-272 (cryptographic integrity protection) and PID-2722 "Device includes digitally signed firmware (with private key)." Mitigations (MID-001 to MID-089, 89 in total) carry no category digit; their tier is a separate field. Gaps in the numbering (there is no TID-104, for example) are normal.

In the STIX file, threats are vulnerability objects, mitigations are course-of-action objects, and properties are custom x-mitre-emb3d-property objects. They are linked by relates-to (property → threat, 90 links), mitigates (mitigation → threat, 213 links) and subproperty-of (40 links).

What does a threat's maturity level tell you?

It tells you how much real-world evidence exists that attackers can do it. The white paper defines four levels, and each threat page shows its level with the evidence behind it:

Maturity level Evidence EMB3D expects Threats at this level (v2.0.1)
Observed Adversarial Technique An ATT&CK technique or documented report 32 (plus 2 labelled "Observed Adversarial Behavior": TID-210, TID-216)
Known Exploitable Weakness Documented exploitation of a weakness, such as a CWE tied to a KEV catalog entry 22
Proof of Concept A research paper or report 25
Theoretic — 0

TID-119 "Latent Hardware Debug Port Allows Memory/Code Manipulation" is a Proof of Concept threat, citing a published JTAG memory read/write demonstration and CWE-1191. TID-213 "Faulty FW/SW Update Integrity Verification" is a Known Exploitable Weakness that cites, among others, CVE-2023-33768, incorrect firmware signature verification in a smart plug's update process. Maturity is evidence, not likelihood for your product: a Proof of Concept threat against an exposed debug header can still be your top risk.

How does EMB3D relate to ATT&CK, CWE and CVE?

EMB3D is explicitly designed to interoperate with, not replace, MITRE's other frameworks. Per MITRE's own description, EMB3D "expands on existing models including MITRE's ATT&CK framework and Common Weakness Enumeration" — a given EMB3D Threat entry cites the CWEs and CVEs that make the threat concrete (since v2.0, every threat maps to at least one CWE), and separately can be cross-referenced against the adversary tactics and techniques in ATT&CK Enterprise or ATT&CK for ICS that describe how an attacker would actually carry the threat out in the field. For defensive mapping once mitigations are in place, MITRE's D3FEND knowledge graph covers the broader defensive-technique taxonomy that EMB3D's device-specific mitigations sit alongside.

What does an EMB3D threat model look like for a real device class?

Worked example — synthetic device, real EMB3D v2.0.1 mappings. Take a Linux-based industrial edge gateway: a UART/JTAG header on the board, a bootloader, digitally signed firmware with remote updates, a web configuration UI with password login, C application code, and a Modbus TCP southbound link to controllers. Selecting those eight properties gives 18 threats:

Property selected Threats EMB3D links to it Foundational mitigations (MID)
PID-15 hardware access port (UART, JTAG) TID-115, TID-116, TID-119 MID-057 Disable physical development and debugging ports; MID-058 Engage hardware readout protection
PID-21 bootloader TID-201 Inadequate bootloader protection and verification MID-001 Software-only bootloader authentication (MID-002 hardware-backed and MID-029 hardware root of trust are Intermediate)
PID-2722 digitally signed firmware TID-213 Faulty FW/SW update integrity verification MID-001; MID-026 Secure firmware update; MID-027 Validated cryptographic libraries
PID-275 remotely initiated updates TID-217 Remotely initiated updates can cause DoS MID-026; MID-031 Physical presence validation; MID-032 System service availability manager
PID-311 web/HTTP application TID-319 to TID-325 (XSS, SQL injection, session hijacking, CSRF, path traversal, direct object reference, response splitting) MID-071 to MID-076, MID-078, MID-035
PID-3321 passwords TID-314 brute force, TID-315 password retrieval abuse, TID-329 improper password storage MID-046 Attempt timeouts and lockouts; MID-017 Security-relevant logging; MID-049 Secure password storage
PID-3122 manual memory management (C/C++) TID-327 Out-of-bounds memory access MID-004 Memory hardening; MID-013 Process and thread memory segmentation
PID-4111 protocol lacks message authentication TID-406 Unauthorized messages or connections MID-034 Authenticate network messages (MID-081 Secure network tunnels is Intermediate)

The engineering team then marks each MID as present, partial or missing. Suppose the review finds the JTAG header still active and nothing authenticating the Modbus traffic: those two threats have no Foundational mitigation in place and become the first two work items. TID-406 is the realistic one for Modbus — classic Modbus TCP has no authentication of its own (see Modbus protocol security), so MID-034 usually means a gateway-side control or MID-081's tunnel rather than a protocol change.

How do EMB3D mitigations map to IEC 62443-4-2?

Each mitigation page carries an "IEC 62443 4-2 Mappings" section, which the STIX file exposes as x_mitre_emb3d_mitigation_IEC_62443_mappings. For the example above:

Mitigation IEC 62443-4-2 requirement(s) listed by EMB3D
MID-057 Disable physical development and debugging ports EDR / HDR / NDR 2.13 Use of physical diagnostic and test interfaces
MID-001 Software-only bootloader authentication EDR / HDR / NDR 3.14 Integrity of the boot process
MID-026 Secure firmware update EDR / HDR / NDR 3.10 RE(1) Update authenticity and integrity
MID-046 Authentication attempt timeouts and lockouts CR 1.11 Unsuccessful login attempts; CR 2.5 Session lock
MID-034 Authenticate network messages CR 3.1 RE(1) Communication authentication

That makes EMB3D a practical bridge: the threat model explains why a control is needed, and the mapped requirement is how a certification body or customer will check it (see IEC 62443-4-2 component requirements).

How has EMB3D changed since release?

Date Version What changed
13 Dec 2023 Pre-release/review draft Announced jointly by MITRE, Red Balloon Security and Narf Industries for public review before full launch
2024 Full public release (Properties + Threats) Properties and Threats became the first content made fully available
Fall 2024 Mitigations added MITRE's own version-history notes describe this as the point EMB3D reached "content completion"
22 Apr 2025 v2.0 First major update since content completion: added a machine-readable STIX 2.1 representation of the full dataset (to support integration with other threat/vulnerability tooling), plus new properties, two new logging-related threats (TID-225, TID-226), and six new mitigations covering formal-methods approaches and log management
29 Apr 2025 v2.0.1 Patch release correcting a threat naming error (TID-213 reverted to its correct name)
1 Jun 2026 v2.0.2 Usability update (shareable Properties Mapper state via URL) plus updates to the site's Terms of Use and copyright references; no change to threat or mitigation content

Source: EMB3D Version History, read 11 November 2026.

MITRE's own documentation describes known limits of the STIX 2.1 export as of v2.0.x: EMB3D Threats map to STIX vulnerability objects and Mitigations to course-of-action objects, but Properties "do not map well to standard STIX data types" and are expressed as custom objects, and reference/evidence material is still carried as free-form Markdown text rather than structured external-reference objects — MITRE notes that a later release may encode that material as STIX external references.

What are the common pitfalls?

  • Selecting properties from the datasheet only. Debug headers, factory test modes and leftover services rarely appear in marketing specs; check the board and the firmware image.
  • Reading the threat list as a findings list. The Mapper output is candidate threats; Getting Started's step 2 is to judge which ones truly apply.
  • Skipping the negative properties. PID-26 "lacks firmware/software update support" and PID-4111 "lacks protocol support for message authentication" are where the serious threats sit.
  • Citing white-paper MID numbers. Some IDs in the September 2024 paper's examples differ from the live site (the paper's MID-074 is a processor-integration mitigation; on the site MID-074 is CSRF mitigations); quote IDs from the live site.
  • Expecting CVE coverage. EMB3D cites example CVEs as evidence; it does not tell you which CVEs affect your firmware build.

Where should a device team start?

  1. Run the Properties Mapper against one real device first, rather than trying to threat-model your whole product line abstractly — EMB3D's output quality depends on accurately identifying which Device Properties actually apply.
  2. Treat Mitigation tiers as a prioritization signal, not a pass/fail grade— Foundational mitigations (48 of them) are the largest, most-established category; Leading mitigations (10) are newer techniques with less field validation, per MITRE's own tier structure.
  3. Cross-reference generated Threats against your existing CVE/CWE tracking— EMB3D's Threat entries already cite the CWEs/CVEs that enable them, so this is largely a matter of confirming your vulnerability-management pipeline (see KEV/EPSS prioritization) already watches for the same weakness classes.
  4. Use the STIX 2.1 export if you have existing threat-intel tooling, but verify your own pipeline can handle EMB3D's custom Property objects and Markdown-based references before assuming full interoperability.
  5. Check the Version History page before citing a specific Threat or Mitigation ID in a document— EMB3D is an actively maintained, living framework, and IDs/definitions have already changed between v2.0 and v2.0.1.

SoftWSP's firmware assessments supply the component-level evidence an EMB3D review needs next to the property list: an SBOM extracted from the firmware image (CycloneDX 1.6 JSON), matched against NVD, CISA KEV, FIRST EPSS and CISA CSAF ICS advisories, in a cited report for engineer review. Choosing the properties and judging which mitigations are in place stays with the engineering team. See device & firmware security.

This guide summarises MITRE's own published EMB3D web site, STIX data file, white paper and news releases (last checked 11 November 2026); it is not a substitute for reading the current emb3d.mitre.org content directly, and does not constitute security or compliance advice.

Put this guide to work

Frequently asked questions

What is MITRE EMB3D?

EMB3D is a free, publicly available threat model for embedded devices — the kind found in critical infrastructure, IoT, automotive, healthcare and manufacturing equipment. MITRE's own About page describes it as "a knowledge base of cyber threats and associated mitigations for embedded devices." It was developed by MITRE together with Red Balloon Security, Narf Industries, and Niyo "Little Thunder" Pearson (then of ONE Gas), with input from pilot organizations across energy, water, manufacturing, robotics, aerospace, health and automotive sectors.

How is EMB3D structured?

Three linked parts, per MITRE's own EMB3D white paper: Device Properties (a device's hardware and software features and capabilities, grouped into categories such as hardware, system software, application software and networking), Threats (attacker goals/impacts achievable against a device with given properties, each threat documenting the targeted properties, the attacker actions required, and the vulnerabilities or weaknesses that enable it), and Mitigations (the technical mechanisms that defend against a given threat, tagged Foundational, Intermediate or Leading by how mature/established the approach is). The site's own "Getting Started" workflow has a user pick applicable Device Properties in the Properties Mapper Tool to generate a relevant Threat list, then check which Mitigations are already in place.

When was EMB3D released, and is it still being updated?

MITRE, Red Balloon Security and Narf Industries announced a pre-release/review version on 13 December 2023, with the full public release of Properties and Threats following in 2024 and Mitigations reaching content completion in fall 2024. Since then it has shipped v2.0 (22 April 2025, adding a machine-readable STIX 2.1 representation plus new properties, threats and mitigations), v2.0.1 (29 April 2025, a naming-correction patch), and v2.0.2 (1 June 2026, usability and Terms of Use/copyright updates). MITRE describes it as a living framework that is updated as new threat actors, vulnerabilities and defenses are documented.

How does EMB3D relate to MITRE ATT&CK, CWE and CVE?

EMB3D is a companion framework, not a replacement. Per MITRE's own materials it "expands on existing models including MITRE's ATT&CK framework and Common Weakness Enumeration," letting a user map an EMB3D Threat to the CWEs and CVEs that enable it and, separately, to the adversary tactics/techniques in [ATT&CK](/guides/mitre-attack-enterprise/) or [ATT&CK for ICS](/guides/mitre-attack-for-ics/) that an attacker would use to exploit it. EMB3D's own focus is device-property-driven threat exposure and technical mitigation guidance, which ATT&CK and CWE do not provide in that form.

Is EMB3D free to use, and under what terms?

Yes — the model, its web site (emb3d.mitre.org) and the Properties Mapper tool are published for public use at no cost. MITRE states the site content is "\u00a92026 The MITRE Corporation" and governed by MITRE's Terms of Use (the same structure used for ATT&CK), and the underlying EMB3D Threat Model white paper is marked "Approved for public release." For anything beyond read-and-reference use (e.g. bulk reuse of the STIX dataset in a commercial product), consult the full Terms of Use text directly before relying on it.

Sources

  1. MITRE EMB3D — official site (home, Device Properties / Threats / Mitigations, Properties Mapper tool)
  2. MITRE EMB3D — About (origin, contributors, mitigation maturity tier counts, Terms of Use reference)
  3. MITRE EMB3D — Version History (v2.0, v2.0.1, v2.0.2 release notes)
  4. MITRE EMB3D — Getting Started (Properties Mapper workflow)
  5. MITRE EMB3D Threat Model white paper (PDF, ©2024 The MITRE Corporation, approved for public release)
  6. MITRE: "MITRE, Red Balloon Security, and Narf Announce EMB3D" (news release, 13 December 2023)
  7. Industrial Cyber: "MITRE's EMB3D 2.0 update improves threat coverage, STIX integration for better security tools compatibility"
  8. MITRE EMB3D — Data (STIX 2.1 representation, object and relationship types, limitations)
  9. MITRE EMB3D STIX 2.1 data file v2.0.1 (properties, threats, mitigations, IEC 62443-4-2 mappings)
  10. MITRE EMB3D — Device Properties List
  11. MITRE EMB3D — Mitigations index (Foundational, Intermediate, Leading)
  12. MITRE EMB3D — TID-213 Faulty FW/SW Update Integrity Verification
Was this guide helpful?

In this cluster

MITRE EMB3D: the embedded device threat model, explained