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 security4 logs to reconstruct events and establish timelines during forensic investigations.5 Use when working with performing log analysis for forensic investigation.6domain: cybersecurity7tags:8- forensics9- log-analysis10- siem11- event-correlation12- timeline-analysis13- evidence-collection14subdomain: digital-forensics15version: '1.0'16author: oyi7717license: Apache-2.018nist_csf:19- RS.AN-0120- RS.AN-0321- DE.AE-0222- RS.MA-0123category: cybersecurity24metadata:25 source: https://skillmd.com/skills/oyi77/performing-log-analysis-for-forensic-investigation26---2728# Performing Log Analysis For Forensic Investigation2930## Overview3132Cybersecurity skill for performing log analysis for forensic investigation. Follows industry best practices and security standards.3334## When to Use35**Trigger phrases:**36- "performing log analysis for forensic investigation"37- "Collect, parse, and correlate system, application, and security logs to reconstr"3839- When reconstructing the timeline of a security incident from available log sources40- During post-breach investigation to identify initial access, lateral movement, and exfiltration41- When correlating events across multiple systems and log sources42- For establishing evidence of unauthorized access or policy violations43- When preparing forensic reports requiring detailed event chronology444546## When NOT to Use4748- When you lack proper authorization for testing49- For production systems without change management50- When the task requires legal or compliance expertise beyond technical scope515253## Prerequisites54- Access to collected log files (Windows Event Logs, syslog, application logs)55- Log parsing tools (LogParser, jq, awk, or ELK stack)56- Understanding of log formats (EVTX, syslog, JSON, CSV)57- NTP-synchronized timestamps across all log sources for correlation58- Sufficient storage for log aggregation and indexing59- Timeline analysis tools (log2timeline, Plaso)6061## Workflow6263```python64# Example: IOC detection65import re6667IOC_PATTERNS = {68 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",69 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",70 "hash_md5": r"\b[a-f0-9]{32}\b",71 "hash_sha256": r"\b[a-f0-9]{64}\b",72}7374def extract_iocs(text: str) -> dict:75 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}76```77781. **Plan Operations** — Define objectives, scope, and success criteria for log analysis operations.792. **Prepare Environment** — Set up tools, access, and data sources required for log analysis.803. **Execute Core Workflow** — Use forensic investigation to perform log analysis operations following established procedures.814. **Validate Results** — Verify that results meet quality standards and objectives.825. **Report Findings** — Document results, observations, and recommendations.836. **Follow Up** — Track remediation actions and verify fixes where applicable.8485## Tools8687- **forensic investigation** — Primary tool for this skill88- **Analysis Platform** — Data processing and visualization89- **Collaboration Tools** — Team coordination and knowledge sharing909192## Process93941. **Reconnaissance** — Gather target information, identify attack surface, enumerate services951. **Analysis/Exploitation** — Execute the technique, analyze results, document findings961. **Reporting** — Document IOCs, write findings, provide remediation recommendations9798## Verification99100- [ ] All log analysis procedures executed completely and documented101- [ ] Findings validated against multiple data sources102- [ ] False positives identified and filtered103- [ ] Results documented with evidence and timestamps104- [ ] Recommendations provided with risk-based prioritization105106## Anti-Rationalization Table107108| Rationalization | Reality |109|---|---|110| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |111| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |112| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |