For the uninitiated: Zeta IR Pack is an automated collection script/bundle designed for Incident Response (triage, memory, artifacts) on Windows endpoints. It aims to compete with tools like KAPE, CyLR, or Velociraptor’s offline collectors.
✅ Low friction – No installation required; runs from a USB or EDR drop point. ✅ Prioritizes forensic soundness – Uses WinAPI calls instead of raw file copies where possible (less metadata tampering). ✅ Compact output – Compresses into a tidy ZIP with a basic log of actions. ✅ Light on target – Minimal CPU/RAM spike; good for production servers. ✅ Extensible – You can drop in custom YARA rules or artifact definitions. zeta ir pack
I’ve been digging into the lately, and here’s my honest take—where it shines, where it stumbles, and who should actually use it. For the uninitiated: Zeta IR Pack is an
Have you run Zeta in a real incident? How did it compare to KAPE or CyLR for you? ✅ Prioritizes forensic soundness – Uses WinAPI calls
👇 Drop your thoughts below.
❌ No built-in parser – You get raw output; you still need Plaso, Timeline Explorer, or your own parser. ❌ Windows-only – Sorry Linux/OSX IR teams. ❌ Less mature than KAPE – Smaller community, fewer pre-built modules. ❌ No encryption/authentication – The collected ZIP can be intercepted if you’re not careful with exfiltration.