[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7364CYV8HPJQJQCMD7F0ADN":3,"skill-same:01M7364CYV8HPJQJQCMD7F0ADN":90},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M7364CYV8HPJQJQCMD7F0ADN","performing-log-analysis-for-forensic-investigation",null,"Collect, parse, and correlate system, application, and security logs to reconstruct events and establish timelines during forensic investigations.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fperforming-log-analysis-for-forensic-investigation\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fperforming-log-analysis-for-forensic-investigation\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: performing-log-analysis-for-forensic-investigation\ndescription: Collect, parse, and correlate system, application, and security logs\n  to reconstruct events and establish timelines during forensic investigations.\ndomain: cybersecurity\nsubdomain: digital-forensics\ntags:\n- forensics\n- log-analysis\n- siem\n- event-correlation\n- timeline-analysis\n- evidence-collection\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- RS.AN-01\n- RS.AN-03\n- DE.AE-02\n- RS.MA-01\nmitre_attack:\n- T1005\n- T1074\n- T1119\n- T1070\n- T1685.002\nsource: https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\nsource_commit: 04450304b12645cb2b974ab96d28c0664758a88d\nnote: \"Vendored verbatim from an external Apache-2.0 security-skill library, pinned by commit. Exceeds the internal 300-line skill guideline (agent-code-constraints.md) -- kept as-is because this is vendored reference material (forensics\u002Fthreat-intel procedure), not Yana AI-authored content, and trimming would damage technical accuracy.\"\n---\n\n# Performing Log Analysis for Forensic Investigation\n\n## When to Use\n- When reconstructing the timeline of a security incident from available log sources\n- During post-breach investigation to identify initial access, lateral movement, and exfiltration\n- When correlating events across multiple systems and log sources\n- For establishing evidence of unauthorized access or policy violations\n- When preparing forensic reports requiring detailed event chronology\n\n## Prerequisites\n- Access to collected log files (Windows Event Logs, syslog, application logs)\n- Log parsing tools (LogParser, jq, awk, or ELK stack)\n- Understanding of log formats (EVTX, syslog, JSON, CSV)\n- NTP-synchronized timestamps across all log sources for correlation\n- Sufficient storage for log aggregation and indexing\n- Timeline analysis tools (log2timeline, Plaso)\n\n## Workflow\n\n### Step 1: Collect and Preserve Log Sources\n\n```bash\n# Create case log directory structure\nmkdir -p \u002Fcases\u002Fcase-2024-001\u002Flogs\u002F{windows,linux,network,application,web}\n\n# Extract Windows Event Logs from forensic image\ncp \u002Fmnt\u002Fevidence\u002FWindows\u002FSystem32\u002Fwinevt\u002FLogs\u002F*.evtx \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Fwindows\u002F\n\n# Key Windows Event Logs to collect\n# Security.evtx - Authentication, access control, policy changes\n# System.evtx - Service starts\u002Fstops, driver loads, system errors\n# Application.evtx - Application errors and events\n# Microsoft-Windows-PowerShell%4Operational.evtx - PowerShell execution\n# Microsoft-Windows-Sysmon%4Operational.evtx - Sysmon detailed events\n# Microsoft-Windows-TaskScheduler%4Operational.evtx - Scheduled tasks\n# Microsoft-Windows-TerminalServices-LocalSessionManager%4Operational.evtx - RDP\n\n# Collect Linux logs\ncp \u002Fmnt\u002Fevidence\u002Fvar\u002Flog\u002Fauth.log* \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Flinux\u002F\ncp \u002Fmnt\u002Fevidence\u002Fvar\u002Flog\u002Fsyslog* \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Flinux\u002F\ncp \u002Fmnt\u002Fevidence\u002Fvar\u002Flog\u002Fkern.log* \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Flinux\u002F\ncp \u002Fmnt\u002Fevidence\u002Fvar\u002Flog\u002Fsecure* \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Flinux\u002F\ncp \u002Fmnt\u002Fevidence\u002Fvar\u002Flog\u002Faudit\u002Faudit.log* \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Flinux\u002F\n\n# Collect web server logs\ncp \u002Fmnt\u002Fevidence\u002Fvar\u002Flog\u002Fapache2\u002Faccess.log* \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Fweb\u002F\ncp \u002Fmnt\u002Fevidence\u002Fvar\u002Flog\u002Fnginx\u002Faccess.log* \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Fweb\u002F\n\n# Hash all collected logs for integrity\nfind \u002Fcases\u002Fcase-2024-001\u002Flogs\u002F -type f -exec sha256sum {} \\; > \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Flog_hashes.txt\n```\n\n### Step 2: Parse Windows Event Logs\n\n```bash\n# Install python-evtx for EVTX parsing\npip install python-evtx\n\n# Convert EVTX to XML\u002FJSON for analysis\npython3 -c \"\nimport Evtx.Evtx as evtx\nimport json, xml.etree.ElementTree as ET\n\nwith evtx.Evtx('\u002Fcases\u002Fcase-2024-001\u002Flogs\u002Fwindows\u002FSecurity.evtx') as log:\n    for record in log.records():\n        print(record.xml())\n\" > \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Fwindows\u002FSecurity_parsed.xml\n\n# Using evtxexport (libevtx-utils)\nsudo apt-get install libevtx-utils\nevtxexport \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Fwindows\u002FSecurity.evtx \\\n   > \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Fwindows\u002FSecurity_exported.txt\n\n# Key Security Event IDs to investigate\n# 4624 - Successful logon\n# 4625 - Failed logon\n# 4648 - Logon using explicit credentials (runas, lateral movement)\n# 4672 - Special privileges assigned (admin logon)\n# 4688 - Process creation (with command line if auditing enabled)\n# 4697 - Service installed\n# 4698\u002F4702 - Scheduled task created\u002Fupdated\n# 4720 - User account created\n# 4732 - Member added to security-enabled local group\n# 1102 - Audit log cleared\n\n# Extract specific events with python-evtx\npython3 \u003C\u003C 'PYEOF'\nimport Evtx.Evtx as evtx\nimport xml.etree.ElementTree as ET\n\ntarget_events = ['4624', '4625', '4648', '4672', '4688', '4697', '1102']\n\nwith evtx.Evtx('\u002Fcases\u002Fcase-2024-001\u002Flogs\u002Fwindows\u002FSecurity.evtx') as log:\n    for record in log.records():\n        root = ET.fromstring(record.xml())\n        ns = {'ns': 'http:\u002F\u002Fschemas.microsoft.com\u002Fwin\u002F2004\u002F08\u002Fevents\u002Fevent'}\n        event_id = root.find('.\u002F\u002Fns:EventID', ns).text\n        if event_id in target_events:\n            time = root.find('.\u002F\u002Fns:TimeCreated', ns).get('SystemTime')\n            print(f\"[{time}] EventID: {event_id}\")\n            for data in root.findall('.\u002F\u002Fns:Data', ns):\n                print(f\"  {data.get('Name')}: {data.text}\")\n            print()\nPYEOF\n```\n\n### Step 3: Parse and Analyze Linux\u002FSyslog Entries\n\n```bash\n# Parse auth.log for SSH and sudo events\ngrep -E '(sshd|sudo|su\\[|passwd|useradd|usermod)' \\\n   \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Flinux\u002Fauth.log* | \\\n   sort > \u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Fauth_events.txt\n\n# Extract failed SSH login attempts\ngrep 'Failed password' \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Flinux\u002Fauth.log* | \\\n   awk '{print $1,$2,$3,$9,$11}' | sort | uniq -c | sort -rn \\\n   > \u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Ffailed_ssh.txt\n\n# Extract successful SSH logins\ngrep 'Accepted' \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Flinux\u002Fauth.log* | \\\n   awk '{print $1,$2,$3,$9,$11}' > \u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Fsuccessful_ssh.txt\n\n# Parse audit logs for file access and command execution\nausearch -if \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Flinux\u002Faudit.log \\\n   --start 2024-01-15 --end 2024-01-20 \\\n   -m EXECVE > \u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Faudit_commands.txt\n\nausearch -if \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Flinux\u002Faudit.log \\\n   -m USER_AUTH,USER_LOGIN,USER_CMD \\\n   > \u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Faudit_auth.txt\n\n# Parse web access logs for suspicious requests\ncat \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Fweb\u002Faccess.log* | \\\n   grep -iE '(union.*select|\u003Cscript|\\.\\.\\\u002F|cmd\\.exe|\u002Fetc\u002Fpasswd)' \\\n   > \u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Fweb_attacks.txt\n\n# Extract unique IP addresses from web logs\nawk '{print $1}' \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Fweb\u002Faccess.log* | \\\n   sort | uniq -c | sort -rn > \u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Fweb_ips.txt\n```\n\n### Step 4: Correlate Events Across Sources\n\n```bash\n# Normalize timestamps and merge log sources\npython3 \u003C\u003C 'PYEOF'\nimport csv\nimport datetime\nfrom collections import defaultdict\n\nevents = []\n\n# Parse Windows Security events (pre-exported to CSV)\nwith open('\u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Fwindows_events.csv') as f:\n    reader = csv.DictReader(f)\n    for row in reader:\n        events.append({\n            'timestamp': row['TimeCreated'],\n            'source': 'Windows-Security',\n            'event_id': row['EventID'],\n            'description': row['Description'],\n            'details': row.get('Details', '')\n        })\n\n# Parse Linux auth events\nwith open('\u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Fauth_events.txt') as f:\n    for line in f:\n        parts = line.strip().split()\n        if len(parts) >= 6:\n            events.append({\n                'timestamp': ' '.join(parts[:3]),\n                'source': 'Linux-Auth',\n                'event_id': parts[4].rstrip(':'),\n                'description': ' '.join(parts[5:]),\n                'details': ''\n            })\n\n# Sort by timestamp\nevents.sort(key=lambda x: x['timestamp'])\n\n# Write correlated timeline\nwith open('\u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Fcorrelated_timeline.csv', 'w', newline='') as f:\n    writer = csv.DictWriter(f, fieldnames=['timestamp', 'source', 'event_id', 'description', 'details'])\n    writer.writeheader()\n    writer.writerows(events)\n\nprint(f\"Total correlated events: {len(events)}\")\nPYEOF\n\n# Quick correlation: find events within time windows\n# Look for lateral movement patterns\ngrep \"4648\\|4624.*Type.*3\\|4624.*Type.*10\" \u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Fwindows_events.csv | \\\n   sort > \u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Flateral_movement.txt\n```\n\n### Step 5: Generate Forensic Timeline Report\n\n```bash\n# Create structured investigation report\ncat \u003C\u003C 'REPORT' > \u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Flog_analysis_report.txt\nLOG ANALYSIS FORENSIC REPORT\n=============================\nCase: 2024-001\nAnalyst: [Examiner Name]\nDate: $(date -u)\n\nLOG SOURCES ANALYZED:\n- Windows Security Event Log (Security.evtx) - 245,678 events\n- Windows System Event Log (System.evtx) - 45,234 events\n- Windows PowerShell Operational - 12,456 events\n- Linux auth.log - 34,567 entries\n- Apache access.log - 567,890 entries\n- Linux audit.log - 89,012 entries\n\nKEY FINDINGS:\n1. Initial Access: [timestamp] - Successful RDP login from external IP\n2. Privilege Escalation: [timestamp] - New admin account created\n3. Lateral Movement: [timestamp] - Pass-the-hash detected across 3 systems\n4. Data Exfiltration: [timestamp] - Large data transfer to external IP\n5. Log Tampering: [timestamp] - Security event log cleared (Event 1102)\n\nTIMELINE OF EVENTS:\n[See correlated_timeline.csv for complete chronology]\nREPORT\n\n# Package analysis artifacts\ntar -czf \u002Fcases\u002Fcase-2024-001\u002Flog_analysis_package.tar.gz \\\n   \u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002F\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| Event correlation | Linking related events across multiple log sources by time, IP, user, or session |\n| Log normalization | Converting diverse log formats into a common schema for unified analysis |\n| Timeline analysis | Chronological ordering of events to reconstruct incident sequence |\n| Log integrity | Verifying logs have not been tampered with using hashes and chain of custody |\n| Logon types | Windows categorization of authentication methods (2=interactive, 3=network, 10=RDP) |\n| Audit policy | System configuration determining which events are recorded in logs |\n| Log rotation | Automatic archiving of log files that affects evidence availability |\n| Anti-forensics | Attacker techniques for clearing or modifying logs to cover tracks |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| python-evtx | Python library for parsing Windows EVTX event log files |\n| evtxexport | Command-line EVTX export utility from libevtx |\n| LogParser | Microsoft SQL-like query engine for Windows logs |\n| ausearch | Linux audit log search utility |\n| jq | JSON query tool for parsing structured log formats |\n| ELK Stack | Elasticsearch, Logstash, Kibana for log aggregation and visualization |\n| Chainsaw | Sigma-based Windows Event Log analysis tool |\n| Hayabusa | Fast Windows Event Log forensic timeline generator |\n\n## Common Scenarios\n\n**Scenario 1: Brute Force Attack Detection**\nFilter Security.evtx for Event ID 4625 (failed logons), group by source IP and target account, identify patterns of rapid successive failures, find the successful logon (4624) that followed, trace subsequent activity from the compromised account.\n\n**Scenario 2: Insider Threat Investigation**\nCollect all log sources from the suspect's workstation and accessed servers, correlate file access events with authentication events, build timeline of data access during non-business hours, identify data transfers to external media or cloud storage.\n\n**Scenario 3: Web Application Compromise**\nParse web server access logs for SQLi, XSS, and path traversal patterns, identify the attack IP and timeline, correlate with application logs for successful exploitation, trace post-exploitation activity through system and auth logs.\n\n**Scenario 4: Ransomware Incident Timeline**\nIdentify the initial execution through process creation events (4688), trace privilege escalation through service installation (4697), map lateral movement via network logons (4624 Type 3), identify encryption start from file system activity, find the earliest IoC for remediation scoping.\n\n## Output Format\n\n```\nLog Analysis Summary:\n  Investigation Period: 2024-01-15 00:00 to 2024-01-20 23:59 UTC\n  Total Events Analyzed: 894,567\n  Log Sources: 6 (3 Windows, 3 Linux)\n\n  Critical Events:\n    Failed Logons:       1,234 (from 5 unique IPs)\n    Successful Logons:   456 (3 anomalous)\n    Account Changes:     12 (1 unauthorized admin creation)\n    Process Creations:   8,234 (15 suspicious)\n    Log Clearings:       2 (Security log cleared at 2024-01-18 03:00 UTC)\n    Service Installs:    3 (1 unknown service)\n\n  Attack Timeline:\n    2024-01-15 14:32 - Initial access via RDP brute force\n    2024-01-15 14:45 - Admin account \"svcbackup\" created\n    2024-01-16 02:15 - Lateral movement to 3 servers\n    2024-01-17 03:00 - Data staging in C:\\ProgramData\\temp\\\n    2024-01-18 01:30 - 4.2 GB exfiltrated to 185.x.x.x\n    2024-01-18 03:00 - Security logs cleared\n\n  Report: \u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Flog_analysis_report.txt\n```\n","# Performing Log Analysis for Forensic Investigation\n\n## When to Use\n- When reconstructing the timeline of a security incident from available log sources\n- During post-breach investigation to identify initial access, lateral movement, and exfiltration\n- When correlating events across multiple systems and log sources\n- For establishing evidence of unauthorized access or policy violations\n- When preparing forensic reports requiring detailed event chronology\n\n## Prerequisites\n- Access to collected log files (Windows Event Logs, syslog, application logs)\n- Log parsing tools (LogParser, jq, awk, or ELK stack)\n- Understanding of log formats (EVTX, syslog, JSON, CSV)\n- NTP-synchronized timestamps across all log sources for correlation\n- Sufficient storage for log aggregation and indexing\n- Timeline analysis tools (log2timeline, Plaso)\n\n## Workflow\n\n### Step 1: Collect and Preserve Log Sources\n\n```bash\n# Create case log directory structure\nmkdir -p \u002Fcases\u002Fcase-2024-001\u002Flogs\u002F{windows,linux,network,application,web}\n\n# Extract Windows Event Logs from forensic image\ncp \u002Fmnt\u002Fevidence\u002FWindows\u002FSystem32\u002Fwinevt\u002FLogs\u002F*.evtx \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Fwindows\u002F\n\n# Key Windows Event Logs to collect\n# Security.evtx - Authentication, access control, policy changes\n# System.evtx - Service starts\u002Fstops, driver loads, system errors\n# Application.evtx - Application errors and events\n# Microsoft-Windows-PowerShell%4Operational.evtx - PowerShell execution\n# Microsoft-Windows-Sysmon%4Operational.evtx - Sysmon detailed events\n# Microsoft-Windows-TaskScheduler%4Operational.evtx - Scheduled tasks\n# Microsoft-Windows-TerminalServices-LocalSessionManager%4Operational.evtx - RDP\n\n# Collect Linux logs\ncp \u002Fmnt\u002Fevidence\u002Fvar\u002Flog\u002Fauth.log* \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Flinux\u002F\ncp \u002Fmnt\u002Fevidence\u002Fvar\u002Flog\u002Fsyslog* \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Flinux\u002F\ncp \u002Fmnt\u002Fevidence\u002Fvar\u002Flog\u002Fkern.log* \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Flinux\u002F\ncp \u002Fmnt\u002Fevidence\u002Fvar\u002Flog\u002Fsecure* \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Flinux\u002F\ncp \u002Fmnt\u002Fevidence\u002Fvar\u002Flog\u002Faudit\u002Faudit.log* \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Flinux\u002F\n\n# Collect web server logs\ncp \u002Fmnt\u002Fevidence\u002Fvar\u002Flog\u002Fapache2\u002Faccess.log* \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Fweb\u002F\ncp \u002Fmnt\u002Fevidence\u002Fvar\u002Flog\u002Fnginx\u002Faccess.log* \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Fweb\u002F\n\n# Hash all collected logs for integrity\nfind \u002Fcases\u002Fcase-2024-001\u002Flogs\u002F -type f -exec sha256sum {} \\; > \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Flog_hashes.txt\n```\n\n### Step 2: Parse Windows Event Logs\n\n```bash\n# Install python-evtx for EVTX parsing\npip install python-evtx\n\n# Convert EVTX to XML\u002FJSON for analysis\npython3 -c \"\nimport Evtx.Evtx as evtx\nimport json, xml.etree.ElementTree as ET\n\nwith evtx.Evtx('\u002Fcases\u002Fcase-2024-001\u002Flogs\u002Fwindows\u002FSecurity.evtx') as log:\n    for record in log.records():\n        print(record.xml())\n\" > \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Fwindows\u002FSecurity_parsed.xml\n\n# Using evtxexport (libevtx-utils)\nsudo apt-get install libevtx-utils\nevtxexport \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Fwindows\u002FSecurity.evtx \\\n   > \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Fwindows\u002FSecurity_exported.txt\n\n# Key Security Event IDs to investigate\n# 4624 - Successful logon\n# 4625 - Failed logon\n# 4648 - Logon using explicit credentials (runas, lateral movement)\n# 4672 - Special privileges assigned (admin logon)\n# 4688 - Process creation (with command line if auditing enabled)\n# 4697 - Service installed\n# 4698\u002F4702 - Scheduled task created\u002Fupdated\n# 4720 - User account created\n# 4732 - Member added to security-enabled local group\n# 1102 - Audit log cleared\n\n# Extract specific events with python-evtx\npython3 \u003C\u003C 'PYEOF'\nimport Evtx.Evtx as evtx\nimport xml.etree.ElementTree as ET\n\ntarget_events = ['4624', '4625', '4648', '4672', '4688', '4697', '1102']\n\nwith evtx.Evtx('\u002Fcases\u002Fcase-2024-001\u002Flogs\u002Fwindows\u002FSecurity.evtx') as log:\n    for record in log.records():\n        root = ET.fromstring(record.xml())\n        ns = {'ns': 'http:\u002F\u002Fschemas.microsoft.com\u002Fwin\u002F2004\u002F08\u002Fevents\u002Fevent'}\n        event_id = root.find('.\u002F\u002Fns:EventID', ns).text\n        if event_id in target_events:\n            time = root.find('.\u002F\u002Fns:TimeCreated', ns).get('SystemTime')\n            print(f\"[{time}] EventID: {event_id}\")\n            for data in root.findall('.\u002F\u002Fns:Data', ns):\n                print(f\"  {data.get('Name')}: {data.text}\")\n            print()\nPYEOF\n```\n\n### Step 3: Parse and Analyze Linux\u002FSyslog Entries\n\n```bash\n# Parse auth.log for SSH and sudo events\ngrep -E '(sshd|sudo|su\\[|passwd|useradd|usermod)' \\\n   \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Flinux\u002Fauth.log* | \\\n   sort > \u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Fauth_events.txt\n\n# Extract failed SSH login attempts\ngrep 'Failed password' \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Flinux\u002Fauth.log* | \\\n   awk '{print $1,$2,$3,$9,$11}' | sort | uniq -c | sort -rn \\\n   > \u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Ffailed_ssh.txt\n\n# Extract successful SSH logins\ngrep 'Accepted' \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Flinux\u002Fauth.log* | \\\n   awk '{print $1,$2,$3,$9,$11}' > \u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Fsuccessful_ssh.txt\n\n# Parse audit logs for file access and command execution\nausearch -if \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Flinux\u002Faudit.log \\\n   --start 2024-01-15 --end 2024-01-20 \\\n   -m EXECVE > \u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Faudit_commands.txt\n\nausearch -if \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Flinux\u002Faudit.log \\\n   -m USER_AUTH,USER_LOGIN,USER_CMD \\\n   > \u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Faudit_auth.txt\n\n# Parse web access logs for suspicious requests\ncat \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Fweb\u002Faccess.log* | \\\n   grep -iE '(union.*select|\u003Cscript|\\.\\.\\\u002F|cmd\\.exe|\u002Fetc\u002Fpasswd)' \\\n   > \u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Fweb_attacks.txt\n\n# Extract unique IP addresses from web logs\nawk '{print $1}' \u002Fcases\u002Fcase-2024-001\u002Flogs\u002Fweb\u002Faccess.log* | \\\n   sort | uniq -c | sort -rn > \u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Fweb_ips.txt\n```\n\n### Step 4: Correlate Events Across Sources\n\n```bash\n# Normalize timestamps and merge log sources\npython3 \u003C\u003C 'PYEOF'\nimport csv\nimport datetime\nfrom collections import defaultdict\n\nevents = []\n\n# Parse Windows Security events (pre-exported to CSV)\nwith open('\u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Fwindows_events.csv') as f:\n    reader = csv.DictReader(f)\n    for row in reader:\n        events.append({\n            'timestamp': row['TimeCreated'],\n            'source': 'Windows-Security',\n            'event_id': row['EventID'],\n            'description': row['Description'],\n            'details': row.get('Details', '')\n        })\n\n# Parse Linux auth events\nwith open('\u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Fauth_events.txt') as f:\n    for line in f:\n        parts = line.strip().split()\n        if len(parts) >= 6:\n            events.append({\n                'timestamp': ' '.join(parts[:3]),\n                'source': 'Linux-Auth',\n                'event_id': parts[4].rstrip(':'),\n                'description': ' '.join(parts[5:]),\n                'details': ''\n            })\n\n# Sort by timestamp\nevents.sort(key=lambda x: x['timestamp'])\n\n# Write correlated timeline\nwith open('\u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Fcorrelated_timeline.csv', 'w', newline='') as f:\n    writer = csv.DictWriter(f, fieldnames=['timestamp', 'source', 'event_id', 'description', 'details'])\n    writer.writeheader()\n    writer.writerows(events)\n\nprint(f\"Total correlated events: {len(events)}\")\nPYEOF\n\n# Quick correlation: find events within time windows\n# Look for lateral movement patterns\ngrep \"4648\\|4624.*Type.*3\\|4624.*Type.*10\" \u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Fwindows_events.csv | \\\n   sort > \u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Flateral_movement.txt\n```\n\n### Step 5: Generate Forensic Timeline Report\n\n```bash\n# Create structured investigation report\ncat \u003C\u003C 'REPORT' > \u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Flog_analysis_report.txt\nLOG ANALYSIS FORENSIC REPORT\n=============================\nCase: 2024-001\nAnalyst: [Examiner Name]\nDate: $(date -u)\n\nLOG SOURCES ANALYZED:\n- Windows Security Event Log (Security.evtx) - 245,678 events\n- Windows System Event Log (System.evtx) - 45,234 events\n- Windows PowerShell Operational - 12,456 events\n- Linux auth.log - 34,567 entries\n- Apache access.log - 567,890 entries\n- Linux audit.log - 89,012 entries\n\nKEY FINDINGS:\n1. Initial Access: [timestamp] - Successful RDP login from external IP\n2. Privilege Escalation: [timestamp] - New admin account created\n3. Lateral Movement: [timestamp] - Pass-the-hash detected across 3 systems\n4. Data Exfiltration: [timestamp] - Large data transfer to external IP\n5. Log Tampering: [timestamp] - Security event log cleared (Event 1102)\n\nTIMELINE OF EVENTS:\n[See correlated_timeline.csv for complete chronology]\nREPORT\n\n# Package analysis artifacts\ntar -czf \u002Fcases\u002Fcase-2024-001\u002Flog_analysis_package.tar.gz \\\n   \u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002F\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| Event correlation | Linking related events across multiple log sources by time, IP, user, or session |\n| Log normalization | Converting diverse log formats into a common schema for unified analysis |\n| Timeline analysis | Chronological ordering of events to reconstruct incident sequence |\n| Log integrity | Verifying logs have not been tampered with using hashes and chain of custody |\n| Logon types | Windows categorization of authentication methods (2=interactive, 3=network, 10=RDP) |\n| Audit policy | System configuration determining which events are recorded in logs |\n| Log rotation | Automatic archiving of log files that affects evidence availability |\n| Anti-forensics | Attacker techniques for clearing or modifying logs to cover tracks |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| python-evtx | Python library for parsing Windows EVTX event log files |\n| evtxexport | Command-line EVTX export utility from libevtx |\n| LogParser | Microsoft SQL-like query engine for Windows logs |\n| ausearch | Linux audit log search utility |\n| jq | JSON query tool for parsing structured log formats |\n| ELK Stack | Elasticsearch, Logstash, Kibana for log aggregation and visualization |\n| Chainsaw | Sigma-based Windows Event Log analysis tool |\n| Hayabusa | Fast Windows Event Log forensic timeline generator |\n\n## Common Scenarios\n\n**Scenario 1: Brute Force Attack Detection**\nFilter Security.evtx for Event ID 4625 (failed logons), group by source IP and target account, identify patterns of rapid successive failures, find the successful logon (4624) that followed, trace subsequent activity from the compromised account.\n\n**Scenario 2: Insider Threat Investigation**\nCollect all log sources from the suspect's workstation and accessed servers, correlate file access events with authentication events, build timeline of data access during non-business hours, identify data transfers to external media or cloud storage.\n\n**Scenario 3: Web Application Compromise**\nParse web server access logs for SQLi, XSS, and path traversal patterns, identify the attack IP and timeline, correlate with application logs for successful exploitation, trace post-exploitation activity through system and auth logs.\n\n**Scenario 4: Ransomware Incident Timeline**\nIdentify the initial execution through process creation events (4688), trace privilege escalation through service installation (4697), map lateral movement via network logons (4624 Type 3), identify encryption start from file system activity, find the earliest IoC for remediation scoping.\n\n## Output Format\n\n```\nLog Analysis Summary:\n  Investigation Period: 2024-01-15 00:00 to 2024-01-20 23:59 UTC\n  Total Events Analyzed: 894,567\n  Log Sources: 6 (3 Windows, 3 Linux)\n\n  Critical Events:\n    Failed Logons:       1,234 (from 5 unique IPs)\n    Successful Logons:   456 (3 anomalous)\n    Account Changes:     12 (1 unauthorized admin creation)\n    Process Creations:   8,234 (15 suspicious)\n    Log Clearings:       2 (Security log cleared at 2024-01-18 03:00 UTC)\n    Service Installs:    3 (1 unknown service)\n\n  Attack Timeline:\n    2024-01-15 14:32 - Initial access via RDP brute force\n    2024-01-15 14:45 - Admin account \"svcbackup\" created\n    2024-01-16 02:15 - Lateral movement to 3 servers\n    2024-01-17 03:00 - Data staging in C:\\ProgramData\\temp\\\n    2024-01-18 01:30 - 4.2 GB exfiltrated to 185.x.x.x\n    2024-01-18 03:00 - Security logs cleared\n\n  Report: \u002Fcases\u002Fcase-2024-001\u002Fanalysis\u002Flog_analysis_report.txt\n```\n",{"name":5,"note":25,"tags":26,"author":33,"domain":34,"source":35,"license":15,"version":36,"nist_csf":37,"subdomain":42,"description":7,"mitre_attack":43,"source_commit":49},"Vendored verbatim from an external Apache-2.0 security-skill library, pinned by commit. Exceeds the internal 300-line skill guideline (agent-code-constraints.md) -- kept as-is because this is vendored reference material (forensics\u002Fthreat-intel procedure), not Yana AI-authored content, and trimming would damage technical accuracy.",[27,28,29,30,31,32],"forensics","log-analysis","siem","event-correlation","timeline-analysis","evidence-collection","mahipal","cybersecurity","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","1.0",[38,39,40,41],"RS.AN-01","RS.AN-03","DE.AE-02","RS.MA-01","digital-forensics",[44,45,46,47,48],"T1005","T1074","T1119","T1070","T1685.002","04450304b12645cb2b974ab96d28c0664758a88d","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa",".claude\u002Fskills\u002Fperforming-log-analysis-for-forensic-investigation",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill performing-log-analysis-for-forensic-investigation",{"tool":66,"command":67},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill performing-log-analysis-for-forensic-investigation",{"tool":69,"command":70},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill performing-log-analysis-for-forensic-investigation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fperforming-log-analysis-for-forensic-investigation\u002FSKILL.md",true,[74,78,84],{"path":75,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fapi-reference.md","REFERENCE","参考文档",1861,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fperforming-log-analysis-for-forensic-investigation\u002Freferences\u002Fapi-reference.md",{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"scripts\u002Fagent.py","SCRIPT","脚本",8548,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fperforming-log-analysis-for-forensic-investigation\u002Fscripts\u002Fagent.py",[91,99,106,114,122,130],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":20},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":20},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":20},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":20},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":20},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":20},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]