Course contentsShow
← Security
Lesson 2384 of 3,05246. Incident ResponseFree lesson

Network Evidence Collection

Capturing packet traces, flow data, proxy logs, and firewall records during active incidents.

Network Evidence Collection

What you'll learn: How to capture and preserve network traffic and logs during an active security incident to support investigation and potential legal proceedings.


The Core Idea

When a security incident unfolds, critical evidence flows across your network for only fleeting moments. Network evidence collection means capturing this ephemeral data—packet traces, flow records, proxy logs, and firewall entries—before it vanishes or rotates out of retention windows.

Think of it like recording security camera footage during a bank robbery: if you don't hit "record" immediately, the crucial moments are lost forever. Network evidence works the same way, except data moves at gigabits per second and storage fills quickly.

What to Collect

Packet captures (PCAP files) contain full network conversations, including payload data. Tools like tcpdump or Wireshark capture packets at specific interfaces. This is your highest-fidelity evidence but generates massive files.

Flow data (NetFlow, sFlow, IPFIX) provides summarized connection metadata: source/destination IPs, ports, protocols, byte counts, and timestamps. It's lightweight and scalable for long-term storage, perfect for understanding "who talked to whom."

Proxy logs reveal web requests, URLs visited, user agents, and response codes—essential for tracking command-and-control communication or data exfiltration attempts.

Firewall records show allowed and blocked connections, helping you understand attack paths and containment effectiveness.

Collection Best Practices

Capture from multiple vantage points (border routers, core switches, critical segments). Document exactly when collection started, which interfaces were monitored, and any filters applied. Preserve original timestamps—clock synchronization via NTP becomes crucial for correlation. Store copies in write-once formats to maintain chain of custody.

Key Takeaway: Network evidence collection during incidents requires immediate action to capture volatile packet data, flow records, and logs from strategic network points before critical evidence disappears—forming the foundation for forensic analysis and threat actor attribution.