MITRE ATT&CK for ICS
ATT&CK for ICS organizes publicly reported adversary tactics, techniques, software, groups, mitigations, and data sources relevant to industrial control systems.
What the authority record establishes
ATT&CK for ICS organizes publicly reported adversary tactics, techniques, software, groups, mitigations, and data sources relevant to industrial control systems.
Not a regulation or standard
The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.
Why it matters to this market
Detection claims can name exact techniques, data sources, evidence, and coverage limits instead of claiming complete ATT&CK coverage.
Affected operating stages
- Threat Modeling
- Detection Design
- Validation
- Investigation
- Response
Capabilities to examine
OT Threat Intelligence And Detection Content
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for OT threat intelligence and detection content.
Anomaly And Behavioral Detection
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for anomaly and behavioral detection.
Alert Triage And Investigation Workflow
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for alert triage and investigation workflow.
Packet Capture And Forensic Evidence
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for packet capture and forensic evidence.
Incident Response And Recovery Support
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for incident response and recovery support.
Compliance Mapping And Control Evidence
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for compliance mapping and control evidence.
Affected buyer audiences
- OT defenders
- threat-intelligence teams
- detection engineers
- incident responders
Implementation questions
- Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
- What is binding, what is guidance, and what is a technical or consensus standard?
- Which publication, adoption, effective, application, transition, and enforcement dates differ?
- Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
- How will a source revision affect open work and historical decisions?
Interpretation boundary
A technique mapping is not proof of detection, prevention, attribution, incident presence, or operationally safe response.