[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A4T76JM7MRZPZFPKXBV3YB":3,"skill-same:01M7A4T76JM7MRZPZFPKXBV3YB":92},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":14,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M7A4T76JM7MRZPZFPKXBV3YB","building-soc-metrics-and-kpi-tracking",null,"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.","NeelakshSaxena\u002FVayu","NeelakshSaxena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87892838?v=4","01M7A3B9YFS6F6N9DD1787DT86","Neelaksh Saxena","01M7A3B9ZKBT09MNMPX2XN69BY",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbuilding-soc-metrics-and-kpi-tracking\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbuilding-soc-metrics-and-kpi-tracking\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: building-soc-metrics-and-kpi-tracking\ndescription: 'Builds SOC performance metrics and KPI tracking dashboards measuring\n  Mean Time to Detect (MTTD), Mean Time to Respond (MTTR), alert quality ratios, analyst\n  productivity, and detection coverage using SIEM data. Use when SOC leadership needs\n  operational visibility, continuous improvement tracking, or executive-level reporting\n  on security operations effectiveness.\n\n  '\ndomain: cybersecurity\nsubdomain: soc-operations\ntags:\n- soc\n- metrics\n- kpi\n- mttd\n- mttr\n- dashboard\n- reporting\n- continuous-improvement\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_ai_rmf:\n- MEASURE-2.7\n- MAP-5.1\n- MANAGE-2.4\natlas_techniques:\n- AML.T0070\n- AML.T0066\n- AML.T0082\nnist_csf:\n- DE.CM-01\n- DE.AE-02\n- RS.MA-01\n- DE.AE-06\nmitre_attack:\n- T1078\n- T1071\n---\n# Building SOC Metrics and KPI Tracking\n\n## When to Use\n\nUse this skill when:\n- SOC leadership needs data-driven visibility into operational performance\n- Continuous improvement programs require baseline measurements and trend tracking\n- Executive reporting demands quantified security posture and ROI metrics\n- Staffing decisions need objective workload and capacity data\n- Compliance audits require documented SOC performance evidence\n\n**Do not use** metrics as punitive measures against analysts — metrics should drive process improvement, not individual performance management.\n\n## Prerequisites\n\n- SIEM with 90+ days of incident and alert disposition data\n- Incident ticketing system (ServiceNow, Jira) with timestamp data for incident lifecycle\n- Analyst shift schedules and staffing data\n- ATT&CK Navigator for detection coverage tracking\n- Dashboard platform (Splunk, Grafana, or Power BI)\n\n## Workflow\n\n### Step 1: Define Core SOC Metrics Framework\n\nEstablish the key metrics aligned to NIST CSF functions:\n\n| Metric | Definition | Target | NIST CSF |\n|--------|-----------|--------|----------|\n| MTTD | Time from threat occurrence to SOC detection | \u003C15 min | Detect |\n| MTTA | Time from alert to analyst acknowledgment | \u003C5 min | Respond |\n| MTTI | Time from acknowledgment to investigation start | \u003C10 min | Respond |\n| MTTC | Time from investigation to containment | \u003C1 hour | Respond |\n| MTTR | Time from detection to full resolution | \u003C4 hours | Recover |\n| FP Rate | Percentage of false positive alerts | \u003C30% | Detect |\n| TP Rate | Percentage of true positive alerts | >40% | Detect |\n| Coverage | ATT&CK techniques with active detection | >60% | Detect |\n| Dwell Time | Attacker time in network before detection | \u003C24 hours | Detect |\n| Escalation Rate | % of Tier 1 alerts escalated to Tier 2\u002F3 | 15-25% | Respond |\n\n### Step 2: Implement MTTD\u002FMTTR Measurement\n\n**Mean Time to Detect (MTTD):**\n```spl\nindex=notable earliest=-30d status_label=\"Resolved*\"\n| eval mttd_seconds = _time - orig_time\n| where mttd_seconds > 0 AND mttd_seconds \u003C 86400  --- Exclude data quality issues\n| stats avg(mttd_seconds) AS avg_mttd,\n        median(mttd_seconds) AS med_mttd,\n        perc90(mttd_seconds) AS p90_mttd,\n        perc95(mttd_seconds) AS p95_mttd\n  by urgency\n| eval avg_mttd_min = round(avg_mttd \u002F 60, 1)\n| eval med_mttd_min = round(med_mttd \u002F 60, 1)\n| eval p90_mttd_min = round(p90_mttd \u002F 60, 1)\n| table urgency, avg_mttd_min, med_mttd_min, p90_mttd_min\n```\n\n**Mean Time to Respond (MTTR):**\n```spl\nindex=notable earliest=-30d status_label=\"Resolved*\"\n| eval mttr_seconds = status_end - _time\n| where mttr_seconds > 0 AND mttr_seconds \u003C 604800  --- \u003C7 days\n| stats avg(mttr_seconds) AS avg_mttr,\n        median(mttr_seconds) AS med_mttr,\n        perc90(mttr_seconds) AS p90_mttr\n  by urgency\n| eval avg_mttr_hours = round(avg_mttr \u002F 3600, 1)\n| eval med_mttr_hours = round(med_mttr \u002F 3600, 1)\n| eval p90_mttr_hours = round(p90_mttr \u002F 3600, 1)\n| table urgency, avg_mttr_hours, med_mttr_hours, p90_mttr_hours\n```\n\n**MTTD\u002FMTTR Trend Over Time:**\n```spl\nindex=notable earliest=-90d status_label=\"Resolved*\"\n| eval mttd_min = (_time - orig_time) \u002F 60\n| eval mttr_hours = (status_end - _time) \u002F 3600\n| bin _time span=1w\n| stats avg(mttd_min) AS avg_mttd_min, avg(mttr_hours) AS avg_mttr_hours,\n        count AS incidents by _time\n| table _time, incidents, avg_mttd_min, avg_mttr_hours\n```\n\n### Step 3: Measure Alert Quality and Analyst Productivity\n\n**Alert Disposition Analysis:**\n```spl\nindex=notable earliest=-30d\n| stats count AS total,\n        sum(eval(if(status_label=\"Resolved - True Positive\", 1, 0))) AS tp,\n        sum(eval(if(status_label=\"Resolved - False Positive\", 1, 0))) AS fp,\n        sum(eval(if(status_label=\"Resolved - Benign\", 1, 0))) AS benign,\n        sum(eval(if(status_label=\"New\" OR status_label=\"In Progress\", 1, 0))) AS pending\n| eval tp_rate = round(tp \u002F total * 100, 1)\n| eval fp_rate = round(fp \u002F total * 100, 1)\n| eval signal_noise = round(tp \u002F (fp + 0.01), 2)\n| table total, tp, fp, benign, pending, tp_rate, fp_rate, signal_noise\n```\n\n**Analyst Productivity Metrics:**\n```spl\nindex=notable earliest=-30d status_label=\"Resolved*\"\n| stats count AS alerts_resolved,\n        avg(eval((status_end - status_transition_time) \u002F 60)) AS avg_triage_min,\n        dc(rule_name) AS unique_rule_types\n  by owner\n| eval alerts_per_day = round(alerts_resolved \u002F 30, 1)\n| sort - alerts_resolved\n| table owner, alerts_resolved, alerts_per_day, avg_triage_min, unique_rule_types\n```\n\n**Shift-Based Workload Distribution:**\n```spl\nindex=notable earliest=-30d\n| eval hour = strftime(_time, \"%H\")\n| eval shift = case(\n    hour >= 6 AND hour \u003C 14, \"Day (06-14)\",\n    hour >= 14 AND hour \u003C 22, \"Swing (14-22)\",\n    1=1, \"Night (22-06)\"\n  )\n| stats count AS alerts, dc(owner) AS analysts by shift\n| eval alerts_per_analyst = round(alerts \u002F analysts \u002F 30, 1)\n| table shift, alerts, analysts, alerts_per_analyst\n```\n\n### Step 4: Track Detection Coverage\n\n**ATT&CK Coverage Score:**\n```spl\n| inputlookup detection_rules_attack_mapping.csv\n| stats dc(technique_id) AS covered_techniques by tactic\n| join tactic type=left [\n    | inputlookup attack_techniques_total.csv\n    | stats dc(technique_id) AS total_techniques by tactic\n  ]\n| eval coverage_pct = round(covered_techniques \u002F total_techniques * 100, 1)\n| sort tactic\n| table tactic, covered_techniques, total_techniques, coverage_pct\n```\n\n**Data Source Coverage:**\n```spl\n| inputlookup expected_data_sources.csv\n| join data_source type=left [\n    | tstats count where index=* by sourcetype\n    | rename sourcetype AS data_source\n    | eval status = \"Active\"\n  ]\n| eval source_status = if(isnotnull(status), \"Collecting\", \"MISSING\")\n| stats count by source_status\n| table source_status, count\n```\n\n### Step 5: Build Executive Reporting Dashboard\n\n**Monthly SOC Executive Summary:**\n```spl\n--- Incident summary by category\nindex=notable earliest=-30d status_label=\"Resolved*\"\n| stats count by urgency\n| eval order = case(urgency=\"critical\", 1, urgency=\"high\", 2, urgency=\"medium\", 3,\n                    urgency=\"low\", 4, urgency=\"informational\", 5)\n| sort order\n\n--- Month-over-month comparison\nindex=notable earliest=-60d\n| eval period = if(_time > relative_time(now(), \"-30d\"), \"This Month\", \"Last Month\")\n| stats count by period, urgency\n| chart sum(count) AS incidents by urgency, period\n\n--- Top 5 incident categories\nindex=notable earliest=-30d status_label=\"Resolved - True Positive\"\n| top rule_name limit=5\n| table rule_name, count, percent\n```\n\n**Security Posture Scorecard:**\n```spl\n| makeresults\n| eval metrics = mvappend(\n    \"MTTD: 8.3 min (Target: \u003C15 min) | STATUS: GREEN\",\n    \"MTTR: 3.2 hours (Target: \u003C4 hours) | STATUS: GREEN\",\n    \"FP Rate: 27% (Target: \u003C30%) | STATUS: GREEN\",\n    \"Detection Coverage: 64% (Target: >60%) | STATUS: GREEN\",\n    \"Analyst Utilization: 78% (Target: 60-80%) | STATUS: GREEN\",\n    \"Incident Backlog: 12 (Target: \u003C20) | STATUS: GREEN\"\n  )\n| mvexpand metrics\n| table metrics\n```\n\n### Step 6: Implement Continuous Improvement Tracking\n\nTrack improvement initiatives and their impact:\n\n```spl\n--- Improvement initiative tracking\n| inputlookup soc_improvement_initiatives.csv\n| eval status_color = case(\n    status=\"Completed\", \"green\",\n    status=\"In Progress\", \"yellow\",\n    status=\"Planned\", \"gray\"\n  )\n| table initiative, start_date, target_date, status, metric_impact, baseline, current\n```\n\nExample initiatives:\n```csv\ninitiative,start_date,target_date,status,metric_impact,baseline,current\nRisk-Based Alerting,2024-01-15,2024-03-15,Completed,Alert Volume,-84%,287\u002Fday\nSigma Rule Library,2024-02-01,2024-04-01,In Progress,ATT&CK Coverage,61%,64%\nSOAR Phishing Playbook,2024-02-15,2024-03-30,In Progress,Phishing MTTR,45min,18min\nAnalyst Training Program,2024-01-01,2024-06-30,In Progress,TP Rate,31%,41%\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **MTTD** | Mean Time to Detect — average time from threat occurrence to SOC alert generation |\n| **MTTR** | Mean Time to Respond — average time from detection to incident resolution |\n| **MTTA** | Mean Time to Acknowledge — average time from alert generation to analyst assignment |\n| **Signal-to-Noise Ratio** | Ratio of true positive alerts to total alerts — higher is better |\n| **Dwell Time** | Duration an attacker remains undetected in the environment — key indicator of detection effectiveness |\n| **Analyst Utilization** | Percentage of analyst time spent on productive investigation vs. overhead tasks |\n\n## Tools & Systems\n\n- **Splunk Dashboard Studio**: Advanced visualization framework for building interactive SOC metric dashboards\n- **Grafana**: Open-source analytics and visualization platform supporting multiple data sources\n- **Power BI**: Microsoft business intelligence tool for executive-level reporting and trend analysis\n- **ATT&CK Navigator**: MITRE tool for visualizing detection coverage as layered heatmaps\n- **ServiceNow Performance Analytics**: ITSM analytics module for tracking incident lifecycle metrics\n\n## Common Scenarios\n\n- **Quarterly Business Review**: Present MTTD\u002FMTTR trends, detection coverage growth, and alert quality improvements\n- **Staffing Justification**: Use workload metrics to justify additional analyst headcount or shift adjustments\n- **Tool ROI Assessment**: Compare alert quality and response times before and after new tool deployment\n- **Compliance Evidence**: Provide documented SOC performance metrics for ISO 27001 or SOC 2 audits\n- **Vendor Comparison**: Benchmark SOC metrics against industry peers using surveys (SANS, Ponemon)\n\n## Output Format\n\n```\nSOC PERFORMANCE REPORT — March 2024\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nKEY METRICS:\n  Metric              Current    Target     Trend    Status\n  MTTD                8.3 min    \u003C15 min    -12%     GREEN\n  MTTR                3.2 hrs    \u003C4 hrs     -18%     GREEN\n  FP Rate             27%        \u003C30%       -5%      GREEN\n  TP Rate             41%        >40%       +3%      GREEN\n  ATT&CK Coverage     64%        >60%       +3%      GREEN\n  Alerts\u002FAnalyst\u002FDay  24         \u003C50        -84%     GREEN\n\nINCIDENT SUMMARY:\n  Total Incidents:     147 (Critical: 3, High: 23, Medium: 78, Low: 43)\n  Avg Resolution:      3.2 hours (Critical: 1.8h, High: 2.9h, Medium: 4.1h)\n  SLA Compliance:      94% (Target: >90%)\n\nIMPROVEMENT HIGHLIGHTS:\n  [1] RBA deployment reduced daily alerts from 1,847 to 287 (-84%)\n  [2] New Sigma rules added 12 ATT&CK techniques to coverage\n  [3] SOAR phishing playbook reduced phishing MTTR by 60%\n\nAREAS FOR IMPROVEMENT:\n  [1] Lateral movement detection coverage at 58% (below 60% target)\n  [2] Night shift MTTD 23% slower than day shift\n  [3] 4 critical vulnerability scan tickets overdue on SLA\n```\n","# Building SOC Metrics and KPI Tracking\n\n## When to Use\n\nUse this skill when:\n- SOC leadership needs data-driven visibility into operational performance\n- Continuous improvement programs require baseline measurements and trend tracking\n- Executive reporting demands quantified security posture and ROI metrics\n- Staffing decisions need objective workload and capacity data\n- Compliance audits require documented SOC performance evidence\n\n**Do not use** metrics as punitive measures against analysts — metrics should drive process improvement, not individual performance management.\n\n## Prerequisites\n\n- SIEM with 90+ days of incident and alert disposition data\n- Incident ticketing system (ServiceNow, Jira) with timestamp data for incident lifecycle\n- Analyst shift schedules and staffing data\n- ATT&CK Navigator for detection coverage tracking\n- Dashboard platform (Splunk, Grafana, or Power BI)\n\n## Workflow\n\n### Step 1: Define Core SOC Metrics Framework\n\nEstablish the key metrics aligned to NIST CSF functions:\n\n| Metric | Definition | Target | NIST CSF |\n|--------|-----------|--------|----------|\n| MTTD | Time from threat occurrence to SOC detection | \u003C15 min | Detect |\n| MTTA | Time from alert to analyst acknowledgment | \u003C5 min | Respond |\n| MTTI | Time from acknowledgment to investigation start | \u003C10 min | Respond |\n| MTTC | Time from investigation to containment | \u003C1 hour | Respond |\n| MTTR | Time from detection to full resolution | \u003C4 hours | Recover |\n| FP Rate | Percentage of false positive alerts | \u003C30% | Detect |\n| TP Rate | Percentage of true positive alerts | >40% | Detect |\n| Coverage | ATT&CK techniques with active detection | >60% | Detect |\n| Dwell Time | Attacker time in network before detection | \u003C24 hours | Detect |\n| Escalation Rate | % of Tier 1 alerts escalated to Tier 2\u002F3 | 15-25% | Respond |\n\n### Step 2: Implement MTTD\u002FMTTR Measurement\n\n**Mean Time to Detect (MTTD):**\n```spl\nindex=notable earliest=-30d status_label=\"Resolved*\"\n| eval mttd_seconds = _time - orig_time\n| where mttd_seconds > 0 AND mttd_seconds \u003C 86400  --- Exclude data quality issues\n| stats avg(mttd_seconds) AS avg_mttd,\n        median(mttd_seconds) AS med_mttd,\n        perc90(mttd_seconds) AS p90_mttd,\n        perc95(mttd_seconds) AS p95_mttd\n  by urgency\n| eval avg_mttd_min = round(avg_mttd \u002F 60, 1)\n| eval med_mttd_min = round(med_mttd \u002F 60, 1)\n| eval p90_mttd_min = round(p90_mttd \u002F 60, 1)\n| table urgency, avg_mttd_min, med_mttd_min, p90_mttd_min\n```\n\n**Mean Time to Respond (MTTR):**\n```spl\nindex=notable earliest=-30d status_label=\"Resolved*\"\n| eval mttr_seconds = status_end - _time\n| where mttr_seconds > 0 AND mttr_seconds \u003C 604800  --- \u003C7 days\n| stats avg(mttr_seconds) AS avg_mttr,\n        median(mttr_seconds) AS med_mttr,\n        perc90(mttr_seconds) AS p90_mttr\n  by urgency\n| eval avg_mttr_hours = round(avg_mttr \u002F 3600, 1)\n| eval med_mttr_hours = round(med_mttr \u002F 3600, 1)\n| eval p90_mttr_hours = round(p90_mttr \u002F 3600, 1)\n| table urgency, avg_mttr_hours, med_mttr_hours, p90_mttr_hours\n```\n\n**MTTD\u002FMTTR Trend Over Time:**\n```spl\nindex=notable earliest=-90d status_label=\"Resolved*\"\n| eval mttd_min = (_time - orig_time) \u002F 60\n| eval mttr_hours = (status_end - _time) \u002F 3600\n| bin _time span=1w\n| stats avg(mttd_min) AS avg_mttd_min, avg(mttr_hours) AS avg_mttr_hours,\n        count AS incidents by _time\n| table _time, incidents, avg_mttd_min, avg_mttr_hours\n```\n\n### Step 3: Measure Alert Quality and Analyst Productivity\n\n**Alert Disposition Analysis:**\n```spl\nindex=notable earliest=-30d\n| stats count AS total,\n        sum(eval(if(status_label=\"Resolved - True Positive\", 1, 0))) AS tp,\n        sum(eval(if(status_label=\"Resolved - False Positive\", 1, 0))) AS fp,\n        sum(eval(if(status_label=\"Resolved - Benign\", 1, 0))) AS benign,\n        sum(eval(if(status_label=\"New\" OR status_label=\"In Progress\", 1, 0))) AS pending\n| eval tp_rate = round(tp \u002F total * 100, 1)\n| eval fp_rate = round(fp \u002F total * 100, 1)\n| eval signal_noise = round(tp \u002F (fp + 0.01), 2)\n| table total, tp, fp, benign, pending, tp_rate, fp_rate, signal_noise\n```\n\n**Analyst Productivity Metrics:**\n```spl\nindex=notable earliest=-30d status_label=\"Resolved*\"\n| stats count AS alerts_resolved,\n        avg(eval((status_end - status_transition_time) \u002F 60)) AS avg_triage_min,\n        dc(rule_name) AS unique_rule_types\n  by owner\n| eval alerts_per_day = round(alerts_resolved \u002F 30, 1)\n| sort - alerts_resolved\n| table owner, alerts_resolved, alerts_per_day, avg_triage_min, unique_rule_types\n```\n\n**Shift-Based Workload Distribution:**\n```spl\nindex=notable earliest=-30d\n| eval hour = strftime(_time, \"%H\")\n| eval shift = case(\n    hour >= 6 AND hour \u003C 14, \"Day (06-14)\",\n    hour >= 14 AND hour \u003C 22, \"Swing (14-22)\",\n    1=1, \"Night (22-06)\"\n  )\n| stats count AS alerts, dc(owner) AS analysts by shift\n| eval alerts_per_analyst = round(alerts \u002F analysts \u002F 30, 1)\n| table shift, alerts, analysts, alerts_per_analyst\n```\n\n### Step 4: Track Detection Coverage\n\n**ATT&CK Coverage Score:**\n```spl\n| inputlookup detection_rules_attack_mapping.csv\n| stats dc(technique_id) AS covered_techniques by tactic\n| join tactic type=left [\n    | inputlookup attack_techniques_total.csv\n    | stats dc(technique_id) AS total_techniques by tactic\n  ]\n| eval coverage_pct = round(covered_techniques \u002F total_techniques * 100, 1)\n| sort tactic\n| table tactic, covered_techniques, total_techniques, coverage_pct\n```\n\n**Data Source Coverage:**\n```spl\n| inputlookup expected_data_sources.csv\n| join data_source type=left [\n    | tstats count where index=* by sourcetype\n    | rename sourcetype AS data_source\n    | eval status = \"Active\"\n  ]\n| eval source_status = if(isnotnull(status), \"Collecting\", \"MISSING\")\n| stats count by source_status\n| table source_status, count\n```\n\n### Step 5: Build Executive Reporting Dashboard\n\n**Monthly SOC Executive Summary:**\n```spl\n--- Incident summary by category\nindex=notable earliest=-30d status_label=\"Resolved*\"\n| stats count by urgency\n| eval order = case(urgency=\"critical\", 1, urgency=\"high\", 2, urgency=\"medium\", 3,\n                    urgency=\"low\", 4, urgency=\"informational\", 5)\n| sort order\n\n--- Month-over-month comparison\nindex=notable earliest=-60d\n| eval period = if(_time > relative_time(now(), \"-30d\"), \"This Month\", \"Last Month\")\n| stats count by period, urgency\n| chart sum(count) AS incidents by urgency, period\n\n--- Top 5 incident categories\nindex=notable earliest=-30d status_label=\"Resolved - True Positive\"\n| top rule_name limit=5\n| table rule_name, count, percent\n```\n\n**Security Posture Scorecard:**\n```spl\n| makeresults\n| eval metrics = mvappend(\n    \"MTTD: 8.3 min (Target: \u003C15 min) | STATUS: GREEN\",\n    \"MTTR: 3.2 hours (Target: \u003C4 hours) | STATUS: GREEN\",\n    \"FP Rate: 27% (Target: \u003C30%) | STATUS: GREEN\",\n    \"Detection Coverage: 64% (Target: >60%) | STATUS: GREEN\",\n    \"Analyst Utilization: 78% (Target: 60-80%) | STATUS: GREEN\",\n    \"Incident Backlog: 12 (Target: \u003C20) | STATUS: GREEN\"\n  )\n| mvexpand metrics\n| table metrics\n```\n\n### Step 6: Implement Continuous Improvement Tracking\n\nTrack improvement initiatives and their impact:\n\n```spl\n--- Improvement initiative tracking\n| inputlookup soc_improvement_initiatives.csv\n| eval status_color = case(\n    status=\"Completed\", \"green\",\n    status=\"In Progress\", \"yellow\",\n    status=\"Planned\", \"gray\"\n  )\n| table initiative, start_date, target_date, status, metric_impact, baseline, current\n```\n\nExample initiatives:\n```csv\ninitiative,start_date,target_date,status,metric_impact,baseline,current\nRisk-Based Alerting,2024-01-15,2024-03-15,Completed,Alert Volume,-84%,287\u002Fday\nSigma Rule Library,2024-02-01,2024-04-01,In Progress,ATT&CK Coverage,61%,64%\nSOAR Phishing Playbook,2024-02-15,2024-03-30,In Progress,Phishing MTTR,45min,18min\nAnalyst Training Program,2024-01-01,2024-06-30,In Progress,TP Rate,31%,41%\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **MTTD** | Mean Time to Detect — average time from threat occurrence to SOC alert generation |\n| **MTTR** | Mean Time to Respond — average time from detection to incident resolution |\n| **MTTA** | Mean Time to Acknowledge — average time from alert generation to analyst assignment |\n| **Signal-to-Noise Ratio** | Ratio of true positive alerts to total alerts — higher is better |\n| **Dwell Time** | Duration an attacker remains undetected in the environment — key indicator of detection effectiveness |\n| **Analyst Utilization** | Percentage of analyst time spent on productive investigation vs. overhead tasks |\n\n## Tools & Systems\n\n- **Splunk Dashboard Studio**: Advanced visualization framework for building interactive SOC metric dashboards\n- **Grafana**: Open-source analytics and visualization platform supporting multiple data sources\n- **Power BI**: Microsoft business intelligence tool for executive-level reporting and trend analysis\n- **ATT&CK Navigator**: MITRE tool for visualizing detection coverage as layered heatmaps\n- **ServiceNow Performance Analytics**: ITSM analytics module for tracking incident lifecycle metrics\n\n## Common Scenarios\n\n- **Quarterly Business Review**: Present MTTD\u002FMTTR trends, detection coverage growth, and alert quality improvements\n- **Staffing Justification**: Use workload metrics to justify additional analyst headcount or shift adjustments\n- **Tool ROI Assessment**: Compare alert quality and response times before and after new tool deployment\n- **Compliance Evidence**: Provide documented SOC performance metrics for ISO 27001 or SOC 2 audits\n- **Vendor Comparison**: Benchmark SOC metrics against industry peers using surveys (SANS, Ponemon)\n\n## Output Format\n\n```\nSOC PERFORMANCE REPORT — March 2024\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nKEY METRICS:\n  Metric              Current    Target     Trend    Status\n  MTTD                8.3 min    \u003C15 min    -12%     GREEN\n  MTTR                3.2 hrs    \u003C4 hrs     -18%     GREEN\n  FP Rate             27%        \u003C30%       -5%      GREEN\n  TP Rate             41%        >40%       +3%      GREEN\n  ATT&CK Coverage     64%        >60%       +3%      GREEN\n  Alerts\u002FAnalyst\u002FDay  24         \u003C50        -84%     GREEN\n\nINCIDENT SUMMARY:\n  Total Incidents:     147 (Critical: 3, High: 23, Medium: 78, Low: 43)\n  Avg Resolution:      3.2 hours (Critical: 1.8h, High: 2.9h, Medium: 4.1h)\n  SLA Compliance:      94% (Target: >90%)\n\nIMPROVEMENT HIGHLIGHTS:\n  [1] RBA deployment reduced daily alerts from 1,847 to 287 (-84%)\n  [2] New Sigma rules added 12 ATT&CK techniques to coverage\n  [3] SOAR phishing playbook reduced phishing MTTR by 60%\n\nAREAS FOR IMPROVEMENT:\n  [1] Lateral movement detection coverage at 58% (below 60% target)\n  [2] Night shift MTTD 23% slower than day shift\n  [3] 4 critical vulnerability scan tickets overdue on SLA\n```\n",{"name":5,"tags":25,"author":34,"domain":35,"license":15,"version":36,"nist_csf":37,"subdomain":42,"description":43,"nist_ai_rmf":44,"mitre_attack":48,"atlas_techniques":51},[26,27,28,29,30,31,32,33],"soc","metrics","kpi","mttd","mttr","dashboard","reporting","continuous-improvement","mahipal","cybersecurity","1.0",[38,39,40,41],"DE.CM-01","DE.AE-02","RS.MA-01","DE.AE-06","soc-operations","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.\n",[45,46,47],"MEASURE-2.7","MAP-5.1","MANAGE-2.4",[49,50],"T1078","T1071",[52,53,54],"AML.T0070","AML.T0066","AML.T0082","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fbuilding-soc-metrics-and-kpi-tracking","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena","Currently exploring the intersection of tech","2026-09-11 03:02:31",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add NeelakshSaxena\u002FVayu --skill building-soc-metrics-and-kpi-tracking",{"tool":68,"command":69},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill building-soc-metrics-and-kpi-tracking",{"tool":71,"command":72},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill building-soc-metrics-and-kpi-tracking","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbuilding-soc-metrics-and-kpi-tracking\u002FSKILL.md",true,[76,80,86],{"path":77,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fapi-reference.md","REFERENCE","参考文档",2469,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbuilding-soc-metrics-and-kpi-tracking\u002Freferences\u002Fapi-reference.md",{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"scripts\u002Fagent.py","SCRIPT","脚本",7384,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbuilding-soc-metrics-and-kpi-tracking\u002Fscripts\u002Fagent.py",[93,100,107,114,121,128],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":20},"01M7ACCCVNCFKMA9X6D15X6G98","runpodctl","Runpod CLI for managing GPU\u002FCPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send\u002Freceive). Use for terminal\u002FCI\u002Fscripting, Hub browse\u002Fdeploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpodctl\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":20},"01M7ACC63SRHEA5KMCHSMZK2TC","runpod","Start here for any Runpod task — running GPU\u002FCPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":20},"01M7ACC0Q1C89N9BZBV91CTQTF","runpod-usage","How Runpod works and how to work it — pods vs serverless, GPU\u002FVRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv\u002Fapt). Use to answer \"how does X work\", \"which GPU\", \"how do I build a container\", or \"how do I stand up a workload on a pod\". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-usage\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":20},"01M7ACBRPE345GF5GM5B8P8RRC","runpod-templates","Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says \"run \u003CX> on a pod\" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-templates\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":20},"01M7ACBJATHKVX1TWES2F44GY8","runpod-migrate","Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-migrate\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":20},"01M7ACBC7GHVH6T9YEAPCG2AP8","runpod-mcp","Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU\u002FCPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-mcp\u002FSKILL.md",[],[]]