Study guide
2.2 Incident Recording, Categorization, and Triage Methodologies
EC-Council Certified Incident Handler ECIH
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction to Incident Handling and Response
1.1 Information Security Fundamentals, Threat Landscapes, and Attack Vectors 1.2 Incident Management Principles, CSIRT Team Structures, and SOAR Automation 1.3 Cyber Defense Frameworks: NIST SP 800-61, ISO 27035, MITRE ATT&CK, and Cyber Kill Chain 1.4 Risk Management, Security Policies, and Security Auditing
2 Chapter 2: Incident Handling Process: Preparation, Detection, and Triage
2.1 Incident Response Preparation, Policies, and Playbook Design 2.2 Incident Recording, Categorization, and Triage Methodologies 2.3 Incident Notification, Escalation Paths, and Stakeholder Communication
3 Chapter 3: Incident Handling Process: Containment, Eradication, and Post-Incident
3.1 Incident Containment Strategies, Isolation, and Evidence Protection 3.2 Eradication Procedures, Remediation, and Secure System Recovery 3.3 Post-Incident Review, Lessons Learned, and Threat Intelligence Sharing
4 Chapter 4: Forensic Readiness and First Response
4.1 Forensic Readiness Planning, Legal Mandates, and Regulatory Compliance 4.2 First Response Principles, Scene Securing, and Order of Volatility 4.3 Digital Evidence Collection, Packaging, and Chain of Custody 4.4 Anti-Forensics Detection, Evidence Gaps, and Countermeasures
5 Chapter 5: Handling and Responding to Malware Incidents
5.1 Malware Classification, Attack Vectors, and Modern Threat Profiles 5.2 Static Analysis, Dynamic Analysis, and Sandboxing Workflows 5.3 Malware Detection, Memory Forensics, and Eradication Strategies
6 Chapter 6: Handling and Responding to Email Security Incidents
6.1 Email Attack Vectors: Phishing, Spear Phishing, BEC, and Spoofing 6.2 Email Header Forensics, Link Triage, and Malicious Attachment Analysis 6.3 Email Authentication Protocols (SPF, DKIM, DMARC) and Incident Containment
7 Chapter 7: Handling and Responding to Network Security Incidents
7.1 Network Reconnaissance, Unauthorized Access, and Port Scanning 7.2 Denial of Service (DoS/DDoS) Attack Mechanisms and Traffic Mitigation 7.3 Wireless Network Incidents, Session Hijacking, and Packet Analysis 7.4 Inappropriate Usage Incidents: Validation, Evidence, and Response
8 Chapter 8: Handling and Responding to Web Application Security Incidents
8.1 Web Application Threat Vectors: Injection, XSS, and CSRF Incidents 8.2 Web Server and Application Log Analysis (Apache, Nginx, IIS) 8.3 Web Application Incident Containment, Patching, and Defense-in-Depth
9 Chapter 9: Handling and Responding to Cloud Security Incidents
9.1 Cloud Shared Responsibility, Threat Landscape, and IAM Attacks 9.2 Cloud Telemetry and Audit Logging (AWS CloudTrail, Azure Activity, GCP Audit) 9.3 Cloud Incident Containment, Snapshot Forensics, and Container Security
10 Chapter 10: Handling and Responding to Insider Threats
10.1 Insider Threat Typologies, Behavioral Indicators, and Risk Profiles 10.2 Insider Threat Detection: UEBA, Data Loss Prevention, and Audit Trails 10.3 Insider Incident Investigation, Evidence Handling, and Legal Reporting
11 Chapter 11: Handling and Responding to Endpoint, IoT, and OT Incidents
11.1 Windows Endpoint Forensics and Volatile Artifact Analysis 11.2 Linux and macOS Endpoint Incident Investigation 11.3 Mobile Device Isolation, Acquisition, and Incident Handling 11.4 IoT Incident Handling and Firmware Investigation 11.5 OT and ICS Incident Handling: Safety, Visibility, and Recovery
2.2 Incident Recording, Categorization, and Triage Methodologies
Key Takeaways Explain This Topic AI
Prompt case creation should preserve original timestamps and clock context while normalizing a working timeline to UTC; NTP synchronization and documented drift improve correlation but do not by themselves prove integrity.
Incidents must be categorized using standardized taxonomies, distinguishing unauthorized access, malicious code, denial of service, improper usage, and social engineering scams.
Severity prioritization matrices evaluate functional operational impact, information confidentiality/integrity loss, and system recoverability effort to assign priority levels (P1 through P4).
Triage workflows systematically filter false positives through alert enrichment, contextualizing telemetry using threat intelligence feeds, DNS history, and asset criticalities.
SIEM correlation engines and User and Entity Behavior Analytics (UEBA) automate the aggregation of disparate log events to uncover complex, multi-stage cyber intrusions.
Last updated: October 2026
2.2 Incident Recording, Categorization, and Triage Methodologies
Enterprise security operations centers (SOCs) ingest millions of events daily from endpoint detection and response (EDR) sensors, firewalls, intrusion detection systems, identity providers, and cloud audit logs. The objective of detection and triage is to filter this operational noise, capture forensic details, establish chronological defensibility, and categorize threats using standardized severity matrices. Disciplined triage reduces alert fatigue and known visibility gaps while directing finite defensive resources toward higher-risk events.
Incident Recording and Intake Protocols
When anomalous activity crosses detection thresholds, formal incident recording must occur immediately. The records generated during intake form the evidentiary foundation for subsequent containment, eradication, and legal proceedings.
Rigorous intake requires adherence to five evidentiary principles:
Ticketing System Intake: Intake occurs within a dedicated SOAR, Incident Management, or SIEM ticketing platform (ServiceNow, Jira Service Management, or TheHive). Every incident receives a unique, stable case identifier, with any correction or reassignment recorded rather than silently overwritten.
Synchronized UTC Timestamping: Record original source timestamps, time zones, clock settings, and observed drift; use NTP where appropriate and normalize a working copy to UTC for correlation without rewriting the source evidence. Timestamp variances between disparate logs obscure adversary sequences and compromise court admissibility.
Comprehensive Evidence Logs: Intake records capture observable indicators: IP addresses, transport protocols, ports, domain names, file paths, cryptographic hashes (MD5, SHA-256), MAC addresses, cloud instance IDs, and user account Security Identifiers (SIDs).
Formulation of Initial Working Hypothesis: Responders document a preliminary hypothesis identifying what occurred, the likely initial access vector, adversary objectives, and immediate operational exposure, refining it as evidence develops.
Chain of Custody Tracking: Any digital or physical artifact collected during intake must be cataloged in a Chain of Custody register, documenting the collector, exact collection timestamp, storage location, and cryptographic hash verification.
Incident Categorization by Attack Taxonomy
Standardized categorization taxonomies, such as those established by EC-Council and NIST, organize cyber threats into operational categories that determine which response playbook executes:
Unauthorized Access: An unauthorized entity gains logical access to an organizational network, application, system, or sensitive data store (e.g., compromised credentials, pass-the-hash attacks, rogue privilege escalation, and unauthorized SSH or RDP sessions).
Malicious Code: Execution of hostile software payloads designed to undermine system integrity, confidentiality, or availability (e.g., ransomware, banking trojans, keyloggers, fileless in-memory DLL injection, kernel rootkits, and cryptominers).
Denial of Service (DoS / DDoS): Deliberate disruption preventing authorized users from accessing critical services or network infrastructure. Encompasses volumetric floods (SYN, UDP, ICMP), state-table exhaustion attacks against firewalls, and application-layer resource starvation.
Improper Usage: Internal users violating corporate Acceptable Use Policies (AUP), such as installing unapproved peer-to-peer file-sharing software, running cryptocurrency miners, or deploying unauthorized shadow IT cloud storage.
Scams and Social Engineering: Psychological manipulation designed to induce human error (e.g., targeted spear-phishing campaigns, executive Business Email Compromise wire fraud, credential harvesting sites, and telephone vishing).
Multiple Components (Blended Threats): Advanced Persistent Threat (APT) campaigns chaining multiple vectors together—such as executing a spear-phishing lure to obtain initial workstation access, dumping credentials, moving laterally, and deploying ransomware.
Severity Rating and Prioritization Matrices
Incident prioritization cannot rely on subjective analyst intuition. Organizations should employ a documented severity matrix that evaluates technical dimensions alongside financial and reputational impact. Priority labels and response-time targets are organization-specific rather than universal ECIH or NIST values: Incident Priority = f ( Functional Impact , Information Impact , Recoverability Effort ) \text{Incident Priority} = f(\text{Functional Impact},\; \text{Information Impact},\; \text{Recoverability Effort}) Incident Priority = f ( Functional Impact , Information Impact , Recoverability Effort )
Functional Impact: Measures operational impairment: None (no disruption), Low (minor non-critical services degraded; workarounds available), Medium (significant impairment of core functions), High (total collapse of critical operations or infrastructure).
Information Impact: Evaluates compromised data: None (no sensitive data accessed), Privacy Breach (PII or PHI exposed), Proprietary Breach (trade secrets, source code, or financial records exfiltrated), Integrity Loss (unauthorized alteration of financial ledgers or audit logs).
Recoverability Effort: Evaluates recovery complexity: Regular (predictable recovery via standard tools), Extended (significant manual rebuilds and credential resets), Difficult (complex recovery requiring custom engineering or external specialists), Not Recoverable (permanent data destruction).
Illustrative Enterprise Incident Priority Levels and SLAs
Priority 1 (Critical): High functional impact and high information impact (e.g., enterprise-wide ransomware or root Active Directory compromise). Example initial response target: under 15 minutes with immediate 24/7 callout.
Priority 2 (High): Medium to high operational impact with localized sensitive data exposure. Example initial response target: under 1 hour .
Priority 3 (Medium): Low to moderate operational impact (e.g., isolated single-host malware infection without propagation). Example initial response target: under 4 hours .
Priority 4 (Low): Negligible impact (e.g., port scans, blocked phishing emails with no user interaction). Example initial response target: under 24 hours .
Triage Workflows: Alert Validation and Threat Enrichment
Triage separates benign operational noise from genuine security compromise:
Distinguishing True Positives from False Positives: A false positive is a benign operational event triggering an overly broad detection rule. Responders validate alerts by examining process ancestry ; for instance, powershell.exe spawned by explorer.exe or an IT automation account represents normal activity, whereas powershell.exe spawned as a child of winword.exe, excel.exe, or a web server process (w3wp.exe) strongly indicates exploit delivery.
Alert Enrichment Protocols: Responders enrich raw indicators with external threat intelligence (VirusTotal, AlienVault OTX, abuse.ch) to assess whether IP addresses, domains, or file hashes match known adversary infrastructure. Passive DNS queries evaluate domain registration age; domains registered under 30 days old resolving to foreign bulletproof hosting represent high risk. Internal context correlates affected systems against Configuration Management Databases (CMDB), prioritizing production databases over test virtual machines.
SIEM Correlation Rules and Behavioral Analytics: Modern SIEM platforms execute automated correlation rules linking temporal sequences (e.g., 50 failed SSH authentication attempts within 60 seconds followed by a successful login and sudo command) and cross-source events. User and Entity Behavior Analytics (UEBA) applies statistical baselines to detect anomalous user activities, such as an employee downloading 50 gigabytes of files outside normal working hours.