All terms

    MITRE D3FEND

    MITRE's knowledge graph of defensive cybersecurity countermeasures, explicitly mapped to the ATT&CK techniques they mitigate.

    Reviewed by Christian Espinosa, Founder, Blue Goat CyberLast reviewed June 20, 2026

    Definition

    D3FEND is a MITRE knowledge graph of defensive cybersecurity techniques organized under Model, Harden, Detect, Isolate, Deceive, Evict and Restore. It models relationships among defensive techniques, digital artifacts and offensive techniques to support defensive analysis. A mapped relationship is not proof that a particular implementation defeats an attack.
    What the regulation says
    D3FEND can provide optional terminology for documenting technical defenses. No verified FDA mandate or general notified-body expectation for D3FEND mapping was established.

    What this means in practice

    For MedTech, D3FEND lets you justify a control library against the threats in your threat model. If your model identifies T1190 (Exploit Public-Facing Application) as a credible threat, D3FEND points you to specific defensive techniques (Application Hardening, Network Traffic Filtering, Process Spawn Analysis) and connects each to measurable design elements that can appear in your security architecture, IEC 81001-5-1 conformance evidence, or premarket cybersecurity submission.

    Examples

    • Illustrative: A MedTech manufacturer uses D3FEND to select and document defensive controls that mitigate specific ATT&CK techniques identified in their medical device threat model.
    • Illustrative: During a premarket cybersecurity submission, an organization demonstrates how its chosen security architecture aligns with D3FEND techniques to counter common MedTech attack patterns.
    • Illustrative: A hospital uses D3FEND to describe segmentation and application-control techniques, then tests their effectiveness against selected attack paths.
    Common pitfalls
    • •Treating D3FEND as a control catalog and ignoring its ontology, the value is in the typed relationships between artifact, technique, and digital effect.
    • •Mapping controls to D3FEND in isolation without first mapping threats to ATT&CK, the bridge breaks both ways.
    • •Expecting 1:1 coverage, many ATT&CK techniques have multiple D3FEND counters, and some have none.

    Frequently asked questions

    ATT&CK describes adversary behavior; D3FEND describes defensive techniques and modeled relationships. They can be used together, but not every countermeasure has a direct, validated one-to-one ATT&CK mitigation mapping.
    Grouped by theme
    Cited by

    Where this term appears across MedTech Terms.

    Latest in MedTech

    Sources

    5 sources

    Sources support the definition or relevant regulatory context, not necessarily every claim on this page. Each is graded against our source-tier hierarchy so you can see what rests on binding law versus commentary.

    Official-source claim check:

    MITRE D3FEND is a defensive-technique knowledge graph; relationships support analysis rather than guaranteeing mitigation.

    Partial review: verified corrections are applied, but this is not a full accuracy certification. The last full review date is unchanged.

    Remaining verification limits
    • Secondary regulatory, standards-clause, market-prevalence or procurement claims were not fully substantiated by accessible original text.
    Tier 2Regulator guidance and consensus· 4Tier 4Trade press and expert commentary· 1
    Link health: 3 verified 2 unchecked· last checked 2026-06-20
    MITRE·4HSCC·1
    1. 1
      MITRE D3FEND
      Tier 2 Verified
      MITREd3fend.mitre.org
    2. 2
      D3FEND ATT&CK mappings
      Tier 2 Verified
      MITREd3fend.mitre.org
    3. 3
      HSCC - Health Sector Coordinating Council
      Tier 4 Verified
      HSCChealthsectorcouncil.org
    4. 4
      MITRE Model tactic
      Tier 2 Unchecked
      MITREd3fend.mitre.org
    5. 5
      MITRE Restore tactic
      Tier 2 Unchecked
      MITREd3fend.mitre.org

    Inline markers like [1] jump to the matching reference above.