Week 12: Network Forensics

Network Forensics

Investigating network-based evidence for incident response

Ali Jaddoa

Ali.Jaddoa@Roehampton.ac.uk


25/26
Week 12: Network Forensics

Learning Objectives

  • Understand the purpose and methodology of network forensics
  • Identify sources of network-based evidence
  • Reconstruct attack timelines from network captures
  • Extract forensic artefacts from traffic
  • Analyse encrypted traffic for investigative indicators

25/26
Week 12: Network Forensics

01

What is Network Forensics?


25/26
Week 12: Network Forensics

Defining Network Forensics

Network Forensics is the capture, recording, and analysis of network traffic to discover the source of security incidents.

Traffic Analysis

  • Real-time monitoring
  • Performance optimisation
  • Anomaly detection

Network Forensics

  • Post-incident investigation
  • Evidence preservation
  • Attack reconstruction

25/26
Week 12: Network Forensics

What Network Forensics Can Reveal

Finding Details
Source of Incidents Origin IP, geographic location, threat actor infrastructure
Path of Intrusion Entry point, lateral movement, pivot hosts
Techniques Used Exploitation methods, tools, C2 protocols
Data Exfiltration What was stolen, when, how much, where it went
Timeline Precise sequencing of attacker actions

25/26
Week 12: Network Forensics

02

Evidence Sources & Capture Methods


25/26
Week 12: Network Forensics

Sources of Network-Based Evidence

Source Description
Full Packet Capture PCAPs via tcpdump, Wireshark
Flow/Session Data NetFlow, Zeek logs
Log Files Firewall, proxy, IDS logs
Alert Data Snort, Suricata, SIEM events

Multiple converging sources strengthen evidence.


25/26
Week 12: Network Forensics

Gaining Access to Network Traffic

Four primary means to access network data:

  1. Hubs
  2. Test Access Point (TAP)
  3. Other inline devices
  4. Switched Port Analyzer (SPAN port)

25/26
Week 12: Network Forensics

Capturing Traffic: Hub vs Switch

Hub

Traffic sent to ALL ports - sniffer captures everything

center

Switch

Traffic only to destination port - sniffer misses unicast

center

Promiscuous mode: NIC captures all packets, not just those addressed to it


25/26
Week 12: Network Forensics

Capturing Traffic: SPAN Port

SPAN Port (Port Mirroring)

  • Switch copies traffic to designated port
  • Sniffer captures ALL traffic
  • Software configured - easy to change
  • Can drop packets under heavy load
  • Lower priority than production traffic

25/26
Week 12: Network Forensics

Capturing Traffic: Network TAP

Test Access Point (TAP)

  • Hardware device placed inline
  • Creates permanent access port
  • Copies all traffic - no packet loss
  • Sees physical layer errors
  • More expensive, requires physical install

TAPs are preferred for forensic capture - complete, unaltered evidence


25/26
Week 12: Network Forensics

03

Attack Reconstruction


25/26
Week 12: Network Forensics

Mapping Traffic to the Kill Chain

Phase Network Indicators
Reconnaissance DNS queries, port scans, web crawling
Delivery Email attachments, malicious downloads
Exploitation Exploit payloads, shellcode
Installation Malware downloads, dropper activity
Command & Control Beaconing, C2 protocols, DNS tunnelling
Exfiltration Large outbound transfers, encoded data

25/26
Week 12: Network Forensics

Building an Attack Timeline

Time Event
14:23:01 First SYN scan from 203.0.113.50
14:25:17 SMB exploit attempt on port 445
14:25:19 Reverse shell established
14:26:44 Mimikatz download from C2
14:31:02 Lateral movement to 10.0.0.25
14:45:33 Large outbound transfer to 198.51.100.10

25/26
Week 12: Network Forensics

Key Wireshark Filters

Filter Use
tcp.flags.syn==1 && tcp.flags.ack==0 SYN scans
ip.addr == 203.0.113.50 Traffic to/from suspect IP
tcp.port == 4444 Reverse shell port
http.request.method == POST Data submissions
dns.qry.name contains "evil" Suspicious DNS

25/26
Week 12: Network Forensics

04

Artefact Extraction


25/26
Week 12: Network Forensics

What Can Be Extracted

From unencrypted traffic, you can recover:

  • Files - PDFs, images, executables
  • Email Content - Messages, headers, attachments
  • Credentials - HTTP Auth, FTP logins
  • Web Activity - URLs, search queries
  • DNS History - Domains resolved, C2 infrastructure

25/26
Week 12: Network Forensics

Extraction Techniques

Wireshark Export Objects
File → Export Objects → HTTP/SMB/TFTP/IMF

Follow TCP Stream
Right-click packet → Follow → TCP Stream → Save raw data

NetworkMiner
Automated extraction of files, images, credentials

Extracted files may contain malware. Analyse in isolation.


25/26
Week 12: Network Forensics

Email Reconstruction from SMTP

Steps

  1. Filter: smtp or tcp.port == 25
  2. Follow TCP Stream
  3. View MAIL FROM, RCPT TO, DATA
  4. Decode Base64 attachments

Header Analysis

  • Received: mail path
  • X-Originating-IP: sender's IP
  • Message-ID: unique identifier

25/26
Week 12: Network Forensics

05

Encrypted Traffic Analysis


25/26
Week 12: Network Forensics

The Encryption Challenge

✅ What You CAN See

  • IP addresses
  • Port numbers
  • Packet sizes and timing
  • TLS handshake metadata
  • Server Name Indication (SNI)
  • Certificate details

❌ What You CANNOT See

  • HTTP headers
  • URLs (path, parameters)
  • POST data
  • File contents
  • Credentials

25/26
Week 12: Network Forensics

TLS Fingerprinting: JA3

Every TLS client has a fingerprint based on how it negotiates the connection.

JA3 = MD5 hash of: TLS version, cipher suites, extensions, elliptic curves

Example: e7d705a3286e19ea42f587b344ee6865 (Cobalt Strike)

Uses:

  • Identify known malware families
  • Detect C2 frameworks
  • Correlate across captures

25/26
Week 12: Network Forensics

06

Challenges


25/26
Week 12: Network Forensics

Challenges: Anonymity & Attribution

  1. Tor / VPNs | Source IP hidden or masked

25/26
Week 12: Network Forensics

Challenges: Anonymity & Attribution

Challenge Impact
Compromised Infrastructure Attacks routed through third parties
IP Spoofing Source address falsified
Shared IPs Multiple users behind NAT

Attribution is rarely definitive. Focus on IOCs and TTPs.


25/26
Week 12: Network Forensics

Summary

  1. Network forensics reconstructs incidents from traffic evidence
  2. Multiple evidence sources strengthen findings
  3. Map network events to kill chain phases
  4. Extract artefacts from unencrypted traffic
  5. Encrypted traffic still reveals metadata and patterns
  6. Attribution is difficult - focus on indicators

25/26
Week 12: Network Forensics

Labs: Pleaee review you activities from below

  1. Lab 1: Attack Investigation
  2. Lab 2: Email Reconstruction
  3. Lab 3: Exfiltration & Encrypted Traffic

25/26

![bg right:40% w:450](https://upload.wikimedia.org/wikipedia/commons/thumb/a/a2/Wireshark_3.6_screenshot.png/1200px-Wireshark_3.6_screenshot.png)