Understanding intrusion event classification for SOC analysts
Intrusion events are security incidents that indicate unauthorized access attempts or malicious activity on a network or system. SOC analysts must quickly categorize these events to prioritize response and allocate resources effectively.
Different event types require different response urgency. Critical intrusions need immediate action.
Categorization enables pattern recognition across multiple events and time periods.
Well-defined categories enable SOAR playbooks to automate initial response actions.
Consistent categorization supports compliance reporting and executive dashboards.
When multiple alerts fire simultaneously, use this priority matrix to decide what to investigate first:
| Priority | Event Type | Response | Example |
|---|---|---|---|
| P1 | Active data exfiltration | Immediate containment | Large outbound transfer to unknown IP during off-hours |
| P1 | Ransomware execution | Isolate + IR team | Mass file encryption detected by EDR |
| P2 | C2 beacon detected | Investigate within 15 min | Regular interval connections to suspicious domain |
| P2 | Credential compromise | Force password reset | Impossible travel login + privilege escalation |
| P3 | Reconnaissance activity | Monitor + document | Port scan from external IP against DMZ |
| P4 | Policy violation | Log + notify manager | Unauthorized software installation |
This topic extends the Threat Hunting presentation from Eye House, adding SOC-specific categorization frameworks.
| Stage | Event Type | Example Indicators | Priority |
|---|---|---|---|
| Reconnaissance | Port Scan, Service Enumeration | Nmap signatures, sequential port access | Low-Medium |
| Weaponization | Malware Download | Known malware hashes, suspicious downloads | High |
| Delivery | Phishing, Drive-by | Email attachments, malicious URLs | High |
| Exploitation | Vulnerability Exploit | CVE signatures, buffer overflow patterns | Critical |
| Installation | Malware Persistence | Registry changes, scheduled tasks | Critical |
| C2 | Command & Control | Beaconing, DNS tunneling | Critical |
| Actions | Data Exfiltration | Large outbound transfers, encryption | Critical |
T1566 Phishing, T1190 Exploit Public-Facing App, T1133 External Remote Services
T1059 Command Line, T1204 User Execution, T1053 Scheduled Task
T1547 Boot Autostart, T1136 Create Account, T1078 Valid Accounts
T1021 Remote Services, T1570 Lateral Tool Transfer, T1080 Taint Shared Content
A single intrusion often spans multiple categories. Analysts must identify the primary category for triage while tracking the full attack chain.
| Event Type | Confidence | Impact | Action |
|---|---|---|---|
| Known Malware Hash | High | High | Immediate containment + IR |
| C2 Beacon Detected | High | Critical | Network isolation + forensics |
| Port Scan from External | High | Low | Log, monitor, block if persistent |
| Failed Login Burst | Medium | Medium | Verify account, check for compromise |
| Anomalous DNS Query | Low-Medium | Unknown | Investigate, correlate with other events |
Context is King: A single port scan from a known penetration testing IP is noise. The same scan from an unknown IP during off-hours targeting sensitive systems is actionable intelligence.
Policy violations, failed authentications, routine scans. Log and trend.
Suspicious patterns, anomalies, potential misconfigurations. Investigate within 24h.
Confirmed malicious activity, successful exploits. Investigate within 4h.
Active breach, data exfiltration, ransomware. Immediate response required.
Test your understanding of intrusion event categorization. Score 80% or higher to pass.
1. Which kill chain stage would a "beaconing" alert typically indicate?
2. A SOC analyst sees 500 failed SSH logins from one IP in 10 minutes. What is the most likely event type?
3. Which MITRE ATT&CK tactic includes creating scheduled tasks for persistence?
4. What is the appropriate response to a confirmed C2 beacon detection?
5. Why is categorization important for SOAR playbooks?