Triaging Security Incidents
When to Use
- A SIEM or EDR alert fires and requires human classification before escalation
- Multiple concurrent alerts arrive and the SOC must prioritize response order
- An end user reports suspicious activity and the incident needs initial categorization
- A threat intelligence feed matches an IOC observed in the environment
Do not use for routine vulnerability scanning results or compliance audit findings that do not represent active security incidents.
Prerequisites
- Access to SIEM platform (Splunk, Elastic, Microsoft Sentinel) with current alert data
- Incident classification taxonomy aligned to NIST SP 800-61r3 categories
- Predefined severity matrix mapping asset criticality to threat type
- Contact roster for escalation paths (Tier 1 through Tier 3 and CIRT)
- Asset inventory with business criticality ratings
Workflow
Step 1: Collect Initial Alert Data
Gather all available context from the triggering alert before making classification decisions:
- Alert source: Which detection system generated the alert (EDR, SIEM, IDS/IPS, firewall, user report)
- Timestamp: When the event occurred and when it was detected (dwell time gap)
- Affected assets: Hostnames, IP addresses, user accounts involved
- Alert fidelity: Historical true-positive rate for this detection rule
- Raw evidence: Log entries, packet captures, process execution chains
Example SIEM alert context:
Source: CrowdStrike Falcon
Detection: Suspicious PowerShell Execution (T1059.001)
Host: WORKSTATION-FIN-042
User: jsmith@corp.example.com
Timestamp: 2025-11-15T14:23:17Z
Severity: High (detection rule confidence: 92%)
Process: powershell.exe -enc SQBFAFgAIAAoAE4AZQB3AC0ATwBiAGoA...
Parent: outlook.exe (PID 4812)
Step 2: Classify the Incident Type
Map the alert to a standard incident category per NIST SP 800-61r3:
| Category |
Examples |
| Unauthorized Access |
Compromised credentials, privilege escalation, IDOR |
| Denial of Service |
Volumetric DDoS, application-layer flood, resource exhaustion |
| Malicious Code |
Malware execution, ransomware detonation, cryptominer |
| Improper Usage |
Policy violation, insider data exfiltration, shadow IT |
| Reconnaissance |
Port scanning, directory enumeration, credential spraying |
| Web Application Attack |
SQL injection, XSS, SSRF exploitation |
Step 3: Assign Severity Using Impact Matrix
Calculate severity by combining asset criticality with threat severity:
Severity = f(Asset Criticality, Threat Type, Data Sensitivity, Lateral Movement Potential)
Critical (P1): Crown jewel systems compromised, active data exfiltration, ransomware spreading
High (P2): Production system compromise, confirmed malware execution, privileged account takeover
Medium (P3): Non-production compromise, unsuccessful exploitation attempt, single endpoint malware
Low (P4): Reconnaissance activity, policy violation, benign true positive
Response SLA targets:
- P1: Acknowledge within 15 minutes, containment within 1 hour
- P2: Acknowledge within 30 minutes, containment within 4 hours
- P3: Acknowledge within 2 hours, investigation within 24 hours
- P4: Acknowledge within 8 hours, investigation within 72 hours
Step 4: Perform Initial Enrichment
Before escalation, enrich the alert with contextual data:
- Threat intelligence: Check IOCs (IP, hash, domain) against TI platforms (VirusTotal, OTX, MISP)
- Asset context: Query CMDB for asset owner, business function, data classification
- User context: Check identity provider for recent authentication anomalies, MFA status
- Historical correlation: Search for related alerts on the same host/user in the past 30 days
- Network context: Verify if source/destination IPs are internal, known partners, or external threat actors
Step 5: Document and Escalate
Create a structured triage record and route to the appropriate response tier:
Incident Triage Record
━━━━━━━━━━━━━━━━━━━━━
Ticket ID: INC-2025-1547
Triage Analyst: [analyst name]
Triage Time: 2025-11-15T14:35:00Z (12 min from alert)
Classification: Malicious Code - Macro-based initial access
Severity: P2 - High
Affected Assets: WORKSTATION-FIN-042 (Finance dept, handles PII)
Affected Users: jsmith@corp.example.com
IOCs Identified: powershell.exe spawned by outlook.exe, encoded command
TI Matches: Base64 payload matches known Qakbot loader pattern
Escalation: Tier 2 - Malware IR team
Recommended: Isolate endpoint, preserve memory dump, block sender domain
Step 6: Initiate Containment Hold
If severity is P1 or P2, initiate immediate containment actions while awaiting full investigation:
- Network-isolate the affected endpoint via EDR (CrowdStrike contain, Defender isolate)
- Disable compromised user accounts in Active Directory or identity provider
- Block identified malicious IPs/domains at firewall and DNS sinkhole
- Preserve volatile evidence (memory dump) before any remediation
Key Concepts
| Term |
Definition |
| Triage |
Rapid assessment process to classify and prioritize security incidents based on severity and business impact |
| PICERL |
SANS incident response framework: Preparation, Identification, Containment, Eradication, Recovery, Lessons Learned |
| Dwell Time |
Duration between initial compromise and detection; average is 10 days per Mandiant M-Trends 2025 |
| True Positive Rate |
Percentage of alerts from a detection rule that represent genuine security incidents |
| Crown Jewel Assets |
Systems and data critical to business operations whose compromise would cause severe organizational impact |
| Alert Fatigue |
Degraded analyst performance caused by high volumes of low-fidelity or false-positive alerts |
| Mean Time to Acknowledge (MTTA) |
Average time from alert generation to analyst acknowledgment; key SOC performance metric |
Tools & Systems
- Splunk Enterprise Security: SIEM platform for alert aggregation, correlation, and triage workflow management
- CrowdStrike Falcon: EDR platform providing endpoint telemetry, detection, and one-click host containment
- TheHive: Open-source incident response platform for case management, task tracking, and team collaboration
- MISP: Threat intelligence sharing platform for IOC enrichment during triage
- Cortex XSOAR: SOAR platform for automating enrichment playbooks and triage decision trees
Common Scenarios
Scenario: Encoded PowerShell from Email Client
Context: SOC analyst receives a P2 alert showing powershell.exe with a Base64-encoded command spawned as a child process of outlook.exe on a finance department workstation.
Approach:
- Decode the Base64 payload to determine the command intent
- Check the parent process chain for anomalies (Outlook spawning PowerShell is abnormal)
- Query VirusTotal for the decoded payload hash
- Correlate with email gateway logs to identify the triggering email and sender
- Check if other recipients in the organization received the same email
- Isolate the endpoint and escalate to Tier 2 with full triage context
Pitfalls:
- Dismissing encoded PowerShell as a false positive without decoding the payload
- Failing to check for lateral spread to other recipients of the same phishing email
- Remediating the endpoint before capturing volatile memory evidence
Output Format
INCIDENT TRIAGE REPORT
======================
Ticket: INC-[YYYY]-[NNNN]
Date/Time: [ISO 8601 timestamp]
Triage Analyst: [Name]
Time to Triage: [minutes from alert to classification]
CLASSIFICATION
Type: [NIST category]
Severity: [P1-P4] - [Critical/High/Medium/Low]
Confidence: [High/Medium/Low]
MITRE ATT&CK: [Technique ID and name]
AFFECTED SCOPE
Assets: [hostname(s), IP(s)]
Users: [account(s)]
Data at Risk: [classification level]
Business Unit: [department]
EVIDENCE SUMMARY
[Bullet list of key observations]
ENRICHMENT RESULTS
TI Matches: [Yes/No - details]
Historical: [Related prior incidents]
Asset Criticality: [rating]
RECOMMENDED ACTIONS
1. [Immediate action]
2. [Investigation step]
3. [Escalation target]
ESCALATION
Routed To: [Team/Individual]
SLA Target: [Containment deadline]
1---2name: triaging-security-incident3description: 'Performs initial triage of security incidents using the NIST SP4 800-61r3 and SANS PICERL frameworks, classifying incident type, assigning priority5 by business impact, and routing to the appropriate response team. Use when a6 SIEM/EDR alert needs human classification, concurrent alerts must be prioritized,7 or a user report or threat-intel IOC match requires initial incident categorization.'8domain: cybersecurity9subdomain: incident-response10tags:11- incident-triage12- NIST-800-6113- SANS-PICERL14- severity-classification15- SOC-operations16mitre_attack:17- T148618- T149019- T107020- T107821version: 1.0.022author: mahipal23license: Apache-2.024d3fend_techniques:25- Executable Denylisting26- Execution Isolation27- File Metadata Consistency Validation28- Content Format Conversion29- File Content Analysis30nist_csf:31- RS.MA-0132- RS.MA-0233- RS.AN-0334- RC.RP-0135metadata:36 source: https://skillmd.com/skills/26zl/triaging-security-incident37---3839# Triaging Security Incidents4041## When to Use4243- A SIEM or EDR alert fires and requires human classification before escalation44- Multiple concurrent alerts arrive and the SOC must prioritize response order45- An end user reports suspicious activity and the incident needs initial categorization46- A threat intelligence feed matches an IOC observed in the environment4748**Do not use** for routine vulnerability scanning results or compliance audit findings that do not represent active security incidents.4950## Prerequisites5152- Access to SIEM platform (Splunk, Elastic, Microsoft Sentinel) with current alert data53- Incident classification taxonomy aligned to NIST SP 800-61r3 categories54- Predefined severity matrix mapping asset criticality to threat type55- Contact roster for escalation paths (Tier 1 through Tier 3 and CIRT)56- Asset inventory with business criticality ratings5758## Workflow5960### Step 1: Collect Initial Alert Data6162Gather all available context from the triggering alert before making classification decisions:6364- **Alert source**: Which detection system generated the alert (EDR, SIEM, IDS/IPS, firewall, user report)65- **Timestamp**: When the event occurred and when it was detected (dwell time gap)66- **Affected assets**: Hostnames, IP addresses, user accounts involved67- **Alert fidelity**: Historical true-positive rate for this detection rule68- **Raw evidence**: Log entries, packet captures, process execution chains6970```71Example SIEM alert context:72Source: CrowdStrike Falcon73Detection: Suspicious PowerShell Execution (T1059.001)74Host: WORKSTATION-FIN-04275User: jsmith@corp.example.com76Timestamp: 2025-11-15T14:23:17Z77Severity: High (detection rule confidence: 92%)78Process: powershell.exe -enc SQBFAFgAIAAoAE4AZQB3AC0ATwBiAGoA...79Parent: outlook.exe (PID 4812)80```8182### Step 2: Classify the Incident Type8384Map the alert to a standard incident category per NIST SP 800-61r3:8586| Category | Examples |87|----------|----------|88| Unauthorized Access | Compromised credentials, privilege escalation, IDOR |89| Denial of Service | Volumetric DDoS, application-layer flood, resource exhaustion |90| Malicious Code | Malware execution, ransomware detonation, cryptominer |91| Improper Usage | Policy violation, insider data exfiltration, shadow IT |92| Reconnaissance | Port scanning, directory enumeration, credential spraying |93| Web Application Attack | SQL injection, XSS, SSRF exploitation |9495### Step 3: Assign Severity Using Impact Matrix9697Calculate severity by combining asset criticality with threat severity:9899```100Severity = f(Asset Criticality, Threat Type, Data Sensitivity, Lateral Movement Potential)101102Critical (P1): Crown jewel systems compromised, active data exfiltration, ransomware spreading103High (P2): Production system compromise, confirmed malware execution, privileged account takeover104Medium (P3): Non-production compromise, unsuccessful exploitation attempt, single endpoint malware105Low (P4): Reconnaissance activity, policy violation, benign true positive106```107108Response SLA targets:109- P1: Acknowledge within 15 minutes, containment within 1 hour110- P2: Acknowledge within 30 minutes, containment within 4 hours111- P3: Acknowledge within 2 hours, investigation within 24 hours112- P4: Acknowledge within 8 hours, investigation within 72 hours113114### Step 4: Perform Initial Enrichment115116Before escalation, enrich the alert with contextual data:117118- **Threat intelligence**: Check IOCs (IP, hash, domain) against TI platforms (VirusTotal, OTX, MISP)119- **Asset context**: Query CMDB for asset owner, business function, data classification120- **User context**: Check identity provider for recent authentication anomalies, MFA status121- **Historical correlation**: Search for related alerts on the same host/user in the past 30 days122- **Network context**: Verify if source/destination IPs are internal, known partners, or external threat actors123124### Step 5: Document and Escalate125126Create a structured triage record and route to the appropriate response tier:127128```129Incident Triage Record130━━━━━━━━━━━━━━━━━━━━━131Ticket ID: INC-2025-1547132Triage Analyst: [analyst name]133Triage Time: 2025-11-15T14:35:00Z (12 min from alert)134Classification: Malicious Code - Macro-based initial access135Severity: P2 - High136Affected Assets: WORKSTATION-FIN-042 (Finance dept, handles PII)137Affected Users: jsmith@corp.example.com138IOCs Identified: powershell.exe spawned by outlook.exe, encoded command139TI Matches: Base64 payload matches known Qakbot loader pattern140Escalation: Tier 2 - Malware IR team141Recommended: Isolate endpoint, preserve memory dump, block sender domain142```143144### Step 6: Initiate Containment Hold145146If severity is P1 or P2, initiate immediate containment actions while awaiting full investigation:147148- Network-isolate the affected endpoint via EDR (CrowdStrike contain, Defender isolate)149- Disable compromised user accounts in Active Directory or identity provider150- Block identified malicious IPs/domains at firewall and DNS sinkhole151- Preserve volatile evidence (memory dump) before any remediation152153## Key Concepts154155| Term | Definition |156|------|------------|157| **Triage** | Rapid assessment process to classify and prioritize security incidents based on severity and business impact |158| **PICERL** | SANS incident response framework: Preparation, Identification, Containment, Eradication, Recovery, Lessons Learned |159| **Dwell Time** | Duration between initial compromise and detection; average is 10 days per Mandiant M-Trends 2025 |160| **True Positive Rate** | Percentage of alerts from a detection rule that represent genuine security incidents |161| **Crown Jewel Assets** | Systems and data critical to business operations whose compromise would cause severe organizational impact |162| **Alert Fatigue** | Degraded analyst performance caused by high volumes of low-fidelity or false-positive alerts |163| **Mean Time to Acknowledge (MTTA)** | Average time from alert generation to analyst acknowledgment; key SOC performance metric |164165## Tools & Systems166167- **Splunk Enterprise Security**: SIEM platform for alert aggregation, correlation, and triage workflow management168- **CrowdStrike Falcon**: EDR platform providing endpoint telemetry, detection, and one-click host containment169- **TheHive**: Open-source incident response platform for case management, task tracking, and team collaboration170- **MISP**: Threat intelligence sharing platform for IOC enrichment during triage171- **Cortex XSOAR**: SOAR platform for automating enrichment playbooks and triage decision trees172173## Common Scenarios174175### Scenario: Encoded PowerShell from Email Client176177**Context**: SOC analyst receives a P2 alert showing `powershell.exe` with a Base64-encoded command spawned as a child process of `outlook.exe` on a finance department workstation.178179**Approach**:1801. Decode the Base64 payload to determine the command intent1812. Check the parent process chain for anomalies (Outlook spawning PowerShell is abnormal)1823. Query VirusTotal for the decoded payload hash1834. Correlate with email gateway logs to identify the triggering email and sender1845. Check if other recipients in the organization received the same email1856. Isolate the endpoint and escalate to Tier 2 with full triage context186187**Pitfalls**:188- Dismissing encoded PowerShell as a false positive without decoding the payload189- Failing to check for lateral spread to other recipients of the same phishing email190- Remediating the endpoint before capturing volatile memory evidence191192## Output Format193194```195INCIDENT TRIAGE REPORT196======================197Ticket: INC-[YYYY]-[NNNN]198Date/Time: [ISO 8601 timestamp]199Triage Analyst: [Name]200Time to Triage: [minutes from alert to classification]201202CLASSIFICATION203Type: [NIST category]204Severity: [P1-P4] - [Critical/High/Medium/Low]205Confidence: [High/Medium/Low]206MITRE ATT&CK: [Technique ID and name]207208AFFECTED SCOPE209Assets: [hostname(s), IP(s)]210Users: [account(s)]211Data at Risk: [classification level]212Business Unit: [department]213214EVIDENCE SUMMARY215[Bullet list of key observations]216217ENRICHMENT RESULTS218TI Matches: [Yes/No - details]219Historical: [Related prior incidents]220Asset Criticality: [rating]221222RECOMMENDED ACTIONS2231. [Immediate action]2242. [Investigation step]2253. [Escalation target]226227ESCALATION228Routed To: [Team/Individual]229SLA Target: [Containment deadline]230```