What problem does it solve?
Reconstructing what actually happened in a packet capture is error-prone: Zeek silently discards packets with invalid TCP checksums (common in captures from NICs with checksum offloading), producing missing protocol logs and wrong connection tables that look like real findings. This Skill provides a disciplined, read-only workflow for listing sessions, filtering by service, and following a connection uid across dns/http/ssl logs while always accounting for checksum posture.
Core Features & Use Cases
- Session Reconstruction: Run nsm_analyze and nsm_sessions to enumerate connections, services, conn_state, and byte counts from a .pcap/.pcapng file.
- Cross-Protocol Pivoting: Follow a connection uid from conn.log into dns, http, ssl, and weird logs for exact, non-heuristic correlation.
- Checksum Posture Awareness: Every response carries zeek_posture (IGNORING_CHECKSUMS, PACKETS_DISCARDED, VALIDATING) so conclusions about absent traffic are honest.
- Use Case: Given a Suricata alert from nsm-ids-triage, match its IP pair and port to a connection uid, pull the http log for that uid, and report the alert with full session context including duration, bytes, and conn_state.
Quick Start
Analyze the capture file incident.pcap, list its sessions, and follow the suspicious connection's uid into the http and dns logs.