--- name: building-soc-metrics-and-kpi-tracking-0b3207cf42e4 description: 'Builds SOC performance metrics and KPI tracking dashboards measuring Mean Time to Detect (MTTD), Mean Time to Respond (MTTR), alert quality ratios, analyst productivity, and detection coverage using SIEM data. Use when SOC leadership needs operational visibility, continuous improvement tracking, or executive-level reporting on security operations effectiveness. ' domain: cybersecurity subdomain: soc-operations tags: - soc - metrics - kpi - mttd - mttr - dashboard - reporting - continuous-improvement version: '1.0' author: Krishna Kumar (xalgord) license: Apache-2.0 nist_ai_rmf: - MEASURE-2.7 - MAP-5.1 - MANAGE-2.4 atlas_techniques: - AML.T0070 - AML.T0066 - AML.T0082 nist_csf: - DE.CM-01 - DE.AE-02 - RS.MA-01 - DE.AE-06 --- # Building SOC Metrics and KPI Tracking ## When to Use Use this skill when: - SOC leadership needs data-driven visibility into operational performance - Continuous improvement programs require baseline measurements and trend tracking - Executive reporting demands quantified security posture and ROI metrics - Staffing decisions need objective workload and capacity data - Compliance audits require documented SOC performance evidence **Do not use** metrics as punitive measures against analysts — metrics should drive process improvement, not individual performance management. ## Common Misconfigurations & Verification - **Metric reads the wrong timestamp field:** MTTD/MTTR depend on `orig_time`, `_time`, `status_end`, `status_transition_time` in `index=notable`. If your ES version doesn't populate `status_end` (or stores resolution in `incident_review` via `| from datamodel`), the search returns `0` or null and the scorecard shows a fake "GREEN". Validate each field is non-null on resolved notables before publishing. - **Silent filtering skews the average:** the guards `where mttd_seconds > 0 AND < 86400` and `< 604800` quietly drop long-dwell incidents — exactly the ones leadership cares about. A 30-day MTTR looks great because every breach over 7 days was excluded. Report the count dropped alongside the average, or the KPI lies by omission. - **Coverage lookup mismatch:** ATT&CK coverage joins `detection_rules_attack_mapping.csv` to `attack_techniques_total.csv` on `tactic`; a sub-technique vs technique ID mismatch (`T1003` vs `T1003.001`) or stale total-technique list inflates `coverage_pct` past 100% or undercounts. Verify the join key format matches on both sides. - **Disposition strings don't match:** `status_label="Resolved - True Positive"` is an exact-string match; if analysts close as "True Positive" or "Resolved-TP", TP/FP rates undercount and signal-to-noise is wrong. Normalize disposition values via a lookup. - **Verification:** hand-calculate MTTD/MTTR for 3-5 known incidents and reconcile against the dashboard; confirm `tstats` data-source coverage reflects sourcetypes actually ingesting (not just defined in `expected_data_sources.csv`) before reporting a posture score. ## Prerequisites - SIEM with 90+ days of incident and alert disposition data - Incident ticketing system (ServiceNow, Jira) with timestamp data for incident lifecycle - Analyst shift schedules and staffing data - ATT&CK Navigator for detection coverage tracking - Dashboard platform (Splunk, Grafana, or Power BI) ## Workflow ### Step 1: Define Core SOC Metrics Framework Establish the key metrics aligned to NIST CSF functions: | Metric | Definition | Target | NIST CSF | |--------|-----------|--------|----------| | MTTD | Time from threat occurrence to SOC detection | <15 min | Detect | | MTTA | Time from alert to analyst acknowledgment | <5 min | Respond | | MTTI | Time from acknowledgment to investigation start | <10 min | Respond | | MTTC | Time from investigation to containment | <1 hour | Respond | | MTTR | Time from detection to full resolution | <4 hours | Recover | | FP Rate | Percentage of false positive alerts | <30% | Detect | | TP Rate | Percentage of true positive alerts | >40% | Detect | | Coverage | ATT&CK techniques with active detection | >60% | Detect | | Dwell Time | Attacker time in network before detection | <24 hours | Detect | | Escalation Rate | % of Tier 1 alerts escalated to Tier 2/3 | 15-25% | Respond | ### Step 2: Implement MTTD/MTTR Measurement **Mean Time to Detect (MTTD):** ```spl index=notable earliest=-30d status_label="Resolved*" | eval mttd_seconds = _time - orig_time | where mttd_seconds > 0 AND mttd_seconds < 86400 --- Exclude data quality issues | stats avg(mttd_seconds) AS avg_mttd, median(mttd_seconds) AS med_mttd, perc90(mttd_seconds) AS p90_mttd, perc95(mttd_seconds) AS p95_mttd by urgency | eval avg_mttd_min = round(avg_mttd / 60, 1) | eval med_mttd_min = round(med_mttd / 60, 1) | eval p90_mttd_min = round(p90_mttd / 60, 1) | table urgency, avg_mttd_min, med_mttd_min, p90_mttd_min ``` **Mean Time to Respond (MTTR):** ```spl index=notable earliest=-30d status_label="Resolved*" | eval mttr_seconds = status_end - _time | where mttr_seconds > 0 AND mttr_seconds < 604800 --- <7 days | stats avg(mttr_seconds) AS avg_mttr, median(mttr_seconds) AS med_mttr, perc90(mttr_seconds) AS p90_mttr by urgency | eval avg_mttr_hours = round(avg_mttr / 3600, 1) | eval med_mttr_hours = round(med_mttr / 3600, 1) | eval p90_mttr_hours = round(p90_mttr / 3600, 1) | table urgency, avg_mttr_hours, med_mttr_hours, p90_mttr_hours ``` **MTTD/MTTR Trend Over Time:** ```spl index=notable earliest=-90d status_label="Resolved*" | eval mttd_min = (_time - orig_time) / 60 | eval mttr_hours = (status_end - _time) / 3600 | bin _time span=1w | stats avg(mttd_min) AS avg_mttd_min, avg(mttr_hours) AS avg_mttr_hours, count AS incidents by _time | table _time, incidents, avg_mttd_min, avg_mttr_hours ``` ### Step 3: Measure Alert Quality and Analyst Productivity **Alert Disposition Analysis:** ```spl index=notable earliest=-30d | stats count AS total, sum(eval(if(status_label="Resolved - True Positive", 1, 0))) AS tp, sum(eval(if(status_label="Resolved - False Positive", 1, 0))) AS fp, sum(eval(if(status_label="Resolved - Benign", 1, 0))) AS benign, sum(eval(if(status_label="New" OR status_label="In Progress", 1, 0))) AS pending | eval tp_rate = round(tp / total * 100, 1) | eval fp_rate = round(fp / total * 100, 1) | eval signal_noise = round(tp / (fp + 0.01), 2) | table total, tp, fp, benign, pending, tp_rate, fp_rate, signal_noise ``` **Analyst Productivity Metrics:** ```spl index=notable earliest=-30d status_label="Resolved*" | stats count AS alerts_resolved, avg(eval((status_end - status_transition_time) / 60)) AS avg_triage_min, dc(rule_name) AS unique_rule_types by owner | eval alerts_per_day = round(alerts_resolved / 30, 1) | sort - alerts_resolved | table owner, alerts_resolved, alerts_per_day, avg_triage_min, unique_rule_types ``` **Shift-Based Workload Distribution:** ```spl index=notable earliest=-30d | eval hour = strftime(_time, "%H") | eval shift = case( hour >= 6 AND hour < 14, "Day (06-14)", hour >= 14 AND hour < 22, "Swing (14-22)", 1=1, "Night (22-06)" ) | stats count AS alerts, dc(owner) AS analysts by shift | eval alerts_per_analyst = round(alerts / analysts / 30, 1) | table shift, alerts, analysts, alerts_per_analyst ``` ### Step 4: Track Detection Coverage **ATT&CK Coverage Score:** ```spl | inputlookup detection_rules_attack_mapping.csv | stats dc(technique_id) AS covered_techniques by tactic | join tactic type=left [ | inputlookup attack_techniques_total.csv | stats dc(technique_id) AS total_techniques by tactic ] | eval coverage_pct = round(covered_techniques / total_techniques * 100, 1) | sort tactic | table tactic, covered_techniques, total_techniques, coverage_pct ``` **Data Source Coverage:** ```spl | inputlookup expected_data_sources.csv | join data_source type=left [ | tstats count where index=* by sourcetype | rename sourcetype AS data_source | eval status = "Active" ] | eval source_status = if(isnotnull(status), "Collecting", "MISSING") | stats count by source_status | table source_status, count ``` ### Step 5: Build Executive Reporting Dashboard **Monthly SOC Executive Summary:** ```spl --- Incident summary by category index=notable earliest=-30d status_label="Resolved*" | stats count by urgency | eval order = case(urgency="critical", 1, urgency="high", 2, urgency="medium", 3, urgency="low", 4, urgency="informational", 5) | sort order --- Month-over-month comparison index=notable earliest=-60d | eval period = if(_time > relative_time(now(), "-30d"), "This Month", "Last Month") | stats count by period, urgency | chart sum(count) AS incidents by urgency, period --- Top 5 incident categories index=notable earliest=-30d status_label="Resolved - True Positive" | top rule_name limit=5 | table rule_name, count, percent ``` **Security Posture Scorecard:** ```spl | makeresults | eval metrics = mvappend( "MTTD: 8.3 min (Target: <15 min) | STATUS: GREEN", "MTTR: 3.2 hours (Target: <4 hours) | STATUS: GREEN", "FP Rate: 27% (Target: <30%) | STATUS: GREEN", "Detection Coverage: 64% (Target: >60%) | STATUS: GREEN", "Analyst Utilization: 78% (Target: 60-80%) | STATUS: GREEN", "Incident Backlog: 12 (Target: <20) | STATUS: GREEN" ) | mvexpand metrics | table metrics ``` ### Step 6: Implement Continuous Improvement Tracking Track improvement initiatives and their impact: ```spl --- Improvement initiative tracking | inputlookup soc_improvement_initiatives.csv | eval status_color = case( status="Completed", "green", status="In Progress", "yellow", status="Planned", "gray" ) | table initiative, start_date, target_date, status, metric_impact, baseline, current ``` Example initiatives: ```csv initiative,start_date,target_date,status,metric_impact,baseline,current Risk-Based Alerting,2024-01-15,2024-03-15,Completed,Alert Volume,-84%,287/day Sigma Rule Library,2024-02-01,2024-04-01,In Progress,ATT&CK Coverage,61%,64% SOAR Phishing Playbook,2024-02-15,2024-03-30,In Progress,Phishing MTTR,45min,18min Analyst Training Program,2024-01-01,2024-06-30,In Progress,TP Rate,31%,41% ``` ## Key Concepts | Term | Definition | |------|-----------| | **MTTD** | Mean Time to Detect — average time from threat occurrence to SOC alert generation | | **MTTR** | Mean Time to Respond — average time from detection to incident resolution | | **MTTA** | Mean Time to Acknowledge — average time from alert generation to analyst assignment | | **Signal-to-Noise Ratio** | Ratio of true positive alerts to total alerts — higher is better | | **Dwell Time** | Duration an attacker remains undetected in the environment — key indicator of detection effectiveness | | **Analyst Utilization** | Percentage of analyst time spent on productive investigation vs. overhead tasks | ## Tools & Systems - **Splunk Dashboard Studio**: Advanced visualization framework for building interactive SOC metric dashboards - **Grafana**: Open-source analytics and visualization platform supporting multiple data sources - **Power BI**: Microsoft business intelligence tool for executive-level reporting and trend analysis - **ATT&CK Navigator**: MITRE tool for visualizing detection coverage as layered heatmaps - **ServiceNow Performance Analytics**: ITSM analytics module for tracking incident lifecycle metrics ## Common Scenarios - **Quarterly Business Review**: Present MTTD/MTTR trends, detection coverage growth, and alert quality improvements - **Staffing Justification**: Use workload metrics to justify additional analyst headcount or shift adjustments - **Tool ROI Assessment**: Compare alert quality and response times before and after new tool deployment - **Compliance Evidence**: Provide documented SOC performance metrics for ISO 27001 or SOC 2 audits - **Vendor Comparison**: Benchmark SOC metrics against industry peers using surveys (SANS, Ponemon) ## Output Format ``` SOC PERFORMANCE REPORT — March 2024 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ KEY METRICS: Metric Current Target Trend Status MTTD 8.3 min <15 min -12% GREEN MTTR 3.2 hrs <4 hrs -18% GREEN FP Rate 27% <30% -5% GREEN TP Rate 41% >40% +3% GREEN ATT&CK Coverage 64% >60% +3% GREEN Alerts/Analyst/Day 24 <50 -84% GREEN INCIDENT SUMMARY: Total Incidents: 147 (Critical: 3, High: 23, Medium: 78, Low: 43) Avg Resolution: 3.2 hours (Critical: 1.8h, High: 2.9h, Medium: 4.1h) SLA Compliance: 94% (Target: >90%) IMPROVEMENT HIGHLIGHTS: [1] RBA deployment reduced daily alerts from 1,847 to 287 (-84%) [2] New Sigma rules added 12 ATT&CK techniques to coverage [3] SOAR phishing playbook reduced phishing MTTR by 60% AREAS FOR IMPROVEMENT: [1] Lateral movement detection coverage at 58% (below 60% target) [2] Night shift MTTD 23% slower than day shift [3] 4 critical vulnerability scan tickets overdue on SLA ``` --- Source attribution: xalgord Original project: https://github.com/xalgord/xalgorix/blob/cec44d71b1d998208e1e2091982d0ee2f928041f/internal/tools/skills/data/soc-operations/building-soc-metrics-and-kpi-tracking/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Dave AI. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright 2026 xalgord Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Dave AI resource metadata Creator / publisher: xalgord Original project: https://github.com/xalgord/xalgorix/blob/cec44d71b1d998208e1e2091982d0ee2f928041f/internal/tools/skills/data/soc-operations/building-soc-metrics-and-kpi-tracking/SKILL.md Attribution basis: Source repository record Fields of work: Data & Analytics, Marketing, Operations, Product Management Roles: Data Analyst, Growth Marketer, Marketing Analyst, Operations Manager, Product Manager Specialties: Specialty not specified Tools: Grafana, Jira, Power Bi, Service Now, Siem, Splunk Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 8904c380d6ada2ce5d32fcd21d888d7419c28e113326298147425d3aae5c2c4f