Two operators at a control-room desk with a row of monitors, a laptop and keyboards

OT/ICS security

MITRE ATT&CK for ICS: the adversary tactics and techniques matrix, explained

Last updated:

MITRE ATT&CK for ICS, now 12 tactics strong, is a dedicated knowledge base, inside MITRE's broader ATT&CK framework, of the tactics and techniques adversaries use against industrial control systems. It launched on 7 January 2020, and per Help Net Security's coverage of that launch, it "adds the behavior adversaries use within ICS environments," highlighting "the unique aspects of the specialized applications and protocols that ICS system operators typically use, and adversaries take advantage of, to interface with physical equipment." The current release is v20.0, published 13 October 2026 per MITRE's own version-history page, and it still organizes that behavior into 12 tactics — the same count the matrix has used since launch.

Key takeaways

  • MITRE ATT&CK for ICS, now 12 tactics strong, is a dedicated knowledge base, inside MITRE's broader ATT&CK framework, of the tactics and techniques adversaries use against industrial control systems.
  • MITRE's general ATT&CK knowledge base — which its own FAQ page states "started in 2013" — was built around enterprise IT behavior.
  • ATT&CK v19, released 28 April 2026, added sub-techniques to the ICS matrix for the first time.
  • Many ICS techniques describe what an adversary does to a controller, gateway or field device.

Why is there a separate matrix for ICS?

MITRE's general ATT&CK knowledge base — which its own FAQ page states "started in 2013" — was built around enterprise IT behavior. Help Net Security's reporting on the ICS launch notes that "some aspects of the existing ATT&CK knowledge base for enterprise IT systems are applicable to ICS, and in many cases may represent an entry point into those ICS systems for adversaries," but industrial environments introduce behavior with no enterprise-IT equivalent: interaction with engineering workstations, industrial protocols, and the physical process itself. ATT&CK for ICS exists to document that behavior on its own terms rather than force it into the Enterprise matrix.

What are the 12 tactics?

MITRE's ICS matrix page lists the following tactics, in this order:

# Tactic
1 Initial Access
2 Execution
3 Persistence
4 Privilege Escalation
5 Evasion
6 Discovery
7 Lateral Movement
8 Collection
9 Command and Control
10 Inhibit Response Function
11 Impair Process Control
12 Impact

The last three — Inhibit Response Function, Impair Process Control, and Impact — have no direct Enterprise-matrix counterpart; they describe an adversary acting on the physical process itself, which is the behavior unique to ICS.

What's in the current (v20) matrix?

MITRE's October 2026 update page gives the following counts for the ICS matrix in v20:

Object type Count (v20, October 2026)
Tactics 12
Techniques 78
Sub-techniques 26
Groups 14
Software 25
Campaigns 10
Mitigations 53
Assets 18
Detection strategies 106

The same update page notes that v20 introduced a Command and Scripting Interpreter technique with six new sub-techniques (covering PowerShell, Windows Command Shell, Unix Shell, Visual Basic, Python and JavaScript execution in ICS environments), added two new campaigns ("2026 U.S. Water Utilities Attacks" and an "AI-Assisted Breach of Mexico's Government Infrastructure"), added nine detection strategies for behavioral detection of scripting and protocol abuse, and deprecated two older techniques (Command-Line Interface and Scripting) in favor of the new sub-techniques. These counts move with every six-month ATT&CK release, so a reader relying on a specific number should check MITRE's live update page for the current release rather than treat this table as permanently current. The site itself now shows content version v20.1, per the version history.

What changed when ICS got sub-techniques in v19?

ATT&CK v19, released 28 April 2026, added sub-techniques to the ICS matrix for the first time. The April 2026 update page lists the new parent techniques and the older techniques they revoked. Old IDs still resolve on the website, but they redirect to the new entry:

Old technique (revoked in v19) New technique ID
T0812 Default Credentials T1694.001 Insecure Credentials: Default Credentials
T0891 Hardcoded Credentials T1694.002 Insecure Credentials: Hardcoded Credentials
T0857 System Firmware T1693.001 Modify Firmware: System Firmware
T0839 Module Firmware T1693.002 Modify Firmware: Module Firmware
T0855 Unauthorized Command Message T1692.001 Unauthorized Message: Command Message
T0856 Spoof Reporting Message T1692.002 Unauthorized Message: Reporting Message
T0803 / T0804 Block Command / Reporting Message T1691.001 / .002 Block Operational Technology Message
T0805 Block Serial COM T1695.001 Block Communications: Serial COM

The same release added sub-techniques under existing parents, such as Program Download (Download All, Online Edit, Program Append) and Remote System Discovery (Port Scan, Broadcast Discovery, Multicast Discovery). Any threat model, test plan or customer document written before April 2026 that cites the T08xx IDs above needs its references updated.

Which techniques target the device itself?

Many ICS techniques describe what an adversary does to a controller, gateway or field device. Those are the ones a device maker can design against. The tactics and mitigations below come from each technique page, read 10 November 2026.

Technique Tactics What the product can do about it
T1694 Insecure Credentials Lateral Movement, Persistence No shared default or hard-coded passwords; force a credential change at commissioning
T1693 Modify Firmware Persistence, Inhibit Response Function, Impair Process Control Signed firmware and boot integrity; authenticated update path
T1692 Unauthorized Message Evasion, Impair Process Control Authenticated protocol variants; allow-list of permitted masters
T0843 Program Download Lateral Movement Require authentication and authorization for logic download and online edits; log them
T0858 Change Operating Mode Execution, Evasion Protect mode changes (run / program / remote) with authorization
T0866 Exploitation of Remote Services Initial Access, Lateral Movement Reduce exposed services; publish fixes and track known CVEs in shipped components
T0883 Internet Accessible Device Initial Access Safe defaults: no services on public interfaces, guidance on remote access

Protocol-level techniques map onto specific industrial protocols; for two common examples, see Modbus security and S7comm security.

How do mitigations and assets help a product team?

Mitigations name the defensive capability; assets name the device classes a technique applies to. Together they turn the matrix into a product checklist.

Modify Firmware, for example, lists 15 mitigations, including M0945 Code Signing, M0946 Boot Integrity, M0802 Communication Authenticity and M0813 Software Process and Device Authentication. Its asset list is PLC, safety controller, DCS controller and programmable automation controller. Insecure Credentials lists one mitigation, M0801 Access Management, and a much wider asset list that runs from workstations and HMIs to PLCs, RTUs and IEDs.

The asset page for PLCs (A0003) works the other way round: it lists the techniques that apply to that device class. A PLC maker can start there to see which techniques its product category attracts.

Where did detections and mitigations come from?

ATT&CK for ICS launched with techniques, software and group data; per MITRE's October 2022 (v12) update — the release that first brought formal detection content to ATT&CK for ICS, matching a model already introduced to ATT&CK Enterprise in v11 — ICS detections began describing ways of detecting specific ICS techniques tied to named data sources and data components. That detection layer is what the 106 detection strategies in the v20 table above build on; v20 adds platform and asset context to them.

How do you get the matrix as data?

MITRE publishes ATT&CK in machine-readable form, so a product team does not need to copy tables by hand:

  • STIX 2.1 bundles. The attack-stix-data repository holds every release as STIX 2.1 JSON collections, with an ics-attack folder for ATT&CK for ICS and one unversioned bundle that always matches the latest release.
  • Navigator layers. The ATT&CK Navigator lets a team colour the ICS matrix, for example "covered by a product feature" vs "out of scope", and export the layer with the release version recorded.
  • Pin the version. Store the ATT&CK version next to every mapping, because IDs change between releases, as v19 showed.

Worked example: how would a gateway maker threat-model with ATT&CK for ICS?

Synthetic example: "GW-200" is not a real product or customer. GW-200 is a DIN-rail protocol gateway: Modbus RTU in, OPC UA and MQTT out, with a web configuration page and a firmware update function. The maker wants a threat model its customers can read.

  1. Pick the assetsGW-200 fits MITRE's Data Gateway asset (A0009), and its web page adds an Application Server role (A0008). The team lists the techniques MITRE associates with those two asset classes and drops those that need a feature GW-200 lacks (no ladder-logic runtime, so no Program Download).
  2. Keep techniques that reach the deviceThe shortlist: T0883 Internet Accessible Device, T0866 Exploitation of Remote Services, T1694 Insecure Credentials, T1693 Modify Firmware, T1692 Unauthorized Message.
  3. Map each to a design feature and a testT1694 → unique per-device password, changed at first login, tested by a commissioning test case. T1693 → signed firmware images, rejected on signature failure, tested with a tampered image. T1692 → an allow-list of Modbus masters, tested by sending from an unknown address.
  4. Record the gapsModbus RTU has no authentication; the maker documents this as a residual risk and recommends a segmented serial bus.
  5. Track known vulnerabilities for T0866The design stops misuse of features; known CVEs in the embedded web server and TLS library are a separate, ongoing task, handled by matching the firmware SBOM against public vulnerability data each release.
  6. Pin the versionThe table states "ATT&CK for ICS v20.1", so a reviewer knows T1694 is current and T0812 is not.

Takeaway. ATT&CK for ICS gives the threat model shared names. The requirements still come from a standard such as IEC 62443-4-2.

How does it fit with IEC 62443 and SP 800-82?

ATT&CK for ICS is a behavior-mapping framework, not a requirements standard — it doesn't replace a program like IEC 62443-2-1 asset-owner security program or NIST SP 800-82 OT security guidance. NIST lists ATT&CK for ICS among its resources in Appendix D.3.5 of SP 800-82 Rev. 3, describing it as "a curated knowledge base for cyber adversary behavior in the ICS technology domain." The practical fit is complementary: those standards tell an asset owner what controls and program elements to put in place, and IEC 62443-3-3 and 4-2 tell suppliers what capabilities to build, while ATT&CK for ICS gives a common vocabulary for describing a threat group's or incident's behavior, checking it against documented mitigations and detections, and finding gaps in monitoring coverage.

What is a workable starting point?

  1. Pick the matrix that matches your environment— a single OT network may touch techniques from multiple tactics (e.g. Lateral Movement into Impair Process Control); don't assume Initial Access coverage implies coverage further down the kill chain.
  2. Map known incidents and threat-group reporting onto ATT&CK for ICS techniquesbefore building new detections from scratch, since MITRE's own groups/software/campaign entries already link many public incidents to specific techniques.
  3. Use the mitigations list as a starting checklist, then verify against your own architecture — generic ATT&CK mitigations (network segmentation, allow-listing) still need to be scoped to the specific protocols and assets in your environment.
  4. Re-check counts against the live matrix on a cadence— MITRE revises ATT&CK roughly twice a year, and technique/sub-technique counts (and occasionally tactic definitions) change between releases.

What are the common pitfalls?

  • Citing revoked IDs. T0812, T0839, T0855 and T0857 redirect to v19 sub-techniques; documents that still use them look out of date to reviewers.
  • Treating coverage as compliance. A fully coloured Navigator layer is not evidence for IEC 62443, the CRA or any certification.
  • Mapping only the network. Device-level techniques (firmware, credentials, mode changes) are the ones a product team can design out.
  • Ignoring the version. A mapping without "v20.1" (or whichever release) cannot be checked later.
  • Assuming every mitigation fits. Host-based tools listed as mitigations may not run on a resource-constrained controller.

SoftWSP does not map findings to ATT&CK techniques. Its OT Snapshot works from Zeek protocol logs of a plant's own traffic capture: it lists hosts, shows which speak Modbus, S7comm, DNP3, EtherNet/IP or BACnet, and flags interactive remote-access sessions (SSH, Telnet, RDP, VNC) — inputs an engineer can use for the Initial Access and Lateral Movement questions above: see OT network assessment. For the known-vulnerability step in the worked example, SoftWSP extracts a firmware SBOM as CycloneDX JSON, matches it against NVD, CISA KEV, FIRST EPSS and CISA CSAF ICS advisories, and drafts a cited report for engineer review: see device firmware security.

This guide summarises public MITRE ATT&CK publications and contemporaneous reporting on the ICS matrix's 2020 launch; it does not constitute security or compliance advice.

Put this guide to work

Frequently asked questions

What is MITRE ATT&CK for ICS?

A knowledge base of the tactics and techniques that cyber adversaries use against industrial control systems — the specialized applications, protocols and physical equipment that ICS operators work with. Help Net Security's coverage of the launch, published 8 January 2020, describes it as adding "the behavior adversaries use within ICS environments," highlighting "the unique aspects of the specialized applications and protocols that ICS system operators typically use, and adversaries take advantage of, to interface with physical equipment." It is a dedicated ICS matrix inside MITRE's broader ATT&CK framework, which MITRE's own FAQ states it "started in 2013."

How many tactics and techniques does the current ICS matrix have?

12 tactics, unchanged since launch. The technique count moves with each release: MITRE's own October 2026 (v20) update page lists 78 techniques, 26 sub-techniques, 14 groups, 25 pieces of software, 10 campaigns, 53 mitigations and 18 assets for the ICS matrix in that release — current as of v20.0, released 13 October 2026 per MITRE's version-history page.

How does ATT&CK for ICS differ from ATT&CK Enterprise?

They are separate matrices covering different environments, built on the same underlying framework. Per Help Net Security's coverage of the ICS launch, "some aspects of the existing ATT&CK knowledge base for enterprise IT systems are applicable to ICS, and in many cases may represent an entry point into those ICS systems for adversaries," but ATT&CK for ICS documents behavior specific to industrial environments — the engineering workstations, protocols (e.g. Modbus, S7) and physical-process steps that have no equivalent in a general enterprise IT matrix. ATT&CK for ICS also uses its own tactic set (12, listed on MITRE's ICS matrix page) rather than reusing Enterprise's 14 tactics.

How do asset owners and defenders use it?

As a common vocabulary for describing and detecting adversary behavior against industrial environments: mapping a known intrusion or threat group's reported behavior onto ATT&CK for ICS tactics/techniques to compare it against existing detections and mitigations, and using the matrix's own mitigations and (since MITRE's ATT&CK v12, per its October 2022 update) detection content to identify coverage gaps. MITRE's v20 update notes, for example, nine new detection strategies for behavioral detection of scripting and protocol abuse in ICS command-and-control activity.

Sources

  1. MITRE ATT&CK: ICS Matrix
  2. MITRE ATT&CK: Updates — October 2026 (v20)
  3. MITRE ATT&CK: Version History (release dates)
  4. MITRE ATT&CK: FAQ
  5. Help Net Security: ATT&CK for ICS — knowledge base of techniques used by cyber adversaries (8 January 2020)
  6. MITRE ATT&CK: Updates — April 2026 (v19, ICS sub-techniques and revocations)
  7. MITRE ATT&CK: ICS technique T1694, Insecure Credentials
  8. MITRE ATT&CK: ICS technique T1693, Modify Firmware
  9. MITRE ATT&CK: ICS technique T1692, Unauthorized Message
  10. MITRE ATT&CK: ICS asset A0003, Programmable Logic Controller (PLC)
  11. MITRE ATT&CK: ICS mitigation M0945, Code Signing
  12. GitHub mitre-attack: attack-stix-data (ATT&CK in STIX 2.1)
  13. GitHub mitre-attack: ATT&CK Navigator
  14. NIST: SP 800-82 Rev. 3, Appendix D.3.5 MITRE ATT&CK for ICS (PDF)
Was this guide helpful?

In this cluster

MITRE ATT&CK for ICS: the adversary tactics and techniques matrix, explained