triaging-security-alerts-in-splunk

Featured

Triages security alerts in Splunk Enterprise Security by classifying severity, investigating notable events, correlating related telemetry, and making escalation or closure decisions using SPL queries and the Incident Review dashboard. Use when SOC analysts face queued alerts from correlation searches, need to prioritize investigation order, or must document triage decisions for handoff to Tier 2/3 analysts.

AI & Automation 36,355 stars 4443 forks Updated 2 months ago Apache-2.0

Install

View on GitHub

Quality Score: 94/100

Stars 20%
100
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Triaging Security Alerts in Splunk ## When to Use Use this skill when: - SOC Tier 1 analysts need to process the Incident Review queue in Splunk Enterprise Security (ES) - Notable events require rapid severity classification and initial investigation before escalation - Alert volume exceeds capacity and analysts need a systematic triage methodology - Management requests metrics on alert disposition (true positive, false positive, benign) **Do not use** for deep forensic investigation — escalate to Tier 2/3 after initial triage confirms malicious activity. ## Prerequisites - Splunk Enterprise Security 7.x+ with Incident Review dashboard configured - CIM-normalized data sources (Windows Event Logs, firewall, proxy, endpoint) - Role with `ess_analyst` capability for notable event status updates - Familiarity with SPL (Search Processing Language) ## Workflow ### Step 1: Access Incident Review and Prioritize Queue Open the Incident Review dashboard in Splunk ES. Sort notable events by urgency (calculated from severity x priority). Apply filters to focus on unassigned events: ```spl | `notable` | search status="new" OR status="unassigned" | sort - urgency | table _time, rule_name, src, dest, user, urgency, status | head 50 ``` Focus on Critical and High urgency events first. Group related alerts by `src` or `dest` to identify attack chains rather than treating each alert independently. ### Step 2: Investigate the Notable Event Context For each notable event, pivot to ...

Details

Author
mukul975
Repository
mukul975/Anthropic-Cybersecurity-Skills
Created
8 months ago
Last Updated
2 months ago
Language
Python
License
Apache-2.0

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category