MITRE ATT&CK
Knowledge base of real-world adversary tactics, techniques, and procedures organized into a matrix used to model threats and assess defenses.
Definition
MITRE ATT&CK is a knowledge base of observed adversary tactics, techniques and sub-techniques, with Enterprise, Mobile and ICS domains. Major content releases generally occur twice yearly, with smaller updates between them. As of November 1, 2026 the current content version is v20.0, released October 13, 2026.What this means in practice
Use ATT&CK selectively to enrich device-specific threat models, detection engineering and security testing. ICS techniques should be selected for architectural applicability, not applied automatically to every hospital device.Examples
- Illustrative: A medical device manufacturer uses the ATT&CK for ICS matrix to identify specific techniques an adversary might use to compromise an infusion pump, such as 'Program Download' or 'Input Data Manipulation'.
- Illustrative: A hospital's security operations center maps observed network activity related to a medical imaging system to ATT&CK techniques like 'Remote Service Session Hijacking' to understand the adversary's intent and improve detection rules.
- Illustrative: During a cybersecurity assessment, a red team emulates ATT&CK techniques, such as 'Valid Accounts' and 'Lateral Tool Transfer,' to test the defenses of a hospital's connected surgical robot system.
- •Mapping threats to ATT&CK tactics only (the column headers) instead of specific techniques and sub-techniques, the granularity is the point.
- •Treating ATT&CK as a checklist of controls rather than a reference of attacker behavior, defensive frameworks like D3FEND or NIST CSF cover controls.
- •Ignoring ICS ATT&CK for hospital-deployed devices; many techniques in that matrix apply to networked imaging, lab analyzers, and infusion fleets.
Frequently asked questions
Related terms
Grouped by themeEditor's picks
· Hand-selected related conceptsAAMI Technical Information Report providing MedTech-specific guidance on cybersecurity risk management.
MITRE's knowledge graph of defensive cybersecurity countermeasures, explicitly mapped to the ATT&CK techniques they mitigate.
A risk-based framework of cybersecurity functions and outcomes published by NIST and widely used to organize MedTech security programs.
The bundle of cybersecurity artifacts a sponsor includes in a 510(k), De Novo, PMA, or HDE submission for a cyber device.
More in Cybersecurity
· Same categoryA six-category framework for enumerating threats: Spoofing, Tampering, Repudiation, Information disclosure, Denial of service, Elevation of privilege.
A structured analysis that identifies how an attacker could compromise a medical device and what controls mitigate each threat.
AAMI/ANSI standard establishing requirements for medical-device cybersecurity activities throughout the lifecycle.
AAMI Technical Information Report on post-market security risk management for medical device manufacturers, the operational companion to TIR57.
Where this term appears across MedTech Terms.
Latest in MedTech
Sources
5 sourcesSources 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 catalogs observed adversary behavior in Enterprise, Mobile and ICS knowledge bases.
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.
- 1MITRE ATT&CKTier 2 VerifiedMITREattack.mitre.org
- 2ATT&CK for ICSTier 2 VerifiedMITREattack.mitre.org
- 3Getting Started with ATT&CKTier 2 VerifiedMITREmitre.org
- 4MITRE version historyTier 2 UncheckedMITREattack.mitre.org
- 5FDA final guidance, February 3, 2026Tier 2 UncheckedFDAfda.gov
Inline markers like [1] jump to the matching reference above.