Skip to content

Response, New York. Noah Park: Check Point Patches Actively Exploited Management Server Path Traversal. Detection, Dallas. Ava Okello: Report Finds Nearly Half of Deployed Detections Need Attention Before SOCs Can Trust Them.

SOCtember

Always First. Fast SOC News.

MITRE ATT&CK Detection Strategies index page.
Screenshot: MITRE ATT&CK, Detection Strategies index defining strategies as containers for platform-specific analytics (captured September 2026, fair use).

Detection

Did You Know: ATT&CK Detection Strategies Are Systems, Not Sentences

MITRE ATT&CK v18 replaced single-sentence detection notes with Detection Strategies: behavior-first containers that organize platform-specific Analytics, required log sources, and mutable tuning. For detection engineers, coverage means analytics you can run and tune, not technique IDs collected as if a sentence equals a detection.

Ava Okello, DetectionLondon3 min read

BEDFORD - MITRE ATT&CK's v18 detection overhaul reframes how the framework talks to SOC desks. On the public Detection Strategies index, MITRE defines those objects as high-level approaches for detecting specific adversary techniques and as containers that organize multiple platform-specific analytics into cohesive detection methodologies. As of October 21, 2026, with ATT&CK v20 now released, the live index lists 933 Detection Strategies. Lex Crumpton of MITRE ATT&CK put the design principle plainly in a July 2025 Medium post (updated October 22, 2025): detection strategy is not a sentence, it is a system. Amy L. Robertson's October 28, 2025 ATT&CK v18 release note said the same shift in operational terms: guidance moves from single-sentence notes to structured, behavior-focused strategies, with Workbench support for the new objects.

MITRE ATT&CK DET0455 Abuse of PowerShell for Arbitrary Execution strategy page.
Screenshot: MITRE ATT&CK, DET0455 PowerShell Detection Strategy with Analytic AN1252, log sources, and mutable elements (fair use).

Under the new model, a technique connects to a Detection Strategy object that does not hold all of the detection logic itself. It references one or more Analytics that describe how to detect the behavior in different environments. Each Analytic is platform-specific and carries a detection statement, required log sources tied to data components, and mutable elements such as thresholds, time windows, or command-line patterns. Log sources use a PRE:POST naming pattern (for example wineventlog:security or auditd:SYSCALL) and now live as fields on Data Components rather than as separate objects. That chain is the unit of coverage: behavior, platform analytic, telemetry, and tunables.

MITRE ATT&CK brand panel.
Photo: MITRE ATT&CK, official brand marks and homepage, for coverage of the v18 detection overhaul.
SOCtember diagram of the system-versus-sentence Detection Strategies model.
Illustration: SOCtember, system versus sentence: the Detection Strategies model paraphrased from MITRE guidance.

A concrete public example is DET0455, Abuse of PowerShell for Arbitrary Execution, mapped to technique T1059.001. The strategy page lists Analytic AN1252 for Windows, which looks for behavioral chains where PowerShell launches with encoded commands, unusual parents, or suspicious modules, potentially followed by network connections or child processes. Required log sources include process creation (Sysmon EventCode 1) and PowerShell command execution channels (EventCode 4103 through 4106), with mutable fields such as CommandLinePattern, ParentProcessName, TimeWindow, and ScriptBlockLengthThreshold. For desks mapping matrices to SIEM content, the practical takeaway is blunt: collecting technique IDs as if a sentence equals a detection is not coverage. Coverage is a Detection Strategy backed by platform Analytics, the logs those analytics need, and the knobs your environment can actually tune.

SOCtember diagram of the technique to Detection Strategy to Analytics to log sources chain.
Illustration: SOCtember, technique to Detection Strategy to Analytics to log sources, paraphrased from MITRE DET0455.

Sources:


Ava Okello covers detection engineering and SOC analytics for SOCtember from London.

Related stories

Detection desk