[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D76HX4WRTRZ8VXYD4JDGSV":3,"skill-same:01M7D76HX4WRTRZ8VXYD4JDGSV":103},{"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":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M7D76HX4WRTRZ8VXYD4JDGSV","collecting-volatile-evidence-from-compromised-host",null,"Collect volatile forensic evidence from a compromised host by following the order of volatility, preserving memory, network connections, running processes, and system state with documented chain of custody before they are lost. Use before isolating, shutting down, or remediating a compromised host, especially when fileless or memory-resident malware is suspected, root cause analysis is needed, or the evidence must hold up in legal proceedings.","SaiVatsal\u002FSkills-I-Use","SaiVatsal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F242597752?v=4","01M7D5YM1T4VXW9203M0GFAHZ1","SaiVatsalPolimera","01M7D5YM2D61ST39XVR2V7B7ZJ",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fcollecting-volatile-evidence-from-compromised-host\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fcollecting-volatile-evidence-from-compromised-host\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: collecting-volatile-evidence-from-compromised-host\ndescription: Collect volatile forensic evidence from a compromised host by following the order of volatility, preserving memory, network connections, running processes, and system state with documented chain of custody before they are lost. Use before isolating, shutting down, or remediating a compromised host, especially when fileless or memory-resident malware is suspected, root cause analysis is needed, or the evidence must hold up in legal proceedings.\ndomain: cybersecurity\nsubdomain: incident-response\ntags:\n- incident-response\n- dfir\n- forensics\n- volatile-evidence\n- memory-forensics\n- chain-of-custody\nmitre_attack:\n- T1059.001\n- T1057\n- T1049\n- T1003.001\n- T1543.003\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- RS.MA-01\n- RS.MA-02\n- RS.AN-03\n- RC.RP-01\n---\n\n# Collecting Volatile Evidence from Compromised Hosts\n\n## When to Use\n- Security incident confirmed and compromised host identified\n- Before system isolation, shutdown, or remediation begins\n- Memory-resident malware suspected (fileless attacks)\n- Need to capture network connections, running processes, and system state\n- Legal proceedings may require forensic evidence preservation\n- Incident requires root cause analysis with volatile data\n\n## Prerequisites\n- Forensic collection toolkit on USB or network share (trusted tools)\n- WinPmem\u002FLiME for memory acquisition\n- Write-blocker or forensic workstation for disk imaging\n- Chain of custody documentation forms\n- Secure evidence storage with integrity verification\n- Authorization to collect evidence (legal\u002FHR approval for insider cases)\n\n## Workflow\n\n### Step 1: Prepare Collection Environment\n```bash\n# Mount forensic USB toolkit (do NOT install tools on compromised system)\n# Verify toolkit integrity\nsha256sum \u002Fmnt\u002Fforensic_usb\u002Ftools\u002F* > \u002Ftmp\u002Ftoolkit_hashes.txt\ndiff \u002Fmnt\u002Fforensic_usb\u002Ftools\u002Fknown_good_hashes.txt \u002Ftmp\u002Ftoolkit_hashes.txt\n\n# Create evidence output directory with timestamps\nEVIDENCE_DIR=\"\u002Fmnt\u002Fevidence\u002F$(hostname)_$(date +%Y%m%d_%H%M%S)\"\nmkdir -p \"$EVIDENCE_DIR\"\necho \"Collection started: $(date -u)\" > \"$EVIDENCE_DIR\u002Fcollection_log.txt\"\necho \"Collector: $(whoami)\" >> \"$EVIDENCE_DIR\u002Fcollection_log.txt\"\necho \"System: $(hostname)\" >> \"$EVIDENCE_DIR\u002Fcollection_log.txt\"\n```\n\n### Step 2: Capture System Memory (Highest Volatility)\n```bash\n# Windows - WinPmem memory acquisition\nwinpmem_mini_x64.exe \"$EVIDENCE_DIR\\memdump_$(hostname).raw\"\n\n# Linux - LiME kernel module for memory acquisition\ninsmod \u002Fmnt\u002Fforensic_usb\u002Flime.ko \"path=$EVIDENCE_DIR\u002Fmemdump_$(hostname).lime format=lime\"\n\n# Linux - Alternative using \u002Fproc\u002Fkcore\ndd if=\u002Fproc\u002Fkcore of=\"$EVIDENCE_DIR\u002Fkcore_dump.raw\" bs=1M\n\n# macOS - osxpmem\nosxpmem -o \"$EVIDENCE_DIR\u002Fmemdump_$(hostname).aff4\"\n\n# Hash the memory dump immediately\nsha256sum \"$EVIDENCE_DIR\u002Fmemdump_\"* > \"$EVIDENCE_DIR\u002Fmemory_hash.sha256\"\n```\n\n### Step 3: Capture Network State\n```bash\n# Active network connections\n# Windows\nnetstat -anob > \"$EVIDENCE_DIR\u002Fnetstat_connections.txt\" 2>&1\nGet-NetTCPConnection | Export-Csv \"$EVIDENCE_DIR\u002Ftcp_connections.csv\" -NoTypeInformation\nGet-NetUDPEndpoint | Export-Csv \"$EVIDENCE_DIR\u002Fudp_endpoints.csv\" -NoTypeInformation\n\n# Linux\nss -tulnp > \"$EVIDENCE_DIR\u002Fsocket_stats.txt\"\nnetstat -anp > \"$EVIDENCE_DIR\u002Fnetstat_all.txt\" 2>\u002Fdev\u002Fnull\ncat \u002Fproc\u002Fnet\u002Ftcp > \"$EVIDENCE_DIR\u002Fproc_net_tcp.txt\"\ncat \u002Fproc\u002Fnet\u002Fudp > \"$EVIDENCE_DIR\u002Fproc_net_udp.txt\"\n\n# ARP cache\narp -a > \"$EVIDENCE_DIR\u002Farp_cache.txt\"\n\n# Routing table\nroute print > \"$EVIDENCE_DIR\u002Frouting_table.txt\"  # Windows\nip route show > \"$EVIDENCE_DIR\u002Frouting_table.txt\"  # Linux\n\n# DNS cache\nipconfig \u002Fdisplaydns > \"$EVIDENCE_DIR\u002Fdns_cache.txt\"  # Windows\n# Linux: varies by resolver, check systemd-resolve or nscd\nsystemd-resolve --statistics > \"$EVIDENCE_DIR\u002Fdns_stats.txt\" 2>\u002Fdev\u002Fnull\n\n# Active firewall rules\nnetsh advfirewall show allprofiles > \"$EVIDENCE_DIR\u002Ffirewall_rules.txt\"  # Windows\niptables -L -n -v > \"$EVIDENCE_DIR\u002Fiptables_rules.txt\"  # Linux\n```\n\n### Step 4: Capture Running Processes\n```bash\n# Windows - Detailed process list\ntasklist \u002FV \u002FFO CSV > \"$EVIDENCE_DIR\u002Fprocess_list_verbose.csv\"\nwmic process list full > \"$EVIDENCE_DIR\u002Fwmic_process_full.txt\"\nGet-Process | Select-Object Id,ProcessName,Path,StartTime,CPU,WorkingSet |\n  Export-Csv \"$EVIDENCE_DIR\u002Fps_processes.csv\" -NoTypeInformation\n\n# Windows - Process with command line and parent\nwmic process get ProcessId,Name,CommandLine,ParentProcessId,ExecutablePath \u002FFORMAT:CSV > \\\n  \"$EVIDENCE_DIR\u002Fprocess_commandlines.csv\"\n\n# Linux - Full process tree\nps auxwwf > \"$EVIDENCE_DIR\u002Fprocess_tree.txt\"\nps -eo pid,ppid,user,args --forest > \"$EVIDENCE_DIR\u002Fprocess_forest.txt\"\ncat \u002Fproc\u002F*\u002Fcmdline 2>\u002Fdev\u002Fnull | tr '\\0' ' ' > \"$EVIDENCE_DIR\u002Fproc_cmdline_all.txt\"\n\n# Process modules\u002FDLLs loaded\n# Windows\nlistdlls.exe -accepteula > \"$EVIDENCE_DIR\u002Floaded_dlls.txt\"\n# Linux\nfor pid in $(ls \u002Fproc\u002F | grep -E '^[0-9]+$'); do\n  echo \"=== PID $pid ===\" >> \"$EVIDENCE_DIR\u002Fproc_maps.txt\"\n  cat \"\u002Fproc\u002F$pid\u002Fmaps\" 2>\u002Fdev\u002Fnull >> \"$EVIDENCE_DIR\u002Fproc_maps.txt\"\ndone\n\n# Open file handles\nhandle.exe -accepteula > \"$EVIDENCE_DIR\u002Fopen_handles.txt\"  # Windows (Sysinternals)\nlsof > \"$EVIDENCE_DIR\u002Fopen_files.txt\"  # Linux\n```\n\n### Step 5: Capture Logged-in Users and Sessions\n```bash\n# Windows\nquery user > \"$EVIDENCE_DIR\u002Flogged_in_users.txt\"\nquery session > \"$EVIDENCE_DIR\u002Factive_sessions.txt\"\nnet session > \"$EVIDENCE_DIR\u002Fnet_sessions.txt\" 2>&1\nnet use > \"$EVIDENCE_DIR\u002Fmapped_drives.txt\" 2>&1\n\n# Linux\nwho > \"$EVIDENCE_DIR\u002Fwho_output.txt\"\nw > \"$EVIDENCE_DIR\u002Fw_output.txt\"\nlast -50 > \"$EVIDENCE_DIR\u002Flast_logins.txt\"\nlastlog > \"$EVIDENCE_DIR\u002Flastlog.txt\"\ncat \u002Fvar\u002Flog\u002Fauth.log | tail -200 > \"$EVIDENCE_DIR\u002Frecent_auth.txt\" 2>\u002Fdev\u002Fnull\n```\n\n### Step 6: Capture System Configuration State\n```bash\n# System time (critical for timeline)\ndate -u > \"$EVIDENCE_DIR\u002Fsystem_time_utc.txt\"\nw32tm \u002Fquery \u002Fstatus > \"$EVIDENCE_DIR\u002Fntp_status.txt\"  # Windows\nntpq -p > \"$EVIDENCE_DIR\u002Fntp_status.txt\"  # Linux\n\n# Environment variables\nset > \"$EVIDENCE_DIR\u002Fenvironment_vars.txt\"  # Windows\nenv > \"$EVIDENCE_DIR\u002Fenvironment_vars.txt\"  # Linux\n\n# Scheduled tasks \u002F Cron jobs\nschtasks \u002Fquery \u002Ffo CSV \u002Fv > \"$EVIDENCE_DIR\u002Fscheduled_tasks.csv\"  # Windows\ncrontab -l > \"$EVIDENCE_DIR\u002Fcrontab_current.txt\" 2>\u002Fdev\u002Fnull  # Linux\nls -la \u002Fetc\u002Fcron.* > \"$EVIDENCE_DIR\u002Fcron_dirs.txt\" 2>\u002Fdev\u002Fnull\n\n# Services\nsc queryex type=service state=all > \"$EVIDENCE_DIR\u002Fservices_all.txt\"  # Windows\nsystemctl list-units --type=service --all > \"$EVIDENCE_DIR\u002Fsystemd_services.txt\"  # Linux\n\n# Windows Registry - key autostart locations\nreg export \"HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Run\" \"$EVIDENCE_DIR\u002Freg_run_hklm.reg\" \u002Fy\nreg export \"HKCU\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Run\" \"$EVIDENCE_DIR\u002Freg_run_hkcu.reg\" \u002Fy\nreg export \"HKLM\\SYSTEM\\CurrentControlSet\\Services\" \"$EVIDENCE_DIR\u002Freg_services.reg\" \u002Fy\n```\n\n### Step 7: Hash All Evidence and Document Chain of Custody\n```bash\n# Generate SHA256 hashes for all collected evidence\ncd \"$EVIDENCE_DIR\"\nsha256sum * > evidence_manifest.sha256\n\n# Create chain of custody record\ncat > \"$EVIDENCE_DIR\u002Fchain_of_custody.txt\" \u003C\u003C EOF\nCHAIN OF CUSTODY RECORD\n========================\nCase ID: IR-YYYY-NNN\nCollection Date: $(date -u)\nCollected By: $(whoami)\nSystem: $(hostname)\nSystem IP: $(hostname -I 2>\u002Fdev\u002Fnull || ipconfig | grep IPv4)\nCollection Method: Live forensic collection via trusted USB toolkit\n\nEvidence Items:\n$(ls -la \"$EVIDENCE_DIR\u002F\" | grep -v chain_of_custody)\n\nSHA256 Manifest: evidence_manifest.sha256\nTransfer: [TO BE COMPLETED]\nStorage Location: [TO BE COMPLETED]\nEOF\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| Order of Volatility | RFC 3227 - Collect most volatile data first: registers > cache > memory > disk |\n| Live Forensics | Collecting evidence from a running system before shutdown |\n| Chain of Custody | Documentation tracking evidence handling from collection to court |\n| Forensic Soundness | Ensuring evidence collection doesn't alter the original evidence |\n| Trusted Tools | Using verified tools from external media, not from the compromised system |\n| Evidence Integrity | SHA256 hashing of all evidence immediately after collection |\n| Locard's Exchange Principle | Every contact leaves a trace - minimize investigator artifacts |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| WinPmem | Windows memory acquisition |\n| LiME (Linux Memory Extractor) | Linux kernel memory acquisition |\n| Sysinternals Suite | Process, handle, and DLL analysis (Windows) |\n| Velociraptor | Remote forensic collection at scale |\n| KAPE (Kroll Artifact Parser) | Automated artifact collection on Windows |\n| CyLR | Cross-platform live response collection |\n| GRR Rapid Response | Remote live forensics framework |\n\n## Common Scenarios\n\n1. **Fileless Malware Attack**: PowerShell-based attack with no files on disk. Memory dump is critical evidence containing the malicious scripts.\n2. **Active C2 Session**: Attacker has live connection. Network connections and process data reveal C2 infrastructure.\n3. **Insider Data Theft**: Employee copying files. Process list, mapped drives, and network connections show exfiltration activity.\n4. **Compromised Web Server**: Web shell detected. Memory may contain additional backdoors not yet written to disk.\n5. **Lateral Movement in Progress**: Attacker moving between systems. Authentication tokens and network sessions in memory reveal scope.\n\n## Output Format\n- Memory dump file (.raw or .lime format) with SHA256 hash\n- Network state captures (connections, ARP, DNS, routes)\n- Process listings with command lines and parent processes\n- User session and authentication data\n- System configuration snapshots\n- Evidence manifest with SHA256 checksums\n- Chain of custody documentation\n","# Collecting Volatile Evidence from Compromised Hosts\n\n## When to Use\n- Security incident confirmed and compromised host identified\n- Before system isolation, shutdown, or remediation begins\n- Memory-resident malware suspected (fileless attacks)\n- Need to capture network connections, running processes, and system state\n- Legal proceedings may require forensic evidence preservation\n- Incident requires root cause analysis with volatile data\n\n## Prerequisites\n- Forensic collection toolkit on USB or network share (trusted tools)\n- WinPmem\u002FLiME for memory acquisition\n- Write-blocker or forensic workstation for disk imaging\n- Chain of custody documentation forms\n- Secure evidence storage with integrity verification\n- Authorization to collect evidence (legal\u002FHR approval for insider cases)\n\n## Workflow\n\n### Step 1: Prepare Collection Environment\n```bash\n# Mount forensic USB toolkit (do NOT install tools on compromised system)\n# Verify toolkit integrity\nsha256sum \u002Fmnt\u002Fforensic_usb\u002Ftools\u002F* > \u002Ftmp\u002Ftoolkit_hashes.txt\ndiff \u002Fmnt\u002Fforensic_usb\u002Ftools\u002Fknown_good_hashes.txt \u002Ftmp\u002Ftoolkit_hashes.txt\n\n# Create evidence output directory with timestamps\nEVIDENCE_DIR=\"\u002Fmnt\u002Fevidence\u002F$(hostname)_$(date +%Y%m%d_%H%M%S)\"\nmkdir -p \"$EVIDENCE_DIR\"\necho \"Collection started: $(date -u)\" > \"$EVIDENCE_DIR\u002Fcollection_log.txt\"\necho \"Collector: $(whoami)\" >> \"$EVIDENCE_DIR\u002Fcollection_log.txt\"\necho \"System: $(hostname)\" >> \"$EVIDENCE_DIR\u002Fcollection_log.txt\"\n```\n\n### Step 2: Capture System Memory (Highest Volatility)\n```bash\n# Windows - WinPmem memory acquisition\nwinpmem_mini_x64.exe \"$EVIDENCE_DIR\\memdump_$(hostname).raw\"\n\n# Linux - LiME kernel module for memory acquisition\ninsmod \u002Fmnt\u002Fforensic_usb\u002Flime.ko \"path=$EVIDENCE_DIR\u002Fmemdump_$(hostname).lime format=lime\"\n\n# Linux - Alternative using \u002Fproc\u002Fkcore\ndd if=\u002Fproc\u002Fkcore of=\"$EVIDENCE_DIR\u002Fkcore_dump.raw\" bs=1M\n\n# macOS - osxpmem\nosxpmem -o \"$EVIDENCE_DIR\u002Fmemdump_$(hostname).aff4\"\n\n# Hash the memory dump immediately\nsha256sum \"$EVIDENCE_DIR\u002Fmemdump_\"* > \"$EVIDENCE_DIR\u002Fmemory_hash.sha256\"\n```\n\n### Step 3: Capture Network State\n```bash\n# Active network connections\n# Windows\nnetstat -anob > \"$EVIDENCE_DIR\u002Fnetstat_connections.txt\" 2>&1\nGet-NetTCPConnection | Export-Csv \"$EVIDENCE_DIR\u002Ftcp_connections.csv\" -NoTypeInformation\nGet-NetUDPEndpoint | Export-Csv \"$EVIDENCE_DIR\u002Fudp_endpoints.csv\" -NoTypeInformation\n\n# Linux\nss -tulnp > \"$EVIDENCE_DIR\u002Fsocket_stats.txt\"\nnetstat -anp > \"$EVIDENCE_DIR\u002Fnetstat_all.txt\" 2>\u002Fdev\u002Fnull\ncat \u002Fproc\u002Fnet\u002Ftcp > \"$EVIDENCE_DIR\u002Fproc_net_tcp.txt\"\ncat \u002Fproc\u002Fnet\u002Fudp > \"$EVIDENCE_DIR\u002Fproc_net_udp.txt\"\n\n# ARP cache\narp -a > \"$EVIDENCE_DIR\u002Farp_cache.txt\"\n\n# Routing table\nroute print > \"$EVIDENCE_DIR\u002Frouting_table.txt\"  # Windows\nip route show > \"$EVIDENCE_DIR\u002Frouting_table.txt\"  # Linux\n\n# DNS cache\nipconfig \u002Fdisplaydns > \"$EVIDENCE_DIR\u002Fdns_cache.txt\"  # Windows\n# Linux: varies by resolver, check systemd-resolve or nscd\nsystemd-resolve --statistics > \"$EVIDENCE_DIR\u002Fdns_stats.txt\" 2>\u002Fdev\u002Fnull\n\n# Active firewall rules\nnetsh advfirewall show allprofiles > \"$EVIDENCE_DIR\u002Ffirewall_rules.txt\"  # Windows\niptables -L -n -v > \"$EVIDENCE_DIR\u002Fiptables_rules.txt\"  # Linux\n```\n\n### Step 4: Capture Running Processes\n```bash\n# Windows - Detailed process list\ntasklist \u002FV \u002FFO CSV > \"$EVIDENCE_DIR\u002Fprocess_list_verbose.csv\"\nwmic process list full > \"$EVIDENCE_DIR\u002Fwmic_process_full.txt\"\nGet-Process | Select-Object Id,ProcessName,Path,StartTime,CPU,WorkingSet |\n  Export-Csv \"$EVIDENCE_DIR\u002Fps_processes.csv\" -NoTypeInformation\n\n# Windows - Process with command line and parent\nwmic process get ProcessId,Name,CommandLine,ParentProcessId,ExecutablePath \u002FFORMAT:CSV > \\\n  \"$EVIDENCE_DIR\u002Fprocess_commandlines.csv\"\n\n# Linux - Full process tree\nps auxwwf > \"$EVIDENCE_DIR\u002Fprocess_tree.txt\"\nps -eo pid,ppid,user,args --forest > \"$EVIDENCE_DIR\u002Fprocess_forest.txt\"\ncat \u002Fproc\u002F*\u002Fcmdline 2>\u002Fdev\u002Fnull | tr '\\0' ' ' > \"$EVIDENCE_DIR\u002Fproc_cmdline_all.txt\"\n\n# Process modules\u002FDLLs loaded\n# Windows\nlistdlls.exe -accepteula > \"$EVIDENCE_DIR\u002Floaded_dlls.txt\"\n# Linux\nfor pid in $(ls \u002Fproc\u002F | grep -E '^[0-9]+$'); do\n  echo \"=== PID $pid ===\" >> \"$EVIDENCE_DIR\u002Fproc_maps.txt\"\n  cat \"\u002Fproc\u002F$pid\u002Fmaps\" 2>\u002Fdev\u002Fnull >> \"$EVIDENCE_DIR\u002Fproc_maps.txt\"\ndone\n\n# Open file handles\nhandle.exe -accepteula > \"$EVIDENCE_DIR\u002Fopen_handles.txt\"  # Windows (Sysinternals)\nlsof > \"$EVIDENCE_DIR\u002Fopen_files.txt\"  # Linux\n```\n\n### Step 5: Capture Logged-in Users and Sessions\n```bash\n# Windows\nquery user > \"$EVIDENCE_DIR\u002Flogged_in_users.txt\"\nquery session > \"$EVIDENCE_DIR\u002Factive_sessions.txt\"\nnet session > \"$EVIDENCE_DIR\u002Fnet_sessions.txt\" 2>&1\nnet use > \"$EVIDENCE_DIR\u002Fmapped_drives.txt\" 2>&1\n\n# Linux\nwho > \"$EVIDENCE_DIR\u002Fwho_output.txt\"\nw > \"$EVIDENCE_DIR\u002Fw_output.txt\"\nlast -50 > \"$EVIDENCE_DIR\u002Flast_logins.txt\"\nlastlog > \"$EVIDENCE_DIR\u002Flastlog.txt\"\ncat \u002Fvar\u002Flog\u002Fauth.log | tail -200 > \"$EVIDENCE_DIR\u002Frecent_auth.txt\" 2>\u002Fdev\u002Fnull\n```\n\n### Step 6: Capture System Configuration State\n```bash\n# System time (critical for timeline)\ndate -u > \"$EVIDENCE_DIR\u002Fsystem_time_utc.txt\"\nw32tm \u002Fquery \u002Fstatus > \"$EVIDENCE_DIR\u002Fntp_status.txt\"  # Windows\nntpq -p > \"$EVIDENCE_DIR\u002Fntp_status.txt\"  # Linux\n\n# Environment variables\nset > \"$EVIDENCE_DIR\u002Fenvironment_vars.txt\"  # Windows\nenv > \"$EVIDENCE_DIR\u002Fenvironment_vars.txt\"  # Linux\n\n# Scheduled tasks \u002F Cron jobs\nschtasks \u002Fquery \u002Ffo CSV \u002Fv > \"$EVIDENCE_DIR\u002Fscheduled_tasks.csv\"  # Windows\ncrontab -l > \"$EVIDENCE_DIR\u002Fcrontab_current.txt\" 2>\u002Fdev\u002Fnull  # Linux\nls -la \u002Fetc\u002Fcron.* > \"$EVIDENCE_DIR\u002Fcron_dirs.txt\" 2>\u002Fdev\u002Fnull\n\n# Services\nsc queryex type=service state=all > \"$EVIDENCE_DIR\u002Fservices_all.txt\"  # Windows\nsystemctl list-units --type=service --all > \"$EVIDENCE_DIR\u002Fsystemd_services.txt\"  # Linux\n\n# Windows Registry - key autostart locations\nreg export \"HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Run\" \"$EVIDENCE_DIR\u002Freg_run_hklm.reg\" \u002Fy\nreg export \"HKCU\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Run\" \"$EVIDENCE_DIR\u002Freg_run_hkcu.reg\" \u002Fy\nreg export \"HKLM\\SYSTEM\\CurrentControlSet\\Services\" \"$EVIDENCE_DIR\u002Freg_services.reg\" \u002Fy\n```\n\n### Step 7: Hash All Evidence and Document Chain of Custody\n```bash\n# Generate SHA256 hashes for all collected evidence\ncd \"$EVIDENCE_DIR\"\nsha256sum * > evidence_manifest.sha256\n\n# Create chain of custody record\ncat > \"$EVIDENCE_DIR\u002Fchain_of_custody.txt\" \u003C\u003C EOF\nCHAIN OF CUSTODY RECORD\n========================\nCase ID: IR-YYYY-NNN\nCollection Date: $(date -u)\nCollected By: $(whoami)\nSystem: $(hostname)\nSystem IP: $(hostname -I 2>\u002Fdev\u002Fnull || ipconfig | grep IPv4)\nCollection Method: Live forensic collection via trusted USB toolkit\n\nEvidence Items:\n$(ls -la \"$EVIDENCE_DIR\u002F\" | grep -v chain_of_custody)\n\nSHA256 Manifest: evidence_manifest.sha256\nTransfer: [TO BE COMPLETED]\nStorage Location: [TO BE COMPLETED]\nEOF\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| Order of Volatility | RFC 3227 - Collect most volatile data first: registers > cache > memory > disk |\n| Live Forensics | Collecting evidence from a running system before shutdown |\n| Chain of Custody | Documentation tracking evidence handling from collection to court |\n| Forensic Soundness | Ensuring evidence collection doesn't alter the original evidence |\n| Trusted Tools | Using verified tools from external media, not from the compromised system |\n| Evidence Integrity | SHA256 hashing of all evidence immediately after collection |\n| Locard's Exchange Principle | Every contact leaves a trace - minimize investigator artifacts |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| WinPmem | Windows memory acquisition |\n| LiME (Linux Memory Extractor) | Linux kernel memory acquisition |\n| Sysinternals Suite | Process, handle, and DLL analysis (Windows) |\n| Velociraptor | Remote forensic collection at scale |\n| KAPE (Kroll Artifact Parser) | Automated artifact collection on Windows |\n| CyLR | Cross-platform live response collection |\n| GRR Rapid Response | Remote live forensics framework |\n\n## Common Scenarios\n\n1. **Fileless Malware Attack**: PowerShell-based attack with no files on disk. Memory dump is critical evidence containing the malicious scripts.\n2. **Active C2 Session**: Attacker has live connection. Network connections and process data reveal C2 infrastructure.\n3. **Insider Data Theft**: Employee copying files. Process list, mapped drives, and network connections show exfiltration activity.\n4. **Compromised Web Server**: Web shell detected. Memory may contain additional backdoors not yet written to disk.\n5. **Lateral Movement in Progress**: Attacker moving between systems. Authentication tokens and network sessions in memory reveal scope.\n\n## Output Format\n- Memory dump file (.raw or .lime format) with SHA256 hash\n- Network state captures (connections, ARP, DNS, routes)\n- Process listings with command lines and parent processes\n- User session and authentication data\n- System configuration snapshots\n- Evidence manifest with SHA256 checksums\n- Chain of custody documentation\n",{"name":5,"tags":25,"author":32,"domain":33,"license":15,"version":34,"nist_csf":35,"subdomain":26,"description":7,"mitre_attack":40},[26,27,28,29,30,31],"incident-response","dfir","forensics","volatile-evidence","memory-forensics","chain-of-custody","mahipal","cybersecurity","1.0",[36,37,38,39],"RS.MA-01","RS.MA-02","RS.AN-03","RC.RP-01",[41,42,43,44,45],"T1059.001","T1057","T1049","T1003.001","T1543.003","main","8a3b3de73262a4c4db64523949360f3c599c2fb1","Anthropic-Cybersecurity-Skills-main\u002Fskills\u002Fcollecting-volatile-evidence-from-compromised-host",0,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use","https:\u002F\u002Fgithub.com\u002FSaiVatsal","https:\u002F\u002Fsaivatsal.github.io\u002FPortfolio\u002F","The Longer It Takes The Stronger It Becomes ","2026-09-21 22:45:58",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add SaiVatsal\u002FSkills-I-Use --skill collecting-volatile-evidence-from-compromised-host",{"tool":61,"command":62},"bunx","bunx skills add SaiVatsal\u002FSkills-I-Use --skill collecting-volatile-evidence-from-compromised-host",{"tool":64,"command":65},"pnpm","pnpm dlx skills add SaiVatsal\u002FSkills-I-Use --skill collecting-volatile-evidence-from-compromised-host","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fcollecting-volatile-evidence-from-compromised-host\u002FSKILL.md",true,[69,75,79,85,89,93,99],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"assets\u002Ftemplate.md","ASSET","资产文件",2125,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fcollecting-volatile-evidence-from-compromised-host\u002Fassets\u002Ftemplate.md",{"path":76,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fapi-reference.md","REFERENCE","参考文档",2075,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fcollecting-volatile-evidence-from-compromised-host\u002Freferences\u002Fapi-reference.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fstandards.md",3041,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fcollecting-volatile-evidence-from-compromised-host\u002Freferences\u002Fstandards.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fworkflows.md",4004,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fcollecting-volatile-evidence-from-compromised-host\u002Freferences\u002Fworkflows.md",{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"scripts\u002Fagent.py","SCRIPT","脚本",7167,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fcollecting-volatile-evidence-from-compromised-host\u002Fscripts\u002Fagent.py",{"path":100,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":101,"sourceHtmlUrl":102},"scripts\u002Fprocess.py",17820,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fcollecting-volatile-evidence-from-compromised-host\u002Fscripts\u002Fprocess.py",[104,112,120,129,136,143],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":20},"01M7DJZP6E6KMBQV4CZSDPZEZ8","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":20},"01M7DJZFTS5TS06K2TV3MDTE67","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":124,"licenseFileUrl":125,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":20},"01M7DJRK4SRQ908F2TJM6EZ7EV","ui-styling","Create beautiful, accessible user interfaces with shadcn\u002Fui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.","MIT","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fui-styling\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fui-styling\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":124,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":20},"01M7DJR902059VEQP23PVM2WA0","design","Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social\u002Fads\u002Fweb\u002Fprint), icon design (15 styles, SVG, Gemini 3.1 Pro), social photos (HTML→screenshot, multi-platform). Actions: design logo, create CIP, generate mockups, build slides, design banner, generate icon, create social photos, social media images, brand identity, design system. Platforms: Facebook, Twitter, LinkedIn, YouTube, Instagram, Pinterest, TikTok, Threads, Google Ads.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fdesign\u002FSKILL.md",[],[],{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":124,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":20},"01M7DJR56QF5N6XYTCPCFHFMNP","design-system","Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing\u002Ftypography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fdesign-system\u002FSKILL.md",[],[],{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":124,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":20},"01M7DJQXB6M0SFF7NX8J5N01AH","banner-design","Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with AI-generated visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter\u002FX, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage. Uses ui-ux-pro-max, frontend-design, ai-artist, ai-multimodal skills.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fbanner-design\u002FSKILL.md",[],[]]