@blamejs/exceptd-skills 0.13.18 → 0.13.20
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +79 -0
- package/data/_indexes/_meta.json +9 -9
- package/data/_indexes/activity-feed.json +2 -2
- package/data/_indexes/catalog-summaries.json +2 -2
- package/data/_indexes/chains.json +14 -0
- package/data/_indexes/frequency.json +1 -0
- package/data/attack-techniques.json +2600 -109
- package/data/cve-catalog.json +147 -2678
- package/data/cwe-catalog.json +60 -1
- package/data/framework-control-gaps.json +252 -84
- package/data/rfc-references.json +286 -125
- package/data/zeroday-lessons.json +17 -2909
- package/lib/canonical-eq.js +88 -0
- package/lib/cve-regression-watcher.js +130 -9
- package/lib/source-advisories.js +9 -34
- package/lib/version-pins.js +73 -0
- package/lib/xml-tokenizer.js +344 -0
- package/manifest.json +44 -44
- package/package.json +6 -2
- package/sbom.cdx.json +108 -33
- package/scripts/audit-catalog-gaps.js +347 -0
- package/scripts/check-test-coverage.js +16 -10
- package/scripts/refresh-mitre-ics-attack.js +15 -0
- package/scripts/refresh-upstream-catalogs.js +171 -54
|
@@ -23,36 +23,114 @@
|
|
|
23
23
|
},
|
|
24
24
|
"T0001": {
|
|
25
25
|
"name": "Authority Spoof",
|
|
26
|
-
"version": "v19"
|
|
26
|
+
"version": "v19",
|
|
27
|
+
"_gap_skip": {
|
|
28
|
+
"fields": [
|
|
29
|
+
"tactic",
|
|
30
|
+
"description",
|
|
31
|
+
"platforms"
|
|
32
|
+
],
|
|
33
|
+
"reason": "legacy MITRE ID not present in current Enterprise or ICS-attack STIX bundles; retained for operator-curated CVE cross-references that pre-date the modern technique IDs"
|
|
34
|
+
},
|
|
35
|
+
"description": "Legacy MITRE ATT&CK ID retained for backward-compat with operator-curated CVE cross-references. Not in current Enterprise / ICS-attack STIX bundles."
|
|
27
36
|
},
|
|
28
37
|
"T0017": {
|
|
29
38
|
"name": "Spearphishing Attachment (ICS)",
|
|
30
|
-
"version": "v19"
|
|
39
|
+
"version": "v19",
|
|
40
|
+
"_gap_skip": {
|
|
41
|
+
"fields": [
|
|
42
|
+
"tactic",
|
|
43
|
+
"description",
|
|
44
|
+
"platforms"
|
|
45
|
+
],
|
|
46
|
+
"reason": "legacy MITRE ID not present in current Enterprise or ICS-attack STIX bundles; retained for operator-curated CVE cross-references that pre-date the modern technique IDs"
|
|
47
|
+
},
|
|
48
|
+
"description": "Legacy MITRE ATT&CK ID retained for backward-compat with operator-curated CVE cross-references. Not in current Enterprise / ICS-attack STIX bundles."
|
|
31
49
|
},
|
|
32
50
|
"T0051": {
|
|
33
51
|
"name": "Position Tampering",
|
|
34
|
-
"version": "v19"
|
|
52
|
+
"version": "v19",
|
|
53
|
+
"_gap_skip": {
|
|
54
|
+
"fields": [
|
|
55
|
+
"tactic",
|
|
56
|
+
"description",
|
|
57
|
+
"platforms"
|
|
58
|
+
],
|
|
59
|
+
"reason": "legacy MITRE ID not present in current Enterprise or ICS-attack STIX bundles; retained for operator-curated CVE cross-references that pre-date the modern technique IDs"
|
|
60
|
+
},
|
|
61
|
+
"description": "Legacy MITRE ATT&CK ID retained for backward-compat with operator-curated CVE cross-references. Not in current Enterprise / ICS-attack STIX bundles."
|
|
35
62
|
},
|
|
36
63
|
"T0096": {
|
|
37
64
|
"name": "Remote System Discovery (ICS)",
|
|
38
|
-
"version": "v19"
|
|
65
|
+
"version": "v19",
|
|
66
|
+
"_gap_skip": {
|
|
67
|
+
"fields": [
|
|
68
|
+
"tactic",
|
|
69
|
+
"description",
|
|
70
|
+
"platforms"
|
|
71
|
+
],
|
|
72
|
+
"reason": "legacy MITRE ID not present in current Enterprise or ICS-attack STIX bundles; retained for operator-curated CVE cross-references that pre-date the modern technique IDs"
|
|
73
|
+
},
|
|
74
|
+
"description": "Legacy MITRE ATT&CK ID retained for backward-compat with operator-curated CVE cross-references. Not in current Enterprise / ICS-attack STIX bundles."
|
|
39
75
|
},
|
|
40
76
|
"T0853": {
|
|
41
77
|
"name": "Scripting",
|
|
42
|
-
"version": "v19"
|
|
78
|
+
"version": "v19",
|
|
79
|
+
"description": "Adversaries may use scripting languages to execute arbitrary code in the form of a pre-written script or in the form of user-supplied code to an interpreter.",
|
|
80
|
+
"tactic": [
|
|
81
|
+
"Execution (ICS)"
|
|
82
|
+
],
|
|
83
|
+
"description_full": "Adversaries may use scripting languages to execute arbitrary code in the form of a pre-written script or in the form of user-supplied code to an interpreter. Scripting languages are programming languages that differ from compiled languages, in that scripting languages use an interpreter, instead of a compiler. These interpreters read and compile part of the source code just before it is executed, as opposed to compilers, which compile each and every line of code to an executable file. Scripting allows software developers to run their code on any system where the interpreter exists. This way, they can distribute one package, instead of precompiling executables for many different systems. Scripting languages, such as Python, have their interpreters shipped as a default with many Linux distributions. In addition to being a useful tool for developers and administrators, scripting language interpreters may be abused by the adversary to execute code in the target environment. Due to the nature of scripting languages, this allows for weaponized code to be deployed to a target easily, and leaves open the possibility of on-the-fly scripting to perform a task.",
|
|
84
|
+
"platforms": [
|
|
85
|
+
"None"
|
|
86
|
+
],
|
|
87
|
+
"reference_url": "https://attack.mitre.org/techniques/T0853",
|
|
88
|
+
"stix_id": "attack-pattern--2dc2b567-8821-49f9-9045-8740f3d0b958",
|
|
89
|
+
"last_verified": "2026-05-19"
|
|
43
90
|
},
|
|
44
91
|
"T0855": {
|
|
45
92
|
"name": "Unauthorized Command Message",
|
|
46
|
-
"version": "v19"
|
|
93
|
+
"version": "v19",
|
|
94
|
+
"_gap_skip": {
|
|
95
|
+
"fields": [
|
|
96
|
+
"tactic",
|
|
97
|
+
"description",
|
|
98
|
+
"platforms"
|
|
99
|
+
],
|
|
100
|
+
"reason": "legacy MITRE ID not present in current Enterprise or ICS-attack STIX bundles; retained for operator-curated CVE cross-references that pre-date the modern technique IDs"
|
|
101
|
+
},
|
|
102
|
+
"description": "Legacy MITRE ATT&CK ID retained for backward-compat with operator-curated CVE cross-references. Not in current Enterprise / ICS-attack STIX bundles."
|
|
47
103
|
},
|
|
48
104
|
"T0867": {
|
|
49
105
|
"name": "Lateral Tool Transfer",
|
|
50
106
|
"version": "v19",
|
|
51
|
-
"domain": "ICS"
|
|
107
|
+
"domain": "ICS",
|
|
108
|
+
"description": "Adversaries may transfer tools or other files from one system to another to stage adversary tools or other files over the course of an operation.",
|
|
109
|
+
"tactic": [
|
|
110
|
+
"Lateral Movement (ICS)"
|
|
111
|
+
],
|
|
112
|
+
"description_full": "Adversaries may transfer tools or other files from one system to another to stage adversary tools or other files over the course of an operation. (Citation: Enterprise ATT&CK) Copying of files may also be performed laterally between internal victim systems to support Lateral Movement with remote Execution using inherent file sharing protocols such as file sharing over SMB to connected network shares. (Citation: Enterprise ATT&CK) In control systems environments, malware may use SMB and other file sharing protocols to move laterally through industrial networks.",
|
|
113
|
+
"platforms": [
|
|
114
|
+
"None"
|
|
115
|
+
],
|
|
116
|
+
"reference_url": "https://attack.mitre.org/techniques/T0867",
|
|
117
|
+
"stix_id": "attack-pattern--ead7bd34-186e-4c79-9a4d-b65bcce6ed9d",
|
|
118
|
+
"last_verified": "2026-05-19"
|
|
52
119
|
},
|
|
53
120
|
"T0883": {
|
|
54
121
|
"name": "Internet Accessible Device",
|
|
55
|
-
"version": "v19"
|
|
122
|
+
"version": "v19",
|
|
123
|
+
"description": "Adversaries may gain access into industrial environments through systems exposed directly to the internet for remote access rather than through [External Remote Services](https://attack.mitre.org/techniques/T0822).",
|
|
124
|
+
"tactic": [
|
|
125
|
+
"Initial Access (ICS)"
|
|
126
|
+
],
|
|
127
|
+
"description_full": "Adversaries may gain access into industrial environments through systems exposed directly to the internet for remote access rather than through [External Remote Services](https://attack.mitre.org/techniques/T0822). Internet Accessible Devices are exposed to the internet unintentionally or intentionally without adequate protections. This may allow for adversaries to move directly into the control system network. Access onto these devices is accomplished without the use of exploits, these would be represented within the [Exploit Public-Facing Application](https://attack.mitre.org/techniques/T0819) technique. Adversaries may leverage built in functions for remote access which may not be protected or utilize minimal legacy protections that may be targeted. (Citation: NCCIC January 2014) These services may be discoverable through the use of online scanning tools. In the case of the Bowman dam incident, adversaries leveraged access to the dam control network through a cellular modem. Access to the device was protected by password authentication, although the application was vulnerable to brute forcing. (Citation: NCCIC January 2014) (Citation: Danny Yadron December 2015) (Citation: Mark Thompson March 2016) In Trend Micros manufacturing deception operations adversaries were detected leveraging direct internet access to an ICS environment through the exposure of operational protocols such as Siemens S7, Omron FINS, and EtherNet/IP, in addition to misconfigured VNC access. (Citation: Stephen Hilt, Federico Maggi, Charles Perine, Lord Remorin, Martin Rsler, and Rainer Vosseler)",
|
|
128
|
+
"platforms": [
|
|
129
|
+
"None"
|
|
130
|
+
],
|
|
131
|
+
"reference_url": "https://attack.mitre.org/techniques/T0883",
|
|
132
|
+
"stix_id": "attack-pattern--f8df6b57-14bc-425f-9a91-6f59f6799307",
|
|
133
|
+
"last_verified": "2026-05-19"
|
|
56
134
|
},
|
|
57
135
|
"T1021": {
|
|
58
136
|
"name": "Remote Services",
|
|
@@ -68,7 +146,11 @@
|
|
|
68
146
|
"reference_url": "https://attack.mitre.org/techniques/T1021",
|
|
69
147
|
"stix_id": "attack-pattern--54a649ff-439a-41a4-9856-8d144a2551ba",
|
|
70
148
|
"is_subtechnique": false,
|
|
71
|
-
"last_verified": "2026-05-19"
|
|
149
|
+
"last_verified": "2026-05-19",
|
|
150
|
+
"description": "Adversaries may use [Valid Accounts](https://attack.mitre.org/techniques/T1078) to log into a service that accepts remote connections, such as telnet, SSH, and VNC.",
|
|
151
|
+
"tactic": [
|
|
152
|
+
"Lateral Movement"
|
|
153
|
+
]
|
|
72
154
|
},
|
|
73
155
|
"T1027": {
|
|
74
156
|
"name": "Obfuscated Files or Information",
|
|
@@ -93,7 +175,8 @@
|
|
|
93
175
|
"reference_url": "https://attack.mitre.org/techniques/T1027",
|
|
94
176
|
"stix_id": "attack-pattern--b3d682b6-98f2-4fb0-aa3b-b4df007ca70a",
|
|
95
177
|
"is_subtechnique": false,
|
|
96
|
-
"last_verified": "2026-05-19"
|
|
178
|
+
"last_verified": "2026-05-19",
|
|
179
|
+
"description": "Adversaries may attempt to make an executable or file difficult to discover or analyze by encrypting, encoding, or otherwise obfuscating its contents on the system or in transit."
|
|
97
180
|
},
|
|
98
181
|
"T1040": {
|
|
99
182
|
"name": "Network Sniffing",
|
|
@@ -109,7 +192,12 @@
|
|
|
109
192
|
"reference_url": "https://attack.mitre.org/techniques/T1040",
|
|
110
193
|
"stix_id": "attack-pattern--3257eb21-f9a7-4430-8de1-d8b6e288f529",
|
|
111
194
|
"is_subtechnique": false,
|
|
112
|
-
"last_verified": "2026-05-19"
|
|
195
|
+
"last_verified": "2026-05-19",
|
|
196
|
+
"description": "Adversaries may passively sniff network traffic to capture information about an environment, including authentication material passed over the network.",
|
|
197
|
+
"tactic": [
|
|
198
|
+
"Credential Access",
|
|
199
|
+
"Discovery"
|
|
200
|
+
]
|
|
113
201
|
},
|
|
114
202
|
"T1041": {
|
|
115
203
|
"name": "Exfiltration Over C2 Channel",
|
|
@@ -127,7 +215,11 @@
|
|
|
127
215
|
"reference_url": "https://attack.mitre.org/techniques/T1041",
|
|
128
216
|
"stix_id": "attack-pattern--92d7da27-2d91-488e-a00c-059dc162766d",
|
|
129
217
|
"is_subtechnique": false,
|
|
130
|
-
"last_verified": "2026-05-19"
|
|
218
|
+
"last_verified": "2026-05-19",
|
|
219
|
+
"description": "Adversaries may steal data by exfiltrating it over an existing command and control channel.",
|
|
220
|
+
"tactic": [
|
|
221
|
+
"Exfiltration"
|
|
222
|
+
]
|
|
131
223
|
},
|
|
132
224
|
"T1053.003": {
|
|
133
225
|
"name": "Scheduled Task/Job: Cron",
|
|
@@ -141,7 +233,13 @@
|
|
|
141
233
|
"reference_url": "https://attack.mitre.org/techniques/T1053/003",
|
|
142
234
|
"stix_id": "attack-pattern--2acf44aa-542f-4366-b4eb-55ef5747759c",
|
|
143
235
|
"is_subtechnique": true,
|
|
144
|
-
"last_verified": "2026-05-19"
|
|
236
|
+
"last_verified": "2026-05-19",
|
|
237
|
+
"description": "Adversaries may abuse the <code>cron</code> utility to perform task scheduling for initial or recurring execution of malicious code.(Citation: 20 macOS Common Tools and Techniques) The <code>cron</code> utility is a time-based job scheduler for Unix-like operating systems.",
|
|
238
|
+
"tactic": [
|
|
239
|
+
"Execution",
|
|
240
|
+
"Persistence",
|
|
241
|
+
"Privilege Escalation"
|
|
242
|
+
]
|
|
145
243
|
},
|
|
146
244
|
"T1055": {
|
|
147
245
|
"name": "Process Injection",
|
|
@@ -155,7 +253,12 @@
|
|
|
155
253
|
"reference_url": "https://attack.mitre.org/techniques/T1055",
|
|
156
254
|
"stix_id": "attack-pattern--43e7dc91-05b2-474c-b9ac-2ed4fe101f4d",
|
|
157
255
|
"is_subtechnique": false,
|
|
158
|
-
"last_verified": "2026-05-19"
|
|
256
|
+
"last_verified": "2026-05-19",
|
|
257
|
+
"description": "Adversaries may inject code into processes in order to evade process-based defenses as well as possibly elevate privileges.",
|
|
258
|
+
"tactic": [
|
|
259
|
+
"Stealth",
|
|
260
|
+
"Privilege Escalation"
|
|
261
|
+
]
|
|
159
262
|
},
|
|
160
263
|
"T1059": {
|
|
161
264
|
"name": "Command and Scripting Interpreter",
|
|
@@ -195,7 +298,8 @@
|
|
|
195
298
|
"reference_url": "https://attack.mitre.org/techniques/T1059",
|
|
196
299
|
"stix_id": "attack-pattern--7385dfaf-6886-4229-9ecd-6fd678040830",
|
|
197
300
|
"is_subtechnique": false,
|
|
198
|
-
"last_verified": "2026-05-19"
|
|
301
|
+
"last_verified": "2026-05-19",
|
|
302
|
+
"description": "Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries."
|
|
199
303
|
},
|
|
200
304
|
"T1059.001": {
|
|
201
305
|
"name": "Command and Scripting Interpreter: PowerShell",
|
|
@@ -210,7 +314,11 @@
|
|
|
210
314
|
"reference_url": "https://attack.mitre.org/techniques/T1059/001",
|
|
211
315
|
"stix_id": "attack-pattern--970a3432-3237-47ad-bcca-7d8cbb217736",
|
|
212
316
|
"is_subtechnique": true,
|
|
213
|
-
"last_verified": "2026-05-19"
|
|
317
|
+
"last_verified": "2026-05-19",
|
|
318
|
+
"description": "Adversaries may abuse PowerShell commands and scripts for execution.",
|
|
319
|
+
"tactic": [
|
|
320
|
+
"Execution"
|
|
321
|
+
]
|
|
214
322
|
},
|
|
215
323
|
"T1059.006": {
|
|
216
324
|
"name": "Command and Scripting Interpreter: Python",
|
|
@@ -229,7 +337,11 @@
|
|
|
229
337
|
"reference_url": "https://attack.mitre.org/techniques/T1059/006",
|
|
230
338
|
"stix_id": "attack-pattern--cc3502b5-30cc-4473-ad48-42d51a6ef6d1",
|
|
231
339
|
"is_subtechnique": true,
|
|
232
|
-
"last_verified": "2026-05-19"
|
|
340
|
+
"last_verified": "2026-05-19",
|
|
341
|
+
"description": "Adversaries may abuse Python commands and scripts for execution.",
|
|
342
|
+
"tactic": [
|
|
343
|
+
"Execution"
|
|
344
|
+
]
|
|
233
345
|
},
|
|
234
346
|
"T1059.007": {
|
|
235
347
|
"name": "Command and Scripting Interpreter: JavaScript",
|
|
@@ -256,7 +368,11 @@
|
|
|
256
368
|
"reference_url": "https://attack.mitre.org/techniques/T1059/007",
|
|
257
369
|
"stix_id": "attack-pattern--0f4a0c76-ab2d-4cb0-85d3-3f0efb8cba0d",
|
|
258
370
|
"is_subtechnique": true,
|
|
259
|
-
"last_verified": "2026-05-19"
|
|
371
|
+
"last_verified": "2026-05-19",
|
|
372
|
+
"description": "Adversaries may abuse various implementations of JavaScript for execution.",
|
|
373
|
+
"tactic": [
|
|
374
|
+
"Execution"
|
|
375
|
+
]
|
|
260
376
|
},
|
|
261
377
|
"T1068": {
|
|
262
378
|
"name": "Exploitation for Privilege Escalation",
|
|
@@ -301,7 +417,11 @@
|
|
|
301
417
|
"reference_url": "https://attack.mitre.org/techniques/T1068",
|
|
302
418
|
"stix_id": "attack-pattern--b21c3b2d-02e6-45b1-980b-e69051040839",
|
|
303
419
|
"is_subtechnique": false,
|
|
304
|
-
"last_verified": "2026-05-19"
|
|
420
|
+
"last_verified": "2026-05-19",
|
|
421
|
+
"description": "Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.",
|
|
422
|
+
"tactic": [
|
|
423
|
+
"Privilege Escalation"
|
|
424
|
+
]
|
|
305
425
|
},
|
|
306
426
|
"T1071": {
|
|
307
427
|
"name": "Application Layer Protocol",
|
|
@@ -317,7 +437,11 @@
|
|
|
317
437
|
"reference_url": "https://attack.mitre.org/techniques/T1071",
|
|
318
438
|
"stix_id": "attack-pattern--355be19c-ffc9-46d5-8d50-d6a036c675b6",
|
|
319
439
|
"is_subtechnique": false,
|
|
320
|
-
"last_verified": "2026-05-19"
|
|
440
|
+
"last_verified": "2026-05-19",
|
|
441
|
+
"description": "Adversaries may communicate using OSI application layer protocols to avoid detection/network filtering by blending in with existing traffic.",
|
|
442
|
+
"tactic": [
|
|
443
|
+
"Command and Control"
|
|
444
|
+
]
|
|
321
445
|
},
|
|
322
446
|
"T1078": {
|
|
323
447
|
"name": "Valid Accounts",
|
|
@@ -371,7 +495,14 @@
|
|
|
371
495
|
"reference_url": "https://attack.mitre.org/techniques/T1078",
|
|
372
496
|
"stix_id": "attack-pattern--b17a1a56-e99c-403c-8948-561df0cffe81",
|
|
373
497
|
"is_subtechnique": false,
|
|
374
|
-
"last_verified": "2026-05-19"
|
|
498
|
+
"last_verified": "2026-05-19",
|
|
499
|
+
"description": "Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.",
|
|
500
|
+
"tactic": [
|
|
501
|
+
"Stealth",
|
|
502
|
+
"Persistence",
|
|
503
|
+
"Privilege Escalation",
|
|
504
|
+
"Initial Access"
|
|
505
|
+
]
|
|
375
506
|
},
|
|
376
507
|
"T1078.001": {
|
|
377
508
|
"name": "Valid Accounts: Default Accounts",
|
|
@@ -395,7 +526,14 @@
|
|
|
395
526
|
"reference_url": "https://attack.mitre.org/techniques/T1078/001",
|
|
396
527
|
"stix_id": "attack-pattern--6151cbea-819b-455a-9fa6-99a1cc58797d",
|
|
397
528
|
"is_subtechnique": true,
|
|
398
|
-
"last_verified": "2026-05-19"
|
|
529
|
+
"last_verified": "2026-05-19",
|
|
530
|
+
"description": "Adversaries may obtain and abuse credentials of a default account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.",
|
|
531
|
+
"tactic": [
|
|
532
|
+
"Stealth",
|
|
533
|
+
"Persistence",
|
|
534
|
+
"Privilege Escalation",
|
|
535
|
+
"Initial Access"
|
|
536
|
+
]
|
|
399
537
|
},
|
|
400
538
|
"T1078.002": {
|
|
401
539
|
"name": "Valid Accounts: Domain Accounts",
|
|
@@ -410,7 +548,14 @@
|
|
|
410
548
|
"reference_url": "https://attack.mitre.org/techniques/T1078/002",
|
|
411
549
|
"stix_id": "attack-pattern--c3d4bdd9-2cfe-4a80-9d0c-07a29ecdce8f",
|
|
412
550
|
"is_subtechnique": true,
|
|
413
|
-
"last_verified": "2026-05-19"
|
|
551
|
+
"last_verified": "2026-05-19",
|
|
552
|
+
"description": "Adversaries may obtain and abuse credentials of a domain account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.(Citation: TechNet Credential Theft) Domain accounts are those managed by Active Directory Domain Services where access and permissions are configured across systems and services that are part of that domain.",
|
|
553
|
+
"tactic": [
|
|
554
|
+
"Stealth",
|
|
555
|
+
"Persistence",
|
|
556
|
+
"Privilege Escalation",
|
|
557
|
+
"Initial Access"
|
|
558
|
+
]
|
|
414
559
|
},
|
|
415
560
|
"T1078.003": {
|
|
416
561
|
"name": "Valid Accounts: Local Accounts",
|
|
@@ -427,7 +572,14 @@
|
|
|
427
572
|
"reference_url": "https://attack.mitre.org/techniques/T1078/003",
|
|
428
573
|
"stix_id": "attack-pattern--fdc47f44-dd32-4b99-af5f-209f556f63c2",
|
|
429
574
|
"is_subtechnique": true,
|
|
430
|
-
"last_verified": "2026-05-19"
|
|
575
|
+
"last_verified": "2026-05-19",
|
|
576
|
+
"description": "Adversaries may obtain and abuse credentials of a local account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.",
|
|
577
|
+
"tactic": [
|
|
578
|
+
"Stealth",
|
|
579
|
+
"Persistence",
|
|
580
|
+
"Privilege Escalation",
|
|
581
|
+
"Initial Access"
|
|
582
|
+
]
|
|
431
583
|
},
|
|
432
584
|
"T1078.004": {
|
|
433
585
|
"name": "Valid Accounts: Cloud Accounts",
|
|
@@ -449,7 +601,14 @@
|
|
|
449
601
|
"reference_url": "https://attack.mitre.org/techniques/T1078/004",
|
|
450
602
|
"stix_id": "attack-pattern--f232fa7a-025c-4d43-abc7-318e81a73d65",
|
|
451
603
|
"is_subtechnique": true,
|
|
452
|
-
"last_verified": "2026-05-19"
|
|
604
|
+
"last_verified": "2026-05-19",
|
|
605
|
+
"description": "Valid accounts in cloud environments may allow adversaries to perform actions to achieve Initial Access, Persistence, Privilege Escalation, or Defense Evasion.",
|
|
606
|
+
"tactic": [
|
|
607
|
+
"Stealth",
|
|
608
|
+
"Persistence",
|
|
609
|
+
"Privilege Escalation",
|
|
610
|
+
"Initial Access"
|
|
611
|
+
]
|
|
453
612
|
},
|
|
454
613
|
"T1098": {
|
|
455
614
|
"name": "Account Manipulation",
|
|
@@ -473,7 +632,12 @@
|
|
|
473
632
|
"reference_url": "https://attack.mitre.org/techniques/T1098",
|
|
474
633
|
"stix_id": "attack-pattern--a10641f4-87b4-45a3-a906-92a149cb2c27",
|
|
475
634
|
"is_subtechnique": false,
|
|
476
|
-
"last_verified": "2026-05-19"
|
|
635
|
+
"last_verified": "2026-05-19",
|
|
636
|
+
"description": "Adversaries may manipulate accounts to maintain and/or elevate access to victim systems.",
|
|
637
|
+
"tactic": [
|
|
638
|
+
"Persistence",
|
|
639
|
+
"Privilege Escalation"
|
|
640
|
+
]
|
|
477
641
|
},
|
|
478
642
|
"T1098.001": {
|
|
479
643
|
"name": "Account Manipulation: Additional Cloud Credentials",
|
|
@@ -492,7 +656,8 @@
|
|
|
492
656
|
"reference_url": "https://attack.mitre.org/techniques/T1098/001",
|
|
493
657
|
"stix_id": "attack-pattern--8a2f40cf-8325-47f9-96e4-b1ca4c7389bd",
|
|
494
658
|
"is_subtechnique": true,
|
|
495
|
-
"last_verified": "2026-05-19"
|
|
659
|
+
"last_verified": "2026-05-19",
|
|
660
|
+
"description": "Adversaries may add adversary-controlled credentials to a cloud account to maintain persistent access to victim accounts and instances within the environment."
|
|
496
661
|
},
|
|
497
662
|
"T1102": {
|
|
498
663
|
"name": "Web Service",
|
|
@@ -507,7 +672,11 @@
|
|
|
507
672
|
"reference_url": "https://attack.mitre.org/techniques/T1102",
|
|
508
673
|
"stix_id": "attack-pattern--830c9528-df21-472c-8c14-a036bf17d665",
|
|
509
674
|
"is_subtechnique": false,
|
|
510
|
-
"last_verified": "2026-05-19"
|
|
675
|
+
"last_verified": "2026-05-19",
|
|
676
|
+
"description": "Adversaries may use an existing, legitimate external Web service as a means for relaying data to/from a compromised system.",
|
|
677
|
+
"tactic": [
|
|
678
|
+
"Command and Control"
|
|
679
|
+
]
|
|
511
680
|
},
|
|
512
681
|
"T1110": {
|
|
513
682
|
"name": "Brute Force",
|
|
@@ -528,7 +697,11 @@
|
|
|
528
697
|
"reference_url": "https://attack.mitre.org/techniques/T1110",
|
|
529
698
|
"stix_id": "attack-pattern--a93494bb-4b80-4ea1-8695-3236a49916fd",
|
|
530
699
|
"is_subtechnique": false,
|
|
531
|
-
"last_verified": "2026-05-19"
|
|
700
|
+
"last_verified": "2026-05-19",
|
|
701
|
+
"description": "Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.(Citation: TrendMicro Pawn Storm Dec 2020) Without knowledge of the password for an account or set of accounts, an adversary may systematically guess the password using a repetitive or iterative mechanism.(Citation: Dragos Crashoverride 2018) Brute forcing passwords can take place via interaction with a service that will check the validity of those credentials ...",
|
|
702
|
+
"tactic": [
|
|
703
|
+
"Credential Access"
|
|
704
|
+
]
|
|
532
705
|
},
|
|
533
706
|
"T1110.001": {
|
|
534
707
|
"name": "Brute Force: Password Guessing",
|
|
@@ -549,7 +722,11 @@
|
|
|
549
722
|
"reference_url": "https://attack.mitre.org/techniques/T1110/001",
|
|
550
723
|
"stix_id": "attack-pattern--09c4c11e-4fa1-4f8c-8dad-3cf8e69ad119",
|
|
551
724
|
"is_subtechnique": true,
|
|
552
|
-
"last_verified": "2026-05-19"
|
|
725
|
+
"last_verified": "2026-05-19",
|
|
726
|
+
"description": "Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts.",
|
|
727
|
+
"tactic": [
|
|
728
|
+
"Credential Access"
|
|
729
|
+
]
|
|
553
730
|
},
|
|
554
731
|
"T1133": {
|
|
555
732
|
"name": "External Remote Services",
|
|
@@ -569,7 +746,12 @@
|
|
|
569
746
|
"reference_url": "https://attack.mitre.org/techniques/T1133",
|
|
570
747
|
"stix_id": "attack-pattern--10d51417-ee35-4589-b1ff-b6df1c334e8d",
|
|
571
748
|
"is_subtechnique": false,
|
|
572
|
-
"last_verified": "2026-05-19"
|
|
749
|
+
"last_verified": "2026-05-19",
|
|
750
|
+
"description": "Adversaries may leverage external-facing remote services to initially access and/or persist within a network.",
|
|
751
|
+
"tactic": [
|
|
752
|
+
"Persistence",
|
|
753
|
+
"Initial Access"
|
|
754
|
+
]
|
|
573
755
|
},
|
|
574
756
|
"T1136.001": {
|
|
575
757
|
"name": "Create Account: Local Account",
|
|
@@ -586,7 +768,11 @@
|
|
|
586
768
|
"reference_url": "https://attack.mitre.org/techniques/T1136/001",
|
|
587
769
|
"stix_id": "attack-pattern--635cbe30-392d-4e27-978e-66774357c762",
|
|
588
770
|
"is_subtechnique": true,
|
|
589
|
-
"last_verified": "2026-05-19"
|
|
771
|
+
"last_verified": "2026-05-19",
|
|
772
|
+
"description": "Adversaries may create a local account to maintain access to victim systems.",
|
|
773
|
+
"tactic": [
|
|
774
|
+
"Persistence"
|
|
775
|
+
]
|
|
590
776
|
},
|
|
591
777
|
"T1190": {
|
|
592
778
|
"name": "Exploit Public-Facing Application",
|
|
@@ -788,7 +974,11 @@
|
|
|
788
974
|
"reference_url": "https://attack.mitre.org/techniques/T1190",
|
|
789
975
|
"stix_id": "attack-pattern--3f886f2a-874f-4333-b794-aa6075009b1c",
|
|
790
976
|
"is_subtechnique": false,
|
|
791
|
-
"last_verified": "2026-05-19"
|
|
977
|
+
"last_verified": "2026-05-19",
|
|
978
|
+
"description": "Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.",
|
|
979
|
+
"tactic": [
|
|
980
|
+
"Initial Access"
|
|
981
|
+
]
|
|
792
982
|
},
|
|
793
983
|
"T1195": {
|
|
794
984
|
"name": "Supply Chain Compromise",
|
|
@@ -803,7 +993,11 @@
|
|
|
803
993
|
"reference_url": "https://attack.mitre.org/techniques/T1195",
|
|
804
994
|
"stix_id": "attack-pattern--3f18edba-28f4-4bb9-82c3-8aa60dcac5f7",
|
|
805
995
|
"is_subtechnique": false,
|
|
806
|
-
"last_verified": "2026-05-19"
|
|
996
|
+
"last_verified": "2026-05-19",
|
|
997
|
+
"description": "Adversaries may manipulate products or product delivery mechanisms prior to receipt by a final consumer for the purpose of data or system compromise.",
|
|
998
|
+
"tactic": [
|
|
999
|
+
"Initial Access"
|
|
1000
|
+
]
|
|
807
1001
|
},
|
|
808
1002
|
"T1195.001": {
|
|
809
1003
|
"name": "Supply Chain Compromise: Software Dependencies and Development Tools",
|
|
@@ -823,7 +1017,11 @@
|
|
|
823
1017
|
"reference_url": "https://attack.mitre.org/techniques/T1195/001",
|
|
824
1018
|
"stix_id": "attack-pattern--191cc6af-1bb2-4344-ab5f-28e496638720",
|
|
825
1019
|
"is_subtechnique": true,
|
|
826
|
-
"last_verified": "2026-05-19"
|
|
1020
|
+
"last_verified": "2026-05-19",
|
|
1021
|
+
"description": "Adversaries may manipulate software dependencies and development tools prior to receipt by a final consumer for the purpose of data or system compromise.",
|
|
1022
|
+
"tactic": [
|
|
1023
|
+
"Initial Access"
|
|
1024
|
+
]
|
|
827
1025
|
},
|
|
828
1026
|
"T1195.002": {
|
|
829
1027
|
"name": "Supply Chain Compromise: Software Supply Chain",
|
|
@@ -847,7 +1045,11 @@
|
|
|
847
1045
|
"reference_url": "https://attack.mitre.org/techniques/T1195/002",
|
|
848
1046
|
"stix_id": "attack-pattern--bd369cd9-abb8-41ce-b5bb-fff23ee86c00",
|
|
849
1047
|
"is_subtechnique": true,
|
|
850
|
-
"last_verified": "2026-05-19"
|
|
1048
|
+
"last_verified": "2026-05-19",
|
|
1049
|
+
"description": "Adversaries may manipulate application software prior to receipt by a final consumer for the purpose of data or system compromise.",
|
|
1050
|
+
"tactic": [
|
|
1051
|
+
"Initial Access"
|
|
1052
|
+
]
|
|
851
1053
|
},
|
|
852
1054
|
"T1199": {
|
|
853
1055
|
"name": "Trusted Relationship",
|
|
@@ -865,7 +1067,11 @@
|
|
|
865
1067
|
"reference_url": "https://attack.mitre.org/techniques/T1199",
|
|
866
1068
|
"stix_id": "attack-pattern--9fa07bef-9c81-421e-a8e5-ad4366c5a925",
|
|
867
1069
|
"is_subtechnique": false,
|
|
868
|
-
"last_verified": "2026-05-19"
|
|
1070
|
+
"last_verified": "2026-05-19",
|
|
1071
|
+
"description": "Adversaries may breach or otherwise leverage organizations who have access to intended victims.",
|
|
1072
|
+
"tactic": [
|
|
1073
|
+
"Initial Access"
|
|
1074
|
+
]
|
|
869
1075
|
},
|
|
870
1076
|
"T1203": {
|
|
871
1077
|
"name": "Exploitation for Client Execution",
|
|
@@ -903,7 +1109,11 @@
|
|
|
903
1109
|
"reference_url": "https://attack.mitre.org/techniques/T1203",
|
|
904
1110
|
"stix_id": "attack-pattern--be2dcee9-a7a7-4e38-afd6-21b31ecc3d63",
|
|
905
1111
|
"is_subtechnique": false,
|
|
906
|
-
"last_verified": "2026-05-19"
|
|
1112
|
+
"last_verified": "2026-05-19",
|
|
1113
|
+
"description": "Adversaries may exploit software vulnerabilities in client applications to execute code.",
|
|
1114
|
+
"tactic": [
|
|
1115
|
+
"Execution"
|
|
1116
|
+
]
|
|
907
1117
|
},
|
|
908
1118
|
"T1212": {
|
|
909
1119
|
"name": "Exploitation for Credential Access",
|
|
@@ -921,7 +1131,11 @@
|
|
|
921
1131
|
"reference_url": "https://attack.mitre.org/techniques/T1212",
|
|
922
1132
|
"stix_id": "attack-pattern--9c306d8d-cde7-4b4c-b6e8-d0bb16caca36",
|
|
923
1133
|
"is_subtechnique": false,
|
|
924
|
-
"last_verified": "2026-05-19"
|
|
1134
|
+
"last_verified": "2026-05-19",
|
|
1135
|
+
"description": "Adversaries may exploit software vulnerabilities in an attempt to collect credentials.",
|
|
1136
|
+
"tactic": [
|
|
1137
|
+
"Credential Access"
|
|
1138
|
+
]
|
|
925
1139
|
},
|
|
926
1140
|
"T1213": {
|
|
927
1141
|
"name": "Data from Information Repositories",
|
|
@@ -938,7 +1152,11 @@
|
|
|
938
1152
|
"reference_url": "https://attack.mitre.org/techniques/T1213",
|
|
939
1153
|
"stix_id": "attack-pattern--d28ef391-8ed4-45dc-bc4a-2f43abf54416",
|
|
940
1154
|
"is_subtechnique": false,
|
|
941
|
-
"last_verified": "2026-05-19"
|
|
1155
|
+
"last_verified": "2026-05-19",
|
|
1156
|
+
"description": "Adversaries may leverage information repositories to mine valuable information.",
|
|
1157
|
+
"tactic": [
|
|
1158
|
+
"Collection"
|
|
1159
|
+
]
|
|
942
1160
|
},
|
|
943
1161
|
"T1485": {
|
|
944
1162
|
"name": "Data Destruction",
|
|
@@ -958,7 +1176,11 @@
|
|
|
958
1176
|
"reference_url": "https://attack.mitre.org/techniques/T1485",
|
|
959
1177
|
"stix_id": "attack-pattern--d45a3d09-b3cf-48f4-9f0f-f521ee5cb05c",
|
|
960
1178
|
"is_subtechnique": false,
|
|
961
|
-
"last_verified": "2026-05-19"
|
|
1179
|
+
"last_verified": "2026-05-19",
|
|
1180
|
+
"description": "Adversaries may destroy data and files on specific systems or in large numbers on a network to interrupt availability to systems, services, and network resources.",
|
|
1181
|
+
"tactic": [
|
|
1182
|
+
"Impact"
|
|
1183
|
+
]
|
|
962
1184
|
},
|
|
963
1185
|
"T1486": {
|
|
964
1186
|
"name": "Data Encrypted for Impact",
|
|
@@ -979,7 +1201,8 @@
|
|
|
979
1201
|
"reference_url": "https://attack.mitre.org/techniques/T1486",
|
|
980
1202
|
"stix_id": "attack-pattern--b80d107d-fa0d-4b60-9684-b0433e8bdba0",
|
|
981
1203
|
"is_subtechnique": false,
|
|
982
|
-
"last_verified": "2026-05-19"
|
|
1204
|
+
"last_verified": "2026-05-19",
|
|
1205
|
+
"description": "Adversaries may encrypt data on target systems or on large numbers of systems in a network to interrupt availability to system and network resources."
|
|
983
1206
|
},
|
|
984
1207
|
"T1505": {
|
|
985
1208
|
"name": "Server Software Component",
|
|
@@ -995,7 +1218,11 @@
|
|
|
995
1218
|
"reference_url": "https://attack.mitre.org/techniques/T1505",
|
|
996
1219
|
"stix_id": "attack-pattern--d456de47-a16f-4e46-8980-e67478a12dcb",
|
|
997
1220
|
"is_subtechnique": false,
|
|
998
|
-
"last_verified": "2026-05-19"
|
|
1221
|
+
"last_verified": "2026-05-19",
|
|
1222
|
+
"description": "Adversaries may abuse legitimate extensible development features of servers to establish persistent access to systems.",
|
|
1223
|
+
"tactic": [
|
|
1224
|
+
"Persistence"
|
|
1225
|
+
]
|
|
999
1226
|
},
|
|
1000
1227
|
"T1518": {
|
|
1001
1228
|
"name": "Software Discovery",
|
|
@@ -1011,7 +1238,11 @@
|
|
|
1011
1238
|
"reference_url": "https://attack.mitre.org/techniques/T1518",
|
|
1012
1239
|
"stix_id": "attack-pattern--e3b6daca-e963-4a69-aee6-ed4fd653ad58",
|
|
1013
1240
|
"is_subtechnique": false,
|
|
1014
|
-
"last_verified": "2026-05-19"
|
|
1241
|
+
"last_verified": "2026-05-19",
|
|
1242
|
+
"description": "Adversaries may attempt to get a listing of software and software versions that are installed on a system or in a cloud environment.",
|
|
1243
|
+
"tactic": [
|
|
1244
|
+
"Discovery"
|
|
1245
|
+
]
|
|
1015
1246
|
},
|
|
1016
1247
|
"T1525": {
|
|
1017
1248
|
"name": "Implant Internal Image",
|
|
@@ -1027,7 +1258,11 @@
|
|
|
1027
1258
|
"reference_url": "https://attack.mitre.org/techniques/T1525",
|
|
1028
1259
|
"stix_id": "attack-pattern--4fd8a28b-4b3a-4cd6-a8cf-85ba5f824a7f",
|
|
1029
1260
|
"is_subtechnique": false,
|
|
1030
|
-
"last_verified": "2026-05-19"
|
|
1261
|
+
"last_verified": "2026-05-19",
|
|
1262
|
+
"description": "Adversaries may implant cloud or container images with malicious code to establish persistence after gaining access to an environment.",
|
|
1263
|
+
"tactic": [
|
|
1264
|
+
"Persistence"
|
|
1265
|
+
]
|
|
1031
1266
|
},
|
|
1032
1267
|
"T1528": {
|
|
1033
1268
|
"name": "Steal Application Access Token",
|
|
@@ -1043,7 +1278,11 @@
|
|
|
1043
1278
|
"reference_url": "https://attack.mitre.org/techniques/T1528",
|
|
1044
1279
|
"stix_id": "attack-pattern--890c9858-598c-401d-a4d5-c67ebcdd703a",
|
|
1045
1280
|
"is_subtechnique": false,
|
|
1046
|
-
"last_verified": "2026-05-19"
|
|
1281
|
+
"last_verified": "2026-05-19",
|
|
1282
|
+
"description": "Adversaries can steal application access tokens as a means of acquiring credentials to access remote systems and resources.",
|
|
1283
|
+
"tactic": [
|
|
1284
|
+
"Credential Access"
|
|
1285
|
+
]
|
|
1047
1286
|
},
|
|
1048
1287
|
"T1530": {
|
|
1049
1288
|
"name": "Data from Cloud Storage",
|
|
@@ -1057,7 +1296,11 @@
|
|
|
1057
1296
|
"reference_url": "https://attack.mitre.org/techniques/T1530",
|
|
1058
1297
|
"stix_id": "attack-pattern--3298ce88-1628-43b1-87d9-0b5336b193d7",
|
|
1059
1298
|
"is_subtechnique": false,
|
|
1060
|
-
"last_verified": "2026-05-19"
|
|
1299
|
+
"last_verified": "2026-05-19",
|
|
1300
|
+
"description": "Adversaries may access data from cloud storage.",
|
|
1301
|
+
"tactic": [
|
|
1302
|
+
"Collection"
|
|
1303
|
+
]
|
|
1061
1304
|
},
|
|
1062
1305
|
"T1543": {
|
|
1063
1306
|
"name": "Create or Modify System Process",
|
|
@@ -1072,7 +1315,12 @@
|
|
|
1072
1315
|
"reference_url": "https://attack.mitre.org/techniques/T1543",
|
|
1073
1316
|
"stix_id": "attack-pattern--106c0cf6-bf73-4601-9aa8-0945c2715ec5",
|
|
1074
1317
|
"is_subtechnique": false,
|
|
1075
|
-
"last_verified": "2026-05-19"
|
|
1318
|
+
"last_verified": "2026-05-19",
|
|
1319
|
+
"description": "Adversaries may create or modify system-level processes to repeatedly execute malicious payloads as part of persistence.",
|
|
1320
|
+
"tactic": [
|
|
1321
|
+
"Persistence",
|
|
1322
|
+
"Privilege Escalation"
|
|
1323
|
+
]
|
|
1076
1324
|
},
|
|
1077
1325
|
"T1546": {
|
|
1078
1326
|
"name": "Event Triggered Execution",
|
|
@@ -1089,7 +1337,12 @@
|
|
|
1089
1337
|
"reference_url": "https://attack.mitre.org/techniques/T1546",
|
|
1090
1338
|
"stix_id": "attack-pattern--b6301b64-ef57-4cce-bb0b-77026f14a8db",
|
|
1091
1339
|
"is_subtechnique": false,
|
|
1092
|
-
"last_verified": "2026-05-19"
|
|
1340
|
+
"last_verified": "2026-05-19",
|
|
1341
|
+
"description": "Adversaries may establish persistence and/or elevate privileges using system mechanisms that trigger execution based on specific events.",
|
|
1342
|
+
"tactic": [
|
|
1343
|
+
"Privilege Escalation",
|
|
1344
|
+
"Persistence"
|
|
1345
|
+
]
|
|
1093
1346
|
},
|
|
1094
1347
|
"T1547": {
|
|
1095
1348
|
"name": "Boot or Logon Autostart Execution",
|
|
@@ -1104,7 +1357,12 @@
|
|
|
1104
1357
|
"reference_url": "https://attack.mitre.org/techniques/T1547",
|
|
1105
1358
|
"stix_id": "attack-pattern--1ecb2399-e8ba-4f6b-8ba7-5c27d49405cf",
|
|
1106
1359
|
"is_subtechnique": false,
|
|
1107
|
-
"last_verified": "2026-05-19"
|
|
1360
|
+
"last_verified": "2026-05-19",
|
|
1361
|
+
"description": "Adversaries may configure system settings to automatically execute a program during system boot or logon to maintain persistence or gain higher-level privileges on compromised systems.",
|
|
1362
|
+
"tactic": [
|
|
1363
|
+
"Persistence",
|
|
1364
|
+
"Privilege Escalation"
|
|
1365
|
+
]
|
|
1108
1366
|
},
|
|
1109
1367
|
"T1548.001": {
|
|
1110
1368
|
"name": "Abuse Elevation Control Mechanism: Setuid and Setgid",
|
|
@@ -1122,7 +1380,11 @@
|
|
|
1122
1380
|
"reference_url": "https://attack.mitre.org/techniques/T1548/001",
|
|
1123
1381
|
"stix_id": "attack-pattern--6831414d-bb70-42b7-8030-d4e06b2660c9",
|
|
1124
1382
|
"is_subtechnique": true,
|
|
1125
|
-
"last_verified": "2026-05-19"
|
|
1383
|
+
"last_verified": "2026-05-19",
|
|
1384
|
+
"description": "An adversary may abuse configurations where an application has the setuid or setgid bits set in order to get code running in a different (and possibly more privileged) user’s context.",
|
|
1385
|
+
"tactic": [
|
|
1386
|
+
"Privilege Escalation"
|
|
1387
|
+
]
|
|
1126
1388
|
},
|
|
1127
1389
|
"T1548.003": {
|
|
1128
1390
|
"name": "Abuse Elevation Control Mechanism: Sudo and Sudo Caching",
|
|
@@ -1135,8 +1397,12 @@
|
|
|
1135
1397
|
"reference_url": "https://attack.mitre.org/techniques/T1548/003",
|
|
1136
1398
|
"stix_id": "attack-pattern--1365fe3b-0f50-455d-b4da-266ce31c23b0",
|
|
1137
1399
|
"is_subtechnique": true,
|
|
1138
|
-
"last_verified": "2026-05-19"
|
|
1139
|
-
|
|
1400
|
+
"last_verified": "2026-05-19",
|
|
1401
|
+
"description": "Adversaries may perform sudo caching and/or use the sudoers file to elevate privileges.",
|
|
1402
|
+
"tactic": [
|
|
1403
|
+
"Privilege Escalation"
|
|
1404
|
+
]
|
|
1405
|
+
},
|
|
1140
1406
|
"T1552": {
|
|
1141
1407
|
"name": "Unsecured Credentials",
|
|
1142
1408
|
"version": "v19",
|
|
@@ -1160,7 +1426,11 @@
|
|
|
1160
1426
|
"reference_url": "https://attack.mitre.org/techniques/T1552",
|
|
1161
1427
|
"stix_id": "attack-pattern--435dfb86-2697-4867-85b5-2fef496c0517",
|
|
1162
1428
|
"is_subtechnique": false,
|
|
1163
|
-
"last_verified": "2026-05-19"
|
|
1429
|
+
"last_verified": "2026-05-19",
|
|
1430
|
+
"description": "Adversaries may search compromised systems to find and obtain insecurely stored credentials.",
|
|
1431
|
+
"tactic": [
|
|
1432
|
+
"Credential Access"
|
|
1433
|
+
]
|
|
1164
1434
|
},
|
|
1165
1435
|
"T1552.001": {
|
|
1166
1436
|
"name": "Unsecured Credentials: Credentials In Files",
|
|
@@ -1183,7 +1453,11 @@
|
|
|
1183
1453
|
"reference_url": "https://attack.mitre.org/techniques/T1552/001",
|
|
1184
1454
|
"stix_id": "attack-pattern--837f9164-50af-4ac0-8219-379d8a74cefc",
|
|
1185
1455
|
"is_subtechnique": true,
|
|
1186
|
-
"last_verified": "2026-05-19"
|
|
1456
|
+
"last_verified": "2026-05-19",
|
|
1457
|
+
"description": "Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials.",
|
|
1458
|
+
"tactic": [
|
|
1459
|
+
"Credential Access"
|
|
1460
|
+
]
|
|
1187
1461
|
},
|
|
1188
1462
|
"T1552.004": {
|
|
1189
1463
|
"name": "Unsecured Credentials: Private Keys",
|
|
@@ -1198,7 +1472,11 @@
|
|
|
1198
1472
|
"reference_url": "https://attack.mitre.org/techniques/T1552/004",
|
|
1199
1473
|
"stix_id": "attack-pattern--60b508a1-6a5e-46b1-821a-9f7b78752abf",
|
|
1200
1474
|
"is_subtechnique": true,
|
|
1201
|
-
"last_verified": "2026-05-19"
|
|
1475
|
+
"last_verified": "2026-05-19",
|
|
1476
|
+
"description": "Adversaries may search for private key certificate files on compromised systems for insecurely stored credentials.",
|
|
1477
|
+
"tactic": [
|
|
1478
|
+
"Credential Access"
|
|
1479
|
+
]
|
|
1202
1480
|
},
|
|
1203
1481
|
"T1552.005": {
|
|
1204
1482
|
"name": "Unsecured Credentials: Cloud Instance Metadata API",
|
|
@@ -1210,7 +1488,11 @@
|
|
|
1210
1488
|
"reference_url": "https://attack.mitre.org/techniques/T1552/005",
|
|
1211
1489
|
"stix_id": "attack-pattern--19bf235b-8620-4997-b5b4-94e0659ed7c3",
|
|
1212
1490
|
"is_subtechnique": true,
|
|
1213
|
-
"last_verified": "2026-05-19"
|
|
1491
|
+
"last_verified": "2026-05-19",
|
|
1492
|
+
"description": "Adversaries may attempt to access the Cloud Instance Metadata API to collect credentials and other sensitive data.",
|
|
1493
|
+
"tactic": [
|
|
1494
|
+
"Credential Access"
|
|
1495
|
+
]
|
|
1214
1496
|
},
|
|
1215
1497
|
"T1552.007": {
|
|
1216
1498
|
"name": "Unsecured Credentials: Container API",
|
|
@@ -1222,7 +1504,11 @@
|
|
|
1222
1504
|
"reference_url": "https://attack.mitre.org/techniques/T1552/007",
|
|
1223
1505
|
"stix_id": "attack-pattern--f8ef3a62-3f44-40a4-abca-761ab235c436",
|
|
1224
1506
|
"is_subtechnique": true,
|
|
1225
|
-
"last_verified": "2026-05-19"
|
|
1507
|
+
"last_verified": "2026-05-19",
|
|
1508
|
+
"description": "Adversaries may gather credentials via APIs within a containers environment.",
|
|
1509
|
+
"tactic": [
|
|
1510
|
+
"Credential Access"
|
|
1511
|
+
]
|
|
1226
1512
|
},
|
|
1227
1513
|
"T1554": {
|
|
1228
1514
|
"name": "Compromise Host Software Binary",
|
|
@@ -1241,7 +1527,11 @@
|
|
|
1241
1527
|
"reference_url": "https://attack.mitre.org/techniques/T1554",
|
|
1242
1528
|
"stix_id": "attack-pattern--960c3c86-1480-4d72-b4e0-8c242e84a5c5",
|
|
1243
1529
|
"is_subtechnique": false,
|
|
1244
|
-
"last_verified": "2026-05-19"
|
|
1530
|
+
"last_verified": "2026-05-19",
|
|
1531
|
+
"description": "Adversaries may modify host software binaries to establish persistent access to systems.",
|
|
1532
|
+
"tactic": [
|
|
1533
|
+
"Persistence"
|
|
1534
|
+
]
|
|
1245
1535
|
},
|
|
1246
1536
|
"T1555": {
|
|
1247
1537
|
"name": "Credentials from Password Stores",
|
|
@@ -1256,7 +1546,11 @@
|
|
|
1256
1546
|
"reference_url": "https://attack.mitre.org/techniques/T1555",
|
|
1257
1547
|
"stix_id": "attack-pattern--3fc9b85a-2862-4363-a64d-d692e3ffbee0",
|
|
1258
1548
|
"is_subtechnique": false,
|
|
1259
|
-
"last_verified": "2026-05-19"
|
|
1549
|
+
"last_verified": "2026-05-19",
|
|
1550
|
+
"description": "Adversaries may search for common password storage locations to obtain user credentials.(Citation: F-Secure The Dukes) Passwords are stored in several places on a system, depending on the operating system or application holding the credentials.",
|
|
1551
|
+
"tactic": [
|
|
1552
|
+
"Credential Access"
|
|
1553
|
+
]
|
|
1260
1554
|
},
|
|
1261
1555
|
"T1556": {
|
|
1262
1556
|
"name": "Modify Authentication Process",
|
|
@@ -1279,7 +1573,8 @@
|
|
|
1279
1573
|
"reference_url": "https://attack.mitre.org/techniques/T1556",
|
|
1280
1574
|
"stix_id": "attack-pattern--f4c1826f-a322-41cd-9557-562100848c84",
|
|
1281
1575
|
"is_subtechnique": false,
|
|
1282
|
-
"last_verified": "2026-05-19"
|
|
1576
|
+
"last_verified": "2026-05-19",
|
|
1577
|
+
"description": "Adversaries may modify authentication mechanisms and processes to access user credentials or enable otherwise unwarranted access to accounts."
|
|
1283
1578
|
},
|
|
1284
1579
|
"T1557": {
|
|
1285
1580
|
"name": "Adversary-in-the-Middle",
|
|
@@ -1294,7 +1589,12 @@
|
|
|
1294
1589
|
"reference_url": "https://attack.mitre.org/techniques/T1557",
|
|
1295
1590
|
"stix_id": "attack-pattern--035bb001-ab69-4a0b-9f6c-2de8b09e1b9d",
|
|
1296
1591
|
"is_subtechnique": false,
|
|
1297
|
-
"last_verified": "2026-05-19"
|
|
1592
|
+
"last_verified": "2026-05-19",
|
|
1593
|
+
"description": "Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.mitre.org/techniques/T1040), [Transmitted Data Manipulation](https://attack.mitre.org/techniques/T1565/002), or replay attacks ([Exploitation for Credential Access](https://attack.mitre.org/techniques/T1212)).",
|
|
1594
|
+
"tactic": [
|
|
1595
|
+
"Credential Access",
|
|
1596
|
+
"Collection"
|
|
1597
|
+
]
|
|
1298
1598
|
},
|
|
1299
1599
|
"T1562.001": {
|
|
1300
1600
|
"name": "Impair Defenses: Disable or Modify Tools",
|
|
@@ -1308,7 +1608,21 @@
|
|
|
1308
1608
|
],
|
|
1309
1609
|
"cve_refs": [
|
|
1310
1610
|
"BUG-2026-NIGHTMARE-ECLIPSE-UNDEFEND"
|
|
1311
|
-
]
|
|
1611
|
+
],
|
|
1612
|
+
"description": "Adversaries may modify and/or disable security tools to avoid possible detection of their malware/tools and activities.",
|
|
1613
|
+
"description_full": "Adversaries may modify and/or disable security tools to avoid possible detection of their malware/tools and activities. This may take many forms, such as killing security software processes or services, modifying / deleting Registry keys or configuration files so that tools do not operate properly, or other methods to interfere with security tools scanning or reporting information. Adversaries may also disable updates to prevent the latest security patches from reaching tools on victim systems.(Citation: SCADAfence_ransomware) Adversaries may trigger a denial-of-service attack via legitimate system processes. It has been previously observed that the Windows Time Travel Debugging (TTD) monitor driver can be used to initiate a debugging session for a security tool (e.g., an EDR) and render the tool non-functional. By hooking the debugger into the EDR process, all child processes from the EDR will be automatically suspended. The attacker can terminate any EDR helper processes (unprotected by Windows Protected Process Light) by abusing the Process Explorer driver. In combination this will halt any attempt to restart services and cause the tool to crash.(Citation: Cocomazzi FIN7 Reboot) Adversaries may also tamper with artifacts deployed and utilized by security tools. Security tools may make dynamic changes to system components in order to maintain visibility into specific events. For example, security products may load their own modules and/or modify those loaded by processes to facilitate data collection. Similar to [Indicator Blocking](https://attack.mitre.org/techniques/T1562/006), adversaries may unhook or otherwise modify these features added by tools (especially those that exist in userland or are otherwise potentially accessible to adversaries) to avoid detection.(Citation: OutFlank System Calls)(Citation: MDSec System Calls) For example, adversaries may abuse the Windows process mitigation policy to block certain endpoint detection and response (EDR) products from loading their user-mode code via DLLs. By spawning a process with the PROCESS_CREATION_MITIGATION_POLICY_BLOCK_NON_MICROSOFT_BINARIES_ALWAYS_ON attribute using API calls like UpdateProcThreadAttribute, adversaries may evade detection by endpoint security solutions that rely on DLLs that are not signed by Microsoft. Alternatively, they may add new directories to an EDR tool’s exclusion list, enabling them to hide malicious files via [File/Path Exclusions](https://attack.mitre.org/techniques/T1564/012).(Citation: BlackBerry WhisperGate 2022)(Citation: Google Cloud Threat Intelligence FIN13 2021) Adversaries may also focus on specific applications such as Sysmon. For example, the “Start” and “Enable” values in <code>HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\WMI\\Autologger\\EventLog-Microsoft-Windows-Sysmon-Operational</code> may be modified to tamper with and potentially disable Sysmon logging.(Citation: disable_win_evt_logging) On network devices, adversaries may attempt to skip digital signature verification checks by altering startup configuration files and effectively disabling firmware verification that typically occurs at boot.(Citation: Fortinet Zero-Day and Custom Malware Used by Suspected Chinese Actor in Espionage Operation)(Citation: Analysis of FG-IR-22-369) In cloud environments, tools disabled by adversaries may include cloud monitoring agents that report back to services such as AWS CloudWatch or Google Cloud Monitor. Furthermore, although defensive tools may have anti-tampering mechanisms, adversaries may abuse tools such as legitimate rootkit removal kits to impair and/or disable these tools.(Citation: chasing_avaddon_ransomware)(Citation: dharma_ransomware)(Citation: demystifying_ryuk)(Citation: doppelpaymer_crowdstrike) For example, adversaries have used tools such as GMER to find and shut down hidden processes and antivirus software on infected systems.(Citation: demystifying_ryuk) Additionally, adversaries may exploit legitimate drivers from anti-virus software to gain access to kernel space (i.e. [Exploitation for Privilege Escalation](https://attack.mitre.org/techniques/T1068)), which may lead to bypassing anti-tampering features.(Citation: avoslocker_ransomware)",
|
|
1614
|
+
"platforms": [
|
|
1615
|
+
"Containers",
|
|
1616
|
+
"IaaS",
|
|
1617
|
+
"Linux",
|
|
1618
|
+
"macOS",
|
|
1619
|
+
"Network Devices",
|
|
1620
|
+
"Windows"
|
|
1621
|
+
],
|
|
1622
|
+
"reference_url": "https://attack.mitre.org/techniques/T1562/001",
|
|
1623
|
+
"stix_id": "attack-pattern--ac08589e-ee59-4935-8667-d845e38fe579",
|
|
1624
|
+
"is_subtechnique": true,
|
|
1625
|
+
"last_verified": "2026-05-19"
|
|
1312
1626
|
},
|
|
1313
1627
|
"T1562.006": {
|
|
1314
1628
|
"name": "Impair Defenses: Indicator Blocking",
|
|
@@ -1318,7 +1632,19 @@
|
|
|
1318
1632
|
"tactic_id": "TA0112",
|
|
1319
1633
|
"detection_strategies": [
|
|
1320
1634
|
"DS0017"
|
|
1321
|
-
]
|
|
1635
|
+
],
|
|
1636
|
+
"description": "An adversary may attempt to block indicators or events typically captured by sensors from being gathered and analyzed.",
|
|
1637
|
+
"description_full": "An adversary may attempt to block indicators or events typically captured by sensors from being gathered and analyzed. This could include maliciously redirecting(Citation: Microsoft Lamin Sept 2017) or even disabling host-based sensors, such as Event Tracing for Windows (ETW)(Citation: Microsoft About Event Tracing 2018), by tampering settings that control the collection and flow of event telemetry.(Citation: Medium Event Tracing Tampering 2018) These settings may be stored on the system in configuration files and/or in the Registry as well as being accessible via administrative utilities such as [PowerShell](https://attack.mitre.org/techniques/T1059/001) or [Windows Management Instrumentation](https://attack.mitre.org/techniques/T1047). For example, adversaries may modify the `File` value in <code>HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\EventLog\\Security</code> to hide their malicious actions in a new or different .evtx log file. This action does not require a system reboot and takes effect immediately.(Citation: disable_win_evt_logging) ETW interruption can be achieved multiple ways, however most directly by defining conditions using the [PowerShell](https://attack.mitre.org/techniques/T1059/001) <code>Set-EtwTraceProvider</code> cmdlet or by interfacing directly with the Registry to make alterations. In the case of network-based reporting of indicators, an adversary may block traffic associated with reporting to prevent central analysis. This may be accomplished by many means, such as stopping a local process responsible for forwarding telemetry and/or creating a host-based firewall rule to block traffic to specific hosts responsible for aggregating events, such as security information and event management (SIEM) products. In Linux environments, adversaries may disable or reconfigure log processing tools such as syslog or nxlog to inhibit detection and monitoring capabilities to facilitate follow on behaviors. (Citation: LemonDuck) ESXi also leverages syslog, which can be reconfigured via commands such as `esxcli system syslog config set` and `esxcli system syslog config reload`.(Citation: Google Cloud Threat Intelligence ESXi VIBs 2022)(Citation: Broadcom Configuring syslog on ESXi)",
|
|
1638
|
+
"platforms": [
|
|
1639
|
+
"Windows",
|
|
1640
|
+
"macOS",
|
|
1641
|
+
"Linux",
|
|
1642
|
+
"ESXi"
|
|
1643
|
+
],
|
|
1644
|
+
"reference_url": "https://attack.mitre.org/techniques/T1562/006",
|
|
1645
|
+
"stix_id": "attack-pattern--74d2a63f-3c7b-4852-92da-02d8fbab16da",
|
|
1646
|
+
"is_subtechnique": true,
|
|
1647
|
+
"last_verified": "2026-05-19"
|
|
1322
1648
|
},
|
|
1323
1649
|
"T1565": {
|
|
1324
1650
|
"name": "Data Manipulation",
|
|
@@ -1332,7 +1658,11 @@
|
|
|
1332
1658
|
"reference_url": "https://attack.mitre.org/techniques/T1565",
|
|
1333
1659
|
"stix_id": "attack-pattern--ac9e6b22-11bf-45d7-9181-c1cb08360931",
|
|
1334
1660
|
"is_subtechnique": false,
|
|
1335
|
-
"last_verified": "2026-05-19"
|
|
1661
|
+
"last_verified": "2026-05-19",
|
|
1662
|
+
"description": "Adversaries may insert, delete, or manipulate data in order to influence external outcomes or hide activity, thus threatening the integrity of the data.(Citation: Sygnia Elephant Beetle Jan 2022) By manipulating data, adversaries may attempt to affect a business process, organizational understanding, or decision making.",
|
|
1663
|
+
"tactic": [
|
|
1664
|
+
"Impact"
|
|
1665
|
+
]
|
|
1336
1666
|
},
|
|
1337
1667
|
"T1566": {
|
|
1338
1668
|
"name": "Phishing",
|
|
@@ -1353,7 +1683,11 @@
|
|
|
1353
1683
|
"reference_url": "https://attack.mitre.org/techniques/T1566",
|
|
1354
1684
|
"stix_id": "attack-pattern--a62a8db3-f23a-4d8f-afd6-9dbc77e7813b",
|
|
1355
1685
|
"is_subtechnique": false,
|
|
1356
|
-
"last_verified": "2026-05-19"
|
|
1686
|
+
"last_verified": "2026-05-19",
|
|
1687
|
+
"description": "Adversaries may send phishing messages to gain access to victim systems.",
|
|
1688
|
+
"tactic": [
|
|
1689
|
+
"Initial Access"
|
|
1690
|
+
]
|
|
1357
1691
|
},
|
|
1358
1692
|
"T1566.001": {
|
|
1359
1693
|
"name": "Phishing: Spearphishing Attachment",
|
|
@@ -1367,7 +1701,11 @@
|
|
|
1367
1701
|
"reference_url": "https://attack.mitre.org/techniques/T1566/001",
|
|
1368
1702
|
"stix_id": "attack-pattern--2e34237d-8574-43f6-aace-ae2915de8597",
|
|
1369
1703
|
"is_subtechnique": true,
|
|
1370
|
-
"last_verified": "2026-05-19"
|
|
1704
|
+
"last_verified": "2026-05-19",
|
|
1705
|
+
"description": "Adversaries may send spearphishing emails with a malicious attachment in an attempt to gain access to victim systems.",
|
|
1706
|
+
"tactic": [
|
|
1707
|
+
"Initial Access"
|
|
1708
|
+
]
|
|
1371
1709
|
},
|
|
1372
1710
|
"T1566.002": {
|
|
1373
1711
|
"name": "Phishing: Spearphishing Link",
|
|
@@ -1384,7 +1722,11 @@
|
|
|
1384
1722
|
"reference_url": "https://attack.mitre.org/techniques/T1566/002",
|
|
1385
1723
|
"stix_id": "attack-pattern--2b742742-28c3-4e1b-bab7-8350d6300fa7",
|
|
1386
1724
|
"is_subtechnique": true,
|
|
1387
|
-
"last_verified": "2026-05-19"
|
|
1725
|
+
"last_verified": "2026-05-19",
|
|
1726
|
+
"description": "Adversaries may send spearphishing emails with a malicious link in an attempt to gain access to victim systems.",
|
|
1727
|
+
"tactic": [
|
|
1728
|
+
"Initial Access"
|
|
1729
|
+
]
|
|
1388
1730
|
},
|
|
1389
1731
|
"T1566.003": {
|
|
1390
1732
|
"name": "Phishing: Spearphishing via Service",
|
|
@@ -1398,7 +1740,11 @@
|
|
|
1398
1740
|
"reference_url": "https://attack.mitre.org/techniques/T1566/003",
|
|
1399
1741
|
"stix_id": "attack-pattern--f6ad61ee-65f3-4bd0-a3f5-2f0accb36317",
|
|
1400
1742
|
"is_subtechnique": true,
|
|
1401
|
-
"last_verified": "2026-05-19"
|
|
1743
|
+
"last_verified": "2026-05-19",
|
|
1744
|
+
"description": "Adversaries may send spearphishing messages via third-party services in an attempt to gain access to victim systems.",
|
|
1745
|
+
"tactic": [
|
|
1746
|
+
"Initial Access"
|
|
1747
|
+
]
|
|
1402
1748
|
},
|
|
1403
1749
|
"T1567": {
|
|
1404
1750
|
"name": "Exfiltration Over Web Service",
|
|
@@ -1418,7 +1764,11 @@
|
|
|
1418
1764
|
"reference_url": "https://attack.mitre.org/techniques/T1567",
|
|
1419
1765
|
"stix_id": "attack-pattern--40597f16-0963-4249-bf4c-ac93b7fb9807",
|
|
1420
1766
|
"is_subtechnique": false,
|
|
1421
|
-
"last_verified": "2026-05-19"
|
|
1767
|
+
"last_verified": "2026-05-19",
|
|
1768
|
+
"description": "Adversaries may use an existing, legitimate external Web service to exfiltrate data rather than their primary command and control channel.",
|
|
1769
|
+
"tactic": [
|
|
1770
|
+
"Exfiltration"
|
|
1771
|
+
]
|
|
1422
1772
|
},
|
|
1423
1773
|
"T1568": {
|
|
1424
1774
|
"name": "Dynamic Resolution",
|
|
@@ -1433,7 +1783,11 @@
|
|
|
1433
1783
|
"reference_url": "https://attack.mitre.org/techniques/T1568",
|
|
1434
1784
|
"stix_id": "attack-pattern--7bd9c723-2f78-4309-82c5-47cad406572b",
|
|
1435
1785
|
"is_subtechnique": false,
|
|
1436
|
-
"last_verified": "2026-05-19"
|
|
1786
|
+
"last_verified": "2026-05-19",
|
|
1787
|
+
"description": "Adversaries may dynamically establish connections to command and control infrastructure to evade common detections and remediations.",
|
|
1788
|
+
"tactic": [
|
|
1789
|
+
"Command and Control"
|
|
1790
|
+
]
|
|
1437
1791
|
},
|
|
1438
1792
|
"T1570": {
|
|
1439
1793
|
"name": "Lateral Tool Transfer",
|
|
@@ -1449,7 +1803,11 @@
|
|
|
1449
1803
|
"reference_url": "https://attack.mitre.org/techniques/T1570",
|
|
1450
1804
|
"stix_id": "attack-pattern--bf90d72c-c00b-45e3-b3aa-68560560d4c5",
|
|
1451
1805
|
"is_subtechnique": false,
|
|
1452
|
-
"last_verified": "2026-05-19"
|
|
1806
|
+
"last_verified": "2026-05-19",
|
|
1807
|
+
"description": "Adversaries may transfer tools or other files between systems in a compromised environment.",
|
|
1808
|
+
"tactic": [
|
|
1809
|
+
"Lateral Movement"
|
|
1810
|
+
]
|
|
1453
1811
|
},
|
|
1454
1812
|
"T1573": {
|
|
1455
1813
|
"name": "Encrypted Channel",
|
|
@@ -1465,7 +1823,11 @@
|
|
|
1465
1823
|
"reference_url": "https://attack.mitre.org/techniques/T1573",
|
|
1466
1824
|
"stix_id": "attack-pattern--b8902400-e6c5-4ba2-95aa-2d35b442b118",
|
|
1467
1825
|
"is_subtechnique": false,
|
|
1468
|
-
"last_verified": "2026-05-19"
|
|
1826
|
+
"last_verified": "2026-05-19",
|
|
1827
|
+
"description": "Adversaries may employ an encryption algorithm to conceal command and control traffic rather than relying on any inherent protections provided by a communication protocol.",
|
|
1828
|
+
"tactic": [
|
|
1829
|
+
"Command and Control"
|
|
1830
|
+
]
|
|
1469
1831
|
},
|
|
1470
1832
|
"T1574": {
|
|
1471
1833
|
"name": "Hijack Execution Flow",
|
|
@@ -1482,7 +1844,12 @@
|
|
|
1482
1844
|
"reference_url": "https://attack.mitre.org/techniques/T1574",
|
|
1483
1845
|
"stix_id": "attack-pattern--aedfca76-3b30-4866-b2aa-0f1d7fd1e4b6",
|
|
1484
1846
|
"is_subtechnique": false,
|
|
1485
|
-
"last_verified": "2026-05-19"
|
|
1847
|
+
"last_verified": "2026-05-19",
|
|
1848
|
+
"description": "Adversaries may execute their own malicious payloads by hijacking the way operating systems run programs.",
|
|
1849
|
+
"tactic": [
|
|
1850
|
+
"Stealth",
|
|
1851
|
+
"Execution"
|
|
1852
|
+
]
|
|
1486
1853
|
},
|
|
1487
1854
|
"T1574.005": {
|
|
1488
1855
|
"name": "Hijack Execution Flow: Executable Installer File Permissions Weakness",
|
|
@@ -1494,7 +1861,12 @@
|
|
|
1494
1861
|
"reference_url": "https://attack.mitre.org/techniques/T1574/005",
|
|
1495
1862
|
"stix_id": "attack-pattern--70d81154-b187-45f9-8ec5-295d01255979",
|
|
1496
1863
|
"is_subtechnique": true,
|
|
1497
|
-
"last_verified": "2026-05-19"
|
|
1864
|
+
"last_verified": "2026-05-19",
|
|
1865
|
+
"description": "Adversaries may execute their own malicious payloads by hijacking the binaries used by an installer.",
|
|
1866
|
+
"tactic": [
|
|
1867
|
+
"Stealth",
|
|
1868
|
+
"Execution"
|
|
1869
|
+
]
|
|
1498
1870
|
},
|
|
1499
1871
|
"T1595": {
|
|
1500
1872
|
"name": "Active Scanning",
|
|
@@ -1506,7 +1878,11 @@
|
|
|
1506
1878
|
"reference_url": "https://attack.mitre.org/techniques/T1595",
|
|
1507
1879
|
"stix_id": "attack-pattern--67073dde-d720-45ae-83da-b12d5e73ca3b",
|
|
1508
1880
|
"is_subtechnique": false,
|
|
1509
|
-
"last_verified": "2026-05-19"
|
|
1881
|
+
"last_verified": "2026-05-19",
|
|
1882
|
+
"description": "Adversaries may execute active reconnaissance scans to gather information that can be used during targeting.",
|
|
1883
|
+
"tactic": [
|
|
1884
|
+
"Reconnaissance"
|
|
1885
|
+
]
|
|
1510
1886
|
},
|
|
1511
1887
|
"T1600": {
|
|
1512
1888
|
"name": "Weaken Encryption",
|
|
@@ -1521,7 +1897,11 @@
|
|
|
1521
1897
|
"reference_url": "https://attack.mitre.org/techniques/T1600",
|
|
1522
1898
|
"stix_id": "attack-pattern--1f9012ef-1e10-4e48-915e-e03563435fe8",
|
|
1523
1899
|
"is_subtechnique": false,
|
|
1524
|
-
"last_verified": "2026-05-19"
|
|
1900
|
+
"last_verified": "2026-05-19",
|
|
1901
|
+
"description": "Adversaries may compromise a network device’s encryption capability in order to bypass encryption that would otherwise protect data communications.(Citation: Cisco Synful Knock Evolution) Encryption can be used to protect transmitted network traffic to maintain its confidentiality (protect against unauthorized disclosure) and integrity (protect against unauthorized changes).",
|
|
1902
|
+
"tactic": [
|
|
1903
|
+
"Defense Impairment"
|
|
1904
|
+
]
|
|
1525
1905
|
},
|
|
1526
1906
|
"T1606.001": {
|
|
1527
1907
|
"name": "Forge Web Credentials: Web Cookies",
|
|
@@ -1537,7 +1917,11 @@
|
|
|
1537
1917
|
"reference_url": "https://attack.mitre.org/techniques/T1606/001",
|
|
1538
1918
|
"stix_id": "attack-pattern--861b8fd2-57f3-4ee1-ab5d-c19c3b8c7a4a",
|
|
1539
1919
|
"is_subtechnique": true,
|
|
1540
|
-
"last_verified": "2026-05-19"
|
|
1920
|
+
"last_verified": "2026-05-19",
|
|
1921
|
+
"description": "Adversaries may forge web cookies that can be used to gain access to web applications or Internet services.",
|
|
1922
|
+
"tactic": [
|
|
1923
|
+
"Credential Access"
|
|
1924
|
+
]
|
|
1541
1925
|
},
|
|
1542
1926
|
"T1606.002": {
|
|
1543
1927
|
"name": "Forge Web Credentials: SAML Tokens",
|
|
@@ -1558,7 +1942,8 @@
|
|
|
1558
1942
|
"reference_url": "https://attack.mitre.org/techniques/T1606/002",
|
|
1559
1943
|
"stix_id": "attack-pattern--1f9c2bae-b441-4f66-a8af-b65946ee72f2",
|
|
1560
1944
|
"is_subtechnique": true,
|
|
1561
|
-
"last_verified": "2026-05-19"
|
|
1945
|
+
"last_verified": "2026-05-19",
|
|
1946
|
+
"description": "An adversary may forge SAML tokens with any permissions claims and lifetimes if they possess a valid SAML token-signing certificate.(Citation: Microsoft SolarWinds Steps) The default lifetime of a SAML token is one hour, but the validity period can be specified in the <code>NotOnOrAfter</code> value of the <code>conditions ...</code> element in a token."
|
|
1562
1947
|
},
|
|
1563
1948
|
"T1610": {
|
|
1564
1949
|
"name": "Deploy Container",
|
|
@@ -1570,7 +1955,11 @@
|
|
|
1570
1955
|
"reference_url": "https://attack.mitre.org/techniques/T1610",
|
|
1571
1956
|
"stix_id": "attack-pattern--56e0d8b8-3e25-49dd-9050-3aa252f5aa92",
|
|
1572
1957
|
"is_subtechnique": false,
|
|
1573
|
-
"last_verified": "2026-05-19"
|
|
1958
|
+
"last_verified": "2026-05-19",
|
|
1959
|
+
"description": "Adversaries may deploy a container into an environment to facilitate execution or evade defenses.",
|
|
1960
|
+
"tactic": [
|
|
1961
|
+
"Execution"
|
|
1962
|
+
]
|
|
1574
1963
|
},
|
|
1575
1964
|
"T1611": {
|
|
1576
1965
|
"name": "Escape to Host",
|
|
@@ -1598,7 +1987,8 @@
|
|
|
1598
1987
|
"reference_url": "https://attack.mitre.org/techniques/T1611",
|
|
1599
1988
|
"stix_id": "attack-pattern--4a5b7ade-8bb5-4853-84ed-23f262002665",
|
|
1600
1989
|
"is_subtechnique": false,
|
|
1601
|
-
"last_verified": "2026-05-19"
|
|
1990
|
+
"last_verified": "2026-05-19",
|
|
1991
|
+
"description": "Adversaries may break out of a container or virtualized environment to gain access to the underlying host."
|
|
1602
1992
|
},
|
|
1603
1993
|
"T1613": {
|
|
1604
1994
|
"name": "Container and Resource Discovery",
|
|
@@ -1610,7 +2000,11 @@
|
|
|
1610
2000
|
"reference_url": "https://attack.mitre.org/techniques/T1613",
|
|
1611
2001
|
"stix_id": "attack-pattern--0470e792-32f8-46b0-a351-652bc35e9336",
|
|
1612
2002
|
"is_subtechnique": false,
|
|
1613
|
-
"last_verified": "2026-05-19"
|
|
2003
|
+
"last_verified": "2026-05-19",
|
|
2004
|
+
"description": "Adversaries may attempt to discover containers and other resources that are available within a containers environment.",
|
|
2005
|
+
"tactic": [
|
|
2006
|
+
"Discovery"
|
|
2007
|
+
]
|
|
1614
2008
|
},
|
|
1615
2009
|
"T1480.002": {
|
|
1616
2010
|
"name": "Execution Guardrails: Mutual Exclusion",
|
|
@@ -1630,7 +2024,8 @@
|
|
|
1630
2024
|
"reference_url": "https://attack.mitre.org/techniques/T1480/002",
|
|
1631
2025
|
"stix_id": "attack-pattern--49fca0d2-685d-41eb-8bd4-05451cc3a742",
|
|
1632
2026
|
"is_subtechnique": true,
|
|
1633
|
-
"last_verified": "2026-05-19"
|
|
2027
|
+
"last_verified": "2026-05-19",
|
|
2028
|
+
"description": "Adversaries may constrain execution or actions based on the presence of a mutex associated with malware."
|
|
1634
2029
|
},
|
|
1635
2030
|
"T1480.003": {
|
|
1636
2031
|
"name": "Execution Guardrails: Mutex Lock",
|
|
@@ -1640,7 +2035,15 @@
|
|
|
1640
2035
|
"added_in": "v19",
|
|
1641
2036
|
"detection_strategies": [
|
|
1642
2037
|
"DS0009"
|
|
1643
|
-
]
|
|
2038
|
+
],
|
|
2039
|
+
"_gap_skip": {
|
|
2040
|
+
"fields": [
|
|
2041
|
+
"platforms",
|
|
2042
|
+
"description"
|
|
2043
|
+
],
|
|
2044
|
+
"reason": "Operator-added technique ID not yet present in published MITRE ATT&CK STIX bundle. Refresher cannot backfill; this is a forward-looking placeholder."
|
|
2045
|
+
},
|
|
2046
|
+
"description": "Operator-added technique ID not yet present in published MITRE ATT&CK STIX bundle; tracked here as a forward-looking placeholder. Refine when MITRE publishes."
|
|
1644
2047
|
},
|
|
1645
2048
|
"T1059.013": {
|
|
1646
2049
|
"name": "Command and Scripting Interpreter: Cloud API",
|
|
@@ -1658,7 +2061,8 @@
|
|
|
1658
2061
|
"reference_url": "https://attack.mitre.org/techniques/T1059/013",
|
|
1659
2062
|
"stix_id": "attack-pattern--c283d88f-8c23-4318-9da5-3d50cecad756",
|
|
1660
2063
|
"is_subtechnique": true,
|
|
1661
|
-
"last_verified": "2026-05-19"
|
|
2064
|
+
"last_verified": "2026-05-19",
|
|
2065
|
+
"description": "Adversaries may abuse built-in CLI tools or API calls to execute malicious commands in containerized environments."
|
|
1662
2066
|
},
|
|
1663
2067
|
"T1556.007": {
|
|
1664
2068
|
"name": "Modify Authentication Process: Hybrid Identity",
|
|
@@ -1680,7 +2084,8 @@
|
|
|
1680
2084
|
"reference_url": "https://attack.mitre.org/techniques/T1556/007",
|
|
1681
2085
|
"stix_id": "attack-pattern--54ca26f3-c172-4231-93e5-ccebcac2161f",
|
|
1682
2086
|
"is_subtechnique": true,
|
|
1683
|
-
"last_verified": "2026-05-19"
|
|
2087
|
+
"last_verified": "2026-05-19",
|
|
2088
|
+
"description": "Adversaries may patch, modify, or otherwise backdoor cloud authentication processes that are tied to on-premises user identities in order to bypass typical authentication mechanisms, access credentials, and enable persistent access to accounts."
|
|
1684
2089
|
},
|
|
1685
2090
|
"T1486.004": {
|
|
1686
2091
|
"name": "Data Encrypted for Impact: Data Theft Before Encryption",
|
|
@@ -1691,7 +2096,15 @@
|
|
|
1691
2096
|
"DS0007",
|
|
1692
2097
|
"DS0011",
|
|
1693
2098
|
"DS0029"
|
|
1694
|
-
]
|
|
2099
|
+
],
|
|
2100
|
+
"_gap_skip": {
|
|
2101
|
+
"fields": [
|
|
2102
|
+
"platforms",
|
|
2103
|
+
"description"
|
|
2104
|
+
],
|
|
2105
|
+
"reason": "Operator-added technique ID not yet present in published MITRE ATT&CK STIX bundle. Refresher cannot backfill; this is a forward-looking placeholder."
|
|
2106
|
+
},
|
|
2107
|
+
"description": "Operator-added technique ID not yet present in published MITRE ATT&CK STIX bundle; tracked here as a forward-looking placeholder. Refine when MITRE publishes."
|
|
1695
2108
|
},
|
|
1696
2109
|
"T1682": {
|
|
1697
2110
|
"name": "Query Public AI Services",
|
|
@@ -1708,7 +2121,8 @@
|
|
|
1708
2121
|
"reference_url": "https://attack.mitre.org/techniques/T1682",
|
|
1709
2122
|
"stix_id": "attack-pattern--143122a8-fcda-4dd7-aded-5b9387d9c2d6",
|
|
1710
2123
|
"is_subtechnique": false,
|
|
1711
|
-
"last_verified": "2026-05-19"
|
|
2124
|
+
"last_verified": "2026-05-19",
|
|
2125
|
+
"description": "Adversaries may query publicly accessible artificial intelligence (AI) services, such as large language models (LLMs), to support targeting and operations."
|
|
1712
2126
|
},
|
|
1713
2127
|
"T1683": {
|
|
1714
2128
|
"name": "Generate Content",
|
|
@@ -1725,7 +2139,8 @@
|
|
|
1725
2139
|
"reference_url": "https://attack.mitre.org/techniques/T1683",
|
|
1726
2140
|
"stix_id": "attack-pattern--b512fb8a-18dd-4bfc-bbad-acbaaeb7dde3",
|
|
1727
2141
|
"is_subtechnique": false,
|
|
1728
|
-
"last_verified": "2026-05-19"
|
|
2142
|
+
"last_verified": "2026-05-19",
|
|
2143
|
+
"description": "Adversaries may create or generate content to support targeting and operations."
|
|
1729
2144
|
},
|
|
1730
2145
|
"T1685": {
|
|
1731
2146
|
"name": "Disable or Modify Tools",
|
|
@@ -1750,7 +2165,8 @@
|
|
|
1750
2165
|
"reference_url": "https://attack.mitre.org/techniques/T1685",
|
|
1751
2166
|
"stix_id": "attack-pattern--bbde9781-60aa-4b8a-a911-895b0c1b3872",
|
|
1752
2167
|
"is_subtechnique": false,
|
|
1753
|
-
"last_verified": "2026-05-19"
|
|
2168
|
+
"last_verified": "2026-05-19",
|
|
2169
|
+
"description": "Adversaries may disable, degrade, or tamper with security tools or applications (e.g., endpoint detection and response (EDR) tools, intrusion detection systems (IDS), antivirus, logging agents, sensors, etc.) to impair or reduce visibility of defensive capabilities."
|
|
1754
2170
|
},
|
|
1755
2171
|
"T1686": {
|
|
1756
2172
|
"name": "Disable or Modify System Firewall",
|
|
@@ -1772,7 +2188,8 @@
|
|
|
1772
2188
|
"reference_url": "https://attack.mitre.org/techniques/T1686",
|
|
1773
2189
|
"stix_id": "attack-pattern--eec096b8-c207-43df-b6c1-11523861e452",
|
|
1774
2190
|
"is_subtechnique": false,
|
|
1775
|
-
"last_verified": "2026-05-19"
|
|
2191
|
+
"last_verified": "2026-05-19",
|
|
2192
|
+
"description": "Adversaries may disable or modify host-based or network firewalls to impair defensive mechanisms and enable further action."
|
|
1776
2193
|
},
|
|
1777
2194
|
"T1687": {
|
|
1778
2195
|
"name": "Exploitation for Defense Impairment",
|
|
@@ -1794,7 +2211,8 @@
|
|
|
1794
2211
|
"reference_url": "https://attack.mitre.org/techniques/T1687",
|
|
1795
2212
|
"stix_id": "attack-pattern--01c9b54f-c04e-41ba-b0c3-cfe784b3a463",
|
|
1796
2213
|
"is_subtechnique": false,
|
|
1797
|
-
"last_verified": "2026-05-19"
|
|
2214
|
+
"last_verified": "2026-05-19",
|
|
2215
|
+
"description": "Adversaries may exploit vulnerabilities in security software, infrastructure, or defensive components to degrade, disable, or otherwise continue to impair their ability to prevent, detect, or respond to malicious activity."
|
|
1798
2216
|
},
|
|
1799
2217
|
"T1689": {
|
|
1800
2218
|
"name": "Downgrade Attack",
|
|
@@ -1814,7 +2232,8 @@
|
|
|
1814
2232
|
"reference_url": "https://attack.mitre.org/techniques/T1689",
|
|
1815
2233
|
"stix_id": "attack-pattern--30904c16-39f9-41c6-b01a-500eb8878442",
|
|
1816
2234
|
"is_subtechnique": false,
|
|
1817
|
-
"last_verified": "2026-05-19"
|
|
2235
|
+
"last_verified": "2026-05-19",
|
|
2236
|
+
"description": "Adversaries may downgrade or use a version of system features that may be outdated, vulnerable, and/or does not support updated security controls."
|
|
1818
2237
|
},
|
|
1819
2238
|
"T1690": {
|
|
1820
2239
|
"name": "Prevent Command History Logging",
|
|
@@ -1836,7 +2255,8 @@
|
|
|
1836
2255
|
"reference_url": "https://attack.mitre.org/techniques/T1690",
|
|
1837
2256
|
"stix_id": "attack-pattern--b831f51c-d22f-4724-bbab-60d056bd1150",
|
|
1838
2257
|
"is_subtechnique": false,
|
|
1839
|
-
"last_verified": "2026-05-19"
|
|
2258
|
+
"last_verified": "2026-05-19",
|
|
2259
|
+
"description": "Adversaries may impair command history logging to hide commands they run on a compromised system."
|
|
1840
2260
|
},
|
|
1841
2261
|
"T1580": {
|
|
1842
2262
|
"name": "Cloud Infrastructure Discovery",
|
|
@@ -1848,7 +2268,11 @@
|
|
|
1848
2268
|
"reference_url": "https://attack.mitre.org/techniques/T1580",
|
|
1849
2269
|
"stix_id": "attack-pattern--57a3d31a-d04f-4663-b2da-7df8ec3f8c9d",
|
|
1850
2270
|
"is_subtechnique": false,
|
|
1851
|
-
"last_verified": "2026-05-19"
|
|
2271
|
+
"last_verified": "2026-05-19",
|
|
2272
|
+
"description": "An adversary may attempt to discover infrastructure and resources that are available within an infrastructure-as-a-service (IaaS) environment.",
|
|
2273
|
+
"tactic": [
|
|
2274
|
+
"Discovery"
|
|
2275
|
+
]
|
|
1852
2276
|
},
|
|
1853
2277
|
"T1538": {
|
|
1854
2278
|
"name": "Cloud Service Dashboard",
|
|
@@ -1863,11 +2287,30 @@
|
|
|
1863
2287
|
"reference_url": "https://attack.mitre.org/techniques/T1538",
|
|
1864
2288
|
"stix_id": "attack-pattern--e49920b0-6c54-40c1-9571-73723653205f",
|
|
1865
2289
|
"is_subtechnique": false,
|
|
1866
|
-
"last_verified": "2026-05-19"
|
|
2290
|
+
"last_verified": "2026-05-19",
|
|
2291
|
+
"description": "An adversary may use a cloud service dashboard GUI with stolen credentials to gain useful information from an operational cloud environment, such as specific services, resources, and features.",
|
|
2292
|
+
"tactic": [
|
|
2293
|
+
"Discovery"
|
|
2294
|
+
]
|
|
1867
2295
|
},
|
|
1868
2296
|
"T1562.008": {
|
|
1869
2297
|
"name": "Impair Defenses: Disable or Modify Cloud Logs",
|
|
1870
|
-
"version": "v19"
|
|
2298
|
+
"version": "v19",
|
|
2299
|
+
"description": "An adversary may disable or modify cloud logging capabilities and integrations to limit what data is collected on their activities and avoid detection.",
|
|
2300
|
+
"tactic": [
|
|
2301
|
+
"Stealth"
|
|
2302
|
+
],
|
|
2303
|
+
"description_full": "An adversary may disable or modify cloud logging capabilities and integrations to limit what data is collected on their activities and avoid detection. Cloud environments allow for collection and analysis of audit and application logs that provide insight into what activities a user does within the environment. If an adversary has sufficient permissions, they can disable or modify logging to avoid detection of their activities. For example, in AWS an adversary may disable CloudWatch/CloudTrail integrations prior to conducting further malicious activity.(Citation: Following the CloudTrail: Generating strong AWS security signals with Sumo Logic) They may alternatively tamper with logging functionality – for example, by removing any associated SNS topics, disabling multi-region logging, or disabling settings that validate and/or encrypt log files.(Citation: AWS Update Trail)(Citation: Pacu Detection Disruption Module) In Office 365, an adversary may disable logging on mail collection activities for specific users by using the `Set-MailboxAuditBypassAssociation` cmdlet, by disabling M365 Advanced Auditing for the user, or by downgrading the user’s license from an Enterprise E5 to an Enterprise E3 license.(Citation: Dark Reading Microsoft 365 Attacks 2021)",
|
|
2304
|
+
"platforms": [
|
|
2305
|
+
"IaaS",
|
|
2306
|
+
"SaaS",
|
|
2307
|
+
"Office Suite",
|
|
2308
|
+
"Identity Provider"
|
|
2309
|
+
],
|
|
2310
|
+
"reference_url": "https://attack.mitre.org/techniques/T1562/008",
|
|
2311
|
+
"stix_id": "attack-pattern--cacc40da-4c9e-462c-80d5-fd70a178b12d",
|
|
2312
|
+
"is_subtechnique": true,
|
|
2313
|
+
"last_verified": "2026-05-19"
|
|
1871
2314
|
},
|
|
1872
2315
|
"T1136.003": {
|
|
1873
2316
|
"name": "Create Account: Cloud Account",
|
|
@@ -1882,7 +2325,11 @@
|
|
|
1882
2325
|
"reference_url": "https://attack.mitre.org/techniques/T1136/003",
|
|
1883
2326
|
"stix_id": "attack-pattern--a009cb25-4801-4116-9105-80a91cf15c1b",
|
|
1884
2327
|
"is_subtechnique": true,
|
|
1885
|
-
"last_verified": "2026-05-19"
|
|
2328
|
+
"last_verified": "2026-05-19",
|
|
2329
|
+
"description": "Adversaries may create a cloud account to maintain access to victim systems.",
|
|
2330
|
+
"tactic": [
|
|
2331
|
+
"Persistence"
|
|
2332
|
+
]
|
|
1886
2333
|
},
|
|
1887
2334
|
"T1098.003": {
|
|
1888
2335
|
"name": "Account Manipulation: Additional Cloud Roles",
|
|
@@ -1900,7 +2347,12 @@
|
|
|
1900
2347
|
"reference_url": "https://attack.mitre.org/techniques/T1098/003",
|
|
1901
2348
|
"stix_id": "attack-pattern--2dbbdcd5-92cf-44c0-aea2-fe24783a6bc3",
|
|
1902
2349
|
"is_subtechnique": true,
|
|
1903
|
-
"last_verified": "2026-05-19"
|
|
2350
|
+
"last_verified": "2026-05-19",
|
|
2351
|
+
"description": "An adversary may add additional roles or permissions to an adversary-controlled cloud account to maintain persistent access to a tenant.",
|
|
2352
|
+
"tactic": [
|
|
2353
|
+
"Persistence",
|
|
2354
|
+
"Privilege Escalation"
|
|
2355
|
+
]
|
|
1904
2356
|
},
|
|
1905
2357
|
"T1005": {
|
|
1906
2358
|
"name": "Data from Local System",
|
|
@@ -1928,7 +2380,11 @@
|
|
|
1928
2380
|
"reference_url": "https://attack.mitre.org/techniques/T1005",
|
|
1929
2381
|
"stix_id": "attack-pattern--3c4a2599-71ee-4405-ba1e-0e28414b4bc5",
|
|
1930
2382
|
"is_subtechnique": false,
|
|
1931
|
-
"last_verified": "2026-05-19"
|
|
2383
|
+
"last_verified": "2026-05-19",
|
|
2384
|
+
"description": "Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.",
|
|
2385
|
+
"tactic": [
|
|
2386
|
+
"Collection"
|
|
2387
|
+
]
|
|
1932
2388
|
},
|
|
1933
2389
|
"T1189": {
|
|
1934
2390
|
"name": "Drive-by Compromise",
|
|
@@ -1950,7 +2406,11 @@
|
|
|
1950
2406
|
"reference_url": "https://attack.mitre.org/techniques/T1189",
|
|
1951
2407
|
"stix_id": "attack-pattern--d742a578-d70e-4d0e-96a6-02a9c30204e6",
|
|
1952
2408
|
"is_subtechnique": false,
|
|
1953
|
-
"last_verified": "2026-05-19"
|
|
2409
|
+
"last_verified": "2026-05-19",
|
|
2410
|
+
"description": "Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.",
|
|
2411
|
+
"tactic": [
|
|
2412
|
+
"Initial Access"
|
|
2413
|
+
]
|
|
1954
2414
|
},
|
|
1955
2415
|
"T1496": {
|
|
1956
2416
|
"name": "Resource Hijacking",
|
|
@@ -1970,7 +2430,11 @@
|
|
|
1970
2430
|
"reference_url": "https://attack.mitre.org/techniques/T1496",
|
|
1971
2431
|
"stix_id": "attack-pattern--cd25c1b4-935c-4f0e-ba8d-552f28bc4783",
|
|
1972
2432
|
"is_subtechnique": false,
|
|
1973
|
-
"last_verified": "2026-05-19"
|
|
2433
|
+
"last_verified": "2026-05-19",
|
|
2434
|
+
"description": "Adversaries may leverage the resources of co-opted systems to complete resource-intensive tasks, which may impact system and/or hosted service availability.",
|
|
2435
|
+
"tactic": [
|
|
2436
|
+
"Impact"
|
|
2437
|
+
]
|
|
1974
2438
|
},
|
|
1975
2439
|
"T1498": {
|
|
1976
2440
|
"name": "Network Denial of Service",
|
|
@@ -1989,7 +2453,11 @@
|
|
|
1989
2453
|
"reference_url": "https://attack.mitre.org/techniques/T1498",
|
|
1990
2454
|
"stix_id": "attack-pattern--d74c4a7e-ffbf-432f-9365-7ebf1f787cab",
|
|
1991
2455
|
"is_subtechnique": false,
|
|
1992
|
-
"last_verified": "2026-05-19"
|
|
2456
|
+
"last_verified": "2026-05-19",
|
|
2457
|
+
"description": "Adversaries may perform Network Denial of Service (DoS) attacks to degrade or block the availability of targeted resources to users.",
|
|
2458
|
+
"tactic": [
|
|
2459
|
+
"Impact"
|
|
2460
|
+
]
|
|
1993
2461
|
},
|
|
1994
2462
|
"T1499.001": {
|
|
1995
2463
|
"name": "Endpoint Denial of Service: OS Exhaustion Flood",
|
|
@@ -2006,7 +2474,11 @@
|
|
|
2006
2474
|
"reference_url": "https://attack.mitre.org/techniques/T1499/001",
|
|
2007
2475
|
"stix_id": "attack-pattern--0df05477-c572-4ed6-88a9-47c581f548f7",
|
|
2008
2476
|
"is_subtechnique": true,
|
|
2009
|
-
"last_verified": "2026-05-19"
|
|
2477
|
+
"last_verified": "2026-05-19",
|
|
2478
|
+
"description": "Adversaries may launch a denial of service (DoS) attack targeting an endpoint's operating system (OS).",
|
|
2479
|
+
"tactic": [
|
|
2480
|
+
"Impact"
|
|
2481
|
+
]
|
|
2010
2482
|
},
|
|
2011
2483
|
"T1499.002": {
|
|
2012
2484
|
"name": "Endpoint Denial of Service: Service Exhaustion Flood",
|
|
@@ -2024,7 +2496,11 @@
|
|
|
2024
2496
|
"reference_url": "https://attack.mitre.org/techniques/T1499/002",
|
|
2025
2497
|
"stix_id": "attack-pattern--38eb0c22-6caf-46ce-8869-5964bd735858",
|
|
2026
2498
|
"is_subtechnique": true,
|
|
2027
|
-
"last_verified": "2026-05-19"
|
|
2499
|
+
"last_verified": "2026-05-19",
|
|
2500
|
+
"description": "Adversaries may target the different network services provided by systems to conduct a denial of service (DoS).",
|
|
2501
|
+
"tactic": [
|
|
2502
|
+
"Impact"
|
|
2503
|
+
]
|
|
2028
2504
|
},
|
|
2029
2505
|
"T1539": {
|
|
2030
2506
|
"name": "Steal Web Session Cookie",
|
|
@@ -2043,7 +2519,11 @@
|
|
|
2043
2519
|
"reference_url": "https://attack.mitre.org/techniques/T1539",
|
|
2044
2520
|
"stix_id": "attack-pattern--10ffac09-e42d-4f56-ab20-db94c67d76ff",
|
|
2045
2521
|
"is_subtechnique": false,
|
|
2046
|
-
"last_verified": "2026-05-19"
|
|
2522
|
+
"last_verified": "2026-05-19",
|
|
2523
|
+
"description": "An adversary may steal web application or service session cookies and use them to gain access to web applications or Internet services as an authenticated user without needing credentials.",
|
|
2524
|
+
"tactic": [
|
|
2525
|
+
"Credential Access"
|
|
2526
|
+
]
|
|
2047
2527
|
},
|
|
2048
2528
|
"T1657": {
|
|
2049
2529
|
"name": "Financial Theft",
|
|
@@ -2062,7 +2542,11 @@
|
|
|
2062
2542
|
"reference_url": "https://attack.mitre.org/techniques/T1657",
|
|
2063
2543
|
"stix_id": "attack-pattern--851e071f-208d-4c79-adc6-5974c85c78f3",
|
|
2064
2544
|
"is_subtechnique": false,
|
|
2065
|
-
"last_verified": "2026-05-19"
|
|
2545
|
+
"last_verified": "2026-05-19",
|
|
2546
|
+
"description": "Adversaries may steal monetary resources from targets through extortion, social engineering, technical theft, or other methods aimed at their own financial gain at the expense of the availability of these resources for victims.",
|
|
2547
|
+
"tactic": [
|
|
2548
|
+
"Impact"
|
|
2549
|
+
]
|
|
2066
2550
|
},
|
|
2067
2551
|
"T1606": {
|
|
2068
2552
|
"id": "T1606",
|
|
@@ -2099,11 +2583,22 @@
|
|
|
2099
2583
|
"Defense Evasion"
|
|
2100
2584
|
],
|
|
2101
2585
|
"description": "Adversaries may disable or modify system firewalls in order to bypass controls limiting network usage. While the technique is named for system firewalls specifically, the parent T1562 (Impair Defenses) covers the broader class of defense impairment that includes silently degrading update channels and signature freshness — UnDefend belongs to this class even when the specific sub-technique is closer to T1562.001 (Disable or Modify Tools). T1562.004 retained as a secondary ref because the UnDefend chain leaves Windows Firewall update logs in a corrupted state alongside the Defender pipeline tampering.",
|
|
2102
|
-
"last_verified": "2026-05-
|
|
2586
|
+
"last_verified": "2026-05-19",
|
|
2103
2587
|
"notes": "Added v0.13.17 to support BUG-2026-NIGHTMARE-ECLIPSE-UNDEFEND attack_refs. The dominant technique is T1562.001 (already in local catalog); T1562.004 is the secondary mapping for the firewall-state side-effects of UnDefend.",
|
|
2104
2588
|
"cve_refs": [
|
|
2105
2589
|
"BUG-2026-NIGHTMARE-ECLIPSE-UNDEFEND"
|
|
2106
|
-
]
|
|
2590
|
+
],
|
|
2591
|
+
"description_full": "Adversaries may disable or modify system firewalls in order to bypass controls limiting network usage. Changes could be disabling the entire mechanism as well as adding, deleting, or modifying particular rules. This can be done numerous ways depending on the operating system, including via command-line, editing Windows Registry keys, and Windows Control Panel. Modifying or disabling a system firewall may enable adversary C2 communications, lateral movement, and/or data exfiltration that would otherwise not be allowed. For example, adversaries may add a new firewall rule for a well-known protocol (such as RDP) using a non-traditional and potentially less securitized port (i.e. [Non-Standard Port](https://attack.mitre.org/techniques/T1571)).(Citation: change_rdp_port_conti) Adversaries may also modify host networking settings that indirectly manipulate system firewalls, such as interface bandwidth or network connection request thresholds.(Citation: Huntress BlackCat) Settings related to enabling abuse of various [Remote Services](https://attack.mitre.org/techniques/T1021) may also indirectly modify firewall rules. In ESXi, firewall rules may be modified directly via the esxcli command line interface (e.g., via `esxcli network firewall set`) or via the vCenter user interface.(Citation: Trellix Rnasomhouse 2024)(Citation: Broadcom ESXi Firewall)",
|
|
2592
|
+
"platforms": [
|
|
2593
|
+
"ESXi",
|
|
2594
|
+
"Linux",
|
|
2595
|
+
"macOS",
|
|
2596
|
+
"Network Devices",
|
|
2597
|
+
"Windows"
|
|
2598
|
+
],
|
|
2599
|
+
"reference_url": "https://attack.mitre.org/techniques/T1562/004",
|
|
2600
|
+
"stix_id": "attack-pattern--5372c5fe-f424-4def-bcd5-d3a8e770f07b",
|
|
2601
|
+
"is_subtechnique": true
|
|
2107
2602
|
},
|
|
2108
2603
|
"T1592": {
|
|
2109
2604
|
"id": "T1592",
|
|
@@ -2125,6 +2620,7 @@
|
|
|
2125
2620
|
"CVE-2021-43798",
|
|
2126
2621
|
"CVE-2022-20775",
|
|
2127
2622
|
"CVE-2023-38950",
|
|
2623
|
+
"CVE-2023-43472",
|
|
2128
2624
|
"CVE-2024-1708",
|
|
2129
2625
|
"CVE-2024-27199",
|
|
2130
2626
|
"CVE-2024-57728",
|
|
@@ -17387,5 +17883,2000 @@
|
|
|
17387
17883
|
"last_verified": "2026-05-19",
|
|
17388
17884
|
"_auto_imported": true,
|
|
17389
17885
|
"_intake_method": "mitre-attack-stix"
|
|
17886
|
+
},
|
|
17887
|
+
"T0881": {
|
|
17888
|
+
"id": "T0881",
|
|
17889
|
+
"name": "Service Stop",
|
|
17890
|
+
"version": "ics-attack-v15",
|
|
17891
|
+
"tactic": [
|
|
17892
|
+
"Inhibit Response Function"
|
|
17893
|
+
],
|
|
17894
|
+
"description": "Adversaries may stop or disable services on a system to render those services unavailable to legitimate users.",
|
|
17895
|
+
"description_full": "Adversaries may stop or disable services on a system to render those services unavailable to legitimate users. Stopping critical services can inhibit or stop response to an incident or aid in the adversary's overall objectives to cause damage to the environment. (Citation: Enterprise ATT&CK) Services may not allow for modification of their data stores while running. Adversaries may stop services in order to conduct Data Destruction. (Citation: Enterprise ATT&CK)",
|
|
17896
|
+
"platforms": [
|
|
17897
|
+
"None"
|
|
17898
|
+
],
|
|
17899
|
+
"detection": null,
|
|
17900
|
+
"reference_url": "https://attack.mitre.org/techniques/T0881",
|
|
17901
|
+
"stix_id": "attack-pattern--063b5b92-5361-481a-9c3f-95492ed9a2d8",
|
|
17902
|
+
"last_verified": "2026-05-19",
|
|
17903
|
+
"_auto_imported": true,
|
|
17904
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
17905
|
+
"_matrix": "ics-attack"
|
|
17906
|
+
},
|
|
17907
|
+
"T0836": {
|
|
17908
|
+
"id": "T0836",
|
|
17909
|
+
"name": "Modify Parameter",
|
|
17910
|
+
"version": "ics-attack-v15",
|
|
17911
|
+
"tactic": [
|
|
17912
|
+
"Impair Process Control"
|
|
17913
|
+
],
|
|
17914
|
+
"description": "Adversaries may modify parameters used to instruct industrial control system devices.",
|
|
17915
|
+
"description_full": "Adversaries may modify parameters used to instruct industrial control system devices. These devices operate via programs that dictate how and when to perform actions based on such parameters. Such parameters can determine the extent to which an action is performed and may specify additional options. For example, a program on a control system device dictating motor processes may take a parameter defining the total number of seconds to run that motor. An adversary can potentially modify these parameters to produce an outcome outside of what was intended by the operators. By modifying system and process critical parameters, the adversary may cause [Impact](https://attack.mitre.org/tactics/TA0105) to equipment and/or control processes. Modified parameters may be turned into dangerous, out-of-bounds, or unexpected values from typical operations. For example, specifying that a process run for more or less time than it should, or dictating an unusually high, low, or invalid value as a parameter.",
|
|
17916
|
+
"platforms": [
|
|
17917
|
+
"None"
|
|
17918
|
+
],
|
|
17919
|
+
"detection": null,
|
|
17920
|
+
"reference_url": "https://attack.mitre.org/techniques/T0836",
|
|
17921
|
+
"stix_id": "attack-pattern--097924ce-a9a9-4039-8591-e0deedfb8722",
|
|
17922
|
+
"last_verified": "2026-05-19",
|
|
17923
|
+
"_auto_imported": true,
|
|
17924
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
17925
|
+
"_matrix": "ics-attack"
|
|
17926
|
+
},
|
|
17927
|
+
"T0821": {
|
|
17928
|
+
"id": "T0821",
|
|
17929
|
+
"name": "Modify Controller Tasking",
|
|
17930
|
+
"version": "ics-attack-v15",
|
|
17931
|
+
"tactic": [
|
|
17932
|
+
"Execution (ICS)"
|
|
17933
|
+
],
|
|
17934
|
+
"description": "Adversaries may modify the tasking of a controller to allow for the execution of their own programs.",
|
|
17935
|
+
"description_full": "Adversaries may modify the tasking of a controller to allow for the execution of their own programs. This can allow an adversary to manipulate the execution flow and behavior of a controller. According to 61131-3, the association of a Task with a Program Organization Unit (POU) defines a task association. (Citation: IEC February 2013) An adversary may modify these associations or create new ones to manipulate the execution flow of a controller. Modification of controller tasking can be accomplished using a Program Download in addition to other types of program modification such as online edit and program append. Tasks have properties, such as interval, frequency and priority to meet the requirements of program execution. Some controller vendors implement tasks with implicit, pre-defined properties whereas others allow for these properties to be formulated explicitly. An adversary may associate their program with tasks that have a higher priority or execute associated programs more frequently. For instance, to ensure cyclic execution of their program on a Siemens controller, an adversary may add their program to the task, Organization Block 1 (OB1).",
|
|
17936
|
+
"platforms": [
|
|
17937
|
+
"None"
|
|
17938
|
+
],
|
|
17939
|
+
"detection": null,
|
|
17940
|
+
"reference_url": "https://attack.mitre.org/techniques/T0821",
|
|
17941
|
+
"stix_id": "attack-pattern--09a61657-46e1-439e-b3ed-3e4556a78243",
|
|
17942
|
+
"last_verified": "2026-05-19",
|
|
17943
|
+
"_auto_imported": true,
|
|
17944
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
17945
|
+
"_matrix": "ics-attack"
|
|
17946
|
+
},
|
|
17947
|
+
"T0887": {
|
|
17948
|
+
"id": "T0887",
|
|
17949
|
+
"name": "Wireless Sniffing",
|
|
17950
|
+
"version": "ics-attack-v15",
|
|
17951
|
+
"tactic": [
|
|
17952
|
+
"Discovery (ICS)",
|
|
17953
|
+
"Collection (ICS)"
|
|
17954
|
+
],
|
|
17955
|
+
"description": "Adversaries may seek to capture radio frequency (RF) communication used for remote control and reporting in distributed environments.",
|
|
17956
|
+
"description_full": "Adversaries may seek to capture radio frequency (RF) communication used for remote control and reporting in distributed environments. RF communication frequencies vary between 3 kHz to 300 GHz, although are commonly between 300 MHz to 6 GHz. (Citation: Candell, R., Hany, M., Lee, K. B., Liu,Y., Quimby, J., Remley, K. April 2018) The wavelength and frequency of the signal affect how the signal propagates through open air, obstacles (e.g. walls and trees) and the type of radio required to capture them. These characteristics are often standardized in the protocol and hardware and may have an effect on how the signal is captured. Some examples of wireless protocols that may be found in cyber-physical environments are: WirelessHART, Zigbee, WIA-FA, and 700 MHz Public Safety Spectrum. Adversaries may capture RF communications by using specialized hardware, such as software defined radio (SDR), handheld radio, or a computer with radio demodulator tuned to the communication frequency. (Citation: Bastille April 2017) Information transmitted over a wireless medium may be captured in-transit whether the sniffing device is the intended destination or not. This technique may be particularly useful to an adversary when the communications are not encrypted. (Citation: Gallagher, S. April 2017) In the 2017 Dallas Siren incident, it is suspected that adversaries likely captured wireless command message broadcasts on a 700 MHz frequency during a regular test of the system. These messages were later replayed to trigger the alarm systems. (Citation: Gallagher, S. April 2017)",
|
|
17957
|
+
"platforms": [
|
|
17958
|
+
"None"
|
|
17959
|
+
],
|
|
17960
|
+
"detection": null,
|
|
17961
|
+
"reference_url": "https://attack.mitre.org/techniques/T0887",
|
|
17962
|
+
"stix_id": "attack-pattern--0fe075d5-beac-4d02-b93e-0f874997db72",
|
|
17963
|
+
"last_verified": "2026-05-19",
|
|
17964
|
+
"_auto_imported": true,
|
|
17965
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
17966
|
+
"_matrix": "ics-attack"
|
|
17967
|
+
},
|
|
17968
|
+
"T0829": {
|
|
17969
|
+
"id": "T0829",
|
|
17970
|
+
"name": "Loss of View",
|
|
17971
|
+
"version": "ics-attack-v15",
|
|
17972
|
+
"tactic": [
|
|
17973
|
+
"Impact (ICS)"
|
|
17974
|
+
],
|
|
17975
|
+
"description": "Adversaries may cause a sustained or permanent loss of view where the ICS equipment will require local, hands-on operator intervention; for instance, a restart or manual operation.",
|
|
17976
|
+
"description_full": "Adversaries may cause a sustained or permanent loss of view where the ICS equipment will require local, hands-on operator intervention; for instance, a restart or manual operation. By causing a sustained reporting or visibility loss, the adversary can effectively hide the present state of operations. This loss of view can occur without affecting the physical processes themselves. (Citation: Corero) (Citation: Michael J. Assante and Robert M. Lee) (Citation: Tyson Macaulay)",
|
|
17977
|
+
"platforms": [
|
|
17978
|
+
"None"
|
|
17979
|
+
],
|
|
17980
|
+
"detection": null,
|
|
17981
|
+
"reference_url": "https://attack.mitre.org/techniques/T0829",
|
|
17982
|
+
"stix_id": "attack-pattern--138979ba-0430-4de6-a128-2fc0b056ba36",
|
|
17983
|
+
"last_verified": "2026-05-19",
|
|
17984
|
+
"_auto_imported": true,
|
|
17985
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
17986
|
+
"_matrix": "ics-attack"
|
|
17987
|
+
},
|
|
17988
|
+
"T1691.001": {
|
|
17989
|
+
"id": "T1691.001",
|
|
17990
|
+
"name": "Command Message",
|
|
17991
|
+
"version": "ics-attack-v15",
|
|
17992
|
+
"tactic": [
|
|
17993
|
+
"Inhibit Response Function"
|
|
17994
|
+
],
|
|
17995
|
+
"description": "Adversaries may block a command message from reaching its intended target to prevent command execution.",
|
|
17996
|
+
"description_full": "Adversaries may block a command message from reaching its intended target to prevent command execution. In OT networks, command messages are sent to provide instructions to control system devices. A blocked command message can inhibit response functions from correcting a disruption or unsafe condition.(Citation: Bonnie Zhu, Anthony Joseph, Shankar Sastry 2011)(Citation: Electricity Information Sharing and Analysis Center; SANS Industrial Control Systems March 2016)",
|
|
17997
|
+
"platforms": [],
|
|
17998
|
+
"detection": null,
|
|
17999
|
+
"reference_url": "https://attack.mitre.org/techniques/T1691/001",
|
|
18000
|
+
"stix_id": "attack-pattern--15ca2a99-2d3e-457f-b1d7-c52a1d5849c9",
|
|
18001
|
+
"last_verified": "2026-05-19",
|
|
18002
|
+
"_auto_imported": true,
|
|
18003
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18004
|
+
"_matrix": "ics-attack",
|
|
18005
|
+
"_gap_skip": {
|
|
18006
|
+
"fields": [
|
|
18007
|
+
"platforms"
|
|
18008
|
+
],
|
|
18009
|
+
"reason": "ICS-attack techniques do not carry a platforms field in MITRE STIX — they target the ICS matrix as a whole rather than specific OS/cloud platforms"
|
|
18010
|
+
}
|
|
18011
|
+
},
|
|
18012
|
+
"T0800": {
|
|
18013
|
+
"id": "T0800",
|
|
18014
|
+
"name": "Activate Firmware Update Mode",
|
|
18015
|
+
"version": "ics-attack-v15",
|
|
18016
|
+
"tactic": [
|
|
18017
|
+
"Inhibit Response Function"
|
|
18018
|
+
],
|
|
18019
|
+
"description": "Adversaries may activate firmware update mode on devices to prevent expected response functions from engaging in reaction to an emergency or process malfunction.",
|
|
18020
|
+
"description_full": "Adversaries may activate firmware update mode on devices to prevent expected response functions from engaging in reaction to an emergency or process malfunction. For example, devices such as protection relays may have an operation mode designed for firmware installation. This mode may halt process monitoring and related functions to allow new firmware to be loaded. A device left in update mode may be placed in an inactive holding state if no firmware is provided to it. By entering and leaving a device in this mode, the adversary may deny its usual functionalities.",
|
|
18021
|
+
"platforms": [
|
|
18022
|
+
"None"
|
|
18023
|
+
],
|
|
18024
|
+
"detection": null,
|
|
18025
|
+
"reference_url": "https://attack.mitre.org/techniques/T0800",
|
|
18026
|
+
"stix_id": "attack-pattern--19a71d1e-6334-4233-8260-b749cae37953",
|
|
18027
|
+
"last_verified": "2026-05-19",
|
|
18028
|
+
"_auto_imported": true,
|
|
18029
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18030
|
+
"_matrix": "ics-attack"
|
|
18031
|
+
},
|
|
18032
|
+
"T0831": {
|
|
18033
|
+
"id": "T0831",
|
|
18034
|
+
"name": "Manipulation of Control",
|
|
18035
|
+
"version": "ics-attack-v15",
|
|
18036
|
+
"tactic": [
|
|
18037
|
+
"Impact (ICS)"
|
|
18038
|
+
],
|
|
18039
|
+
"description": "Adversaries may manipulate physical process control within the industrial environment.",
|
|
18040
|
+
"description_full": "Adversaries may manipulate physical process control within the industrial environment. Methods of manipulating control can include changes to set point values, tags, or other parameters. Adversaries may manipulate control systems devices or possibly leverage their own, to communicate with and command physical control processes. The duration of manipulation may be temporary or longer sustained, depending on operator detection. Methods of Manipulation of Control include: * Man-in-the-middle * Spoof command message * Changing setpoints A Polish student used a remote controller device to interface with the Lodz city tram system in Poland. (Citation: John Bill May 2017) (Citation: Shelley Smith February 2008) (Citation: Bruce Schneier January 2008) Using this remote, the student was able to capture and replay legitimate tram signals. As a consequence, four trams were derailed and twelve people injured due to resulting emergency stops. (Citation: Shelley Smith February 2008) The track controlling commands issued may have also resulted in tram collisions, a further risk to those on board and nearby the areas of impact. (Citation: Bruce Schneier January 2008)",
|
|
18041
|
+
"platforms": [
|
|
18042
|
+
"None"
|
|
18043
|
+
],
|
|
18044
|
+
"detection": null,
|
|
18045
|
+
"reference_url": "https://attack.mitre.org/techniques/T0831",
|
|
18046
|
+
"stix_id": "attack-pattern--1af9e3fd-2bcc-414d-adbd-fe3b95c02ca1",
|
|
18047
|
+
"last_verified": "2026-05-19",
|
|
18048
|
+
"_auto_imported": true,
|
|
18049
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18050
|
+
"_matrix": "ics-attack"
|
|
18051
|
+
},
|
|
18052
|
+
"T0814": {
|
|
18053
|
+
"id": "T0814",
|
|
18054
|
+
"name": "Denial of Service",
|
|
18055
|
+
"version": "ics-attack-v15",
|
|
18056
|
+
"tactic": [
|
|
18057
|
+
"Inhibit Response Function"
|
|
18058
|
+
],
|
|
18059
|
+
"description": "Adversaries may perform Denial-of-Service (DoS) attacks to disrupt expected device functionality.",
|
|
18060
|
+
"description_full": "Adversaries may perform Denial-of-Service (DoS) attacks to disrupt expected device functionality. Examples of DoS attacks include overwhelming the target device with a high volume of requests in a short time period and sending the target device a request it does not know how to handle. Disrupting device state may temporarily render it unresponsive, possibly lasting until a reboot can occur. When placed in this state, devices may be unable to send and receive requests, and may not perform expected response functions in reaction to other events in the environment. Some ICS devices are particularly sensitive to DoS events, and may become unresponsive in reaction to even a simple ping sweep. Adversaries may also attempt to execute a Permanent Denial-of-Service (PDoS) against certain devices, such as in the case of the BrickerBot malware. (Citation: ICS-CERT April 2017) Adversaries may exploit a software vulnerability to cause a denial of service by taking advantage of a programming error in a program, service, or within the operating system software or kernel itself to execute adversary-controlled code. Vulnerabilities may exist in software that can be used to cause a denial of service condition. Adversaries may have prior knowledge about industrial protocols or control devices used in the environment through [Remote System Information Discovery](https://attack.mitre.org/techniques/T0888). There are examples of adversaries remotely causing a [Device Restart/Shutdown](https://attack.mitre.org/techniques/T0816) by exploiting a vulnerability that induces uncontrolled resource consumption. (Citation: ICS-CERT August 2018) (Citation: Common Weakness Enumeration January 2019) (Citation: MITRE March 2018)",
|
|
18061
|
+
"platforms": [
|
|
18062
|
+
"None"
|
|
18063
|
+
],
|
|
18064
|
+
"detection": null,
|
|
18065
|
+
"reference_url": "https://attack.mitre.org/techniques/T0814",
|
|
18066
|
+
"stix_id": "attack-pattern--1b22b676-9347-4c55-9a35-ef0dc653db5b",
|
|
18067
|
+
"last_verified": "2026-05-19",
|
|
18068
|
+
"_auto_imported": true,
|
|
18069
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18070
|
+
"_matrix": "ics-attack"
|
|
18071
|
+
},
|
|
18072
|
+
"T0894": {
|
|
18073
|
+
"id": "T0894",
|
|
18074
|
+
"name": "System Binary Proxy Execution",
|
|
18075
|
+
"version": "ics-attack-v15",
|
|
18076
|
+
"tactic": [
|
|
18077
|
+
"Evasion (ICS)"
|
|
18078
|
+
],
|
|
18079
|
+
"description": "Adversaries may bypass process and/or signature-based defenses by proxying execution of malicious content with signed, or otherwise trusted, binaries.",
|
|
18080
|
+
"description_full": "Adversaries may bypass process and/or signature-based defenses by proxying execution of malicious content with signed, or otherwise trusted, binaries. Binaries used in this technique are often Microsoft-signed files, indicating that they have been either downloaded from Microsoft or are already native in the operating system. (Citation: LOLBAS Project) Binaries signed with trusted digital certificates can typically execute on Windows systems protected by digital signature validation. Several Microsoft signed binaries that are default on Windows installations can be used to proxy execution of other files or commands. Similarly, on Linux systems adversaries may abuse trusted binaries such as split to proxy execution of malicious commands. (Citation: split man page)(Citation: GTFO split) Adversaries may abuse application binaries installed on a system for proxy execution of malicious code or domain-specific commands. These commands could be used to target local resources on the device or networked devices within the environment through defined APIs ([Execution through API](https://attack.mitre.org/techniques/T0871)) or application-specific programming languages (e.g., MicroSCADA SCIL). Application binaries may be signed by the developer or generally trusted by the operators, analysts, and monitoring tools accustomed to the environment. These applications may be developed and/or directly provided by the device vendor to enable configuration, management, and operation of their devices without many alternatives. Adversaries may seek to target these trusted application binaries to execute or send commands without the development of custom malware. For example, adversaries may target a SCADA server binary which has the existing ability to send commands to substation devices, such as through IEC 104 command messages. Proxy execution may still require the development of custom tools to hook into the application binary’s execution.",
|
|
18081
|
+
"platforms": [
|
|
18082
|
+
"None"
|
|
18083
|
+
],
|
|
18084
|
+
"detection": null,
|
|
18085
|
+
"reference_url": "https://attack.mitre.org/techniques/T0894",
|
|
18086
|
+
"stix_id": "attack-pattern--1c5cf58c-a34a-40d7-82f4-f987cdfc2b91",
|
|
18087
|
+
"last_verified": "2026-05-19",
|
|
18088
|
+
"_auto_imported": true,
|
|
18089
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18090
|
+
"_matrix": "ics-attack"
|
|
18091
|
+
},
|
|
18092
|
+
"T0807": {
|
|
18093
|
+
"id": "T0807",
|
|
18094
|
+
"name": "Command-Line Interface",
|
|
18095
|
+
"version": "ics-attack-v15",
|
|
18096
|
+
"tactic": [
|
|
18097
|
+
"Execution (ICS)"
|
|
18098
|
+
],
|
|
18099
|
+
"description": "Adversaries may utilize command-line interfaces (CLIs) to interact with systems and execute commands.",
|
|
18100
|
+
"description_full": "Adversaries may utilize command-line interfaces (CLIs) to interact with systems and execute commands. CLIs provide a means of interacting with computer systems and are a common feature across many types of platforms and devices within control systems environments. (Citation: Enterprise ATT&CK January 2018) Adversaries may also use CLIs to install and run new software, including malicious tools that may be installed over the course of an operation. CLIs are typically accessed locally, but can also be exposed via services, such as SSH, Telnet, and RDP. Commands that are executed in the CLI execute with the current permissions level of the process running the terminal emulator, unless the command specifies a change in permissions context. Many controllers have CLI interfaces for management purposes.",
|
|
18101
|
+
"platforms": [
|
|
18102
|
+
"None"
|
|
18103
|
+
],
|
|
18104
|
+
"detection": null,
|
|
18105
|
+
"reference_url": "https://attack.mitre.org/techniques/T0807",
|
|
18106
|
+
"stix_id": "attack-pattern--24a9253e-8948-4c98-b751-8e2aee53127c",
|
|
18107
|
+
"last_verified": "2026-05-19",
|
|
18108
|
+
"_auto_imported": true,
|
|
18109
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18110
|
+
"_matrix": "ics-attack"
|
|
18111
|
+
},
|
|
18112
|
+
"T0861": {
|
|
18113
|
+
"id": "T0861",
|
|
18114
|
+
"name": "Point & Tag Identification",
|
|
18115
|
+
"version": "ics-attack-v15",
|
|
18116
|
+
"tactic": [
|
|
18117
|
+
"Collection (ICS)"
|
|
18118
|
+
],
|
|
18119
|
+
"description": "Adversaries may collect point and tag values to gain a more comprehensive understanding of the process environment.",
|
|
18120
|
+
"description_full": "Adversaries may collect point and tag values to gain a more comprehensive understanding of the process environment. Points may be values such as inputs, memory locations, outputs or other process specific variables. (Citation: Dennis L. Sloatman September 2016) Tags are the identifiers given to points for operator convenience. Collecting such tags provides valuable context to environmental points and enables an adversary to map inputs, outputs, and other values to their control processes. Understanding the points being collected may inform an adversary on which processes and values to keep track of over the course of an operation.",
|
|
18121
|
+
"platforms": [
|
|
18122
|
+
"None"
|
|
18123
|
+
],
|
|
18124
|
+
"detection": null,
|
|
18125
|
+
"reference_url": "https://attack.mitre.org/techniques/T0861",
|
|
18126
|
+
"stix_id": "attack-pattern--25852363-5968-4673-b81d-341d5ed90bd1",
|
|
18127
|
+
"last_verified": "2026-05-19",
|
|
18128
|
+
"_auto_imported": true,
|
|
18129
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18130
|
+
"_matrix": "ics-attack"
|
|
18131
|
+
},
|
|
18132
|
+
"T0816": {
|
|
18133
|
+
"id": "T0816",
|
|
18134
|
+
"name": "Device Restart/Shutdown",
|
|
18135
|
+
"version": "ics-attack-v15",
|
|
18136
|
+
"tactic": [
|
|
18137
|
+
"Inhibit Response Function"
|
|
18138
|
+
],
|
|
18139
|
+
"description": "Adversaries may forcibly restart or shutdown a device in an ICS environment to disrupt and potentially negatively impact physical processes.",
|
|
18140
|
+
"description_full": "Adversaries may forcibly restart or shutdown a device in an ICS environment to disrupt and potentially negatively impact physical processes. Methods of device restart and shutdown exist in some devices as built-in, standard functionalities. These functionalities can be executed using interactive device web interfaces, CLIs, and network protocol commands. Unexpected restart or shutdown of control system devices may prevent expected response functions happening during critical states. A device restart can also be a sign of malicious device modifications, as many updates require a shutdown in order to take effect.",
|
|
18141
|
+
"platforms": [
|
|
18142
|
+
"None"
|
|
18143
|
+
],
|
|
18144
|
+
"detection": null,
|
|
18145
|
+
"reference_url": "https://attack.mitre.org/techniques/T0816",
|
|
18146
|
+
"stix_id": "attack-pattern--25dfc8ad-bd73-4dfd-84a9-3c3d383f76e9",
|
|
18147
|
+
"last_verified": "2026-05-19",
|
|
18148
|
+
"_auto_imported": true,
|
|
18149
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18150
|
+
"_matrix": "ics-attack"
|
|
18151
|
+
},
|
|
18152
|
+
"T0863": {
|
|
18153
|
+
"id": "T0863",
|
|
18154
|
+
"name": "User Execution",
|
|
18155
|
+
"version": "ics-attack-v15",
|
|
18156
|
+
"tactic": [
|
|
18157
|
+
"Execution (ICS)"
|
|
18158
|
+
],
|
|
18159
|
+
"description": "Adversaries may rely on a targeted organizations user interaction for the execution of malicious code.",
|
|
18160
|
+
"description_full": "Adversaries may rely on a targeted organizations user interaction for the execution of malicious code. User interaction may consist of installing applications, opening email attachments, or granting higher permissions to documents. Adversaries may embed malicious code or visual basic code into files such as Microsoft Word and Excel documents or software installers. (Citation: Booz Allen Hamilton) Execution of this code requires that the user enable scripting or write access within the document. Embedded code may not always be noticeable to the user especially in cases of trojanized software. (Citation: Daavid Hentunen, Antti Tikkanen June 2014) A Chinese spearphishing campaign running from December 9, 2011 through February 29, 2012 delivered malware through spearphishing attachments which required user action to achieve execution. (Citation: CISA AA21-201A Pipeline Intrusion July 2021)",
|
|
18161
|
+
"platforms": [
|
|
18162
|
+
"None"
|
|
18163
|
+
],
|
|
18164
|
+
"detection": null,
|
|
18165
|
+
"reference_url": "https://attack.mitre.org/techniques/T0863",
|
|
18166
|
+
"stix_id": "attack-pattern--2736b752-4ec5-4421-a230-8977dea7649c",
|
|
18167
|
+
"last_verified": "2026-05-19",
|
|
18168
|
+
"_auto_imported": true,
|
|
18169
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18170
|
+
"_matrix": "ics-attack"
|
|
18171
|
+
},
|
|
18172
|
+
"T0860": {
|
|
18173
|
+
"id": "T0860",
|
|
18174
|
+
"name": "Wireless Compromise",
|
|
18175
|
+
"version": "ics-attack-v15",
|
|
18176
|
+
"tactic": [
|
|
18177
|
+
"Initial Access (ICS)"
|
|
18178
|
+
],
|
|
18179
|
+
"description": "Adversaries may perform wireless compromise as a method of gaining communications and unauthorized access to a wireless network.",
|
|
18180
|
+
"description_full": "Adversaries may perform wireless compromise as a method of gaining communications and unauthorized access to a wireless network. Access to a wireless network may be gained through the compromise of a wireless device. (Citation: Alexander Bolshev, Gleb Cherbov July 2014) (Citation: Alexander Bolshev March 2014) Adversaries may also utilize radios and other wireless communication devices on the same frequency as the wireless network. Wireless compromise can be done as an initial access vector from a remote distance. A Polish student used a modified TV remote controller to gain access to and control over the Lodz city tram system in Poland. (Citation: John Bill May 2017) (Citation: Shelley Smith February 2008) The remote controller device allowed the student to interface with the trams network to modify track settings and override operator control. The adversary may have accomplished this by aligning the controller to the frequency and amplitude of IR control protocol signals. (Citation: Bruce Schneier January 2008) The controller then enabled initial access to the network, allowing the capture and replay of tram signals. (Citation: John Bill May 2017)",
|
|
18181
|
+
"platforms": [
|
|
18182
|
+
"None"
|
|
18183
|
+
],
|
|
18184
|
+
"detection": null,
|
|
18185
|
+
"reference_url": "https://attack.mitre.org/techniques/T0860",
|
|
18186
|
+
"stix_id": "attack-pattern--2877063e-1851-48d2-bcc6-bc1d2733157e",
|
|
18187
|
+
"last_verified": "2026-05-19",
|
|
18188
|
+
"_auto_imported": true,
|
|
18189
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18190
|
+
"_matrix": "ics-attack"
|
|
18191
|
+
},
|
|
18192
|
+
"T0858": {
|
|
18193
|
+
"id": "T0858",
|
|
18194
|
+
"name": "Change Operating Mode",
|
|
18195
|
+
"version": "ics-attack-v15",
|
|
18196
|
+
"tactic": [
|
|
18197
|
+
"Execution (ICS)",
|
|
18198
|
+
"Evasion (ICS)"
|
|
18199
|
+
],
|
|
18200
|
+
"description": "Adversaries may change the operating mode of a controller to gain additional access to engineering functions such as Program Download.",
|
|
18201
|
+
"description_full": "Adversaries may change the operating mode of a controller to gain additional access to engineering functions such as Program Download. Programmable controllers typically have several modes of operation that control the state of the user program and control access to the controllers API. Operating modes can be physically selected using a key switch on the face of the controller but may also be selected with calls to the controllers API. Operating modes and the mechanisms by which they are selected often vary by vendor and product line. Some commonly implemented operating modes are described below: * Program - This mode must be enabled before changes can be made to a devices program. This allows program uploads and downloads between the device and an engineering workstation. Often the PLCs logic Is halted, and all outputs may be forced off. (Citation: N.A. October 2017) * Run - Execution of the devices program occurs in this mode. Input and output (values, points, tags, elements, etc.) are monitored and used according to the programs logic. [Program Upload](https://attack.mitre.org/techniques/T0845) and [Program Download](https://attack.mitre.org/techniques/T0843) are disabled while in this mode. (Citation: Omron) (Citation: Machine Information Systems 2007) (Citation: N.A. October 2017) (Citation: PLCgurus 2021) * Remote - Allows for remote changes to a PLCs operation mode. (Citation: PLCgurus 2021) * Stop - The PLC and program is stopped, while in this mode, outputs are forced off. (Citation: Machine Information Systems 2007) * Reset - Conditions on the PLC are reset to their original states. Warm resets may retain some memory while cold resets will reset all I/O and data registers. (Citation: Machine Information Systems 2007) * Test / Monitor mode - Similar to run mode, I/O is processed, although this mode allows for monitoring, force set, resets, and more generally tuning or debugging of the system. Often monitor mode may be used as a trial for initialization. (Citation: Omron)",
|
|
18202
|
+
"platforms": [
|
|
18203
|
+
"None"
|
|
18204
|
+
],
|
|
18205
|
+
"detection": null,
|
|
18206
|
+
"reference_url": "https://attack.mitre.org/techniques/T0858",
|
|
18207
|
+
"stix_id": "attack-pattern--2883c520-7957-46ca-89bd-dab1ad53b601",
|
|
18208
|
+
"last_verified": "2026-05-19",
|
|
18209
|
+
"_auto_imported": true,
|
|
18210
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18211
|
+
"_matrix": "ics-attack"
|
|
18212
|
+
},
|
|
18213
|
+
"T0878": {
|
|
18214
|
+
"id": "T0878",
|
|
18215
|
+
"name": "Alarm Suppression",
|
|
18216
|
+
"version": "ics-attack-v15",
|
|
18217
|
+
"tactic": [
|
|
18218
|
+
"Inhibit Response Function"
|
|
18219
|
+
],
|
|
18220
|
+
"description": "Adversaries may target protection function alarms to prevent them from notifying operators of critical conditions.",
|
|
18221
|
+
"description_full": "Adversaries may target protection function alarms to prevent them from notifying operators of critical conditions. Alarm messages may be a part of an overall reporting system and of particular interest for adversaries. Disruption of the alarm system does not imply the disruption of the reporting system as a whole. A Secura presentation on targeting OT notes a dual fold goal for adversaries attempting alarm suppression: prevent outgoing alarms from being raised and prevent incoming alarms from being responded to. (Citation: Jos Wetzels, Marina Krotofil 2019) The method of suppression may greatly depend on the type of alarm in question: * An alarm raised by a protocol message * An alarm signaled with I/O * An alarm bit set in a flag (and read) In ICS environments, the adversary may have to suppress or contend with multiple alarms and/or alarm propagation to achieve a specific goal to evade detection or prevent intended responses from occurring. (Citation: Jos Wetzels, Marina Krotofil 2019) Methods of suppression may involve tampering or altering device displays and logs, modifying in memory code to fixed values, or even tampering with assembly level instruction code.",
|
|
18222
|
+
"platforms": [
|
|
18223
|
+
"None"
|
|
18224
|
+
],
|
|
18225
|
+
"detection": null,
|
|
18226
|
+
"reference_url": "https://attack.mitre.org/techniques/T0878",
|
|
18227
|
+
"stix_id": "attack-pattern--2900bbd8-308a-4274-b074-5b8bde8347bc",
|
|
18228
|
+
"last_verified": "2026-05-19",
|
|
18229
|
+
"_auto_imported": true,
|
|
18230
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18231
|
+
"_matrix": "ics-attack"
|
|
18232
|
+
},
|
|
18233
|
+
"T0868": {
|
|
18234
|
+
"id": "T0868",
|
|
18235
|
+
"name": "Detect Operating Mode",
|
|
18236
|
+
"version": "ics-attack-v15",
|
|
18237
|
+
"tactic": [
|
|
18238
|
+
"Collection (ICS)"
|
|
18239
|
+
],
|
|
18240
|
+
"description": "Adversaries may gather information about a PLCs or controllers current operating mode.",
|
|
18241
|
+
"description_full": "Adversaries may gather information about a PLCs or controllers current operating mode. Operating modes dictate what change or maintenance functions can be manipulated and are often controlled by a key switch on the PLC (e.g., run, prog [program], and remote). Knowledge of these states may be valuable to an adversary to determine if they are able to reprogram the PLC. Operating modes and the mechanisms by which they are selected often vary by vendor and product line. Some commonly implemented operating modes are described below: * Program - This mode must be enabled before changes can be made to a devices program. This allows program uploads and downloads between the device and an engineering workstation. Often the PLCs logic Is halted, and all outputs may be forced off. (Citation: N.A. October 2017) * Run - Execution of the devices program occurs in this mode. Input and output (values, points, tags, elements, etc.) are monitored and used according to the programs logic.[Program Upload](https://attack.mitre.org/techniques/T0845) and [Program Download](https://attack.mitre.org/techniques/T0843) are disabled while in this mode. (Citation: Omron) (Citation: Machine Information Systems 2007) (Citation: N.A. October 2017) (Citation: PLCgurus 2021) * Remote - Allows for remote changes to a PLCs operation mode. (Citation: PLCgurus 2021) * Stop - The PLC and program is stopped, while in this mode, outputs are forced off. (Citation: Machine Information Systems 2007) * Reset - Conditions on the PLC are reset to their original states. Warm resets may retain some memory while cold resets will reset all I/O and data registers. (Citation: Machine Information Systems 2007) * Test / Monitor mode - Similar to run mode, I/O is processed, although this mode allows for monitoring, force set, resets, and more generally tuning or debugging of the system. Often monitor mode may be used as a trial for initialization. (Citation: Omron)",
|
|
18242
|
+
"platforms": [
|
|
18243
|
+
"None"
|
|
18244
|
+
],
|
|
18245
|
+
"detection": null,
|
|
18246
|
+
"reference_url": "https://attack.mitre.org/techniques/T0868",
|
|
18247
|
+
"stix_id": "attack-pattern--2aa406ed-81c3-4c1d-ba83-cfbee5a2847a",
|
|
18248
|
+
"last_verified": "2026-05-19",
|
|
18249
|
+
"_auto_imported": true,
|
|
18250
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18251
|
+
"_matrix": "ics-attack"
|
|
18252
|
+
},
|
|
18253
|
+
"T0837": {
|
|
18254
|
+
"id": "T0837",
|
|
18255
|
+
"name": "Loss of Protection",
|
|
18256
|
+
"version": "ics-attack-v15",
|
|
18257
|
+
"tactic": [
|
|
18258
|
+
"Impact (ICS)"
|
|
18259
|
+
],
|
|
18260
|
+
"description": "Adversaries may compromise protective system functions designed to prevent the effects of faults and abnormal conditions.",
|
|
18261
|
+
"description_full": "Adversaries may compromise protective system functions designed to prevent the effects of faults and abnormal conditions. This can result in equipment damage, prolonged process disruptions and hazards to personnel. Many faults and abnormal conditions in process control happen too quickly for a human operator to react to. Speed is critical in correcting these conditions to limit serious impacts such as Loss of Control and Property Damage. Adversaries may target and disable protective system functions as a prerequisite to subsequent attack execution or to allow for future faults and abnormal conditions to go unchecked. Detection of a Loss of Protection by operators can result in the shutdown of a process due to strict policies regarding protection systems. This can cause a Loss of Productivity and Revenue and may meet the technical goals of adversaries seeking to cause process disruptions.",
|
|
18262
|
+
"platforms": [
|
|
18263
|
+
"None"
|
|
18264
|
+
],
|
|
18265
|
+
"detection": null,
|
|
18266
|
+
"reference_url": "https://attack.mitre.org/techniques/T0837",
|
|
18267
|
+
"stix_id": "attack-pattern--2bb4d762-bf4a-4bc3-9318-15cc6a354163",
|
|
18268
|
+
"last_verified": "2026-05-19",
|
|
18269
|
+
"_auto_imported": true,
|
|
18270
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18271
|
+
"_matrix": "ics-attack"
|
|
18272
|
+
},
|
|
18273
|
+
"T0801": {
|
|
18274
|
+
"id": "T0801",
|
|
18275
|
+
"name": "Monitor Process State",
|
|
18276
|
+
"version": "ics-attack-v15",
|
|
18277
|
+
"tactic": [
|
|
18278
|
+
"Collection (ICS)"
|
|
18279
|
+
],
|
|
18280
|
+
"description": "Adversaries may gather information about the physical process state.",
|
|
18281
|
+
"description_full": "Adversaries may gather information about the physical process state. This information may be used to gain more information about the process itself or used as a trigger for malicious actions. The sources of process state information may vary such as, OPC tags, historian data, specific PLC block information, or network traffic.",
|
|
18282
|
+
"platforms": [
|
|
18283
|
+
"None"
|
|
18284
|
+
],
|
|
18285
|
+
"detection": null,
|
|
18286
|
+
"reference_url": "https://attack.mitre.org/techniques/T0801",
|
|
18287
|
+
"stix_id": "attack-pattern--2d0d40ad-22fa-4cc8-b264-072557e1364b",
|
|
18288
|
+
"last_verified": "2026-05-19",
|
|
18289
|
+
"_auto_imported": true,
|
|
18290
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18291
|
+
"_matrix": "ics-attack"
|
|
18292
|
+
},
|
|
18293
|
+
"T0888": {
|
|
18294
|
+
"id": "T0888",
|
|
18295
|
+
"name": "Remote System Information Discovery",
|
|
18296
|
+
"version": "ics-attack-v15",
|
|
18297
|
+
"tactic": [
|
|
18298
|
+
"Discovery (ICS)"
|
|
18299
|
+
],
|
|
18300
|
+
"description": "An adversary may attempt to get detailed information about remote systems and their peripherals, such as make/model, role, and configuration.",
|
|
18301
|
+
"description_full": "An adversary may attempt to get detailed information about remote systems and their peripherals, such as make/model, role, and configuration. Adversaries may use information from Remote System Information Discovery to aid in targeting and shaping follow-on behaviors. For example, the system's operational role and model information can dictate whether it is a relevant target for the adversary's operational objectives. In addition, the system's configuration may be used to scope subsequent technique usage. Requests for system information are typically implemented using automation and management protocols and are often automatically requested by vendor software during normal operation. This information may be used to tailor management actions, such as program download and system or module firmware. An adversary may leverage this same information by issuing calls directly to the system's API.",
|
|
18302
|
+
"platforms": [
|
|
18303
|
+
"None"
|
|
18304
|
+
],
|
|
18305
|
+
"detection": null,
|
|
18306
|
+
"reference_url": "https://attack.mitre.org/techniques/T0888",
|
|
18307
|
+
"stix_id": "attack-pattern--2fedbe69-581f-447d-8a78-32ee7db939a9",
|
|
18308
|
+
"last_verified": "2026-05-19",
|
|
18309
|
+
"_auto_imported": true,
|
|
18310
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18311
|
+
"_matrix": "ics-attack"
|
|
18312
|
+
},
|
|
18313
|
+
"T0845": {
|
|
18314
|
+
"id": "T0845",
|
|
18315
|
+
"name": "Program Upload",
|
|
18316
|
+
"version": "ics-attack-v15",
|
|
18317
|
+
"tactic": [
|
|
18318
|
+
"Collection (ICS)"
|
|
18319
|
+
],
|
|
18320
|
+
"description": "Adversaries may attempt to upload a program from a PLC to gather information about an industrial process.",
|
|
18321
|
+
"description_full": "Adversaries may attempt to upload a program from a PLC to gather information about an industrial process. Uploading a program may allow them to acquire and study the underlying logic. Methods of program upload include vendor software, which enables the user to upload and read a program running on a PLC. This software can be used to upload the target program to a workstation, jump box, or an interfacing device.",
|
|
18322
|
+
"platforms": [
|
|
18323
|
+
"None"
|
|
18324
|
+
],
|
|
18325
|
+
"detection": null,
|
|
18326
|
+
"reference_url": "https://attack.mitre.org/techniques/T0845",
|
|
18327
|
+
"stix_id": "attack-pattern--3067b85e-271e-4bc5-81ad-ab1a81d411e3",
|
|
18328
|
+
"last_verified": "2026-05-19",
|
|
18329
|
+
"_auto_imported": true,
|
|
18330
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18331
|
+
"_matrix": "ics-attack"
|
|
18332
|
+
},
|
|
18333
|
+
"T0819": {
|
|
18334
|
+
"id": "T0819",
|
|
18335
|
+
"name": "Exploit Public-Facing Application",
|
|
18336
|
+
"version": "ics-attack-v15",
|
|
18337
|
+
"tactic": [
|
|
18338
|
+
"Initial Access (ICS)"
|
|
18339
|
+
],
|
|
18340
|
+
"description": "Adversaries may leverage weaknesses to exploit internet-facing software for initial access into an industrial network.",
|
|
18341
|
+
"description_full": "Adversaries may leverage weaknesses to exploit internet-facing software for initial access into an industrial network. Internet-facing software may be user applications, underlying networking implementations, an assets operating system, weak defenses, etc. Targets of this technique may be intentionally exposed for the purpose of remote management and visibility. An adversary may seek to target public-facing applications as they may provide direct access into an ICS environment or the ability to move into the ICS network. Publicly exposed applications may be found through online tools that scan the internet for open ports and services. Version numbers for the exposed application may provide adversaries an ability to target specific known vulnerabilities. Exposed control protocol or remote access ports found in Commonly Used Port may be of interest by adversaries.",
|
|
18342
|
+
"platforms": [
|
|
18343
|
+
"None"
|
|
18344
|
+
],
|
|
18345
|
+
"detection": null,
|
|
18346
|
+
"reference_url": "https://attack.mitre.org/techniques/T0819",
|
|
18347
|
+
"stix_id": "attack-pattern--32632a95-6856-47b9-9ab7-fea5cd7dce00",
|
|
18348
|
+
"last_verified": "2026-05-19",
|
|
18349
|
+
"_auto_imported": true,
|
|
18350
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18351
|
+
"_matrix": "ics-attack"
|
|
18352
|
+
},
|
|
18353
|
+
"T1691": {
|
|
18354
|
+
"id": "T1691",
|
|
18355
|
+
"name": "Block Operational Technology Message",
|
|
18356
|
+
"version": "ics-attack-v15",
|
|
18357
|
+
"tactic": [
|
|
18358
|
+
"Inhibit Response Function"
|
|
18359
|
+
],
|
|
18360
|
+
"description": "Adversaries may block messages between systems and devices in an OT/ICS environment to disrupt processes.",
|
|
18361
|
+
"description_full": "Adversaries may block messages between systems and devices in an OT/ICS environment to disrupt processes. Messages typically fall into two categories: (1) reporting messages that contain telemetry data about the current state of systems, devices, and processes and (2) command messages that contain instructions to control systems, devices, and processes. Both types of messages are critical for the proper functioning of industrial control processes and failure of the messages to reach their intended destinations could inhibit response functions or create an unsafe condition that could have physical impacts.(Citation: Bonnie Zhu, Anthony Joseph, Shankar Sastry 2011)(Citation: Electricity Information Sharing and Analysis Center; SANS Industrial Control Systems March 2016) Adversaries may block communications by either making modifications to software ([System Firmware](https://attack.mitre.org/techniques/T0857), [Module Firmware](https://attack.mitre.org/techniques/T0839), [Hooking](https://attack.mitre.org/techniques/T0874), and [Rootkit](https://attack.mitre.org/techniques/T0851)) and services ([Service Stop](https://attack.mitre.org/techniques/T0881), [Denial of Service](https://attack.mitre.org/techniques/T0814)) on systems and devices or by positioning themselves between systems and devices and intercepting and blocking the communications such as the case with an [Adversary-in-the-Middle](https://attack.mitre.org/techniques/T0830) attack.",
|
|
18362
|
+
"platforms": [],
|
|
18363
|
+
"detection": null,
|
|
18364
|
+
"reference_url": "https://attack.mitre.org/techniques/T1691",
|
|
18365
|
+
"stix_id": "attack-pattern--338f4364-2269-4f70-9079-b20384b16628",
|
|
18366
|
+
"last_verified": "2026-05-19",
|
|
18367
|
+
"_auto_imported": true,
|
|
18368
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18369
|
+
"_matrix": "ics-attack",
|
|
18370
|
+
"_gap_skip": {
|
|
18371
|
+
"fields": [
|
|
18372
|
+
"platforms"
|
|
18373
|
+
],
|
|
18374
|
+
"reason": "ICS-attack techniques do not carry a platforms field in MITRE STIX — they target the ICS matrix as a whole rather than specific OS/cloud platforms"
|
|
18375
|
+
}
|
|
18376
|
+
},
|
|
18377
|
+
"T0811": {
|
|
18378
|
+
"id": "T0811",
|
|
18379
|
+
"name": "Data from Information Repositories",
|
|
18380
|
+
"version": "ics-attack-v15",
|
|
18381
|
+
"tactic": [
|
|
18382
|
+
"Collection (ICS)"
|
|
18383
|
+
],
|
|
18384
|
+
"description": "Adversaries may target and collect data from information repositories.",
|
|
18385
|
+
"description_full": "Adversaries may target and collect data from information repositories. This can include sensitive data such as specifications, schematics, or diagrams of control system layouts, devices, and processes. Examples of information repositories include reference databases in the process environment, as well as databases in the corporate network that might contain information about the ICS.(Citation: Cybersecurity & Infrastructure Security Agency March 2018) Information collected from these systems may provide the adversary with a better understanding of the operational environment, vendors used, processes, or procedures of the ICS. In a campaign between 2011 and 2013 against ONG organizations, Chinese state-sponsored actors searched document repositories for specific information such as, system manuals, remote terminal unit (RTU) sites, personnel lists, documents that included the string SCAD*, user credentials, and remote dial-up access information. (Citation: CISA AA21-201A Pipeline Intrusion July 2021)",
|
|
18386
|
+
"platforms": [
|
|
18387
|
+
"None"
|
|
18388
|
+
],
|
|
18389
|
+
"detection": null,
|
|
18390
|
+
"reference_url": "https://attack.mitre.org/techniques/T0811",
|
|
18391
|
+
"stix_id": "attack-pattern--3405891b-16aa-4bd7-bd7c-733501f9b20f",
|
|
18392
|
+
"last_verified": "2026-05-19",
|
|
18393
|
+
"_auto_imported": true,
|
|
18394
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18395
|
+
"_matrix": "ics-attack"
|
|
18396
|
+
},
|
|
18397
|
+
"T0864": {
|
|
18398
|
+
"id": "T0864",
|
|
18399
|
+
"name": "Transient Cyber Asset",
|
|
18400
|
+
"version": "ics-attack-v15",
|
|
18401
|
+
"tactic": [
|
|
18402
|
+
"Initial Access (ICS)"
|
|
18403
|
+
],
|
|
18404
|
+
"description": "Adversaries may target devices that are transient across ICS networks and external networks.",
|
|
18405
|
+
"description_full": "Adversaries may target devices that are transient across ICS networks and external networks. Normally, transient assets are brought into an environment by authorized personnel and do not remain in that environment on a permanent basis. (Citation: North American Electric Reliability Corporation June 2021) Transient assets are commonly needed to support management functions and may be more common in systems where a remotely managed asset is not feasible, external connections for remote access do not exist, or 3rd party contractor/vendor access is required. Adversaries may take advantage of transient assets in different ways. For instance, adversaries may target a transient asset when it is connected to an external network and then leverage its trusted access in another environment to launch an attack. They may also take advantage of installed applications and libraries that are used by legitimate end-users to interact with control system devices. Transient assets, in some cases, may not be deployed with a secure configuration leading to weaknesses that could allow an adversary to propagate malicious executable code, e.g., the transient asset may be infected by malware and when connected to an ICS environment the malware propagates onto other systems.",
|
|
18406
|
+
"platforms": [
|
|
18407
|
+
"None"
|
|
18408
|
+
],
|
|
18409
|
+
"detection": null,
|
|
18410
|
+
"reference_url": "https://attack.mitre.org/techniques/T0864",
|
|
18411
|
+
"stix_id": "attack-pattern--35392fb4-a31d-4c6a-b9f2-1c65b7f5e6b9",
|
|
18412
|
+
"last_verified": "2026-05-19",
|
|
18413
|
+
"_auto_imported": true,
|
|
18414
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18415
|
+
"_matrix": "ics-attack"
|
|
18416
|
+
},
|
|
18417
|
+
"T0873.001": {
|
|
18418
|
+
"id": "T0873.001",
|
|
18419
|
+
"name": "Siemens Project File Format",
|
|
18420
|
+
"version": "ics-attack-v15",
|
|
18421
|
+
"tactic": [
|
|
18422
|
+
"Persistence (ICS)"
|
|
18423
|
+
],
|
|
18424
|
+
"description": "Adversaries may infect Siemens PLC project files (i.e., Step 7, WinCC, etc.) to achieve [Execution](https://attack.mitre.org/tactics/TA0104), [Persistence](https://attack.mitre.org/tactics/TA0110), and [Lateral Movement](https://attack.mitre.org/tactics/TA0109) objectives.",
|
|
18425
|
+
"description_full": "Adversaries may infect Siemens PLC project files (i.e., Step 7, WinCC, etc.) to achieve [Execution](https://attack.mitre.org/tactics/TA0104), [Persistence](https://attack.mitre.org/tactics/TA0110), and [Lateral Movement](https://attack.mitre.org/tactics/TA0109) objectives. Adversaries may modify an existing project file or bring their own project files into the environment.(Citation: Nicolas Falliere, Liam O Murchu, Eric Chien February 2011) The ability for an adversary to deploy an infected project file relies on access to a workstation with Siemens PLC programming software installed on it from which a program download can be performed.",
|
|
18426
|
+
"platforms": [],
|
|
18427
|
+
"detection": null,
|
|
18428
|
+
"reference_url": "https://attack.mitre.org/techniques/T0873/001",
|
|
18429
|
+
"stix_id": "attack-pattern--354ca909-b54d-4c41-b597-9c296b344a43",
|
|
18430
|
+
"last_verified": "2026-05-19",
|
|
18431
|
+
"_auto_imported": true,
|
|
18432
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18433
|
+
"_matrix": "ics-attack",
|
|
18434
|
+
"_gap_skip": {
|
|
18435
|
+
"fields": [
|
|
18436
|
+
"platforms"
|
|
18437
|
+
],
|
|
18438
|
+
"reason": "ICS-attack techniques do not carry a platforms field in MITRE STIX — they target the ICS matrix as a whole rather than specific OS/cloud platforms"
|
|
18439
|
+
}
|
|
18440
|
+
},
|
|
18441
|
+
"T0835": {
|
|
18442
|
+
"id": "T0835",
|
|
18443
|
+
"name": "Manipulate I/O Image",
|
|
18444
|
+
"version": "ics-attack-v15",
|
|
18445
|
+
"tactic": [
|
|
18446
|
+
"Inhibit Response Function"
|
|
18447
|
+
],
|
|
18448
|
+
"description": "Adversaries may manipulate the I/O image of PLCs through various means to prevent them from functioning as expected.",
|
|
18449
|
+
"description_full": "Adversaries may manipulate the I/O image of PLCs through various means to prevent them from functioning as expected. Methods of I/O image manipulation may include overriding the I/O table via direct memory manipulation or using the override function used for testing PLC programs. (Citation: Dr. Kelvin T. Erickson December 2010) During the scan cycle, a PLC reads the status of all inputs and stores them in an image table. (Citation: Nanjundaiah, Vaidyanath) The image table is the PLCs internal storage location where values of inputs/outputs for one scan are stored while it executes the user program. After the PLC has solved the entire logic program, it updates the output image table. The contents of this output image table are written to the corresponding output points in I/O Modules. One of the unique characteristics of PLCs is their ability to override the status of a physical discrete input or to override the logic driving a physical output coil and force the output to a desired status.",
|
|
18450
|
+
"platforms": [
|
|
18451
|
+
"None"
|
|
18452
|
+
],
|
|
18453
|
+
"detection": null,
|
|
18454
|
+
"reference_url": "https://attack.mitre.org/techniques/T0835",
|
|
18455
|
+
"stix_id": "attack-pattern--36e9f5bc-ac13-4da4-a2f4-01f4877d9004",
|
|
18456
|
+
"last_verified": "2026-05-19",
|
|
18457
|
+
"_auto_imported": true,
|
|
18458
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18459
|
+
"_matrix": "ics-attack"
|
|
18460
|
+
},
|
|
18461
|
+
"T0842": {
|
|
18462
|
+
"id": "T0842",
|
|
18463
|
+
"name": "Network Sniffing",
|
|
18464
|
+
"version": "ics-attack-v15",
|
|
18465
|
+
"tactic": [
|
|
18466
|
+
"Discovery (ICS)"
|
|
18467
|
+
],
|
|
18468
|
+
"description": "Network sniffing is the practice of using a network interface on a computer system to monitor or capture information (Citation: Enterprise ATT&CK January 2018) regardless of whether it is the specified destination for the information.",
|
|
18469
|
+
"description_full": "Network sniffing is the practice of using a network interface on a computer system to monitor or capture information (Citation: Enterprise ATT&CK January 2018) regardless of whether it is the specified destination for the information. An adversary may attempt to sniff the traffic to gain information about the target. This information can vary in the level of importance. Relatively unimportant information is general communications to and from machines. Relatively important information would be login information. User credentials may be sent over an unencrypted protocol, such as Telnet, that can be captured and obtained through network packet analysis. In addition, ARP and Domain Name Service (DNS) poisoning can be used to capture credentials to websites, proxies, and internal systems by redirecting traffic to an adversary.",
|
|
18470
|
+
"platforms": [
|
|
18471
|
+
"None"
|
|
18472
|
+
],
|
|
18473
|
+
"detection": null,
|
|
18474
|
+
"reference_url": "https://attack.mitre.org/techniques/T0842",
|
|
18475
|
+
"stix_id": "attack-pattern--38213338-1aab-479d-949b-c81b66ccca5c",
|
|
18476
|
+
"last_verified": "2026-05-19",
|
|
18477
|
+
"_auto_imported": true,
|
|
18478
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18479
|
+
"_matrix": "ics-attack"
|
|
18480
|
+
},
|
|
18481
|
+
"T0851": {
|
|
18482
|
+
"id": "T0851",
|
|
18483
|
+
"name": "Rootkit",
|
|
18484
|
+
"version": "ics-attack-v15",
|
|
18485
|
+
"tactic": [
|
|
18486
|
+
"Evasion (ICS)",
|
|
18487
|
+
"Inhibit Response Function"
|
|
18488
|
+
],
|
|
18489
|
+
"description": "Adversaries may deploy rootkits to hide the presence of programs, files, network connections, services, drivers, and other system components.",
|
|
18490
|
+
"description_full": "Adversaries may deploy rootkits to hide the presence of programs, files, network connections, services, drivers, and other system components. Rootkits are programs that hide the existence of malware by intercepting and modifying operating-system API calls that supply system information. Rootkits or rootkit-enabling functionality may reside at the user or kernel level in the operating system, or lower. (Citation: Enterprise ATT&CK January 2018) Firmware rootkits that affect the operating system yield nearly full control of the system. While firmware rootkits are normally developed for the main processing board, they can also be developed for the I/O that is attached to an asset. Compromise of this firmware allows the modification of all of the process variables and functions the module engages in. This may result in commands being disregarded and false information being fed to the main device. By tampering with device processes, an adversary may inhibit its expected response functions and possibly enable [Impact](https://attack.mitre.org/tactics/TA0105).",
|
|
18491
|
+
"platforms": [
|
|
18492
|
+
"None"
|
|
18493
|
+
],
|
|
18494
|
+
"detection": null,
|
|
18495
|
+
"reference_url": "https://attack.mitre.org/techniques/T0851",
|
|
18496
|
+
"stix_id": "attack-pattern--3b6b9246-43f8-4c69-ad7a-2b11cfe0a0d9",
|
|
18497
|
+
"last_verified": "2026-05-19",
|
|
18498
|
+
"_auto_imported": true,
|
|
18499
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18500
|
+
"_matrix": "ics-attack"
|
|
18501
|
+
},
|
|
18502
|
+
"T0802": {
|
|
18503
|
+
"id": "T0802",
|
|
18504
|
+
"name": "Automated Collection",
|
|
18505
|
+
"version": "ics-attack-v15",
|
|
18506
|
+
"tactic": [
|
|
18507
|
+
"Collection (ICS)"
|
|
18508
|
+
],
|
|
18509
|
+
"description": "Adversaries may automate collection of industrial environment information using tools or scripts.",
|
|
18510
|
+
"description_full": "Adversaries may automate collection of industrial environment information using tools or scripts. This automated collection may leverage native control protocols and tools available in the control systems environment. For example, the OPC protocol may be used to enumerate and gather information. Access to a system or interface with these native protocols may allow collection and enumeration of other attached, communicating servers and devices.",
|
|
18511
|
+
"platforms": [
|
|
18512
|
+
"None"
|
|
18513
|
+
],
|
|
18514
|
+
"detection": null,
|
|
18515
|
+
"reference_url": "https://attack.mitre.org/techniques/T0802",
|
|
18516
|
+
"stix_id": "attack-pattern--3de230d4-3e42-4041-b089-17e1128feded",
|
|
18517
|
+
"last_verified": "2026-05-19",
|
|
18518
|
+
"_auto_imported": true,
|
|
18519
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18520
|
+
"_matrix": "ics-attack"
|
|
18521
|
+
},
|
|
18522
|
+
"T1694": {
|
|
18523
|
+
"id": "T1694",
|
|
18524
|
+
"name": "Insecure Credentials",
|
|
18525
|
+
"version": "ics-attack-v15",
|
|
18526
|
+
"tactic": [
|
|
18527
|
+
"Persistence (ICS)",
|
|
18528
|
+
"Lateral Movement (ICS)"
|
|
18529
|
+
],
|
|
18530
|
+
"description": "Adversaries may target insecure credentials as a means to persist on a system or device or move laterally from one system or device to another.",
|
|
18531
|
+
"description_full": "Adversaries may target insecure credentials as a means to persist on a system or device or move laterally from one system or device to another. Insecure credentials may appear as default credentials which are pre-configured credentials on a system, device, or software that are well-known in documentation or hard-coded credentials which are built into the system, device, or software that cannot be changed or not easily changed because of the impact on control processes.(Citation: NIST SP 800-82r3)(Citation: ICS-ALERT-13-164-01)(Citation: OT IceFall) Adversaries often times use insecure credentials to evade detection as they are typically forgotten about by system and device owners.",
|
|
18532
|
+
"platforms": [],
|
|
18533
|
+
"detection": null,
|
|
18534
|
+
"reference_url": "https://attack.mitre.org/techniques/T1694",
|
|
18535
|
+
"stix_id": "attack-pattern--3e9b182e-e493-49e1-9a9b-bd0dfcd34a7c",
|
|
18536
|
+
"last_verified": "2026-05-19",
|
|
18537
|
+
"_auto_imported": true,
|
|
18538
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18539
|
+
"_matrix": "ics-attack",
|
|
18540
|
+
"_gap_skip": {
|
|
18541
|
+
"fields": [
|
|
18542
|
+
"platforms"
|
|
18543
|
+
],
|
|
18544
|
+
"reason": "ICS-attack techniques do not carry a platforms field in MITRE STIX — they target the ICS matrix as a whole rather than specific OS/cloud platforms"
|
|
18545
|
+
}
|
|
18546
|
+
},
|
|
18547
|
+
"T1692.001": {
|
|
18548
|
+
"id": "T1692.001",
|
|
18549
|
+
"name": "Command Message",
|
|
18550
|
+
"version": "ics-attack-v15",
|
|
18551
|
+
"tactic": [
|
|
18552
|
+
"Evasion (ICS)",
|
|
18553
|
+
"Impair Process Control"
|
|
18554
|
+
],
|
|
18555
|
+
"description": "Adversaries may send unauthorized command messages to instruct control system assets to perform actions outside of their intended functionality, or without the logical preconditions to trigger their expected function.",
|
|
18556
|
+
"description_full": "Adversaries may send unauthorized command messages to instruct control system assets to perform actions outside of their intended functionality, or without the logical preconditions to trigger their expected function. Command messages are used in ICS networks to give direct instructions to control systems devices. If an adversary can send an unauthorized command message to a control system, then it can instruct the control systems device to perform an action outside the normal bounds of the device's actions. An adversary could potentially instruct a control systems device to perform an action that will cause an [Impact](https://attack.mitre.org/tactics/TA0105).(Citation: Bonnie Zhu, Anthony Joseph, Shankar Sastry 2011) In the Dallas Siren incident, adversaries were able to send command messages to activate tornado alarm systems across the city without an impending tornado or other disaster.(Citation: Zack Whittaker April 2017)(Citation: Benjamin Freed March 2019)",
|
|
18557
|
+
"platforms": [],
|
|
18558
|
+
"detection": null,
|
|
18559
|
+
"reference_url": "https://attack.mitre.org/techniques/T1692/001",
|
|
18560
|
+
"stix_id": "attack-pattern--4344d1b8-968b-4697-9ab9-f9abe5f52265",
|
|
18561
|
+
"last_verified": "2026-05-19",
|
|
18562
|
+
"_auto_imported": true,
|
|
18563
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18564
|
+
"_matrix": "ics-attack",
|
|
18565
|
+
"_gap_skip": {
|
|
18566
|
+
"fields": [
|
|
18567
|
+
"platforms"
|
|
18568
|
+
],
|
|
18569
|
+
"reason": "ICS-attack techniques do not carry a platforms field in MITRE STIX — they target the ICS matrix as a whole rather than specific OS/cloud platforms"
|
|
18570
|
+
}
|
|
18571
|
+
},
|
|
18572
|
+
"T0809": {
|
|
18573
|
+
"id": "T0809",
|
|
18574
|
+
"name": "Data Destruction",
|
|
18575
|
+
"version": "ics-attack-v15",
|
|
18576
|
+
"tactic": [
|
|
18577
|
+
"Inhibit Response Function"
|
|
18578
|
+
],
|
|
18579
|
+
"description": "Adversaries may perform data destruction over the course of an operation.",
|
|
18580
|
+
"description_full": "Adversaries may perform data destruction over the course of an operation. The adversary may drop or create malware, tools, or other non-native files on a target system to accomplish this, potentially leaving behind traces of malicious activities. Such non-native files and other data may be removed over the course of an intrusion to maintain a small footprint or as a standard part of the post-intrusion cleanup process. (Citation: Enterprise ATT&CK January 2018) Data destruction may also be used to render operator interfaces unable to respond and to disrupt response functions from occurring as expected. An adversary may also destroy data backups that are vital to recovery after an incident. Standard file deletion commands are available on most operating system and device interfaces to perform cleanup, but adversaries may use other tools as well. Two examples are Windows Sysinternals SDelete and Active@ Killdisk.",
|
|
18581
|
+
"platforms": [
|
|
18582
|
+
"None"
|
|
18583
|
+
],
|
|
18584
|
+
"detection": null,
|
|
18585
|
+
"reference_url": "https://attack.mitre.org/techniques/T0809",
|
|
18586
|
+
"stix_id": "attack-pattern--493832d9-cea6-4b63-abe7-9a65a6473675",
|
|
18587
|
+
"last_verified": "2026-05-19",
|
|
18588
|
+
"_auto_imported": true,
|
|
18589
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18590
|
+
"_matrix": "ics-attack"
|
|
18591
|
+
},
|
|
18592
|
+
"T0832": {
|
|
18593
|
+
"id": "T0832",
|
|
18594
|
+
"name": "Manipulation of View",
|
|
18595
|
+
"version": "ics-attack-v15",
|
|
18596
|
+
"tactic": [
|
|
18597
|
+
"Impact (ICS)"
|
|
18598
|
+
],
|
|
18599
|
+
"description": "Adversaries may attempt to manipulate the information reported back to operators or controllers.",
|
|
18600
|
+
"description_full": "Adversaries may attempt to manipulate the information reported back to operators or controllers. This manipulation may be short term or sustained. During this time the process itself could be in a much different state than what is reported. (Citation: Corero) (Citation: Michael J. Assante and Robert M. Lee) (Citation: Tyson Macaulay) Operators may be fooled into doing something that is harmful to the system in a loss of view situation. With a manipulated view into the systems, operators may issue inappropriate control sequences that introduce faults or catastrophic failures into the system. Business analysis systems can also be provided with inaccurate data leading to bad management decisions.",
|
|
18601
|
+
"platforms": [
|
|
18602
|
+
"None"
|
|
18603
|
+
],
|
|
18604
|
+
"detection": null,
|
|
18605
|
+
"reference_url": "https://attack.mitre.org/techniques/T0832",
|
|
18606
|
+
"stix_id": "attack-pattern--4c2e1408-9d68-4187-8e6b-a77bc52700ec",
|
|
18607
|
+
"last_verified": "2026-05-19",
|
|
18608
|
+
"_auto_imported": true,
|
|
18609
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18610
|
+
"_matrix": "ics-attack"
|
|
18611
|
+
},
|
|
18612
|
+
"T1692.002": {
|
|
18613
|
+
"id": "T1692.002",
|
|
18614
|
+
"name": "Reporting Message",
|
|
18615
|
+
"version": "ics-attack-v15",
|
|
18616
|
+
"tactic": [
|
|
18617
|
+
"Evasion (ICS)",
|
|
18618
|
+
"Impair Process Control"
|
|
18619
|
+
],
|
|
18620
|
+
"description": "Adversaries may spoof reporting messages in control system environments for evasion and to impair process control.",
|
|
18621
|
+
"description_full": "Adversaries may spoof reporting messages in control system environments for evasion and to impair process control. In control systems, reporting messages contain telemetry data (e.g., I/O values) pertaining to the current state of equipment and the industrial process. Reporting messages are important for monitoring the normal operation of a system or identifying important events such as deviations from expected values. If an adversary has the ability to Spoof Reporting Messages, they can impact the control system in many ways. The adversary can Spoof Reporting Messages that state that the process is operating normally, as a form of evasion. The adversary could also Spoof Reporting Messages to make the defenders and operators think that other errors are occurring in order to distract them from the actual source of a problem.(Citation: Bonnie Zhu, Anthony Joseph, Shankar Sastry 2011)",
|
|
18622
|
+
"platforms": [],
|
|
18623
|
+
"detection": null,
|
|
18624
|
+
"reference_url": "https://attack.mitre.org/techniques/T1692/002",
|
|
18625
|
+
"stix_id": "attack-pattern--527106b3-95a2-4ed2-bf89-db7f0e4d0da0",
|
|
18626
|
+
"last_verified": "2026-05-19",
|
|
18627
|
+
"_auto_imported": true,
|
|
18628
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18629
|
+
"_matrix": "ics-attack",
|
|
18630
|
+
"_gap_skip": {
|
|
18631
|
+
"fields": [
|
|
18632
|
+
"platforms"
|
|
18633
|
+
],
|
|
18634
|
+
"reason": "ICS-attack techniques do not carry a platforms field in MITRE STIX — they target the ICS matrix as a whole rather than specific OS/cloud platforms"
|
|
18635
|
+
}
|
|
18636
|
+
},
|
|
18637
|
+
"T0872": {
|
|
18638
|
+
"id": "T0872",
|
|
18639
|
+
"name": "Indicator Removal on Host",
|
|
18640
|
+
"version": "ics-attack-v15",
|
|
18641
|
+
"tactic": [
|
|
18642
|
+
"Evasion (ICS)"
|
|
18643
|
+
],
|
|
18644
|
+
"description": "Adversaries may attempt to remove indicators of their presence on a system in an effort to cover their tracks.",
|
|
18645
|
+
"description_full": "Adversaries may attempt to remove indicators of their presence on a system in an effort to cover their tracks. In cases where an adversary may feel detection is imminent, they may try to overwrite, delete, or cover up changes they have made to the device.",
|
|
18646
|
+
"platforms": [
|
|
18647
|
+
"None"
|
|
18648
|
+
],
|
|
18649
|
+
"detection": null,
|
|
18650
|
+
"reference_url": "https://attack.mitre.org/techniques/T0872",
|
|
18651
|
+
"stix_id": "attack-pattern--53a26eee-1080-4d17-9762-2027d5a1b805",
|
|
18652
|
+
"last_verified": "2026-05-19",
|
|
18653
|
+
"_auto_imported": true,
|
|
18654
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18655
|
+
"_matrix": "ics-attack"
|
|
18656
|
+
},
|
|
18657
|
+
"T0877": {
|
|
18658
|
+
"id": "T0877",
|
|
18659
|
+
"name": "I/O Image",
|
|
18660
|
+
"version": "ics-attack-v15",
|
|
18661
|
+
"tactic": [
|
|
18662
|
+
"Collection (ICS)"
|
|
18663
|
+
],
|
|
18664
|
+
"description": "Adversaries may seek to capture process values related to the inputs and outputs of a PLC.",
|
|
18665
|
+
"description_full": "Adversaries may seek to capture process values related to the inputs and outputs of a PLC. During the scan cycle, a PLC reads the status of all inputs and stores them in an image table. (Citation: Nanjundaiah, Vaidyanath) The image table is the PLCs internal storage location where values of inputs/outputs for one scan are stored while it executes the user program. After the PLC has solved the entire logic program, it updates the output image table. The contents of this output image table are written to the corresponding output points in I/O Modules. The Input and Output Image tables described above make up the I/O Image on a PLC. This image is used by the user program instead of directly interacting with physical I/O. (Citation: Spenneberg, Ralf 2016) Adversaries may collect the I/O Image state of a PLC by utilizing a devices [Native API](https://attack.mitre.org/techniques/T0834) to access the memory regions directly. The collection of the PLCs I/O state could be used to replace values or inform future stages of an attack.",
|
|
18666
|
+
"platforms": [
|
|
18667
|
+
"None"
|
|
18668
|
+
],
|
|
18669
|
+
"detection": null,
|
|
18670
|
+
"reference_url": "https://attack.mitre.org/techniques/T0877",
|
|
18671
|
+
"stix_id": "attack-pattern--53a48c74-0025-45f4-b04a-baa853df8204",
|
|
18672
|
+
"last_verified": "2026-05-19",
|
|
18673
|
+
"_auto_imported": true,
|
|
18674
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18675
|
+
"_matrix": "ics-attack"
|
|
18676
|
+
},
|
|
18677
|
+
"T1695.001": {
|
|
18678
|
+
"id": "T1695.001",
|
|
18679
|
+
"name": "Serial COM",
|
|
18680
|
+
"version": "ics-attack-v15",
|
|
18681
|
+
"tactic": [
|
|
18682
|
+
"Inhibit Response Function"
|
|
18683
|
+
],
|
|
18684
|
+
"description": "Adversaries may block access to serial COM to prevent instructions or configurations from reaching target devices.",
|
|
18685
|
+
"description_full": "Adversaries may block access to serial COM to prevent instructions or configurations from reaching target devices. Serial Communication ports (COM) allow communication with control system devices. Devices can receive command and configuration messages over such serial COM. Devices also use serial COM to send command and reporting messages. Blocking device serial COM may also block command messages and block reporting messages. A serial to Ethernet converter is often connected to a serial COM to facilitate communication between serial and Ethernet devices. One approach to blocking a serial COM would be to create and hold open a TCP session with the Ethernet side of the converter. A serial to Ethernet converter may have a few ports open to facilitate multiple communications. For example, if there are three serial COM available -- 1, 2 and 3 --, the converter might be listening on the corresponding ports 20001, 20002, and 20003. If a TCP/IP connection is opened with one of these ports and held open, then the port will be unavailable for use by another party. One way the adversary could achieve this would be to initiate a TCP session with the serial to Ethernet converter at 10.0.0.1 via Telnet on serial port 1 with the following command: telnet 10.0.0.1 20001.",
|
|
18686
|
+
"platforms": [],
|
|
18687
|
+
"detection": null,
|
|
18688
|
+
"reference_url": "https://attack.mitre.org/techniques/T1695/001",
|
|
18689
|
+
"stix_id": "attack-pattern--55e7e5c1-3760-4451-bae0-e79b29f452c5",
|
|
18690
|
+
"last_verified": "2026-05-19",
|
|
18691
|
+
"_auto_imported": true,
|
|
18692
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18693
|
+
"_matrix": "ics-attack",
|
|
18694
|
+
"_gap_skip": {
|
|
18695
|
+
"fields": [
|
|
18696
|
+
"platforms"
|
|
18697
|
+
],
|
|
18698
|
+
"reason": "ICS-attack techniques do not carry a platforms field in MITRE STIX — they target the ICS matrix as a whole rather than specific OS/cloud platforms"
|
|
18699
|
+
}
|
|
18700
|
+
},
|
|
18701
|
+
"T1694.001": {
|
|
18702
|
+
"id": "T1694.001",
|
|
18703
|
+
"name": "Default Credentials",
|
|
18704
|
+
"version": "ics-attack-v15",
|
|
18705
|
+
"tactic": [
|
|
18706
|
+
"Persistence (ICS)",
|
|
18707
|
+
"Lateral Movement (ICS)"
|
|
18708
|
+
],
|
|
18709
|
+
"description": "Adversaries may leverage manufacturer or supplier set default credentials on control system devices.",
|
|
18710
|
+
"description_full": "Adversaries may leverage manufacturer or supplier set default credentials on control system devices. These default credentials may have administrative permissions and may be necessary for initial configuration of the device. It is general best practice to change the passwords for these accounts as soon as possible, but some manufacturers may have devices that have passwords or usernames that cannot be changed.(Citation: Keith Stouffer May 2015) Default credentials are normally documented in an instruction manual that is either packaged with the device, published online through official means, or published online through unofficial means. Adversaries may leverage default credentials that have not been properly modified or disabled.",
|
|
18711
|
+
"platforms": [],
|
|
18712
|
+
"detection": null,
|
|
18713
|
+
"reference_url": "https://attack.mitre.org/techniques/T1694/001",
|
|
18714
|
+
"stix_id": "attack-pattern--5658ad88-7510-490e-a351-95d50b1bcd91",
|
|
18715
|
+
"last_verified": "2026-05-19",
|
|
18716
|
+
"_auto_imported": true,
|
|
18717
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18718
|
+
"_matrix": "ics-attack",
|
|
18719
|
+
"_gap_skip": {
|
|
18720
|
+
"fields": [
|
|
18721
|
+
"platforms"
|
|
18722
|
+
],
|
|
18723
|
+
"reason": "ICS-attack techniques do not carry a platforms field in MITRE STIX — they target the ICS matrix as a whole rather than specific OS/cloud platforms"
|
|
18724
|
+
}
|
|
18725
|
+
},
|
|
18726
|
+
"T0815": {
|
|
18727
|
+
"id": "T0815",
|
|
18728
|
+
"name": "Denial of View",
|
|
18729
|
+
"version": "ics-attack-v15",
|
|
18730
|
+
"tactic": [
|
|
18731
|
+
"Impact (ICS)"
|
|
18732
|
+
],
|
|
18733
|
+
"description": "Adversaries may cause a denial of view in attempt to disrupt and prevent operator oversight on the status of an ICS environment.",
|
|
18734
|
+
"description_full": "Adversaries may cause a denial of view in attempt to disrupt and prevent operator oversight on the status of an ICS environment. This may manifest itself as a temporary communication failure between a device and its control source, where the interface recovers and becomes available once the interference ceases. (Citation: Corero) (Citation: Michael J. Assante and Robert M. Lee) (Citation: Tyson Macaulay) An adversary may attempt to deny operator visibility by preventing them from receiving status and reporting messages. Denying this view may temporarily block and prevent operators from noticing a change in state or anomalous behavior. The environment's data and processes may still be operational, but functioning in an unintended or adversarial manner.",
|
|
18735
|
+
"platforms": [
|
|
18736
|
+
"None"
|
|
18737
|
+
],
|
|
18738
|
+
"detection": null,
|
|
18739
|
+
"reference_url": "https://attack.mitre.org/techniques/T0815",
|
|
18740
|
+
"stix_id": "attack-pattern--56ddc820-6cfb-407f-850b-52c035d123ac",
|
|
18741
|
+
"last_verified": "2026-05-19",
|
|
18742
|
+
"_auto_imported": true,
|
|
18743
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18744
|
+
"_matrix": "ics-attack"
|
|
18745
|
+
},
|
|
18746
|
+
"T0843.003": {
|
|
18747
|
+
"id": "T0843.003",
|
|
18748
|
+
"name": "Program Append",
|
|
18749
|
+
"version": "ics-attack-v15",
|
|
18750
|
+
"tactic": [
|
|
18751
|
+
"Lateral Movement (ICS)"
|
|
18752
|
+
],
|
|
18753
|
+
"description": "Adversaries may execute a program append to a PLC to update parts of an existing program.",
|
|
18754
|
+
"description_full": "Adversaries may execute a program append to a PLC to update parts of an existing program. It may or may not require stopping the PLC which may allow it to continue running during transfer and reconfiguration without interruption to process control. Adversaries may leverage this approach to minimize downtime and evade detection. The ability to perform a program append to the PLC typically relies on access to a workstation with the vendor-specific PLC programming software installed.",
|
|
18755
|
+
"platforms": [],
|
|
18756
|
+
"detection": null,
|
|
18757
|
+
"reference_url": "https://attack.mitre.org/techniques/T0843/003",
|
|
18758
|
+
"stix_id": "attack-pattern--574d5bfb-9a7a-4b28-ab5c-743ac704c135",
|
|
18759
|
+
"last_verified": "2026-05-19",
|
|
18760
|
+
"_auto_imported": true,
|
|
18761
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18762
|
+
"_matrix": "ics-attack",
|
|
18763
|
+
"_gap_skip": {
|
|
18764
|
+
"fields": [
|
|
18765
|
+
"platforms"
|
|
18766
|
+
],
|
|
18767
|
+
"reason": "ICS-attack techniques do not carry a platforms field in MITRE STIX — they target the ICS matrix as a whole rather than specific OS/cloud platforms"
|
|
18768
|
+
}
|
|
18769
|
+
},
|
|
18770
|
+
"T0871": {
|
|
18771
|
+
"id": "T0871",
|
|
18772
|
+
"name": "Execution through API",
|
|
18773
|
+
"version": "ics-attack-v15",
|
|
18774
|
+
"tactic": [
|
|
18775
|
+
"Execution (ICS)"
|
|
18776
|
+
],
|
|
18777
|
+
"description": "Adversaries may attempt to leverage Application Program Interfaces (APIs) used for communication between control software and the hardware.",
|
|
18778
|
+
"description_full": "Adversaries may attempt to leverage Application Program Interfaces (APIs) used for communication between control software and the hardware. Specific functionality is often coded into APIs which can be called by software to engage specific functions on a device or other software.",
|
|
18779
|
+
"platforms": [
|
|
18780
|
+
"None"
|
|
18781
|
+
],
|
|
18782
|
+
"detection": null,
|
|
18783
|
+
"reference_url": "https://attack.mitre.org/techniques/T0871",
|
|
18784
|
+
"stix_id": "attack-pattern--5a2610f6-9fff-41e1-bc27-575ca20383d4",
|
|
18785
|
+
"last_verified": "2026-05-19",
|
|
18786
|
+
"_auto_imported": true,
|
|
18787
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18788
|
+
"_matrix": "ics-attack"
|
|
18789
|
+
},
|
|
18790
|
+
"T0846.001": {
|
|
18791
|
+
"id": "T0846.001",
|
|
18792
|
+
"name": "Port Scan",
|
|
18793
|
+
"version": "ics-attack-v15",
|
|
18794
|
+
"tactic": [
|
|
18795
|
+
"Discovery (ICS)"
|
|
18796
|
+
],
|
|
18797
|
+
"description": "Adversaries may perform a port scan on a system, device, or network to identify live hosts, enumerate open ports and running services, identify operating systems, and map out the network.(Citation: NIST SP 800-82r3) The results of a port scan may inform adversary [Discovery](https://attack.mitre.org/tactics/TA0102), [Lateral Movement](https://attack.mitre.org/tactics/TA0109), and vulnerability exploitation decisions ([Exploitation for Evasion](https://attack.mitre.org/techniques/T0820), [Expl...",
|
|
18798
|
+
"description_full": "Adversaries may perform a port scan on a system, device, or network to identify live hosts, enumerate open ports and running services, identify operating systems, and map out the network.(Citation: NIST SP 800-82r3) The results of a port scan may inform adversary [Discovery](https://attack.mitre.org/tactics/TA0102), [Lateral Movement](https://attack.mitre.org/tactics/TA0109), and vulnerability exploitation decisions ([Exploitation for Evasion](https://attack.mitre.org/techniques/T0820), [Exploitation for Privilege Escalation](https://attack.mitre.org/techniques/T0890), [Exploitation of Remote Services](https://attack.mitre.org/techniques/T0866)). Some common tools for executing a port scan include `nmap`, `netcat`, and the Advanced Port Scanner.",
|
|
18799
|
+
"platforms": [],
|
|
18800
|
+
"detection": null,
|
|
18801
|
+
"reference_url": "https://attack.mitre.org/techniques/T0846/001",
|
|
18802
|
+
"stix_id": "attack-pattern--5d24bb1d-4487-4923-ae3a-8e679092ac7a",
|
|
18803
|
+
"last_verified": "2026-05-19",
|
|
18804
|
+
"_auto_imported": true,
|
|
18805
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18806
|
+
"_matrix": "ics-attack",
|
|
18807
|
+
"_gap_skip": {
|
|
18808
|
+
"fields": [
|
|
18809
|
+
"platforms"
|
|
18810
|
+
],
|
|
18811
|
+
"reason": "ICS-attack techniques do not carry a platforms field in MITRE STIX — they target the ICS matrix as a whole rather than specific OS/cloud platforms"
|
|
18812
|
+
}
|
|
18813
|
+
},
|
|
18814
|
+
"T0862": {
|
|
18815
|
+
"id": "T0862",
|
|
18816
|
+
"name": "Supply Chain Compromise",
|
|
18817
|
+
"version": "ics-attack-v15",
|
|
18818
|
+
"tactic": [
|
|
18819
|
+
"Initial Access (ICS)"
|
|
18820
|
+
],
|
|
18821
|
+
"description": "Adversaries may perform supply chain compromise to gain control systems environment access by means of infected products, software, and workflows.",
|
|
18822
|
+
"description_full": "Adversaries may perform supply chain compromise to gain control systems environment access by means of infected products, software, and workflows. Supply chain compromise is the manipulation of products, such as devices or software, or their delivery mechanisms before receipt by the end consumer. Adversary compromise of these products and mechanisms is done for the goal of data or system compromise, once infected products are introduced to the target environment. Supply chain compromise can occur at all stages of the supply chain, from manipulation of development tools and environments to manipulation of developed products and tools distribution mechanisms. This may involve the compromise and replacement of legitimate software and patches, such as on third party or vendor websites. Targeting of supply chain compromise can be done in attempts to infiltrate the environments of a specific audience. In control systems environments with assets in both the IT and OT networks, it is possible a supply chain compromise affecting the IT environment could enable further access to the OT environment. Counterfeit devices may be introduced to the global supply chain posing safety and cyber risks to asset owners and operators. These devices may not meet the safety, engineering and manufacturing requirements of regulatory bodies but may feature tagging indicating conformance with industry standards. Due to the lack of adherence to standards and overall lesser quality, the counterfeit products may pose a serious safety and operational risk. (Citation: Control Global May 2019) Yokogawa identified instances in which their customers received counterfeit differential pressure transmitters using the Yokogawa logo. The counterfeit transmitters were nearly indistinguishable with a semblance of functionality and interface that mimics the genuine product. (Citation: Control Global May 2019) F-Secure Labs analyzed the approach the adversary used to compromise victim systems with Havex. (Citation: Daavid Hentunen, Antti Tikkanen June 2014) The adversary planted trojanized software installers available on legitimate ICS/SCADA vendor websites. After being downloaded, this software infected the host computer with a Remote Access Trojan (RAT).",
|
|
18823
|
+
"platforms": [
|
|
18824
|
+
"None"
|
|
18825
|
+
],
|
|
18826
|
+
"detection": null,
|
|
18827
|
+
"reference_url": "https://attack.mitre.org/techniques/T0862",
|
|
18828
|
+
"stix_id": "attack-pattern--5e0f75da-e108-4688-a6de-a4f07cc2cbe3",
|
|
18829
|
+
"last_verified": "2026-05-19",
|
|
18830
|
+
"_auto_imported": true,
|
|
18831
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18832
|
+
"_matrix": "ics-attack"
|
|
18833
|
+
},
|
|
18834
|
+
"T0880": {
|
|
18835
|
+
"id": "T0880",
|
|
18836
|
+
"name": "Loss of Safety",
|
|
18837
|
+
"version": "ics-attack-v15",
|
|
18838
|
+
"tactic": [
|
|
18839
|
+
"Impact (ICS)"
|
|
18840
|
+
],
|
|
18841
|
+
"description": "Adversaries may compromise safety system functions designed to maintain safe operation of a process when unacceptable or dangerous conditions occur.",
|
|
18842
|
+
"description_full": "Adversaries may compromise safety system functions designed to maintain safe operation of a process when unacceptable or dangerous conditions occur. Safety systems are often composed of the same elements as control systems but have the sole purpose of ensuring the process fails in a predetermined safe manner. Many unsafe conditions in process control happen too quickly for a human operator to react to. Speed is critical in correcting these conditions to limit serious impacts such as Loss of Control and Property Damage. Adversaries may target and disable safety system functions as a prerequisite to subsequent attack execution or to allow for future unsafe conditionals to go unchecked. Detection of a Loss of Safety by operators can result in the shutdown of a process due to strict policies regarding safety systems. This can cause a Loss of Productivity and Revenue and may meet the technical goals of adversaries seeking to cause process disruptions.",
|
|
18843
|
+
"platforms": [
|
|
18844
|
+
"None"
|
|
18845
|
+
],
|
|
18846
|
+
"detection": null,
|
|
18847
|
+
"reference_url": "https://attack.mitre.org/techniques/T0880",
|
|
18848
|
+
"stix_id": "attack-pattern--5fa00fdd-4a55-4191-94a0-564181d7fec2",
|
|
18849
|
+
"last_verified": "2026-05-19",
|
|
18850
|
+
"_auto_imported": true,
|
|
18851
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18852
|
+
"_matrix": "ics-attack"
|
|
18853
|
+
},
|
|
18854
|
+
"T1695.002": {
|
|
18855
|
+
"id": "T1695.002",
|
|
18856
|
+
"name": "Ethernet",
|
|
18857
|
+
"version": "ics-attack-v15",
|
|
18858
|
+
"tactic": [
|
|
18859
|
+
"Inhibit Response Function"
|
|
18860
|
+
],
|
|
18861
|
+
"description": "Adversaries may block access to Ethernet communications to prevent instructions or configurations messages from reaching target systems and devices.",
|
|
18862
|
+
"description_full": "Adversaries may block access to Ethernet communications to prevent instructions or configurations messages from reaching target systems and devices. Ethernet connections allow for communications between IT and OT systems and devices. Blocking Ethernet communications may also block command and reporting messages.(Citation: Bonnie Zhu, Anthony Joseph, Shankar Sastry 2011) An adversary may block Ethernet communications by disabling network interfaces, [Service Stop](https://attack.mitre.org/techniques/T0881), or conducting an [Adversary-in-the-Middle](https://attack.mitre.org/techniques/T0830) attack and dropping the network traffic.",
|
|
18863
|
+
"platforms": [],
|
|
18864
|
+
"detection": null,
|
|
18865
|
+
"reference_url": "https://attack.mitre.org/techniques/T1695/002",
|
|
18866
|
+
"stix_id": "attack-pattern--6008c1f0-1b68-4614-8f5b-a547436b8855",
|
|
18867
|
+
"last_verified": "2026-05-19",
|
|
18868
|
+
"_auto_imported": true,
|
|
18869
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18870
|
+
"_matrix": "ics-attack",
|
|
18871
|
+
"_gap_skip": {
|
|
18872
|
+
"fields": [
|
|
18873
|
+
"platforms"
|
|
18874
|
+
],
|
|
18875
|
+
"reason": "ICS-attack techniques do not carry a platforms field in MITRE STIX — they target the ICS matrix as a whole rather than specific OS/cloud platforms"
|
|
18876
|
+
}
|
|
18877
|
+
},
|
|
18878
|
+
"T0828": {
|
|
18879
|
+
"id": "T0828",
|
|
18880
|
+
"name": "Loss of Productivity and Revenue",
|
|
18881
|
+
"version": "ics-attack-v15",
|
|
18882
|
+
"tactic": [
|
|
18883
|
+
"Impact (ICS)"
|
|
18884
|
+
],
|
|
18885
|
+
"description": "Adversaries may cause loss of productivity and revenue through disruption and even damage to the availability and integrity of control system operations, devices, and related processes.",
|
|
18886
|
+
"description_full": "Adversaries may cause loss of productivity and revenue through disruption and even damage to the availability and integrity of control system operations, devices, and related processes. This technique may manifest as a direct effect of an ICS-targeting attack or tangentially, due to an IT-targeting attack against non-segregated environments. In cases where these operations or services are brought to a halt, the loss of productivity may eventually present an impact for the end-users or consumers of products and services. The disrupted supply-chain may result in supply shortages and increased prices, among other consequences. A ransomware attack on an Australian beverage company resulted in the shutdown of some manufacturing sites, including precautionary halts to protect key systems. (Citation: Paganini, Pierluigi June 2020) The company announced the potential for temporary shortages of their products following the attack. (Citation: Paganini, Pierluigi June 2020) (Citation: Lion Corporation June 2020) In the 2021 Colonial Pipeline ransomware incident, the pipeline was unable to transport approximately 2.5 million barrels of fuel per day to the East Coast. (Citation: Colonial Pipeline Company May 2021)",
|
|
18887
|
+
"platforms": [
|
|
18888
|
+
"None"
|
|
18889
|
+
],
|
|
18890
|
+
"detection": null,
|
|
18891
|
+
"reference_url": "https://attack.mitre.org/techniques/T0828",
|
|
18892
|
+
"stix_id": "attack-pattern--63b6942d-8359-4506-bfb3-cf87aa8120ee",
|
|
18893
|
+
"last_verified": "2026-05-19",
|
|
18894
|
+
"_auto_imported": true,
|
|
18895
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18896
|
+
"_matrix": "ics-attack"
|
|
18897
|
+
},
|
|
18898
|
+
"T0865": {
|
|
18899
|
+
"id": "T0865",
|
|
18900
|
+
"name": "Spearphishing Attachment",
|
|
18901
|
+
"version": "ics-attack-v15",
|
|
18902
|
+
"tactic": [
|
|
18903
|
+
"Initial Access (ICS)"
|
|
18904
|
+
],
|
|
18905
|
+
"description": "Adversaries may use a spearphishing attachment, a variant of spearphishing, as a form of a social engineering attack against specific targets.",
|
|
18906
|
+
"description_full": "Adversaries may use a spearphishing attachment, a variant of spearphishing, as a form of a social engineering attack against specific targets. Spearphishing attachments are different from other forms of spearphishing in that they employ malware attached to an email. All forms of spearphishing are electronically delivered and target a specific individual, company, or industry. In this scenario, adversaries attach a file to the spearphishing email and usually rely upon [User Execution](https://attack.mitre.org/techniques/T0863) to gain execution and access. (Citation: Enterprise ATT&CK October 2019) A Chinese spearphishing campaign running from December 9, 2011 through February 29, 2012, targeted ONG organizations and their employees. The emails were constructed with a high level of sophistication to convince employees to open the malicious file attachments. (Citation: CISA AA21-201A Pipeline Intrusion July 2021)",
|
|
18907
|
+
"platforms": [
|
|
18908
|
+
"None"
|
|
18909
|
+
],
|
|
18910
|
+
"detection": null,
|
|
18911
|
+
"reference_url": "https://attack.mitre.org/techniques/T0865",
|
|
18912
|
+
"stix_id": "attack-pattern--648f995e-9c3a-41e4-aeee-98bb41037426",
|
|
18913
|
+
"last_verified": "2026-05-19",
|
|
18914
|
+
"_auto_imported": true,
|
|
18915
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18916
|
+
"_matrix": "ics-attack"
|
|
18917
|
+
},
|
|
18918
|
+
"T0846.003": {
|
|
18919
|
+
"id": "T0846.003",
|
|
18920
|
+
"name": "Multicast Discovery",
|
|
18921
|
+
"version": "ics-attack-v15",
|
|
18922
|
+
"tactic": [
|
|
18923
|
+
"Discovery (ICS)"
|
|
18924
|
+
],
|
|
18925
|
+
"description": "Adversaries may perform multicast discovery requests which is when one system or device sends messages to all systems and devices in a pre-defined group on a network (or subnet) and then waits for a response.",
|
|
18926
|
+
"description_full": "Adversaries may perform multicast discovery requests which is when one system or device sends messages to all systems and devices in a pre-defined group on a network (or subnet) and then waits for a response. If a response is received that means the system or device that responded is live and can communicate over that protocol. Multicast discovery tends to be stealthier than broadcast discovery because every system or device on the network (or subnet) is not being messaged. One common OT protocol that has a multicast discovery mechanism is the Process Field Network (PROFINET) Discovery and Configuration Protocol (DCP) with its Identify All requests.(Citation: Cisco Active Discovery)",
|
|
18927
|
+
"platforms": [],
|
|
18928
|
+
"detection": null,
|
|
18929
|
+
"reference_url": "https://attack.mitre.org/techniques/T0846/003",
|
|
18930
|
+
"stix_id": "attack-pattern--64bbc1b2-101f-4322-af1d-0c9cc25cef91",
|
|
18931
|
+
"last_verified": "2026-05-19",
|
|
18932
|
+
"_auto_imported": true,
|
|
18933
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18934
|
+
"_matrix": "ics-attack",
|
|
18935
|
+
"_gap_skip": {
|
|
18936
|
+
"fields": [
|
|
18937
|
+
"platforms"
|
|
18938
|
+
],
|
|
18939
|
+
"reason": "ICS-attack techniques do not carry a platforms field in MITRE STIX — they target the ICS matrix as a whole rather than specific OS/cloud platforms"
|
|
18940
|
+
}
|
|
18941
|
+
},
|
|
18942
|
+
"T1693.001": {
|
|
18943
|
+
"id": "T1693.001",
|
|
18944
|
+
"name": "System Firmware",
|
|
18945
|
+
"version": "ics-attack-v15",
|
|
18946
|
+
"tactic": [
|
|
18947
|
+
"Persistence (ICS)",
|
|
18948
|
+
"Inhibit Response Function",
|
|
18949
|
+
"Impair Process Control"
|
|
18950
|
+
],
|
|
18951
|
+
"description": "System firmware on modern assets is often designed with an update feature.",
|
|
18952
|
+
"description_full": "System firmware on modern assets is often designed with an update feature. Older device firmware may be factory installed and require special reprograming equipment. When available, the firmware update feature enables vendors to remotely patch bugs and perform upgrades. Device firmware updates are often delegated to the user and may be done using a software update package. It may also be possible to perform this task over the network. An adversary may exploit the firmware update feature on accessible devices to upload malicious or out-of-date firmware. Malicious modification of device firmware may provide an adversary with root access to a device, given firmware is one of the lowest programming abstraction layers.(Citation: Basnight, Zachry, et al.)",
|
|
18953
|
+
"platforms": [],
|
|
18954
|
+
"detection": null,
|
|
18955
|
+
"reference_url": "https://attack.mitre.org/techniques/T1693/001",
|
|
18956
|
+
"stix_id": "attack-pattern--68a9324d-a524-4766-a899-a026f68a33df",
|
|
18957
|
+
"last_verified": "2026-05-19",
|
|
18958
|
+
"_auto_imported": true,
|
|
18959
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18960
|
+
"_matrix": "ics-attack",
|
|
18961
|
+
"_gap_skip": {
|
|
18962
|
+
"fields": [
|
|
18963
|
+
"platforms"
|
|
18964
|
+
],
|
|
18965
|
+
"reason": "ICS-attack techniques do not carry a platforms field in MITRE STIX — they target the ICS matrix as a whole rather than specific OS/cloud platforms"
|
|
18966
|
+
}
|
|
18967
|
+
},
|
|
18968
|
+
"T1694.002": {
|
|
18969
|
+
"id": "T1694.002",
|
|
18970
|
+
"name": "Hardcoded Credentials",
|
|
18971
|
+
"version": "ics-attack-v15",
|
|
18972
|
+
"tactic": [
|
|
18973
|
+
"Persistence (ICS)",
|
|
18974
|
+
"Lateral Movement (ICS)"
|
|
18975
|
+
],
|
|
18976
|
+
"description": "Adversaries may leverage credentials that are hardcoded in software or firmware to gain an unauthorized interactive user session to an asset.",
|
|
18977
|
+
"description_full": "Adversaries may leverage credentials that are hardcoded in software or firmware to gain an unauthorized interactive user session to an asset. Examples credentials that may be hardcoded in an asset include: * Username/Passwords * Cryptographic keys/Certificates * API tokens Unlike [Default Credentials](https://attack.mitre.org/techniques/T0812), these credentials are built into the system in a way that they either cannot be changed by the asset owner, or may be infeasible to change because of the impact it would cause to the control system operation. These credentials may be reused across whole product lines or device models and are often not published or known to the owner and operators of the asset.(Citation: ICS-ALERT-13-164-01)(Citation: OT IceFall) Adversaries may utilize these hardcoded credentials to move throughout the control system environment or provide reliable access for their tools to interact with industrial assets.",
|
|
18978
|
+
"platforms": [],
|
|
18979
|
+
"detection": null,
|
|
18980
|
+
"reference_url": "https://attack.mitre.org/techniques/T1694/002",
|
|
18981
|
+
"stix_id": "attack-pattern--6b335943-c3af-430e-a135-ab09623bdc20",
|
|
18982
|
+
"last_verified": "2026-05-19",
|
|
18983
|
+
"_auto_imported": true,
|
|
18984
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
18985
|
+
"_matrix": "ics-attack",
|
|
18986
|
+
"_gap_skip": {
|
|
18987
|
+
"fields": [
|
|
18988
|
+
"platforms"
|
|
18989
|
+
],
|
|
18990
|
+
"reason": "ICS-attack techniques do not carry a platforms field in MITRE STIX — they target the ICS matrix as a whole rather than specific OS/cloud platforms"
|
|
18991
|
+
}
|
|
18992
|
+
},
|
|
18993
|
+
"T1695.003": {
|
|
18994
|
+
"id": "T1695.003",
|
|
18995
|
+
"name": "Wi-Fi",
|
|
18996
|
+
"version": "ics-attack-v15",
|
|
18997
|
+
"tactic": [
|
|
18998
|
+
"Inhibit Response Function"
|
|
18999
|
+
],
|
|
19000
|
+
"description": "Adversaries may block access to Wi-Fi communications to prevent messages from reaching target systems and devices.",
|
|
19001
|
+
"description_full": "Adversaries may block access to Wi-Fi communications to prevent messages from reaching target systems and devices. Wi-Fi connections allow for communications between IT and OT systems and devices. Blocking Wi-Fi communications may also block command and reporting messages.(Citation: Bonnie Zhu, Anthony Joseph, Shankar Sastry 2011) An adversary may block Wi-Fi communications by disabling network interfaces, [Service Stop](https://attack.mitre.org/techniques/T0881), conducting an [Adversary-in-the-Middle](https://attack.mitre.org/techniques/T0830) attack and dropping the network traffic, or by jamming the Wi-Fi signal.",
|
|
19002
|
+
"platforms": [],
|
|
19003
|
+
"detection": null,
|
|
19004
|
+
"reference_url": "https://attack.mitre.org/techniques/T1695/003",
|
|
19005
|
+
"stix_id": "attack-pattern--71f2d49e-65dd-4fb6-a4cc-0d2b19d427fa",
|
|
19006
|
+
"last_verified": "2026-05-19",
|
|
19007
|
+
"_auto_imported": true,
|
|
19008
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19009
|
+
"_matrix": "ics-attack",
|
|
19010
|
+
"_gap_skip": {
|
|
19011
|
+
"fields": [
|
|
19012
|
+
"platforms"
|
|
19013
|
+
],
|
|
19014
|
+
"reason": "ICS-attack techniques do not carry a platforms field in MITRE STIX — they target the ICS matrix as a whole rather than specific OS/cloud platforms"
|
|
19015
|
+
}
|
|
19016
|
+
},
|
|
19017
|
+
"T1693.002": {
|
|
19018
|
+
"id": "T1693.002",
|
|
19019
|
+
"name": "Module Firmware",
|
|
19020
|
+
"version": "ics-attack-v15",
|
|
19021
|
+
"tactic": [
|
|
19022
|
+
"Persistence (ICS)",
|
|
19023
|
+
"Inhibit Response Function",
|
|
19024
|
+
"Impair Process Control"
|
|
19025
|
+
],
|
|
19026
|
+
"description": "Adversaries may install malicious or vulnerable firmware onto modular hardware devices.",
|
|
19027
|
+
"description_full": "Adversaries may install malicious or vulnerable firmware onto modular hardware devices. Control system devices often contain modular hardware devices. These devices may have their own set of firmware that is separate from the firmware of the main control system equipment. This technique is similar to System Firmware, but is conducted on other system components that may not have the same capabilities or level of integrity checking. Although it results in a device re-image, malicious device firmware may provide persistent access to remaining devices.(Citation: Daniel Peck, Dale Peterson January 2009) An easy point of access for an adversary is the Ethernet card, which may have its own CPU, RAM, and operating system. The adversary may attack and likely exploit the computer on an Ethernet card. Exploitation of the Ethernet card computer may enable the adversary to accomplish additional attacks, such as the following:(Citation: Daniel Peck, Dale Peterson January 2009) * Delayed Attack - The adversary may stage an attack in advance and choose when to launch it, such as at a particularly damaging time. * Brick the Ethernet Card - Malicious firmware may be programmed to result in an Ethernet card failure, requiring a factory return. * Random Attack or Failure - The adversary may load malicious firmware onto multiple field devices. Execution of an attack and the time it occurs is generated by a pseudo-random number generator. * A Field Device Worm - The adversary may choose to identify all field devices of the same model, with the end goal of performing a device-wide compromise. * Attack Other Cards on the Field Device - Although it is not the most important module in a field device, the Ethernet card is most accessible to the adversary and malware. Compromise of the Ethernet card may provide a more direct route to compromising other modules, such as the CPU module.",
|
|
19028
|
+
"platforms": [],
|
|
19029
|
+
"detection": null,
|
|
19030
|
+
"reference_url": "https://attack.mitre.org/techniques/T1693/002",
|
|
19031
|
+
"stix_id": "attack-pattern--75587e49-ab7e-44df-9549-faeb1da57f39",
|
|
19032
|
+
"last_verified": "2026-05-19",
|
|
19033
|
+
"_auto_imported": true,
|
|
19034
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19035
|
+
"_matrix": "ics-attack",
|
|
19036
|
+
"_gap_skip": {
|
|
19037
|
+
"fields": [
|
|
19038
|
+
"platforms"
|
|
19039
|
+
],
|
|
19040
|
+
"reason": "ICS-attack techniques do not carry a platforms field in MITRE STIX — they target the ICS matrix as a whole rather than specific OS/cloud platforms"
|
|
19041
|
+
}
|
|
19042
|
+
},
|
|
19043
|
+
"T0843.001": {
|
|
19044
|
+
"id": "T0843.001",
|
|
19045
|
+
"name": "Download All",
|
|
19046
|
+
"version": "ics-attack-v15",
|
|
19047
|
+
"tactic": [
|
|
19048
|
+
"Lateral Movement (ICS)"
|
|
19049
|
+
],
|
|
19050
|
+
"description": "Adversaries may execute a full program download to a PLC to overwrite the entire PLC program and configuration to deploy a new project or make major changes.",
|
|
19051
|
+
"description_full": "Adversaries may execute a full program download to a PLC to overwrite the entire PLC program and configuration to deploy a new project or make major changes. This typically requires stopping the PLC and adversely impacting control processes. The ability to perform a full program download to the PLC typically relies on access to a workstation with the vendor-specific PLC programming software installed.",
|
|
19052
|
+
"platforms": [],
|
|
19053
|
+
"detection": null,
|
|
19054
|
+
"reference_url": "https://attack.mitre.org/techniques/T0843/001",
|
|
19055
|
+
"stix_id": "attack-pattern--77015a55-eef8-4f71-a071-b152f82ec1ef",
|
|
19056
|
+
"last_verified": "2026-05-19",
|
|
19057
|
+
"_auto_imported": true,
|
|
19058
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19059
|
+
"_matrix": "ics-attack",
|
|
19060
|
+
"_gap_skip": {
|
|
19061
|
+
"fields": [
|
|
19062
|
+
"platforms"
|
|
19063
|
+
],
|
|
19064
|
+
"reason": "ICS-attack techniques do not carry a platforms field in MITRE STIX — they target the ICS matrix as a whole rather than specific OS/cloud platforms"
|
|
19065
|
+
}
|
|
19066
|
+
},
|
|
19067
|
+
"T0895": {
|
|
19068
|
+
"id": "T0895",
|
|
19069
|
+
"name": "Autorun Image",
|
|
19070
|
+
"version": "ics-attack-v15",
|
|
19071
|
+
"tactic": [
|
|
19072
|
+
"Execution (ICS)"
|
|
19073
|
+
],
|
|
19074
|
+
"description": "Adversaries may leverage AutoRun functionality or scripts to execute malicious code.",
|
|
19075
|
+
"description_full": "Adversaries may leverage AutoRun functionality or scripts to execute malicious code. Devices configured to enable AutoRun functionality or legacy operating systems may be susceptible to abuse of these features to run malicious code stored on various forms of removeable media (i.e., USB, Disk Images [.ISO]). Commonly, AutoRun or AutoPlay are disabled in many operating systems configurations to mitigate against this technique. If a device is configured to enable AutoRun or AutoPlay, adversaries may execute code on the device by mounting the removable media to the device, either through physical or virtual means. This may be especially relevant for virtual machine environments where disk images may be dynamically mapped to a guest system on a hypervisor. An example could include an adversary gaining access to a hypervisor through the management interface to modify a virtual machine’s hardware configuration. They could then deploy an iso image with a malicious AutoRun script to cause the virtual machine to automatically execute the code contained on the disk image. This would enable the execution of malicious code within a virtual machine without needing any prior remote access to that system.",
|
|
19076
|
+
"platforms": [],
|
|
19077
|
+
"detection": null,
|
|
19078
|
+
"reference_url": "https://attack.mitre.org/techniques/T0895",
|
|
19079
|
+
"stix_id": "attack-pattern--77d9c726-b53e-481d-8bcc-1068aebfbb9d",
|
|
19080
|
+
"last_verified": "2026-05-19",
|
|
19081
|
+
"_auto_imported": true,
|
|
19082
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19083
|
+
"_matrix": "ics-attack",
|
|
19084
|
+
"_gap_skip": {
|
|
19085
|
+
"fields": [
|
|
19086
|
+
"platforms"
|
|
19087
|
+
],
|
|
19088
|
+
"reason": "ICS-attack techniques do not carry a platforms field in MITRE STIX — they target the ICS matrix as a whole rather than specific OS/cloud platforms"
|
|
19089
|
+
}
|
|
19090
|
+
},
|
|
19091
|
+
"T0817": {
|
|
19092
|
+
"id": "T0817",
|
|
19093
|
+
"name": "Drive-by Compromise",
|
|
19094
|
+
"version": "ics-attack-v15",
|
|
19095
|
+
"tactic": [
|
|
19096
|
+
"Initial Access (ICS)"
|
|
19097
|
+
],
|
|
19098
|
+
"description": "Adversaries may gain access to a system during a drive-by compromise, when a user visits a website as part of a regular browsing session.",
|
|
19099
|
+
"description_full": "Adversaries may gain access to a system during a drive-by compromise, when a user visits a website as part of a regular browsing session. With this technique, the user's web browser is targeted and exploited simply by visiting the compromised website. The adversary may target a specific community, such as trusted third party suppliers or other industry specific groups, which often visit the target website. This kind of targeted attack relies on a common interest, and is known as a strategic web compromise or watering hole attack. The National Cyber Awareness System (NCAS) has issued a Technical Alert (TA) regarding Russian government cyber activity targeting critical infrastructure sectors. (Citation: Cybersecurity & Infrastructure Security Agency March 2018) Analysis by DHS and FBI has noted two distinct categories of victims in the Dragonfly campaign on the Western energy sector: staging and intended targets. The adversary targeted the less secure networks of staging targets, including trusted third-party suppliers and related peripheral organizations. Initial access to the intended targets used watering hole attacks to target process control, ICS, and critical infrastructure related trade publications and informational websites.",
|
|
19100
|
+
"platforms": [
|
|
19101
|
+
"None"
|
|
19102
|
+
],
|
|
19103
|
+
"detection": null,
|
|
19104
|
+
"reference_url": "https://attack.mitre.org/techniques/T0817",
|
|
19105
|
+
"stix_id": "attack-pattern--7830cfcf-b268-4ac0-a69e-73c6affbae9a",
|
|
19106
|
+
"last_verified": "2026-05-19",
|
|
19107
|
+
"_auto_imported": true,
|
|
19108
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19109
|
+
"_matrix": "ics-attack"
|
|
19110
|
+
},
|
|
19111
|
+
"T1691.002": {
|
|
19112
|
+
"id": "T1691.002",
|
|
19113
|
+
"name": "Reporting Message",
|
|
19114
|
+
"version": "ics-attack-v15",
|
|
19115
|
+
"tactic": [
|
|
19116
|
+
"Inhibit Response Function"
|
|
19117
|
+
],
|
|
19118
|
+
"description": "Adversaries may block or prevent a reporting message from reaching its intended target.",
|
|
19119
|
+
"description_full": "Adversaries may block or prevent a reporting message from reaching its intended target. In control systems, reporting messages contain telemetry data (e.g., I/O values) pertaining to the current state of equipment and the industrial process. By blocking these reporting messages, an adversary can potentially hide their actions from an operator. Blocking reporting messages in control systems that manage physical processes may contribute to system impact, causing inhibition of a response function. A control system may not be able to respond in a proper or timely manner to an event, such as a dangerous fault, if its corresponding reporting message is blocked.(Citation: Bonnie Zhu, Anthony Joseph, Shankar Sastry 2011)(Citation: Electricity Information Sharing and Analysis Center; SANS Industrial Control Systems March 2016)",
|
|
19120
|
+
"platforms": [],
|
|
19121
|
+
"detection": null,
|
|
19122
|
+
"reference_url": "https://attack.mitre.org/techniques/T1691/002",
|
|
19123
|
+
"stix_id": "attack-pattern--7866bb5f-98ee-45c2-984c-8a328c5176b2",
|
|
19124
|
+
"last_verified": "2026-05-19",
|
|
19125
|
+
"_auto_imported": true,
|
|
19126
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19127
|
+
"_matrix": "ics-attack",
|
|
19128
|
+
"_gap_skip": {
|
|
19129
|
+
"fields": [
|
|
19130
|
+
"platforms"
|
|
19131
|
+
],
|
|
19132
|
+
"reason": "ICS-attack techniques do not carry a platforms field in MITRE STIX — they target the ICS matrix as a whole rather than specific OS/cloud platforms"
|
|
19133
|
+
}
|
|
19134
|
+
},
|
|
19135
|
+
"T1693": {
|
|
19136
|
+
"id": "T1693",
|
|
19137
|
+
"name": "Modify Firmware",
|
|
19138
|
+
"version": "ics-attack-v15",
|
|
19139
|
+
"tactic": [
|
|
19140
|
+
"Persistence (ICS)",
|
|
19141
|
+
"Inhibit Response Function",
|
|
19142
|
+
"Impair Process Control"
|
|
19143
|
+
],
|
|
19144
|
+
"description": "Firmware is low-level software embedded in hardware that enables systems and devices to function properly and is commonly found in ICS environments.",
|
|
19145
|
+
"description_full": "Firmware is low-level software embedded in hardware that enables systems and devices to function properly and is commonly found in ICS environments. Adversaries may modify firmware on a system or device by installing malicious or vulnerable versions that enable them to achieve objectives such as [Persistence](https://attack.mitre.org/tactics/TA0110), [Impair Process Control](https://attack.mitre.org/tactics/TA0106), and [Inhibit Response Function](https://attack.mitre.org/tactics/TA0107). Adversaries may modify system and device firmware by using the built-in firmware update functionality which may support local or remote installation. The malicious or vulnerable firmware may be delivered via [Replication Through Removable Media](https://attack.mitre.org/techniques/T0847), [Supply Chain Compromise](https://attack.mitre.org/techniques/T0862), or [Remote Services](https://attack.mitre.org/techniques/T0886). Once installed, the malicious or vulnerable firmware could be used to provide [Rootkit](https://attack.mitre.org/techniques/T0851) and [Hooking](https://attack.mitre.org/techniques/T0874) functionality, [Exploitation for Privilege Escalation](https://attack.mitre.org/techniques/T0890), or [Denial of Service](https://attack.mitre.org/techniques/T0814).(Citation: Basnight, Zachry, et al.)",
|
|
19146
|
+
"platforms": [],
|
|
19147
|
+
"detection": null,
|
|
19148
|
+
"reference_url": "https://attack.mitre.org/techniques/T1693",
|
|
19149
|
+
"stix_id": "attack-pattern--7b4c0e19-a9b0-4a74-a196-b38c07b79f20",
|
|
19150
|
+
"last_verified": "2026-05-19",
|
|
19151
|
+
"_auto_imported": true,
|
|
19152
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19153
|
+
"_matrix": "ics-attack",
|
|
19154
|
+
"_gap_skip": {
|
|
19155
|
+
"fields": [
|
|
19156
|
+
"platforms"
|
|
19157
|
+
],
|
|
19158
|
+
"reason": "ICS-attack techniques do not carry a platforms field in MITRE STIX — they target the ICS matrix as a whole rather than specific OS/cloud platforms"
|
|
19159
|
+
}
|
|
19160
|
+
},
|
|
19161
|
+
"T0879": {
|
|
19162
|
+
"id": "T0879",
|
|
19163
|
+
"name": "Damage to Property",
|
|
19164
|
+
"version": "ics-attack-v15",
|
|
19165
|
+
"tactic": [
|
|
19166
|
+
"Impact (ICS)"
|
|
19167
|
+
],
|
|
19168
|
+
"description": "Adversaries may cause damage and destruction of property to infrastructure, equipment, and the surrounding environment when attacking control systems.",
|
|
19169
|
+
"description_full": "Adversaries may cause damage and destruction of property to infrastructure, equipment, and the surrounding environment when attacking control systems. This technique may result in device and operational equipment breakdown, or represent tangential damage from other techniques used in an attack. Depending on the severity of physical damage and disruption caused to control processes and systems, this technique may result in [Loss of Safety](https://attack.mitre.org/techniques/T0880). Operations that result in [Loss of Control](https://attack.mitre.org/techniques/T0827) may also cause damage to property, which may be directly or indirectly motivated by an adversary seeking to cause impact in the form of [Loss of Productivity and Revenue](https://attack.mitre.org/techniques/T0828). The German Federal Office for Information Security (BSI) reported a targeted attack on a steel mill under an incidents affecting business section of its 2014 IT Security Report. (Citation: BSI State of IT Security 2014) These targeted attacks affected industrial operations and resulted in breakdowns of control system components and even entire installations. As a result of these breakdowns, massive impact and damage resulted from the uncontrolled shutdown of a blast furnace. A Polish student used a remote controller device to interface with the Lodz city tram system in Poland. (Citation: John Bill May 2017) (Citation: Shelley Smith February 2008) (Citation: Bruce Schneier January 2008) Using this remote, the student was able to capture and replay legitimate tram signals. This resulted in damage to impacted trams, people, and the surrounding property. Reportedly, four trams were derailed and were forced to make emergency stops. (Citation: Shelley Smith February 2008) Commands issued by the student may have also resulted in tram collisions, causing harm to those on board and the environment outside. (Citation: Bruce Schneier January 2008)",
|
|
19170
|
+
"platforms": [
|
|
19171
|
+
"None"
|
|
19172
|
+
],
|
|
19173
|
+
"detection": null,
|
|
19174
|
+
"reference_url": "https://attack.mitre.org/techniques/T0879",
|
|
19175
|
+
"stix_id": "attack-pattern--83ebd22f-b401-4d59-8219-2294172cf916",
|
|
19176
|
+
"last_verified": "2026-05-19",
|
|
19177
|
+
"_auto_imported": true,
|
|
19178
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19179
|
+
"_matrix": "ics-attack"
|
|
19180
|
+
},
|
|
19181
|
+
"T0866": {
|
|
19182
|
+
"id": "T0866",
|
|
19183
|
+
"name": "Exploitation of Remote Services",
|
|
19184
|
+
"version": "ics-attack-v15",
|
|
19185
|
+
"tactic": [
|
|
19186
|
+
"Initial Access (ICS)",
|
|
19187
|
+
"Lateral Movement (ICS)"
|
|
19188
|
+
],
|
|
19189
|
+
"description": "Adversaries may exploit a software vulnerability to take advantage of a programming error in a program, service, or within the operating system software or kernel itself to enable remote service abuse.",
|
|
19190
|
+
"description_full": "Adversaries may exploit a software vulnerability to take advantage of a programming error in a program, service, or within the operating system software or kernel itself to enable remote service abuse. A common goal for post-compromise exploitation of remote services is for initial access into and lateral movement throughout the ICS environment to enable access to targeted systems. (Citation: Enterprise ATT&CK) ICS asset owners and operators have been affected by ransomware (or disruptive malware masquerading as ransomware) migrating from enterprise IT to ICS environments: WannaCry, NotPetya, and BadRabbit. In each of these cases, self-propagating (wormable) malware initially infected IT networks, but through exploit (particularly the SMBv1-targeting MS17-010 vulnerability) spread to industrial networks, producing significant impacts. (Citation: Joe Slowik April 2019)",
|
|
19191
|
+
"platforms": [
|
|
19192
|
+
"None"
|
|
19193
|
+
],
|
|
19194
|
+
"detection": null,
|
|
19195
|
+
"reference_url": "https://attack.mitre.org/techniques/T0866",
|
|
19196
|
+
"stix_id": "attack-pattern--85a45294-08f1-4539-bf00-7da08aa7b0ee",
|
|
19197
|
+
"last_verified": "2026-05-19",
|
|
19198
|
+
"_auto_imported": true,
|
|
19199
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19200
|
+
"_matrix": "ics-attack"
|
|
19201
|
+
},
|
|
19202
|
+
"T0822": {
|
|
19203
|
+
"id": "T0822",
|
|
19204
|
+
"name": "External Remote Services",
|
|
19205
|
+
"version": "ics-attack-v15",
|
|
19206
|
+
"tactic": [
|
|
19207
|
+
"Initial Access (ICS)"
|
|
19208
|
+
],
|
|
19209
|
+
"description": "Adversaries may leverage external remote services as a point of initial access into your network.",
|
|
19210
|
+
"description_full": "Adversaries may leverage external remote services as a point of initial access into your network. These services allow users to connect to internal network resources from external locations. Examples are VPNs, Citrix, and other access mechanisms. Remote service gateways often manage connections and credential authentication for these services. (Citation: Daniel Oakley, Travis Smith, Tripwire) External remote services allow administration of a control system from outside the system. Often, vendors and internal engineering groups have access to external remote services to control system networks via the corporate network. In some cases, this access is enabled directly from the internet. While remote access enables ease of maintenance when a control system is in a remote area, compromise of remote access solutions is a liability. The adversary may use these services to gain access to and execute attacks against a control system network. Access to valid accounts is often a requirement. As they look for an entry point into the control system network, adversaries may begin searching for existing point-to-point VPN implementations at trusted third party networks or through remote support employee connections where split tunneling is enabled. (Citation: Electricity Information Sharing and Analysis Center; SANS Industrial Control Systems March 2016)",
|
|
19211
|
+
"platforms": [
|
|
19212
|
+
"None"
|
|
19213
|
+
],
|
|
19214
|
+
"detection": null,
|
|
19215
|
+
"reference_url": "https://attack.mitre.org/techniques/T0822",
|
|
19216
|
+
"stix_id": "attack-pattern--8d2f3bab-507c-4424-b58b-edc977bd215c",
|
|
19217
|
+
"last_verified": "2026-05-19",
|
|
19218
|
+
"_auto_imported": true,
|
|
19219
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19220
|
+
"_matrix": "ics-attack"
|
|
19221
|
+
},
|
|
19222
|
+
"T0806": {
|
|
19223
|
+
"id": "T0806",
|
|
19224
|
+
"name": "Brute Force I/O",
|
|
19225
|
+
"version": "ics-attack-v15",
|
|
19226
|
+
"tactic": [
|
|
19227
|
+
"Impair Process Control"
|
|
19228
|
+
],
|
|
19229
|
+
"description": "Adversaries may repetitively or successively change I/O point values to perform an action.",
|
|
19230
|
+
"description_full": "Adversaries may repetitively or successively change I/O point values to perform an action. Brute Force I/O may be achieved by changing either a range of I/O point values or a single point value repeatedly to manipulate a process function. The adversary's goal and the information they have about the target environment will influence which of the options they choose. In the case of brute forcing a range of point values, the adversary may be able to achieve an impact without targeting a specific point. In the case where a single point is targeted, the adversary may be able to generate instability on the process function associated with that particular point. Adversaries may use Brute Force I/O to cause failures within various industrial processes. These failures could be the result of wear on equipment or damage to downstream equipment.",
|
|
19231
|
+
"platforms": [
|
|
19232
|
+
"None"
|
|
19233
|
+
],
|
|
19234
|
+
"detection": null,
|
|
19235
|
+
"reference_url": "https://attack.mitre.org/techniques/T0806",
|
|
19236
|
+
"stix_id": "attack-pattern--8e7089d3-fba2-44f8-94a8-9a79c53920c4",
|
|
19237
|
+
"last_verified": "2026-05-19",
|
|
19238
|
+
"_auto_imported": true,
|
|
19239
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19240
|
+
"_matrix": "ics-attack"
|
|
19241
|
+
},
|
|
19242
|
+
"T0830": {
|
|
19243
|
+
"id": "T0830",
|
|
19244
|
+
"name": "Adversary-in-the-Middle",
|
|
19245
|
+
"version": "ics-attack-v15",
|
|
19246
|
+
"tactic": [
|
|
19247
|
+
"Collection (ICS)"
|
|
19248
|
+
],
|
|
19249
|
+
"description": "Adversaries with privileged network access may seek to modify network traffic in real time using adversary-in-the-middle (AiTM) attacks.",
|
|
19250
|
+
"description_full": "Adversaries with privileged network access may seek to modify network traffic in real time using adversary-in-the-middle (AiTM) attacks. (Citation: Gabriel Sanchez October 2017) This type of attack allows the adversary to intercept traffic to and/or from a particular device on the network. If a AiTM attack is established, then the adversary has the ability to block, log, modify, or inject traffic into the communication stream. There are several ways to accomplish this attack, but some of the most-common are Address Resolution Protocol (ARP) poisoning and the use of a proxy. (Citation: Bonnie Zhu, Anthony Joseph, Shankar Sastry 2011) An AiTM attack may allow an adversary to perform the following attacks: [Block Reporting Message](https://attack.mitre.org/techniques/T0804), [Spoof Reporting Message](https://attack.mitre.org/techniques/T0856), [Modify Parameter](https://attack.mitre.org/techniques/T0836), [Unauthorized Command Message](https://attack.mitre.org/techniques/T0855)",
|
|
19251
|
+
"platforms": [
|
|
19252
|
+
"None"
|
|
19253
|
+
],
|
|
19254
|
+
"detection": null,
|
|
19255
|
+
"reference_url": "https://attack.mitre.org/techniques/T0830",
|
|
19256
|
+
"stix_id": "attack-pattern--9a505987-ab05-4f46-a9a6-6441442eec3b",
|
|
19257
|
+
"last_verified": "2026-05-19",
|
|
19258
|
+
"_auto_imported": true,
|
|
19259
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19260
|
+
"_matrix": "ics-attack"
|
|
19261
|
+
},
|
|
19262
|
+
"T0820": {
|
|
19263
|
+
"id": "T0820",
|
|
19264
|
+
"name": "Exploitation for Evasion",
|
|
19265
|
+
"version": "ics-attack-v15",
|
|
19266
|
+
"tactic": [
|
|
19267
|
+
"Evasion (ICS)"
|
|
19268
|
+
],
|
|
19269
|
+
"description": "Adversaries may exploit a software vulnerability to take advantage of a programming error in a program, service, or within the operating system software or kernel itself to evade detection.",
|
|
19270
|
+
"description_full": "Adversaries may exploit a software vulnerability to take advantage of a programming error in a program, service, or within the operating system software or kernel itself to evade detection. Vulnerabilities may exist in software that can be used to disable or circumvent security features. Adversaries may have prior knowledge through [Remote System Information Discovery](https://attack.mitre.org/techniques/T0888) about security features implemented on control devices. These device security features will likely be targeted directly for exploitation. There are examples of firmware RAM/ROM consistency checks on control devices being targeted by adversaries to enable the installation of malicious [System Firmware](https://attack.mitre.org/techniques/T0857).",
|
|
19271
|
+
"platforms": [
|
|
19272
|
+
"None"
|
|
19273
|
+
],
|
|
19274
|
+
"detection": null,
|
|
19275
|
+
"reference_url": "https://attack.mitre.org/techniques/T0820",
|
|
19276
|
+
"stix_id": "attack-pattern--9f947a1c-3860-48a8-8af0-a2dfa3efde03",
|
|
19277
|
+
"last_verified": "2026-05-19",
|
|
19278
|
+
"_auto_imported": true,
|
|
19279
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19280
|
+
"_matrix": "ics-attack"
|
|
19281
|
+
},
|
|
19282
|
+
"T0827": {
|
|
19283
|
+
"id": "T0827",
|
|
19284
|
+
"name": "Loss of Control",
|
|
19285
|
+
"version": "ics-attack-v15",
|
|
19286
|
+
"tactic": [
|
|
19287
|
+
"Impact (ICS)"
|
|
19288
|
+
],
|
|
19289
|
+
"description": "Adversaries may seek to achieve a sustained loss of control or a runaway condition in which operators cannot issue any commands even if the malicious interference has subsided.",
|
|
19290
|
+
"description_full": "Adversaries may seek to achieve a sustained loss of control or a runaway condition in which operators cannot issue any commands even if the malicious interference has subsided. (Citation: Corero) (Citation: Michael J. Assante and Robert M. Lee) (Citation: Tyson Macaulay) The German Federal Office for Information Security (BSI) reported a targeted attack on a steel mill in its 2014 IT Security Report.(Citation: BSI State of IT Security 2014) These targeted attacks affected industrial operations and resulted in breakdowns of control system components and even entire installations. As a result of these breakdowns, massive impact resulted in damage and unsafe conditions from the uncontrolled shutdown of a blast furnace.",
|
|
19291
|
+
"platforms": [
|
|
19292
|
+
"None"
|
|
19293
|
+
],
|
|
19294
|
+
"detection": null,
|
|
19295
|
+
"reference_url": "https://attack.mitre.org/techniques/T0827",
|
|
19296
|
+
"stix_id": "attack-pattern--a81696ef-c106-482c-8f80-59c30f2569fb",
|
|
19297
|
+
"last_verified": "2026-05-19",
|
|
19298
|
+
"_auto_imported": true,
|
|
19299
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19300
|
+
"_matrix": "ics-attack"
|
|
19301
|
+
},
|
|
19302
|
+
"T0874": {
|
|
19303
|
+
"id": "T0874",
|
|
19304
|
+
"name": "Hooking",
|
|
19305
|
+
"version": "ics-attack-v15",
|
|
19306
|
+
"tactic": [
|
|
19307
|
+
"Execution (ICS)",
|
|
19308
|
+
"Privilege Escalation (ICS)"
|
|
19309
|
+
],
|
|
19310
|
+
"description": "Adversaries may hook into application programming interface (API) functions used by processes to redirect calls for execution and privilege escalation means.",
|
|
19311
|
+
"description_full": "Adversaries may hook into application programming interface (API) functions used by processes to redirect calls for execution and privilege escalation means. Windows processes often leverage these API functions to perform tasks that require reusable system resources. Windows API functions are typically stored in dynamic-link libraries (DLLs) as exported functions. (Citation: Enterprise ATT&CK) One type of hooking seen in ICS involves redirecting calls to these functions via import address table (IAT) hooking. IAT hooking uses modifications to a process IAT, where pointers to imported API functions are stored. (Citation: Nicolas Falliere, Liam O Murchu, Eric Chien February 2011)",
|
|
19312
|
+
"platforms": [
|
|
19313
|
+
"None"
|
|
19314
|
+
],
|
|
19315
|
+
"detection": null,
|
|
19316
|
+
"reference_url": "https://attack.mitre.org/techniques/T0874",
|
|
19317
|
+
"stix_id": "attack-pattern--ab390887-afc0-4715-826d-b1b167d522ae",
|
|
19318
|
+
"last_verified": "2026-05-19",
|
|
19319
|
+
"_auto_imported": true,
|
|
19320
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19321
|
+
"_matrix": "ics-attack"
|
|
19322
|
+
},
|
|
19323
|
+
"T0823": {
|
|
19324
|
+
"id": "T0823",
|
|
19325
|
+
"name": "Graphical User Interface",
|
|
19326
|
+
"version": "ics-attack-v15",
|
|
19327
|
+
"tactic": [
|
|
19328
|
+
"Execution (ICS)"
|
|
19329
|
+
],
|
|
19330
|
+
"description": "Adversaries may attempt to gain access to a machine via a Graphical User Interface (GUI) to enhance execution capabilities.",
|
|
19331
|
+
"description_full": "Adversaries may attempt to gain access to a machine via a Graphical User Interface (GUI) to enhance execution capabilities. Access to a GUI allows a user to interact with a computer in a more visual manner than a CLI. A GUI allows users to move a cursor and click on interface objects, with a mouse and keyboard as the main input devices, as opposed to just using the keyboard. If physical access is not an option, then access might be possible via protocols such as VNC on Linux-based and Unix-based operating systems, and RDP on Windows operating systems. An adversary can use this access to execute programs and applications on the target machine.",
|
|
19332
|
+
"platforms": [
|
|
19333
|
+
"None"
|
|
19334
|
+
],
|
|
19335
|
+
"detection": null,
|
|
19336
|
+
"reference_url": "https://attack.mitre.org/techniques/T0823",
|
|
19337
|
+
"stix_id": "attack-pattern--b0628bfc-5376-4a38-9182-f324501cb4cf",
|
|
19338
|
+
"last_verified": "2026-05-19",
|
|
19339
|
+
"_auto_imported": true,
|
|
19340
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19341
|
+
"_matrix": "ics-attack"
|
|
19342
|
+
},
|
|
19343
|
+
"T0848": {
|
|
19344
|
+
"id": "T0848",
|
|
19345
|
+
"name": "Rogue Master",
|
|
19346
|
+
"version": "ics-attack-v15",
|
|
19347
|
+
"tactic": [
|
|
19348
|
+
"Initial Access (ICS)"
|
|
19349
|
+
],
|
|
19350
|
+
"description": "Adversaries may setup a rogue master to leverage control server functions to communicate with outstations.",
|
|
19351
|
+
"description_full": "Adversaries may setup a rogue master to leverage control server functions to communicate with outstations. A rogue master can be used to send legitimate control messages to other control system devices, affecting processes in unintended ways. It may also be used to disrupt network communications by capturing and receiving the network traffic meant for the actual master. Impersonating a master may also allow an adversary to avoid detection. In the case of the 2017 Dallas Siren incident, adversaries used a rogue master to send command messages to the 156 distributed sirens across the city, either through a single rogue transmitter with a strong signal, or using many distributed repeaters. (Citation: Bastille April 2017) (Citation: Zack Whittaker April 2017)",
|
|
19352
|
+
"platforms": [
|
|
19353
|
+
"None"
|
|
19354
|
+
],
|
|
19355
|
+
"detection": null,
|
|
19356
|
+
"reference_url": "https://attack.mitre.org/techniques/T0848",
|
|
19357
|
+
"stix_id": "attack-pattern--b14395bd-5419-4ef4-9bd8-696936f509bb",
|
|
19358
|
+
"last_verified": "2026-05-19",
|
|
19359
|
+
"_auto_imported": true,
|
|
19360
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19361
|
+
"_matrix": "ics-attack"
|
|
19362
|
+
},
|
|
19363
|
+
"T0834": {
|
|
19364
|
+
"id": "T0834",
|
|
19365
|
+
"name": "Native API",
|
|
19366
|
+
"version": "ics-attack-v15",
|
|
19367
|
+
"tactic": [
|
|
19368
|
+
"Execution (ICS)"
|
|
19369
|
+
],
|
|
19370
|
+
"description": "Adversaries may directly interact with the native OS application programming interface (API) to access system functions.",
|
|
19371
|
+
"description_full": "Adversaries may directly interact with the native OS application programming interface (API) to access system functions. Native APIs provide a controlled means of calling low-level OS services within the kernel, such as those involving hardware/devices, memory, and processes. (Citation: The MITRE Corporation May 2017) These native APIs are leveraged by the OS during system boot (when other system components are not yet initialized) as well as carrying out tasks and requests during routine operations. Functionality provided by native APIs are often also exposed to user-mode applications via interfaces and libraries. For example, functions such as memcpy and direct operations on memory registers can be used to modify user and system memory space.",
|
|
19372
|
+
"platforms": [
|
|
19373
|
+
"None"
|
|
19374
|
+
],
|
|
19375
|
+
"detection": null,
|
|
19376
|
+
"reference_url": "https://attack.mitre.org/techniques/T0834",
|
|
19377
|
+
"stix_id": "attack-pattern--b52870cc-83f3-473c-b895-72d91751030b",
|
|
19378
|
+
"last_verified": "2026-05-19",
|
|
19379
|
+
"_auto_imported": true,
|
|
19380
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19381
|
+
"_matrix": "ics-attack"
|
|
19382
|
+
},
|
|
19383
|
+
"T0826": {
|
|
19384
|
+
"id": "T0826",
|
|
19385
|
+
"name": "Loss of Availability",
|
|
19386
|
+
"version": "ics-attack-v15",
|
|
19387
|
+
"tactic": [
|
|
19388
|
+
"Impact (ICS)"
|
|
19389
|
+
],
|
|
19390
|
+
"description": "Adversaries may attempt to disrupt essential components or systems to prevent owner and operator from delivering products or services.",
|
|
19391
|
+
"description_full": "Adversaries may attempt to disrupt essential components or systems to prevent owner and operator from delivering products or services. (Citation: Corero) (Citation: Michael J. Assante and Robert M. Lee) (Citation: Tyson Macaulay) Adversaries may leverage malware to delete or encrypt critical data on HMIs, workstations, or databases. In the 2021 Colonial Pipeline ransomware incident, pipeline operations were temporally halted on May 7th and were not fully restarted until May 12th. (Citation: Colonial Pipeline Company May 2021)",
|
|
19392
|
+
"platforms": [
|
|
19393
|
+
"None"
|
|
19394
|
+
],
|
|
19395
|
+
"detection": null,
|
|
19396
|
+
"reference_url": "https://attack.mitre.org/techniques/T0826",
|
|
19397
|
+
"stix_id": "attack-pattern--b5b9bacb-97f2-4249-b804-47fd44de1f95",
|
|
19398
|
+
"last_verified": "2026-05-19",
|
|
19399
|
+
"_auto_imported": true,
|
|
19400
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19401
|
+
"_matrix": "ics-attack"
|
|
19402
|
+
},
|
|
19403
|
+
"T0882": {
|
|
19404
|
+
"id": "T0882",
|
|
19405
|
+
"name": "Theft of Operational Information",
|
|
19406
|
+
"version": "ics-attack-v15",
|
|
19407
|
+
"tactic": [
|
|
19408
|
+
"Impact (ICS)"
|
|
19409
|
+
],
|
|
19410
|
+
"description": "Adversaries may steal operational information on a production environment as a direct mission outcome for personal gain or to inform future operations.",
|
|
19411
|
+
"description_full": "Adversaries may steal operational information on a production environment as a direct mission outcome for personal gain or to inform future operations. This information may include design documents, schedules, rotational data, or similar artifacts that provide insight on operations. In the Bowman Dam incident, adversaries probed systems for operational data. (Citation: Mark Thompson March 2016) (Citation: Danny Yadron December 2015)",
|
|
19412
|
+
"platforms": [
|
|
19413
|
+
"None"
|
|
19414
|
+
],
|
|
19415
|
+
"detection": null,
|
|
19416
|
+
"reference_url": "https://attack.mitre.org/techniques/T0882",
|
|
19417
|
+
"stix_id": "attack-pattern--b7e13ee8-182c-4f19-92a4-a88d7d855d54",
|
|
19418
|
+
"last_verified": "2026-05-19",
|
|
19419
|
+
"_auto_imported": true,
|
|
19420
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19421
|
+
"_matrix": "ics-attack"
|
|
19422
|
+
},
|
|
19423
|
+
"T0849": {
|
|
19424
|
+
"id": "T0849",
|
|
19425
|
+
"name": "Masquerading",
|
|
19426
|
+
"version": "ics-attack-v15",
|
|
19427
|
+
"tactic": [
|
|
19428
|
+
"Evasion (ICS)"
|
|
19429
|
+
],
|
|
19430
|
+
"description": "Adversaries may use masquerading to disguise a malicious application or executable as another file, to avoid operator and engineer suspicion.",
|
|
19431
|
+
"description_full": "Adversaries may use masquerading to disguise a malicious application or executable as another file, to avoid operator and engineer suspicion. Possible disguises of these masquerading files can include commonly found programs, expected vendor executables and configuration files, and other commonplace application and naming conventions. By impersonating expected and vendor-relevant files and applications, operators and engineers may not notice the presence of the underlying malicious content and possibly end up running those masquerading as legitimate functions. Applications and other files commonly found on Windows systems or in engineering workstations have been impersonated before. This can be as simple as renaming a file to effectively disguise it in the ICS environment.",
|
|
19432
|
+
"platforms": [
|
|
19433
|
+
"None"
|
|
19434
|
+
],
|
|
19435
|
+
"detection": null,
|
|
19436
|
+
"reference_url": "https://attack.mitre.org/techniques/T0849",
|
|
19437
|
+
"stix_id": "attack-pattern--ba203963-3182-41ac-af14-7e7ebc83cd61",
|
|
19438
|
+
"last_verified": "2026-05-19",
|
|
19439
|
+
"_auto_imported": true,
|
|
19440
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19441
|
+
"_matrix": "ics-attack"
|
|
19442
|
+
},
|
|
19443
|
+
"T0843": {
|
|
19444
|
+
"id": "T0843",
|
|
19445
|
+
"name": "Program Download",
|
|
19446
|
+
"version": "ics-attack-v15",
|
|
19447
|
+
"tactic": [
|
|
19448
|
+
"Lateral Movement (ICS)"
|
|
19449
|
+
],
|
|
19450
|
+
"description": "Adversaries may perform a program download to transfer a user program to a controller.",
|
|
19451
|
+
"description_full": "Adversaries may perform a program download to transfer a user program to a controller. Variations of program download, such as online edit and program append, allow a controller to continue running during the transfer and reconfiguration process without interruption to process control. However, before starting a full program download (i.e., download all) a controller may need to go into a stop state. This can have negative consequences on the physical process, especially if the controller is not able to fulfill a time-sensitive action. Adversaries may choose to avoid a download all in favor of an online edit or program append to avoid disrupting the physical process. An adversary may need to use the technique Detect Operating Mode or Change Operating Mode to make sure the controller is in the proper mode to accept a program download. The granularity of control to transfer a user program in whole or parts is dictated by the management protocol (e.g., S7CommPlus, TriStation) and underlying controller API. Thus, program download is a high-level term for the suite of vendor-specific API calls used to configure a controllers user program memory space. [Modify Controller Tasking](https://attack.mitre.org/techniques/T0821) and [Modify Program](https://attack.mitre.org/techniques/T0889) represent the configuration changes that are transferred to a controller via a program download.",
|
|
19452
|
+
"platforms": [
|
|
19453
|
+
"None"
|
|
19454
|
+
],
|
|
19455
|
+
"detection": null,
|
|
19456
|
+
"reference_url": "https://attack.mitre.org/techniques/T0843",
|
|
19457
|
+
"stix_id": "attack-pattern--be69c571-d746-4b1f-bdd0-c0c9817e9068",
|
|
19458
|
+
"last_verified": "2026-05-19",
|
|
19459
|
+
"_auto_imported": true,
|
|
19460
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19461
|
+
"_matrix": "ics-attack"
|
|
19462
|
+
},
|
|
19463
|
+
"T0847": {
|
|
19464
|
+
"id": "T0847",
|
|
19465
|
+
"name": "Replication Through Removable Media",
|
|
19466
|
+
"version": "ics-attack-v15",
|
|
19467
|
+
"tactic": [
|
|
19468
|
+
"Initial Access (ICS)"
|
|
19469
|
+
],
|
|
19470
|
+
"description": "Adversaries may move onto systems, such as those separated from the enterprise network, by copying malware to removable media which is inserted into the control systems environment.",
|
|
19471
|
+
"description_full": "Adversaries may move onto systems, such as those separated from the enterprise network, by copying malware to removable media which is inserted into the control systems environment. The adversary may rely on unknowing trusted third parties, such as suppliers or contractors with access privileges, to introduce the removable media. This technique enables initial access to target devices that never connect to untrusted networks, but are physically accessible. Operators of the German nuclear power plant, Gundremmingen, discovered malware on a facility computer not connected to the internet. (Citation: Kernkraftwerk Gundremmingen April 2016) (Citation: Trend Micro April 2016) The malware included Conficker and W32.Ramnit, which were also found on eighteen removable disk drives in the facility. (Citation: Christoph Steitz, Eric Auchard April 2016) (Citation: Catalin Cimpanu April 2016) (Citation: Peter Dockrill April 2016) (Citation: Lee Mathews April 2016) (Citation: Sean Gallagher April 2016) (Citation: Dark Reading Staff April 2016) The plant has since checked for infection and cleaned up more than 1,000 computers. (Citation: BBC April 2016) An ESET researcher commented that internet disconnection does not guarantee system safety from infection or payload execution. (Citation: ESET April 2016)",
|
|
19472
|
+
"platforms": [
|
|
19473
|
+
"None"
|
|
19474
|
+
],
|
|
19475
|
+
"detection": null,
|
|
19476
|
+
"reference_url": "https://attack.mitre.org/techniques/T0847",
|
|
19477
|
+
"stix_id": "attack-pattern--c267bbee-bb59-47fe-85e0-3ed210337c21",
|
|
19478
|
+
"last_verified": "2026-05-19",
|
|
19479
|
+
"_auto_imported": true,
|
|
19480
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19481
|
+
"_matrix": "ics-attack"
|
|
19482
|
+
},
|
|
19483
|
+
"T0846.002": {
|
|
19484
|
+
"id": "T0846.002",
|
|
19485
|
+
"name": "Broadcast Discovery",
|
|
19486
|
+
"version": "ics-attack-v15",
|
|
19487
|
+
"tactic": [
|
|
19488
|
+
"Discovery (ICS)"
|
|
19489
|
+
],
|
|
19490
|
+
"description": "Adversaries may perform broadcast discovery requests to enumerate systems and devices on a network.",
|
|
19491
|
+
"description_full": "Adversaries may perform broadcast discovery requests to enumerate systems and devices on a network. Broadcast discovery works by one system or device sending messages to all systems and devices on a network (or subnet) and then waiting for a response. If a response is received that means the system or device that responded is live and can communicate over that protocol. Adversaries may leverage different protocols supported on the network for sending broadcast messages. Some common OT protocols that have broadcast discovery mechanisms are Building Automation and Control Network (BACNet) Who-Is requests, Common Industrial Protocol (CIP) List Identity User Datagram Protocol (UDP) broadcast requests, and Siemens S7 broadcast identification requests.(Citation: Broadcasting BACnet)(Citation: Cisco Active Discovery)",
|
|
19492
|
+
"platforms": [],
|
|
19493
|
+
"detection": null,
|
|
19494
|
+
"reference_url": "https://attack.mitre.org/techniques/T0846/002",
|
|
19495
|
+
"stix_id": "attack-pattern--c55f0be5-044e-4577-8095-65b37680d28c",
|
|
19496
|
+
"last_verified": "2026-05-19",
|
|
19497
|
+
"_auto_imported": true,
|
|
19498
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19499
|
+
"_matrix": "ics-attack",
|
|
19500
|
+
"_gap_skip": {
|
|
19501
|
+
"fields": [
|
|
19502
|
+
"platforms"
|
|
19503
|
+
],
|
|
19504
|
+
"reason": "ICS-attack techniques do not carry a platforms field in MITRE STIX — they target the ICS matrix as a whole rather than specific OS/cloud platforms"
|
|
19505
|
+
}
|
|
19506
|
+
},
|
|
19507
|
+
"T0852": {
|
|
19508
|
+
"id": "T0852",
|
|
19509
|
+
"name": "Screen Capture",
|
|
19510
|
+
"version": "ics-attack-v15",
|
|
19511
|
+
"tactic": [
|
|
19512
|
+
"Collection (ICS)"
|
|
19513
|
+
],
|
|
19514
|
+
"description": "Adversaries may attempt to perform screen capture of devices in the control system environment.",
|
|
19515
|
+
"description_full": "Adversaries may attempt to perform screen capture of devices in the control system environment. Screenshots may be taken of workstations, HMIs, or other devices that display environment-relevant process, device, reporting, alarm, or related data. These device displays may reveal information regarding the ICS process, layout, control, and related schematics. In particular, an HMI can provide a lot of important industrial process information. (Citation: ICS-CERT October 2017) Analysis of screen captures may provide the adversary with an understanding of intended operations and interactions between critical devices.",
|
|
19516
|
+
"platforms": [
|
|
19517
|
+
"None"
|
|
19518
|
+
],
|
|
19519
|
+
"detection": null,
|
|
19520
|
+
"reference_url": "https://attack.mitre.org/techniques/T0852",
|
|
19521
|
+
"stix_id": "attack-pattern--c5e3cdbc-0387-4be9-8f83-ff5c0865f377",
|
|
19522
|
+
"last_verified": "2026-05-19",
|
|
19523
|
+
"_auto_imported": true,
|
|
19524
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19525
|
+
"_matrix": "ics-attack"
|
|
19526
|
+
},
|
|
19527
|
+
"T0859": {
|
|
19528
|
+
"id": "T0859",
|
|
19529
|
+
"name": "Valid Accounts",
|
|
19530
|
+
"version": "ics-attack-v15",
|
|
19531
|
+
"tactic": [
|
|
19532
|
+
"Persistence (ICS)",
|
|
19533
|
+
"Lateral Movement (ICS)"
|
|
19534
|
+
],
|
|
19535
|
+
"description": "Adversaries may steal the credentials of a specific user or service account using credential access techniques.",
|
|
19536
|
+
"description_full": "Adversaries may steal the credentials of a specific user or service account using credential access techniques. In some cases, default credentials for control system devices may be publicly available. Compromised credentials may be used to bypass access controls placed on various resources on hosts and within the network, and may even be used for persistent access to remote systems. Compromised and default credentials may also grant an adversary increased privilege to specific systems and devices or access to restricted areas of the network. Adversaries may choose not to use malware or tools, in conjunction with the legitimate access those credentials provide, to make it harder to detect their presence or to control devices and send legitimate commands in an unintended way. Adversaries may also create accounts, sometimes using predefined account names and passwords, to provide a means of backup access for persistence. (Citation: Booz Allen Hamilton) The overlap of credentials and permissions across a network of systems is of concern because the adversary may be able to pivot across accounts and systems to reach a high level of access (i.e., domain or enterprise administrator) and possibly between the enterprise and operational technology environments. Adversaries may be able to leverage valid credentials from one system to gain access to another system.",
|
|
19537
|
+
"platforms": [
|
|
19538
|
+
"None"
|
|
19539
|
+
],
|
|
19540
|
+
"detection": null,
|
|
19541
|
+
"reference_url": "https://attack.mitre.org/techniques/T0859",
|
|
19542
|
+
"stix_id": "attack-pattern--cd2c76a4-5e23-4ca5-9c40-d5e0604f7101",
|
|
19543
|
+
"last_verified": "2026-05-19",
|
|
19544
|
+
"_auto_imported": true,
|
|
19545
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19546
|
+
"_matrix": "ics-attack"
|
|
19547
|
+
},
|
|
19548
|
+
"T0890": {
|
|
19549
|
+
"id": "T0890",
|
|
19550
|
+
"name": "Exploitation for Privilege Escalation",
|
|
19551
|
+
"version": "ics-attack-v15",
|
|
19552
|
+
"tactic": [
|
|
19553
|
+
"Privilege Escalation (ICS)"
|
|
19554
|
+
],
|
|
19555
|
+
"description": "Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.",
|
|
19556
|
+
"description_full": "Adversaries may exploit software vulnerabilities in an attempt to elevate privileges. Exploitation of a software vulnerability occurs when an adversary takes advantage of a programming error in a program, service, or within the operating system software or kernel itself to execute adversary-controlled code. Security constructs such as permission levels will often hinder access to information and use of certain techniques, so adversaries will likely need to perform privilege escalation to include use of software exploitation to circumvent those restrictions. (Citation: The MITRE Corporation) When initially gaining access to a system, an adversary may be operating within a lower privileged process which will prevent them from accessing certain resources on the system. Vulnerabilities may exist, usually in operating system components and software commonly running at higher permissions, that can be exploited to gain higher levels of access on the system. This could enable someone to move from unprivileged or user level permissions to SYSTEM or root permissions depending on the component that is vulnerable. This may be a necessary step for an adversary compromising an endpoint system that has been properly configured and limits other privilege escalation methods. (Citation: The MITRE Corporation)",
|
|
19557
|
+
"platforms": [
|
|
19558
|
+
"None"
|
|
19559
|
+
],
|
|
19560
|
+
"detection": null,
|
|
19561
|
+
"reference_url": "https://attack.mitre.org/techniques/T0890",
|
|
19562
|
+
"stix_id": "attack-pattern--cfe68e93-ce94-4c0f-a57d-3aa72cedd618",
|
|
19563
|
+
"last_verified": "2026-05-19",
|
|
19564
|
+
"_auto_imported": true,
|
|
19565
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19566
|
+
"_matrix": "ics-attack"
|
|
19567
|
+
},
|
|
19568
|
+
"T0846": {
|
|
19569
|
+
"id": "T0846",
|
|
19570
|
+
"name": "Remote System Discovery",
|
|
19571
|
+
"version": "ics-attack-v15",
|
|
19572
|
+
"tactic": [
|
|
19573
|
+
"Discovery (ICS)"
|
|
19574
|
+
],
|
|
19575
|
+
"description": "Adversaries may attempt to get a listing of other systems by IP address, hostname, or other logical identifier on a network that may be used for subsequent Lateral Movement or Discovery techniques.",
|
|
19576
|
+
"description_full": "Adversaries may attempt to get a listing of other systems by IP address, hostname, or other logical identifier on a network that may be used for subsequent Lateral Movement or Discovery techniques. Functionality could exist within adversary tools to enable this, but utilities available on the operating system or vendor software could also be used.(Citation: Enterprise ATT&CK January 2018)",
|
|
19577
|
+
"platforms": [
|
|
19578
|
+
"None"
|
|
19579
|
+
],
|
|
19580
|
+
"detection": null,
|
|
19581
|
+
"reference_url": "https://attack.mitre.org/techniques/T0846",
|
|
19582
|
+
"stix_id": "attack-pattern--d5a69cfb-fc2a-46cb-99eb-74b236db5061",
|
|
19583
|
+
"last_verified": "2026-05-19",
|
|
19584
|
+
"_auto_imported": true,
|
|
19585
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19586
|
+
"_matrix": "ics-attack"
|
|
19587
|
+
},
|
|
19588
|
+
"T0884": {
|
|
19589
|
+
"id": "T0884",
|
|
19590
|
+
"name": "Connection Proxy",
|
|
19591
|
+
"version": "ics-attack-v15",
|
|
19592
|
+
"tactic": [
|
|
19593
|
+
"Command and Control (ICS)"
|
|
19594
|
+
],
|
|
19595
|
+
"description": "Adversaries may use a connection proxy to direct network traffic between systems or act as an intermediary for network communications.",
|
|
19596
|
+
"description_full": "Adversaries may use a connection proxy to direct network traffic between systems or act as an intermediary for network communications. The definition of a proxy can also be expanded to encompass trust relationships between networks in peer-to-peer, mesh, or trusted connections between networks consisting of hosts or systems that regularly communicate with each other. The network may be within a single organization or across multiple organizations with trust relationships. Adversaries could use these types of relationships to manage command and control communications, to reduce the number of simultaneous outbound network connections, to provide resiliency in the face of connection loss, or to ride over existing trusted communications paths between victims to avoid suspicion. (Citation: Enterprise ATT&CK January 2018)",
|
|
19597
|
+
"platforms": [
|
|
19598
|
+
"None"
|
|
19599
|
+
],
|
|
19600
|
+
"detection": null,
|
|
19601
|
+
"reference_url": "https://attack.mitre.org/techniques/T0884",
|
|
19602
|
+
"stix_id": "attack-pattern--d67adac8-e3b9-44f9-9e6d-6c2a7d69dbe4",
|
|
19603
|
+
"last_verified": "2026-05-19",
|
|
19604
|
+
"_auto_imported": true,
|
|
19605
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19606
|
+
"_matrix": "ics-attack"
|
|
19607
|
+
},
|
|
19608
|
+
"T0843.002": {
|
|
19609
|
+
"id": "T0843.002",
|
|
19610
|
+
"name": "Online Edit",
|
|
19611
|
+
"version": "ics-attack-v15",
|
|
19612
|
+
"tactic": [
|
|
19613
|
+
"Lateral Movement (ICS)"
|
|
19614
|
+
],
|
|
19615
|
+
"description": "Adversaries may execute an online edit of a PLC to update parts of an existing program.",
|
|
19616
|
+
"description_full": "Adversaries may execute an online edit of a PLC to update parts of an existing program. It does not require stopping the PLC which allows it to continue running during transfer and reconfiguration without interruption to process control. Adversaries may leverage this approach to minimize downtime and evade detection. The ability to perform an online edit to the PLC typically relies on access to a workstation with the vendor-specific PLC programming software installed.",
|
|
19617
|
+
"platforms": [],
|
|
19618
|
+
"detection": null,
|
|
19619
|
+
"reference_url": "https://attack.mitre.org/techniques/T0843/002",
|
|
19620
|
+
"stix_id": "attack-pattern--d85a6ee9-820c-4adf-8a64-2392ee70c83c",
|
|
19621
|
+
"last_verified": "2026-05-19",
|
|
19622
|
+
"_auto_imported": true,
|
|
19623
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19624
|
+
"_matrix": "ics-attack",
|
|
19625
|
+
"_gap_skip": {
|
|
19626
|
+
"fields": [
|
|
19627
|
+
"platforms"
|
|
19628
|
+
],
|
|
19629
|
+
"reason": "ICS-attack techniques do not carry a platforms field in MITRE STIX — they target the ICS matrix as a whole rather than specific OS/cloud platforms"
|
|
19630
|
+
}
|
|
19631
|
+
},
|
|
19632
|
+
"T0869": {
|
|
19633
|
+
"id": "T0869",
|
|
19634
|
+
"name": "Standard Application Layer Protocol",
|
|
19635
|
+
"version": "ics-attack-v15",
|
|
19636
|
+
"tactic": [
|
|
19637
|
+
"Command and Control (ICS)"
|
|
19638
|
+
],
|
|
19639
|
+
"description": "Adversaries may establish command and control capabilities over commonly used application layer protocols such as HTTP(S), OPC, RDP, telnet, DNP3, and modbus.",
|
|
19640
|
+
"description_full": "Adversaries may establish command and control capabilities over commonly used application layer protocols such as HTTP(S), OPC, RDP, telnet, DNP3, and modbus. These protocols may be used to disguise adversary actions as benign network traffic. Standard protocols may be seen on their associated port or in some cases over a non-standard port. Adversaries may use these protocols to reach out of the network for command and control, or in some cases to other infected devices within the network.",
|
|
19641
|
+
"platforms": [
|
|
19642
|
+
"None"
|
|
19643
|
+
],
|
|
19644
|
+
"detection": null,
|
|
19645
|
+
"reference_url": "https://attack.mitre.org/techniques/T0869",
|
|
19646
|
+
"stix_id": "attack-pattern--e076cca8-2f08-45c9-aff7-ea5ac798b387",
|
|
19647
|
+
"last_verified": "2026-05-19",
|
|
19648
|
+
"_auto_imported": true,
|
|
19649
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19650
|
+
"_matrix": "ics-attack"
|
|
19651
|
+
},
|
|
19652
|
+
"T1692": {
|
|
19653
|
+
"id": "T1692",
|
|
19654
|
+
"name": "Unauthorized Message",
|
|
19655
|
+
"version": "ics-attack-v15",
|
|
19656
|
+
"tactic": [
|
|
19657
|
+
"Evasion (ICS)",
|
|
19658
|
+
"Impair Process Control"
|
|
19659
|
+
],
|
|
19660
|
+
"description": "Adversaries may send unauthorized messages to ICS systems and devices to evade defenses or manipulate processes.",
|
|
19661
|
+
"description_full": "Adversaries may send unauthorized messages to ICS systems and devices to evade defenses or manipulate processes. Unauthorized messages can be categorized as either reporting messages that contain telemetry data about the current state of systems, devices, and processes or as command messages which instruct systems and devices on how to operate. By injecting unauthorized messages, adversaries can make it appear as if everything is working correctly when it isn’t, trigger alarms to misdirect personnel or impact processes, and manipulate controls to disrupt processes.(Citation: Bonnie Zhu, Anthony Joseph, Shankar Sastry 2011) Adversaries may send unauthorized messages in an ICS environment using software found within the environment (living-off-the-land, vendor-specific interfaces, etc.), custom tooling leveraging OT protocols and libraries, or by positioning themselves between systems and devices and injecting messages into the communications such as the case with an [Adversary-in-the-Middle](https://attack.mitre.org/techniques/T0830) attack.",
|
|
19662
|
+
"platforms": [],
|
|
19663
|
+
"detection": null,
|
|
19664
|
+
"reference_url": "https://attack.mitre.org/techniques/T1692",
|
|
19665
|
+
"stix_id": "attack-pattern--e17cdc00-8b58-4e5f-9d50-4cad1592c4c3",
|
|
19666
|
+
"last_verified": "2026-05-19",
|
|
19667
|
+
"_auto_imported": true,
|
|
19668
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19669
|
+
"_matrix": "ics-attack",
|
|
19670
|
+
"_gap_skip": {
|
|
19671
|
+
"fields": [
|
|
19672
|
+
"platforms"
|
|
19673
|
+
],
|
|
19674
|
+
"reason": "ICS-attack techniques do not carry a platforms field in MITRE STIX — they target the ICS matrix as a whole rather than specific OS/cloud platforms"
|
|
19675
|
+
}
|
|
19676
|
+
},
|
|
19677
|
+
"T0886": {
|
|
19678
|
+
"id": "T0886",
|
|
19679
|
+
"name": "Remote Services",
|
|
19680
|
+
"version": "ics-attack-v15",
|
|
19681
|
+
"tactic": [
|
|
19682
|
+
"Initial Access (ICS)",
|
|
19683
|
+
"Lateral Movement (ICS)"
|
|
19684
|
+
],
|
|
19685
|
+
"description": "Adversaries may leverage remote services to move between assets and network segments.",
|
|
19686
|
+
"description_full": "Adversaries may leverage remote services to move between assets and network segments. These services are often used to allow operators to interact with systems remotely within the network, some examples are RDP, SMB, SSH, and other similar mechanisms. (Citation: Blake Johnson, Dan Caban, Marina Krotofil, Dan Scali, Nathan Brubaker, Christopher Glyer December 2017) (Citation: Dragos December 2017) (Citation: Joe Slowik April 2019) Remote services could be used to support remote access, data transmission, authentication, name resolution, and other remote functions. Further, remote services may be necessary to allow operators and administrators to configure systems within the network from their engineering or management workstations. An adversary may use this technique to access devices which may be dual-homed (Citation: Blake Johnson, Dan Caban, Marina Krotofil, Dan Scali, Nathan Brubaker, Christopher Glyer December 2017) to multiple network segments, and can be used for [Program Download](https://attack.mitre.org/techniques/T0843) or to execute attacks on control devices directly through [Valid Accounts](https://attack.mitre.org/techniques/T0859). Specific remote services (RDP & VNC) may be a precursor to enable [Graphical User Interface](https://attack.mitre.org/techniques/T0823) execution on devices such as HMIs or engineering workstation software. Based on incident data, CISA and FBI assessed that Chinese state-sponsored actors also compromised various authorized remote access channels, including systems designed to transfer data and/or allow access between corporate and ICS networks. (Citation: CISA AA21-201A Pipeline Intrusion July 2021)",
|
|
19687
|
+
"platforms": [
|
|
19688
|
+
"None"
|
|
19689
|
+
],
|
|
19690
|
+
"detection": null,
|
|
19691
|
+
"reference_url": "https://attack.mitre.org/techniques/T0886",
|
|
19692
|
+
"stix_id": "attack-pattern--e1f9cdd2-9511-4fca-90d7-f3e92cfdd0bf",
|
|
19693
|
+
"last_verified": "2026-05-19",
|
|
19694
|
+
"_auto_imported": true,
|
|
19695
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19696
|
+
"_matrix": "ics-attack"
|
|
19697
|
+
},
|
|
19698
|
+
"T0813": {
|
|
19699
|
+
"id": "T0813",
|
|
19700
|
+
"name": "Denial of Control",
|
|
19701
|
+
"version": "ics-attack-v15",
|
|
19702
|
+
"tactic": [
|
|
19703
|
+
"Impact (ICS)"
|
|
19704
|
+
],
|
|
19705
|
+
"description": "Adversaries may cause a denial of control to temporarily prevent operators and engineers from interacting with process controls.",
|
|
19706
|
+
"description_full": "Adversaries may cause a denial of control to temporarily prevent operators and engineers from interacting with process controls. An adversary may attempt to deny process control access to cause a temporary loss of communication with the control device or to prevent operator adjustment of process controls. An affected process may still be operating during the period of control loss, but not necessarily in a desired state. (Citation: Corero) (Citation: Michael J. Assante and Robert M. Lee) (Citation: Tyson Macaulay) In the 2017 Dallas Siren incident operators were unable to disable the false alarms from the Office of Emergency Management headquarters. (Citation: Mark Loveless April 2017)",
|
|
19707
|
+
"platforms": [
|
|
19708
|
+
"None"
|
|
19709
|
+
],
|
|
19710
|
+
"detection": null,
|
|
19711
|
+
"reference_url": "https://attack.mitre.org/techniques/T0813",
|
|
19712
|
+
"stix_id": "attack-pattern--e33c7ecc-5a38-497f-beb2-a9a2049a4c20",
|
|
19713
|
+
"last_verified": "2026-05-19",
|
|
19714
|
+
"_auto_imported": true,
|
|
19715
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19716
|
+
"_matrix": "ics-attack"
|
|
19717
|
+
},
|
|
19718
|
+
"T0838": {
|
|
19719
|
+
"id": "T0838",
|
|
19720
|
+
"name": "Modify Alarm Settings",
|
|
19721
|
+
"version": "ics-attack-v15",
|
|
19722
|
+
"tactic": [
|
|
19723
|
+
"Inhibit Response Function"
|
|
19724
|
+
],
|
|
19725
|
+
"description": "Adversaries may modify alarm settings to prevent alerts that may inform operators of their presence or to prevent responses to dangerous and unintended scenarios.",
|
|
19726
|
+
"description_full": "Adversaries may modify alarm settings to prevent alerts that may inform operators of their presence or to prevent responses to dangerous and unintended scenarios. Reporting messages are a standard part of data acquisition in control systems. Reporting messages are used as a way to transmit system state information and acknowledgements that specific actions have occurred. These messages provide vital information for the management of a physical process, and keep operators, engineers, and administrators aware of the state of system devices and physical processes. If an adversary is able to change the reporting settings, certain events could be prevented from being reported. This type of modification can also prevent operators or devices from performing actions to keep the system in a safe state. If critical reporting messages cannot trigger these actions then a [Impact](https://attack.mitre.org/tactics/TA0105) could occur. In ICS environments, the adversary may have to use [Alarm Suppression](https://attack.mitre.org/techniques/T0878) or contend with multiple alarms and/or alarm propagation to achieve a specific goal to evade detection or prevent intended responses from occurring. (Citation: Jos Wetzels, Marina Krotofil 2019) Methods of suppression often rely on modification of alarm settings, such as modifying in memory code to fixed values or tampering with assembly level instruction code.",
|
|
19727
|
+
"platforms": [
|
|
19728
|
+
"None"
|
|
19729
|
+
],
|
|
19730
|
+
"detection": null,
|
|
19731
|
+
"reference_url": "https://attack.mitre.org/techniques/T0838",
|
|
19732
|
+
"stix_id": "attack-pattern--e5de767e-f513-41cd-aa15-33f6ce5fbf92",
|
|
19733
|
+
"last_verified": "2026-05-19",
|
|
19734
|
+
"_auto_imported": true,
|
|
19735
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19736
|
+
"_matrix": "ics-attack"
|
|
19737
|
+
},
|
|
19738
|
+
"T0885": {
|
|
19739
|
+
"id": "T0885",
|
|
19740
|
+
"name": "Commonly Used Port",
|
|
19741
|
+
"version": "ics-attack-v15",
|
|
19742
|
+
"tactic": [
|
|
19743
|
+
"Command and Control (ICS)"
|
|
19744
|
+
],
|
|
19745
|
+
"description": "Adversaries may communicate over a commonly used port to bypass firewalls or network detection systems and to blend in with normal network activity, to avoid more detailed inspection.",
|
|
19746
|
+
"description_full": "Adversaries may communicate over a commonly used port to bypass firewalls or network detection systems and to blend in with normal network activity, to avoid more detailed inspection. They may use the protocol associated with the port, or a completely different protocol. They may use commonly open ports, such as the examples provided below. * TCP:80 (HTTP) * TCP:443 (HTTPS) * TCP/UDP:53 (DNS) * TCP:1024-4999 (OPC on XP/Win2k3) * TCP:49152-65535 (OPC on Vista and later) * TCP:23 (TELNET) * UDP:161 (SNMP) * TCP:502 (MODBUS) * TCP:102 (S7comm/ISO-TSAP) * TCP:20000 (DNP3) * TCP:44818 (Ethernet/IP)",
|
|
19747
|
+
"platforms": [
|
|
19748
|
+
"None"
|
|
19749
|
+
],
|
|
19750
|
+
"detection": null,
|
|
19751
|
+
"reference_url": "https://attack.mitre.org/techniques/T0885",
|
|
19752
|
+
"stix_id": "attack-pattern--e6c31185-8040-4267-83d3-b217b8a92f07",
|
|
19753
|
+
"last_verified": "2026-05-19",
|
|
19754
|
+
"_auto_imported": true,
|
|
19755
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19756
|
+
"_matrix": "ics-attack"
|
|
19757
|
+
},
|
|
19758
|
+
"T0873": {
|
|
19759
|
+
"id": "T0873",
|
|
19760
|
+
"name": "Project File Infection",
|
|
19761
|
+
"version": "ics-attack-v15",
|
|
19762
|
+
"tactic": [
|
|
19763
|
+
"Persistence (ICS)"
|
|
19764
|
+
],
|
|
19765
|
+
"description": "Adversaries may attempt to infect project files with malicious code.",
|
|
19766
|
+
"description_full": "Adversaries may attempt to infect project files with malicious code. These project files may consist of objects, program organization units, variables such as tags, documentation, and other configurations needed for PLC programs to function.(Citation: Beckhoff) Using built in functions of the engineering software, adversaries may be able to download an infected program to a PLC in the operating environment enabling further [Execution](https://attack.mitre.org/tactics/TA0104) and [Persistence](https://attack.mitre.org/tactics/TA0110) techniques.(Citation: PLCdev) Adversaries may export their own code into project files with conditions to execute at specific intervals.(Citation: Nicolas Falliere, Liam O Murchu, Eric Chien February 2011) Malicious programs allow adversaries control of all aspects of the process enabled by the PLC. Once the project file is downloaded to a PLC the workstation device may be disconnected with the infected project file still executing.(Citation: PLCdev)",
|
|
19767
|
+
"platforms": [
|
|
19768
|
+
"None"
|
|
19769
|
+
],
|
|
19770
|
+
"detection": null,
|
|
19771
|
+
"reference_url": "https://attack.mitre.org/techniques/T0873",
|
|
19772
|
+
"stix_id": "attack-pattern--e72425f8-9ae6-41d3-bfdb-e1b865e60722",
|
|
19773
|
+
"last_verified": "2026-05-19",
|
|
19774
|
+
"_auto_imported": true,
|
|
19775
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19776
|
+
"_matrix": "ics-attack"
|
|
19777
|
+
},
|
|
19778
|
+
"T0840": {
|
|
19779
|
+
"id": "T0840",
|
|
19780
|
+
"name": "Network Connection Enumeration",
|
|
19781
|
+
"version": "ics-attack-v15",
|
|
19782
|
+
"tactic": [
|
|
19783
|
+
"Discovery (ICS)"
|
|
19784
|
+
],
|
|
19785
|
+
"description": "Adversaries may perform network connection enumeration to discover information about device communication patterns.",
|
|
19786
|
+
"description_full": "Adversaries may perform network connection enumeration to discover information about device communication patterns. If an adversary can inspect the state of a network connection with tools, such as Netstat(Citation: Netstat), in conjunction with [System Firmware](https://attack.mitre.org/techniques/T0857), then they can determine the role of certain devices on the network (Citation: MITRE). The adversary can also use [Network Sniffing](https://attack.mitre.org/techniques/T0842) to watch network traffic for details about the source, destination, protocol, and content.",
|
|
19787
|
+
"platforms": [
|
|
19788
|
+
"None"
|
|
19789
|
+
],
|
|
19790
|
+
"detection": null,
|
|
19791
|
+
"reference_url": "https://attack.mitre.org/techniques/T0840",
|
|
19792
|
+
"stix_id": "attack-pattern--ea0c980c-5cf0-43a7-a049-59c4c207566e",
|
|
19793
|
+
"last_verified": "2026-05-19",
|
|
19794
|
+
"_auto_imported": true,
|
|
19795
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19796
|
+
"_matrix": "ics-attack"
|
|
19797
|
+
},
|
|
19798
|
+
"T0893": {
|
|
19799
|
+
"id": "T0893",
|
|
19800
|
+
"name": "Data from Local System",
|
|
19801
|
+
"version": "ics-attack-v15",
|
|
19802
|
+
"tactic": [
|
|
19803
|
+
"Collection (ICS)"
|
|
19804
|
+
],
|
|
19805
|
+
"description": "Adversaries may target and collect data from local system sources, such as file systems, configuration files, or local databases.",
|
|
19806
|
+
"description_full": "Adversaries may target and collect data from local system sources, such as file systems, configuration files, or local databases. This can include sensitive data such as specifications, schematics, or diagrams of control system layouts, devices, and processes. Adversaries may do this using [Command-Line Interface](https://attack.mitre.org/techniques/T0807) or [Scripting](https://attack.mitre.org/techniques/T0853) techniques to interact with the file system to gather information. Adversaries may also use [Automated Collection](https://attack.mitre.org/techniques/T0802) on the local system.",
|
|
19807
|
+
"platforms": [
|
|
19808
|
+
"None"
|
|
19809
|
+
],
|
|
19810
|
+
"detection": null,
|
|
19811
|
+
"reference_url": "https://attack.mitre.org/techniques/T0893",
|
|
19812
|
+
"stix_id": "attack-pattern--fa3aa267-da22-4bdd-961f-03223322a8d5",
|
|
19813
|
+
"last_verified": "2026-05-19",
|
|
19814
|
+
"_auto_imported": true,
|
|
19815
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19816
|
+
"_matrix": "ics-attack"
|
|
19817
|
+
},
|
|
19818
|
+
"T0892": {
|
|
19819
|
+
"id": "T0892",
|
|
19820
|
+
"name": "Change Credential",
|
|
19821
|
+
"version": "ics-attack-v15",
|
|
19822
|
+
"tactic": [
|
|
19823
|
+
"Inhibit Response Function"
|
|
19824
|
+
],
|
|
19825
|
+
"description": "Adversaries may modify software and device credentials to prevent operator and responder access.",
|
|
19826
|
+
"description_full": "Adversaries may modify software and device credentials to prevent operator and responder access. Depending on the device, the modification or addition of this password could prevent any device configuration actions from being accomplished and may require a factory reset or replacement of hardware. These credentials are often built-in features provided by the device vendors as a means to restrict access to management interfaces. An adversary with access to valid or hardcoded credentials could change the credential to prevent future authorized device access. Change Credential may be especially damaging when paired with other techniques such as Modify Program, Data Destruction, or Modify Controller Tasking. In these cases, a device’s configuration may be destroyed or include malicious actions for the process environment, which cannot not be removed through normal device configuration actions. Additionally, recovery of the device and original configuration may be difficult depending on the features provided by the device. In some cases, these passwords cannot be removed onsite and may require that the device be sent back to the vendor for additional recovery steps. A chain of incidents occurred in Germany, where adversaries locked operators out of their building automation system (BAS) controllers by enabling a previously unset BCU key. (Citation: German BAS Lockout Dec 2021)",
|
|
19827
|
+
"platforms": [
|
|
19828
|
+
"None"
|
|
19829
|
+
],
|
|
19830
|
+
"detection": null,
|
|
19831
|
+
"reference_url": "https://attack.mitre.org/techniques/T0892",
|
|
19832
|
+
"stix_id": "attack-pattern--fab8fc7d-f27f-4fbb-9de6-44740aade05f",
|
|
19833
|
+
"last_verified": "2026-05-19",
|
|
19834
|
+
"_auto_imported": true,
|
|
19835
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19836
|
+
"_matrix": "ics-attack"
|
|
19837
|
+
},
|
|
19838
|
+
"T1695": {
|
|
19839
|
+
"id": "T1695",
|
|
19840
|
+
"name": "Block Communications",
|
|
19841
|
+
"version": "ics-attack-v15",
|
|
19842
|
+
"tactic": [
|
|
19843
|
+
"Inhibit Response Function"
|
|
19844
|
+
],
|
|
19845
|
+
"description": "Operational technology communications occur over serial COM, Ethernet, Wi-Fi, cellular (4G/5G), and satellite mediums.",
|
|
19846
|
+
"description_full": "Operational technology communications occur over serial COM, Ethernet, Wi-Fi, cellular (4G/5G), and satellite mediums. Adversaries may block communications to prevent reporting messages and command messages from reaching their intended target devices disrupting processes, operations, and causing cyber-physical impacts.(Citation: Bonnie Zhu, Anthony Joseph, Shankar Sastry 2011) Adversaries may block communications by either making modifications to software ([System Firmware](https://attack.mitre.org/techniques/T0857), [Module Firmware](https://attack.mitre.org/techniques/T0839), [Hooking](https://attack.mitre.org/techniques/T0874), and [Rootkit](https://attack.mitre.org/techniques/T0851)) and services ([Service Stop](https://attack.mitre.org/techniques/T0881), [Denial of Service](https://attack.mitre.org/techniques/T0814)) on systems and devices or by positioning themselves between systems and devices and intercepting and blocking the communications such as the case with an [Adversary-in-the-Middle](https://attack.mitre.org/techniques/T0830) attack.",
|
|
19847
|
+
"platforms": [],
|
|
19848
|
+
"detection": null,
|
|
19849
|
+
"reference_url": "https://attack.mitre.org/techniques/T1695",
|
|
19850
|
+
"stix_id": "attack-pattern--fbb67c2d-37c3-49ee-86e3-bf234cc48ca9",
|
|
19851
|
+
"last_verified": "2026-05-19",
|
|
19852
|
+
"_auto_imported": true,
|
|
19853
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19854
|
+
"_matrix": "ics-attack",
|
|
19855
|
+
"_gap_skip": {
|
|
19856
|
+
"fields": [
|
|
19857
|
+
"platforms"
|
|
19858
|
+
],
|
|
19859
|
+
"reason": "ICS-attack techniques do not carry a platforms field in MITRE STIX — they target the ICS matrix as a whole rather than specific OS/cloud platforms"
|
|
19860
|
+
}
|
|
19861
|
+
},
|
|
19862
|
+
"T0889": {
|
|
19863
|
+
"id": "T0889",
|
|
19864
|
+
"name": "Modify Program",
|
|
19865
|
+
"version": "ics-attack-v15",
|
|
19866
|
+
"tactic": [
|
|
19867
|
+
"Persistence (ICS)"
|
|
19868
|
+
],
|
|
19869
|
+
"description": "Adversaries may modify or add a program on a controller to affect how it interacts with the physical process, peripheral devices and other hosts on the network.",
|
|
19870
|
+
"description_full": "Adversaries may modify or add a program on a controller to affect how it interacts with the physical process, peripheral devices and other hosts on the network. Modification to controller programs can be accomplished using a Program Download in addition to other types of program modification such as online edit and program append. Program modification encompasses the addition and modification of instructions and logic contained in Program Organization Units (POU) (Citation: IEC February 2013) and similar programming elements found on controllers. This can include, for example, adding new functions to a controller, modifying the logic in existing functions and making new calls from one function to another. Some programs may allow an adversary to interact directly with the native API of the controller to take advantage of obscure features or vulnerabilities.",
|
|
19871
|
+
"platforms": [
|
|
19872
|
+
"None"
|
|
19873
|
+
],
|
|
19874
|
+
"detection": null,
|
|
19875
|
+
"reference_url": "https://attack.mitre.org/techniques/T0889",
|
|
19876
|
+
"stix_id": "attack-pattern--fc5fda7e-6b2c-4457-b036-759896a2efa2",
|
|
19877
|
+
"last_verified": "2026-05-19",
|
|
19878
|
+
"_auto_imported": true,
|
|
19879
|
+
"_intake_method": "mitre-ics-attack-stix",
|
|
19880
|
+
"_matrix": "ics-attack"
|
|
17390
19881
|
}
|
|
17391
19882
|
}
|