SOC & use cases framework gaps

Compare SIEM alert TIDs and your use cases framework inventory against the ATT&CK matrix—see what triggered, what your framework covers, where gaps remain, View report exports, and how BAS results compare to documented coverage.

Evaluate your SOC with six months of triggered TIDs

Map alert history onto the Enterprise matrix to see which ATT&CK techniques your SOC actually triggered—not just which rules exist on paper.

SOC maturity is not only about alert volume—it is about whether your detections cover the ATT&CK techniques that matter in your environment. ATT&CK Intelligence View lets you upload the technique IDs your SIEM mapped from real alerts and overlay them on the matrix without changing your filters.

The goal: answer three questions in one working session. Which in-scope techniques triggered alerts in the last six months? Which triggered but sit outside the scope you filtered (mapping or scope mismatch)? Which in-scope techniques never appeared in alert mappings—potential blind spots?

  1. Export triggered TIDs from your SIEM (last 6 months) — Query alerts or cases from the last six months (adjust the window for your review cadence). Export distinct ATT&CK technique IDs—one row per unique TID. Use a single column header named exactly TID. Include sub-techniques (T1059.001) as your SIEM maps them, not only parent techniques (T1059).
  2. Scope the matrix to your SOC environment — Before uploading, set filters that match where your SOC operates: Platform = Windows for endpoint alerts, Platform = IaaS or SaaS for cloud, Tactic = Initial Access for phishing reviews, or Threat Actor = [group] for sector-specific assessments. The matrix defines “in scope” for blue highlights.
  3. Upload with Compare TIDs with Current Filter — Import → Compare TIDs with Current Filter → upload your .xlsx file. This compares your triggered TID list against the current filtered view. It does not apply your file as a filter—you can change Platform, Tactic, or other filters anytime and comparison stats refresh automatically.
  4. Read the filter logic bar stat cards — In file & current view (red) = TIDs in your six-month export that also appear in the scoped matrix—these are techniques your SOC triggered and that match your current view. In file only (yellow) = triggered in SIEM but outside the filtered view. In view only (blue) = in your scoped view but not in the six-month export.
  5. Map triggered TIDs on the matrix — Use Highlight all mode to keep the full matrix visible while comparison highlights appear on technique cards. Red-tagged techniques = triggered or documented in scope. Yellow = in your file but outside your filter scope. Blue = in scope but missing from your file—prioritize for detection engineering or logging gaps.
  6. Expand TID lists and open technique panels — Expand the stat-card TID lists below the filter bar for exact IDs. Click any highlighted technique to open Detections, Threat Actor, and Mitigations tabs—turn blind-spot TIDs (blue) into backlog items with MITRE telemetry and analytics attached.
  7. Export evidence for leadership and QBRs — Click View report for the Framework Gap Analysis Report modal and multi-page A4 PDF. Export PNG with Comparison for workshop slides showing red, yellow, and blue gaps on the matrix. Export Excel or Framework Gap PDF for Matched TIDs, Missing TIDs, and In View Not In File sheets. Repeat quarterly with a fresh six-month SIEM export to track SOC coverage trends.
Matrix signal What it means for your SOC Typical next step
In file & current view (red)Technique triggered in the last six months and visible in your scoped viewTuning review: confirm true-positive rate, reduce noise, document coverage
In file only (yellow)Technique triggered in SIEM but hidden by current filtersFix scope (Platform/Tactic) or SIEM mapping (parent vs sub-technique)
In view only (blue)In-scope technique with no alert mapping in the review windowDetection backlog: no rule, no logging, no activity, or bad ATT&CK tagging
No highlightEither out of scope or not in your six-month exportExpected for techniques outside your environment or review window

Example — quarterly SOC review (Windows endpoints) — Export 142 unique TIDs from Windows-related alerts over six months. Filter Platform = Windows. Import → Compare TIDs with Current Filter. Result: 98 red (triggered and in scope), 18 yellow (triggered but outside filtered scope—mostly cloud-mapped IDs or parent T1059 vs sub-technique mismatches), 26 blue (Windows techniques in scope that never appeared in alert mappings). Leadership narrative: “We triggered on 98 scoped techniques this half; 26 in-scope Windows techniques never mapped to an alert—those are our detection and logging priorities for next quarter.”

Compare your use cases framework TIDs against the matrix

Gap-check the ATT&CK techniques your detection use cases claim to cover versus the techniques in scope for your environment.

Most organizations maintain a use cases framework—a catalog of SIEM rules, Sigma detections, EDR analytics, or internal DET/AN mappings tied to ATT&CK technique IDs. On paper you may cover hundreds of techniques; the harder question is which in-scope behaviors are still missing from that inventory.

ATT&CK Intelligence View compares your framework TID list against a filtered matrix view without applying the file as a filter. Blue highlights show the primary framework gap signal: techniques in your assessment scope that are not in your use cases inventory.

  1. Export TIDs from your use cases framework — Collect distinct ATT&CK technique IDs your framework documents as covered—one row per unique TID, column header exactly TID. Sources include: SIEM use case libraries, Sigma rule tags, EDR detection packs, Confluence or GRC inventories, purple-team requirement lists, and internal mappings to MITRE detection strategies (DET) or analytics (AN). Include sub-techniques (T1059.001) where your use cases map at that level.
  2. Define the same scope as your framework assessment — Apply filters that match how you audit coverage: Platform = Windows for endpoint use cases, Platform + IaaS for hybrid cloud, Tactic = Execution for a rule-engineering sprint, or Threat Actor = [group] for sector-specific frameworks. Mismatched scope produces misleading yellow counts.
  3. Compare with Compare TIDs with Current Filter — Import → Compare TIDs with Current Filter → upload your framework .xlsx file. This overlays your inventory on the matrix. Filters stay unchanged—you can adjust Platform, Tactic, or Threat Actor anytime and gap counts refresh.
  4. Read framework coverage on the matrix — In file & current view (red) = techniques your framework lists and that appear in the scoped matrix—documented coverage you can evidence in this assessment. In view only (blue) = in-scope techniques missing from your framework—the main backlog for new use cases. In file only (yellow) = framework entries outside the current view (wrong platform, parent vs sub-technique, or scope mismatch).
  5. Prioritize blue gaps into engineering work — Click blue-highlighted techniques. Open Detections for MITRE analytics, mutable parameters, and telemetry. View report or Export → Framework Gap PDF for a stakeholder-ready gap list; export Excel when analysts need Detections and Telemetry detail per technique.
  6. Reconcile yellow entries with framework owners — Yellow TIDs often mean the use case exists but was tagged to a parent technique while MITRE scope uses sub-techniques—or the rule targets cloud while you filtered Windows only. Fix mappings in your framework or adjust filters before reporting gap counts.
  7. Track framework maturity over time — Re-run comparison each quarter after framework updates. View report or Export → Framework Gap PDF to show leadership how many blue gaps closed since the last review. Excel export includes Matched, Missing, and In View Not In File sheets.
Matrix signal What it means for your framework Typical next step
In file & current view (red)Use case documented for this technique and visible in scoped matrixEvidence coverage in audits; schedule tuning or purple-team validation
In view only (blue)In-scope technique with no matching TID in your framework fileWrite new use case; check Detections tab for MITRE analytic and telemetry guidance
In file only (yellow)Framework lists the TID but it is outside current filtersFix ATT&CK tagging (parent/sub), platform scope, or filter alignment
Invalid IDsTID not in ATT&CK v20.0 or malformed in your exportClean framework inventory; remove retired or vendor-specific IDs

Example — Windows use cases framework audit — Your framework documents 210 Windows techniques across Sigma and SIEM use cases. Filter Platform = Windows. Import → Compare TIDs with Current Filter with your master inventory. Result: 167 red (documented and in scope), 12 yellow (documented but outside filtered scope—mostly parent T1059 tags vs sub-technique scope), 31 blue (Windows techniques in scope with no documented use case). The 31 blue TIDs become the Q3 detection engineering backlog with Detections tab exports attached for each priority technique.

What this workflow answers

Security teams constantly ask: Which ATT&CK v20.0 techniques do we actually detect? Which ones fire in our SIEM but we have not modeled? Which techniques are in scope for our environment but missing from our rule inventory?

Compare TIDs with Current Filter answers those questions without changing your matrix filters. Upload your TID list and set or adjust filters anytime; comparison results refresh on the matrix. Click View report for the full Framework Gap Analysis Report and A4 PDF export.

Four comparison result categories — In file & current view (red) = in your file and visible after filters. In file only (yellow) = in your file but outside the current view. In view only (blue) = in the current view but not in your file. Invalid IDs = bad technique IDs or TIDs not in ATT&CK v20.0.

SIEM alert checklist

The section Evaluate your SOC with six months of triggered TIDs is the primary walkthrough. Use this checklist during a working session: export distinct TIDs → scope Platform/Tactic filters → Compare TIDs with Current Filter → read red/yellow/blue on matrix and filter bar → View report or export Framework Gap PDF.

For .xlsx file format, template download, View report, and comparison export filenames, see Export & layers → Compare TIDs with Current Filter.

Use cases framework checklist

The section Compare your use cases framework TIDs against the matrix is the primary walkthrough. Checklist: export framework TIDs → match filter scope → Compare TIDs with Current Filter → triage blue (gaps) and yellow (scope/tagging) → View report or export Framework Gap PDF for audit evidence.

BAS executed techniques vs detection coverage

Compare two standalone TID lists—documented use cases and BAS results—without matrix filters.

After a breach-and-attack simulation or purple-team exercise, teams often ask: Did we exercise techniques we already document? Which BAS paths have no matching use case? Compare Two TID Sheets answers both—no Platform or Tactic filters required.

Export two .xlsx files (one TID column each) or one workbook with two sheets. In Import → Compare Two TID Sheets, name the first list Current Detection Coverage and the second BAS Executed Techniques, upload each file, then click Compare lists. The in-app Two-Sheet Comparison tutorial includes a dummy workbook for practice.

  1. Export both TID lists — From your detection repository, export unique ATT&CK TIDs your organization documents as covered. From your BAS platform, export unique TIDs executed in the review window (last quarter, last exercise, etc.).
  2. Name and upload each list — Import → Compare Two TID Sheets. Enter Current Detection Coverage as the first list name and upload its .xlsx; enter BAS Executed Techniques as the second list name and upload its .xlsx—or upload one two-sheet workbook on either button. Click Compare lists when both are ready.
  3. Prioritize only-in-Sheet-2 (yellow) — Yellow highlights = BAS ran a technique your framework does not document—the primary post-exercise detection backlog. Open each technique's Detections tab and attach analytics to backlog tickets.
  4. Review only-in-Sheet-1 (blue) — Blue highlights = documented coverage BAS never exercised—candidates for next simulation scope or stale catalog entries.
  5. Export for stakeholders — Click View report for the two-sheet comparison modal and A4 PDF. Export Excel Two-Sheet Comparison Report for Summary, Matched, Only Sheet 1, and Only Sheet 2 sheets. Use match % in QBR slides alongside the filter-vs-file SIEM review from the six-month workflow above.

Example — post-exercise readout — Sheet 1: 186 documented TIDs. Sheet 2: 142 BAS executed TIDs. Matched: 98 (red). Only in Sheet 1: 88 (blue)—catalog entries not exercised. Only in Sheet 2: 44 (yellow)—BAS paths with no documented use case. Match % ≈ 43%. Action: assign the 44 yellow TIDs to detection engineering with Detections tab exports; schedule BAS to cover high-risk blue gaps next quarter.

When to use filter comparison instead — Use Compare TIDs with Current Filter (Framework Gap Analysis) when you need matrix scope—e.g. only Windows Execution techniques—and want gaps to refresh when filters change. Use Compare Two TID Sheets when both lists are authoritative on their own. See the Two-Sheet TID Comparison guide for the side-by-side comparison table.

Comparison file format

Use .xlsx with a single header row: TID for filter comparison, or two or more sheets each with a TID column for two-sheet comparison. Download templates from Import → Compare TIDs with Current Filter or Compare Two TID Sheets. Full format rules, sample rows, and security restrictions (no CSV/macros) are documented in Export & layers.

Use case reference

Use case Your TID file Suggested filters Primary gap signal
SIEM — alert historyUnique TIDs from alerts over N monthsPlatform, tactic, or environment matching SOC scopeIn view only (blue) = in scope, never alerted; In file only (yellow) = alerted but outside current view
Use cases framework gap reviewTIDs your SIEM rules, Sigma library, or detection catalog claim to coverSame scope as the framework assessment (platform, tactic, actor)In view only (blue) = in-scope techniques missing from your framework inventory
Purple-team test listTIDs required or tested in exerciseThreat Actor + Platform for emulationIn view only (blue) = in exercise scope, not in test inventory
CTI priority backlogTIDs from intel report or ransomware profileThreat Actor + PlatformIn view only (blue) = intel priority not in detection inventory

Share results with stakeholders

For step-by-step import menu details and layer export formats, see the Export & layers guide. This page covers SOC alert evaluation and use cases framework gap analysis with Compare TIDs with Current Filter.

More