Performing Log Analysis For Forensic Investigation
Overview
Cybersecurity skill for performing log analysis for forensic investigation. Follows industry best practices and security standards.
When to Use
Trigger phrases:
"performing log analysis for forensic investigation"
"Collect, parse, and correlate system, application, and security logs to reconstr"
When reconstructing the timeline of a security incident from available log sources
During post-breach investigation to identify initial access, lateral movement, and exfiltration
When correlating events across multiple systems and log sources
For establishing evidence of unauthorized access or policy violations
When preparing forensic reports requiring detailed event chronology
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
- Access to collected log files (Windows Event Logs, syslog, application logs)
- Log parsing tools (LogParser, jq, awk, or ELK stack)
- Understanding of log formats (EVTX, syslog, JSON, CSV)
- NTP-synchronized timestamps across all log sources for correlation
- Sufficient storage for log aggregation and indexing
- Timeline analysis tools (log2timeline, Plaso)
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()}
- Plan Operations — Define objectives, scope, and success criteria for log analysis operations.
- Prepare Environment — Set up tools, access, and data sources required for log analysis.
- Execute Core Workflow — Use forensic investigation to perform log analysis operations following established procedures.
- Validate Results — Verify that results meet quality standards and objectives.
- Report Findings — Document results, observations, and recommendations.
- Follow Up — Track remediation actions and verify fixes where applicable.
Tools
- forensic investigation — 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: performing-log-analysis-for-forensic-investigation3description: Use when collect, parse, and correlate system, application, and security logs to reconstruct events and establish timelines during forensic investigations. Use when working with performing log analysis for forensic investigation.4license: Apache-2.05---67# Performing Log Analysis For Forensic Investigation89## Overview1011Cybersecurity skill for performing log analysis for forensic investigation. Follows industry best practices and security standards.1213## When to Use14**Trigger phrases:**15- "performing log analysis for forensic investigation"16- "Collect, parse, and correlate system, application, and security logs to reconstr"1718- When reconstructing the timeline of a security incident from available log sources19- During post-breach investigation to identify initial access, lateral movement, and exfiltration20- When correlating events across multiple systems and log sources21- For establishing evidence of unauthorized access or policy violations22- When preparing forensic reports requiring detailed event chronology232425## When NOT to Use2627- When you lack proper authorization for testing28- For production systems without change management29- When the task requires legal or compliance expertise beyond technical scope303132## Prerequisites33- Access to collected log files (Windows Event Logs, syslog, application logs)34- Log parsing tools (LogParser, jq, awk, or ELK stack)35- Understanding of log formats (EVTX, syslog, JSON, CSV)36- NTP-synchronized timestamps across all log sources for correlation37- Sufficient storage for log aggregation and indexing38- Timeline analysis tools (log2timeline, Plaso)3940## Workflow4142```python43# Example: IOC detection44import re4546IOC_PATTERNS = {47 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",48 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",49 "hash_md5": r"\b[a-f0-9]{32}\b",50 "hash_sha256": r"\b[a-f0-9]{64}\b",51}5253def extract_iocs(text: str) -> dict:54 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}55```56571. **Plan Operations** — Define objectives, scope, and success criteria for log analysis operations.582. **Prepare Environment** — Set up tools, access, and data sources required for log analysis.593. **Execute Core Workflow** — Use forensic investigation to perform log analysis operations following established procedures.604. **Validate Results** — Verify that results meet quality standards and objectives.615. **Report Findings** — Document results, observations, and recommendations.626. **Follow Up** — Track remediation actions and verify fixes where applicable.6364## Tools6566- **forensic investigation** — Primary tool for this skill67- **Analysis Platform** — Data processing and visualization68- **Collaboration Tools** — Team coordination and knowledge sharing697071## Process72731. **Reconnaissance** — Gather target information, identify attack surface, enumerate services741. **Analysis/Exploitation** — Execute the technique, analyze results, document findings751. **Reporting** — Document IOCs, write findings, provide remediation recommendations7677## Verification7879- [ ] All log analysis procedures executed completely and documented80- [ ] Findings validated against multiple data sources81- [ ] False positives identified and filtered82- [ ] Results documented with evidence and timestamps83- [ ] Recommendations provided with risk-based prioritization8485## Anti-Rationalization Table8687| Rationalization | Reality |88|---|---|89| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |90| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |91| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |