Triaging Security Incident With Ir Playbook
Overview
Cybersecurity skill for triaging security incident with ir playbook. Follows industry best practices and security standards.
When to Use
Trigger phrases:
"triaging security incident with ir playbook"
"Classify and prioritize security incidents using structured IR playbooks to dete"
New security alert received from SIEM, EDR, or other detection sources
SOC analyst needs to determine if an alert is a true positive requiring response
Incident needs severity classification and team assignment
Multiple concurrent incidents require prioritization
Automated triage rules need validation or tuning
When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
Prerequisites
- SIEM platform with alert correlation (Splunk, Elastic, QRadar, Sentinel)
- Incident response playbook library (by incident type)
- Severity classification matrix approved by CISO
- On-call rotation and escalation procedures
- Ticketing system for incident tracking (ServiceNow, Jira, TheHive)
- Threat intelligence feeds for IOC enrichment
Workflow
# Example: IOC detection
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs(text: str) -> dict:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
- Define Objectives — Clarify the goals and scope for security incident.
- Gather Resources — Collect tools, data, and access needed for security incident.
- Execute Process — Carry out security incident operations methodically.
- Verify Quality — Check results against acceptance criteria.
- Document Outcomes — Record findings, decisions, and next steps.
Tools
- ir playbook — Primary tool for this skill
- Analysis Platform — Data processing and visualization
- Collaboration Tools — Team coordination and knowledge sharing
Process
- Reconnaissance — Gather target information, identify attack surface, enumerate services
- Analysis/Exploitation — Execute the technique, analyze results, document findings
- Reporting — Document IOCs, write findings, provide remediation recommendations
Verification
Anti-Rationalization Table
| Rationalization |
Reality |
| "We are too small to be targeted" |
Automated attacks target everyone. Size does not matter. |
| "Security slows us down" |
A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" |
Vulnerabilities in production are exploited within hours. Fix before deploy. |
1---2name: triaging-security-incident-with-ir-playbook3description: Use when classify and prioritize security incidents using structured4 IR playbooks to determine severity, assign response teams, and initiate appropriate5 response procedures. Use when working with triaging security incident with ir playbook.6domain: cybersecurity7tags:8- incident-response9- triage10- playbook11- severity-classification12- soc13subdomain: incident-response14mitre_attack:15- T119016- T156617- T107818version: '1.0'19author: oyi7720license: Apache-2.021nist_csf:22- RS.MA-0123- RS.MA-0224- RS.AN-0325- RC.RP-0126category: cybersecurity27metadata:28 source: https://skillmd.com/skills/oyi77/triaging-security-incident-with-ir-playbook29---3031# Triaging Security Incident With Ir Playbook3233## Overview3435Cybersecurity skill for triaging security incident with ir playbook. Follows industry best practices and security standards.3637## When to Use38**Trigger phrases:**39- "triaging security incident with ir playbook"40- "Classify and prioritize security incidents using structured IR playbooks to dete"4142- New security alert received from SIEM, EDR, or other detection sources43- SOC analyst needs to determine if an alert is a true positive requiring response44- Incident needs severity classification and team assignment45- Multiple concurrent incidents require prioritization46- Automated triage rules need validation or tuning474849## When NOT to Use5051- When you lack proper authorization for testing52- For production systems without change management53- When the task requires legal or compliance expertise beyond technical scope545556## Prerequisites57- SIEM platform with alert correlation (Splunk, Elastic, QRadar, Sentinel)58- Incident response playbook library (by incident type)59- Severity classification matrix approved by CISO60- On-call rotation and escalation procedures61- Ticketing system for incident tracking (ServiceNow, Jira, TheHive)62- Threat intelligence feeds for IOC enrichment6364## Workflow6566```python67# Example: IOC detection68import re6970IOC_PATTERNS = {71 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",72 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",73 "hash_md5": r"\b[a-f0-9]{32}\b",74 "hash_sha256": r"\b[a-f0-9]{64}\b",75}7677def extract_iocs(text: str) -> dict:78 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}79```80811. **Define Objectives** — Clarify the goals and scope for security incident.822. **Gather Resources** — Collect tools, data, and access needed for security incident.833. **Execute Process** — Carry out security incident operations methodically.844. **Verify Quality** — Check results against acceptance criteria.855. **Document Outcomes** — Record findings, decisions, and next steps.8687## Tools8889- **ir playbook** — Primary tool for this skill90- **Analysis Platform** — Data processing and visualization91- **Collaboration Tools** — Team coordination and knowledge sharing929394## Process95961. **Reconnaissance** — Gather target information, identify attack surface, enumerate services971. **Analysis/Exploitation** — Execute the technique, analyze results, document findings981. **Reporting** — Document IOCs, write findings, provide remediation recommendations99100## Verification101102- [ ] All security incident procedures executed completely and documented103- [ ] Findings validated against multiple data sources104- [ ] False positives identified and filtered105- [ ] Results documented with evidence and timestamps106- [ ] Recommendations provided with risk-based prioritization107108## Anti-Rationalization Table109110| Rationalization | Reality |111|---|---|112| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |113| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |114| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |