top of page
40051abd5a76713af8f015988fc6780e-blue-phone-icon-with-a-wave-on-it.webp
Logo-Zalo-Arc.webp
Facebook_Messenger_logo_2020.svg.webp
whatsapp

Applying MITRE ATT&CK for SOC: A Method to Measure Detection Coverage

28 minutes ago
10 min read

A Security Operations Center (SOC) might possess hundreds of detection rules, collect logs from multiple systems, and process thousands of alerts daily. However, the sheer volume of rules or alerts fails to answer the critical question: What attack techniques is the SOC actually capable of detecting, and what is it missing?

This is the challenge that MITRE ATT&CK can help resolve. Instead of evaluating monitoring capabilities based solely on tool count, ATT&CK for SOC can be used to link attacker behaviors with monitoring data, detection rules, testing results, and responsible owners.

This method establishes a foundation for measuring Detection Coverage, identifying detection gaps, and prioritizing improvements based on actual risk.

mitre-att-ck-for-soc
MITRE ATT&CK for SOC

What is MITRE ATT&CK and how to apply it for SOC to measure Detection Coverage?

MITRE ATT&CK is a knowledge base of adversary tactics and techniques, built on real-world observations of attacker behaviors. The framework provides a common taxonomy for defense, threat intelligence, and detection engineering teams to analyze attack methodologies.

In ATT&CK, a tactic reflects the adversary's goal, such as credential theft or lateral movement. A technique describes the method used to achieve that goal, while a sub-technique provides a more granular classification level.

For a SOC, ATT&CK shifts the question from "How many alerts does the system generate?" to "Which prioritized attack behaviors can be detected and validated?".

Detection Coverage is the extent to which detection capabilities cover a defined set of attack techniques, within the scope of specific assets and systems.

Three aspects must be distinguished:

  • Visibility Coverage: Does the SOC have the necessary data to observe the behavior?

  • Detection Coverage: Has the SOC implemented a mechanism to detect that behavior?

  • Validated Coverage: Has the detection mechanism been tested, and is there evidence of its operation?

A technique mapped to a detection rule does not guarantee the SOC will detect every variation of that technique.

This highlights the difference between evaluating coverage and merely inventorying the features of a SIEM, EDR, or XDR.

To fully understand the roles of monitoring, investigation, and response within an operational model, organizations can refer to What is a SOC and how a Security Operations Center works.

Select priority threats and techniques before measuring coverage

A common mistake when applying MITRE ATT&CK for a SOC is attempting to measure coverage across the entire matrix from the outset.

ATT&CK describes numerous behaviors across different platforms and environments. Not every technique holds equal relevance for every organization.

For example, an enterprise primarily using Microsoft 365, Active Directory, and Windows workstations faces a different attack surface compared to an organization operating OT systems or large-scale container infrastructure.

Therefore, the measurement scope should be defined by three factors.

Critical assets and systems

The SOC must identify components with a direct business impact, such as administrative accounts, identity systems, application servers, customer data, and cloud platforms.

Priority threat scenarios

Threat intelligence, incident history, and risk assessment results can help select scenarios to monitor, such as infiltration using valid accounts, credential theft, unauthorized code execution, or lateral movement.

Relevant ATT&CK techniques

After defining threat scenarios, the SOC links each behavior to the corresponding technique or sub-technique.

For instance, T1078 – Valid Accounts describes adversaries abusing the credentials of existing accounts. This is a critical technique to consider in environments heavily reliant on identity systems.

The required outcome is a prioritized list of techniques, accompanied by the rationale for selection, affected systems, and evaluation scope.

A program might start with 10–20 risk-prioritized techniques, then expand once the mapping and validation processes mature. This number is merely an implementation suggestion, not a MITRE requirement.

Mapping Technique – Data Source – Rule – Test – Owner

This is the most critical step when implementing MITRE ATT&CK for a SOC. The objective is to build a verifiable link between attack behaviors and operational detection capabilities.

A complete detection mapping must answer five questions: What technique is the adversary executing? What data must the SOC observe? Which rule processes the signal? Has the detection been tested? Who is responsible for its maintenance?

Step 1: Define the technique and behavior to detect

Each technique needs to be broken down into one or more detection hypotheses – hypotheses regarding indicators that may appear when the adversary executes the behavior.

For example, with T1078 – Valid Accounts, the SOC might construct a hypothesis to detect account usage from an unusual location, device, or time.

However, a single after-hours login is insufficient to prove an account compromise. The detection logic must incorporate context to reduce false positives.

Step 2: Identify telemetry sources

The SOC must verify which data can provide evidence for the detection hypothesis.

Depending on the environment, data might originate from Windows Event Logs, EDR telemetry, VPN authentication logs, Microsoft Entra ID sign-in logs, or cloud audit logs.

A notable technical update: Starting with ATT&CK v18 released in October 2025, MITRE has deprecated the old Data Sources category, shifting the detection content focus to Detection Strategies, Analytics, and Data Components.

Consequently, when implementing mapping today, a SOC should combine MITRE's current detection documentation with the organization's actual telemetry inventory, rather than simply copying the outdated Data Sources table.

Step 3: Link detection rules or analytics

The Detection Engineer defines the detection logic, rule ID, correlation conditions, and execution tool.

For instance, a use case detecting anomalous access might combine IP addresses, user identities, login status, devices, and behavioral history.

A technique can link to multiple rules; conversely, a rule can relate to multiple techniques. Thus, the mapping must accurately reflect the behavior the rule actually detects, avoiding overly broad ATT&CK labeling.

Step 4: Attach test cases and testing evidence

Every critical detection requires a testing method, a pass/fail result, and the date of the most recent validation.

If a rule remains untested, its status should be recorded as "implemented," not "validated."

Step 5: Assign owners

An owner is responsible for monitoring rule quality, checking for telemetry changes, addressing failed test results, and updating coverage status.

The owner could be a Detection Engineer, a SOC Lead, or the relevant platform administration team.

Example Detection Coverage Mapping Matrix

Reference model – hypothetical data, not reflecting an actual IPSIP SOC system.

Technique

Telemetry

Detection Rule

Test

Owner

Status

T1078 – Valid Accounts

Identity sign-in logs

UC-01: Anomalous Login

Pass

SOC Lead

Validated

T1059 – Command and Scripting Interpreter

Process telemetry

UC-02: Suspicious Execution

Untested

Detection Engineer

Implemented

T1110 – Brute Force

Authentication logs

Chưa triển khai

—

IAM Team

Telemetry only

T1021 – Remote Services

Remote access logs

Chưa triển khai

—

SOC Engineer

Telemetry only

In a real-world environment, a mapping row should include the applicable system, rule version, testing evidence, review date, and a link to the response playbook.

Input data must also be checked for quality, continuity, and normalization capabilities. The SOC team can refer to Reference SOC architecture with Log, SIEM, SOAR, EDR/XDR, and the response layer to understand the relationships between data collection, detection, and incident response tiers.

Building a Coverage Matrix: Having a rule does not equate to effective detection

Upon completing the mapping, the SOC must translate the data into a coverage matrix to assess which techniques have implemented detections and which techniques still have gaps.

The simplest approach is marking them as "covered" or "not covered." However, this binary method fails to adequately reflect maturity levels.

A reference model might utilize five statuses:

Status

Meaning

 

No Coverage

No appropriate detection mechanism exists

Telemetry Available

Relevant data exists, but no rule is implemented

Implemented

A rule or detection analytic has been deployed

Validated

The rule has passed testing within the defined scope

Operationalized

The detection is tested, owned, integrated into a response process, and subject to review mechanisms

This is a proposed rating scale for SOC management, not an official MITRE scoring system.

ATT&CK Coverage Heatmap

att-ck-coverage-heatmap
Illustrative ATT&CK Coverage Heatmap

A heatmap assists the SOC Manager in quickly identifying areas lacking telemetry, untested rules, or detections not yet integrated into operational processes.

MITRE provides the ATT&CK Navigator to visualize defensive coverage on the ATT&CK matrix. This tool helps present mapping results, but the colors on the heatmap alone do not prove effective detection.

How to calculate coverage ratios without being misleading

The SOC can utilize two metrics:

  • Implemented Coverage = (Techniques with rules ÷ Priority techniques) x 100%

  • Validated Coverage = (Techniques passing tests ÷ Priority techniques) x 100%

For instance, out of 20 priority techniques, if 14 have rules and 9 have passed testing, the implemented coverage is 70%, while the validated coverage is 45%.

These ratios hold meaning only within the scope of the 20 selected techniques. They cannot be interpreted to mean the SOC detects 70% of all attacks.

Crucially, a single technique possesses multiple implementation variants and applicable environments. A successful test only proves the rule detects the tested scenario under those specific conditions.

Detection Validation to confirm actual Coverage

Detection validation is the step that transitions a rule from an "implemented" state to a detection capability backed by empirical evidence.

In reality, a rule might exist in a SIEM but fail to trigger due to missing data fields, changed log formats, misconfigurations, or outdated correlation logic.

Therefore, the SOC must test using a controlled process.

Check data and rule functionality

First, the Detection Engineer confirms that telemetry is fully collected within the evaluation scope, necessary fields are parsed correctly, and the rule is active.

At this level, the objective is to verify the technical conditions enabling the detection to function, not yet to prove its capability to detect adversary behavior.

Perform detection validation

The SOC builds test cases representing the detection hypotheses and executes them within authorized environments.

For example, with an anomalous login detection use case, the testing team might use a test account to generate an authentication event matching the rule's conditions, then verify:

  • Was the event recorded and forwarded to the analysis system?

  • Did the detection rule trigger under the correct conditions?

  • Does the alert contain sufficient information regarding the user, device, time, and access source?

  • Can an analyst triage and validate the alert?

Testing results must be recorded alongside technical evidence.

Testing behavioral chains with Purple Teaming

Once detection capabilities stabilize, an organization can expand testing to behavioral chains mimicking real-world attack scenarios.

Purple Teaming integrates offensive and defensive perspectives to evaluate how multiple detections operate in concert. This method is particularly valuable when an attack chain cannot be identified by a single isolated event.

However, not every use case necessitates a complex adversary simulation test. The depth of testing must align with risk, system criticality, and SOC resources.

Following each cycle, rules failing the test must have their root causes investigated, adjusted, and retested. Detection Coverage holds operational value only when its status is updated based on evidence, rather than subjective assessment.

Reporting Detection Coverage and prioritizing Detection Gaps

The coverage matrix serves more than just Detection Engineers. When organized logically, this data also assists SOC Managers and security leaders in identifying investments likely to improve detection capabilities.

An effective report must clearly present the scope, status, gaps, and subsequent actions.

Clearly define measurement scope

The report must declare the set of evaluated techniques, protected asset types, relevant technology platforms, and the time of measurement.

For example, coverage results for a Windows Endpoint environment should not be used to depict detection capabilities across the entire cloud or OT infrastructure.

Categorize Detection Gaps

Detection gaps typically fall into three primary categories.

  • Telemetry Gap: The SOC has not yet collected the necessary data, or the data quality fails to meet requirements.

  • Detection Gap: Data is available, but no appropriate detection rule or analytic exists.

  • Validation Gap: A rule is implemented but remains untested, failed testing, or the testing evidence is obsolete.

Each category demands a different remediation approach. A Telemetry Gap might necessitate adjustments to log sources or collection scope, whereas a Detection Gap typically requires designing additional use cases. A Validation Gap mandates testing and tuning.

Evaluate outcomes alongside coverage ratios

The SOC should avoid using coverage ratio as its sole KPI.

Metrics such as alert accuracy, false positive rate, mean time to detect (MTTD), mean time to verify, and escalation efficiency must also be considered.

For instance, a technique with a validated detection rule that generates excessive false positives can still impose severe pressure on analysts and degrade operational efficiency.

Furthermore, priority should be given to addressing gaps related to critical assets, highly probable attack scenarios, and high business impact, rather than solely focusing on increasing the number of colored cells on a heatmap.

When an enterprise utilizes external services, the detection scope, testing responsibilities, and reporting must be agreed upon with the provider. Depending on the deployment model, these responsibilities may differ between SOC and MDR.

For organizations weighing investments in an internal team versus outsourcing to a managed partner, factors like personnel, tools, continuous monitoring capabilities, and maintenance costs must also be evaluated. The content on SOC outsourcing and budget optimization provides further perspective on this decision.

Maintaining Detection Coverage as a SOC continuous improvement process

Measuring coverage should not be a "one-and-done" activity.

As organizations deploy new applications, alter cloud infrastructure, add security tools, or adjust logging policies, previously functional detections may no longer receive appropriate data.

Moreover, attack techniques and detection guidance within MITRE ATT&CK are updated over time.

Therefore, the SOC must integrate coverage management into regular detection engineering operations.

An improvement cycle could be structured as follows:

  1. Review threats: Update attack scenarios relevant to the environment and critical assets.

  2. Review mapping: Examine techniques, telemetry, detection analytics, and owners.

  3. Validate detections: Retest critical rules or rules impacted by infrastructure changes.

  4. Prioritize gaps: Identify the highest-risk gaps to incorporate into the improvement plan.

  5. Report progress: Document changes in validated coverage, alert quality, and response capabilities.

The SOC should also define appropriate review cycles based on detection criticality. Use cases protecting privileged accounts or critical assets might require more frequent evaluation than lower-risk use cases.

The crucial point is maintaining traceability from a technique to telemetry, detection logic, test evidence, and the responsible owner.

When executed consistently, MITRE ATT&CK ceases to be merely a reference framework and becomes an integral part of the SOC's methodology for managing and improving detection capabilities.

Enhancing cybersecurity monitoring capabilities with IPSIP Vietnam

Organizations reviewing their SIEM, EDR/XDR systems, or seeking to enhance their monitoring capabilities can explore IPSIP Vietnam's 24/7 SOC services. IPSIP provides a continuous cybersecurity monitoring solution, combining technology and expert teams to triage alerts, investigate, and coordinate incident response in accordance with the service scope.

Enterprises can schedule a consultation with IPSIP to discuss their current monitoring posture, operational requirements, and suitable deployment options.

ipsip-vietnam

Applying MITRE ATT&CK for a SOC helps enterprises transition from security evaluations based on tool and alert volumes to a structured measurement methodology focused on the attack behaviors that genuinely require detection.

Enterprises need not aim for 100% ATT&CK coverage. Instead, they should build a detection program featuring clear scope, evidence-based testing, and continuous improvement.

References:

  1. MITRE ATT&CK – Knowledge Base

  2. MITRE ATT&CK – Valid Accounts (T1078)

  3. MITRE ATT&CK – Detection Strategies

  4. MITRE ATT&CK – Data Sources

  5. MITRE ATT&CK – October 2025 Updates

  6. MITRE ATT&CK – Data & Tools

follow ipsip vietnam.png
bottom of page