Study guide
13.6 Network Device & Service Log Forensics: Firewall, IDS, Honeypot, Router, DHCP, Switch, VPN, DNS & SSH
Computer Hacking Forensic Investigator CHFI 312-49
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Foundations of Digital Forensics & Cybercrime Investigation
1.1 Cybercrime Classifications, Forensic Science Principles & Legal Admissibility 1.2 RFC 3227 Order of Volatility, Live vs. Dead Acquisition & Forensic Readiness 1.3 Indicators of Compromise (IoCs), Cyber Attribution & Threat Intelligence 1.4 AI-Assisted Forensics, GitOps, Automation/Orchestration & Forensics-as-a-Service (FaaS)
2 Chapter 2: Modern Forensic Environments & Emerging Threats
2.1 Fileless Malware, In-Memory Execution & Living-off-the-Land (LotL) 2.2 IoT & Operational Technology (OT/SCADA) Forensic Fundamentals 2.3 Dark Web, Tor Network, Onion Routing & Hidden Services Forensics 2.4 Blockchain Transactions, Cryptocurrency Tracing & Digital Asset Investigations
3 Chapter 3: Legal Frameworks, Search Warrants & Evidence Rules
3.1 Federal Rules of Evidence (FRE 702, 901, 902, 1001-1003) & Daubert/Frye Standards 3.2 Fourth Amendment, Warrant Exceptions, Workplace Search & Consent Protocols 3.3 International Standards: ISO/IEC 27037, ACPO Principles & ENFSI Guidelines 3.4 Cybercrime Statutes, Privacy Compliance, CAN-SPAM & International Cooperation
4 Chapter 4: eDiscovery, Chain of Custody & Professional Ethics
4.1 Electronic Discovery Reference Model (EDRM) & Legal Spoliation Holds 4.2 Chain of Custody Documentation, Evidence Packaging & Tamper-Evident Handling 4.3 Expert Witness Testimony, Report Writing Standards & EC-Council Code of Ethics
5 Chapter 5: Storage Architecture, Boot Sequences & Media Forensics
5.1 Storage Media Architecture: Sectors, Clusters, RAM/File Slack & Unallocated Space 5.2 Partition Tables & Boot Structures: MBR, GPT, VBR, BIOS vs. UEFI Secure Boot 5.3 RAID Reconstruction (RAID 0, 1, 5, 6, 10) & SSD Forensic Challenges (TRIM, Wear Leveling)
6 Chapter 6: Windows File Systems: NTFS & FAT
6.1 NTFS Architecture: Master File Table ($MFT) Record Structure & Attribute Headers 6.2 NTFS Artifacts: Alternate Data Streams (ADS), Volume Shadow Copies (VSS) & $LogFile 6.3 FAT12/16/32 and exFAT Architecture, Directory Entries & File Deletion Mechanics
7 Chapter 7: Non-Windows File Systems & File Signatures
7.1 Linux File Systems: ext2/ext3/ext4 Inode Architecture, Superblocks & Journaling Forensics 7.2 macOS File Systems: HFS+ and Apple File System (APFS) Architecture & Snapshots 7.3 File Signatures, Magic Bytes, Hex Headers/Footers & File Carving Techniques
8 Chapter 8: Investigation Lifecycle, Lab Setup & First Response
8.1 Forensic Laboratory Accreditation: ISO/IEC 17025 Standards & Hardware/Software Controls 8.2 First Responder Duties: Crime Scene Containment, Electronic Triage & Volatile Triage 8.3 Physical Evidence Packaging, Anti-Static/Faraday Protection & Transport Security
9 Chapter 9: Forensic Acquisition & Verification Methodology
9.1 Hardware and Software Write-Blockers: Operational Validation & Bridge Verification 9.2 Bit-Stream Disk Imaging, Physical vs. Logical vs. Targeted Acquisition Methodology 9.3 Forensic Image Formats (RAW/DD, E01, AFF) & Cryptographic Hashing Verification (MD5, SHA-256)
10 Chapter 10: Anti-Forensics Techniques & Countermeasures
10.1 Steganography Detection: Spatial/Frequency Domain Steganalysis & Hidden Carrier Extraction 10.2 Timestomping Countermeasures: Comparing $STANDARD_INFORMATION vs $FILE_NAME Timestamps 10.3 Secure Wiping, Degaussing, File Shredding Countermeasures & Residual Artifact Recovery
11 Chapter 11: Windows Operating System Forensics
11.1 Windows Registry Forensics: SYSTEM, SOFTWARE, SAM & NTUSER.DAT Hive Analysis 11.2 Execution Artifacts: Prefetch (.pf), Shimcache (AppCompatCache), Amcache.hve & UserAssist 11.3 User Activity Artifacts: ShellBags, LNK Shortcut Files, Jump Lists & Recycle Bin ($I/$R) 11.4 Windows Event Log Forensics: Security Audit IDs (4624, 4625, 4688, 4720, 7045) & EVTX Parsing
12 Chapter 12: Memory Forensics & Malware Analysis
12.1 Volatile Memory Acquisition: RAM Capture, Crash Dumps, Hiberfil.sys & Pagefile.sys 12.2 Memory Analysis with Volatility 3: pslist, pstree, malfind, netscan & Vadinfo 12.3 Static Malware Triage: Strings, PE Headers, Import Tables, Hashes & YARA Rule Matching 12.4 Dynamic Malware Analysis: Sandboxing, Process Monitor (Procmon), Regshot & Network Callouts 12.5 .NET Managed Malware Analysis & the GOOTLOADER Fileless Infection Chain
13 Chapter 13: Network, Web Application & Email Forensics
13.1 Network Forensics: PCAP Analysis, Protocol Dissection, Snort/Suricata & Flow Analysis 13.2 Web Server Forensics: Apache/IIS Access Logs, SQL Injection, XSS & Web Shell Detection 13.3 Email Forensics: RFC 5322 Headers, Authentication (SPF, DKIM, DMARC) & Mbox/PST Extraction 13.4 SIEM Event Correlation, Cross-Source Timeline Analysis & Super-Timeline Construction 13.5 Investigating Directory Traversal, Command Injection, Parameter Tampering, XXE, Cookie Poisoning & Brute Force 13.6 Network Device & Service Log Forensics: Firewall, IDS, Honeypot, Router, DHCP, Switch, VPN, DNS & SSH 13.7 Wireless Network Forensics: Rogue APs, Evil Twins, MAC Spoofing, Deauthentication & Jamming
14 Chapter 14: Mobile, Cloud & IoT Forensics
14.1 Mobile Device Forensics: Manual, Logical, File System & Physical Extraction (Android/iOS) 14.2 Mobile Artifact Analysis: Call Logs, SMS/Chat SQLite Databases, Location Data & Plists 14.3 Cloud Forensics: AWS CloudTrail, Azure Activity Logs & Multi-Tenant Evidence Collection 14.4 IoT Forensics: UART/JTAG Physical Interfaces, Firmware Extraction & Sensor Telemetry
15 Chapter 15: Commercial & Open-Source Forensic Suites
15.1 Commercial Forensic Platforms: EnCase Forensic, FTK (Forensic Toolkit) & FTK Imager 15.2 Open-Source Forensic Platforms: Autopsy, The Sleuth Kit (TSK) & SIFT/CAINE Workstations 15.3 Specialized DFIR Utilities: Eric Zimmerman Tools (EZ Tools) & Sysinternals Forensic Suite
16 Chapter 16: Analysis Toolkits, Python Scripting & Tool Validation
16.1 Reverse Engineering & Password Cracking: Ghidra, IDA Pro, Hashcat & John the Ripper 16.2 Python for Digital Forensics: Parsing Raw Artifacts, Custom Scapy Scripts & Evidence Automation 16.3 Forensic Tool Testing & Validation: NIST CFTT Methodology, ISO/IEC 17025 Standards & Daubert Compliance
17 Chapter 17: Database Forensics & Web Application Firewalls
17.1 MySQL Forensics: Internal Architecture, Data Directory, Information Schema & Utility Programs 17.2 SQL Server Forensics: SSMS, ApexSQL, SQLCMD Transaction-Log Collection, Plan Cache & Trace Files 17.3 Web Application Firewall (WAF) Architecture, Audit Logs, Benefits & Limitations
18 Chapter 18: Social, Virtualized, Multimedia & Browser Investigations
18.1 Social Media, Social Engineering, Insider Threat & Identity Theft Forensics 18.2 Virtualization, Container & Microservices Forensics, Bluetooth and Electron Chat Applications 18.3 Multimedia Forensics: Image, Audio & Video Authentication, EXIF, PRNU and Deepfake Detection 18.4 Browser Artifact Recovery, Private Browsing, USB Enumeration, Partition Recovery & Packer Unpacking Tools
13.6 Network Device & Service Log Forensics: Firewall, IDS, Honeypot, Router, DHCP, Switch, VPN, DNS & SSH
Key Takeaways Explain This Topic AI
Cisco IOS syslog messages follow the %FACILITY-SEVERITY-MNEMONIC format with severity levels 0 (emergency) through 7 (debugging); level 6 (informational) is the level that carries ACL denies and interface state changes needed for investigations.
DHCP lease logs are what convert a historical IP address into a specific MAC address and hostname; the Windows DHCP server writes DhcpSrvLog-<Day>.log with event ID 10 for a new lease, 11 for a renewal, 12 for a release, and 15 for NACK.
SSH authentication evidence lives in /var/log/auth.log on Debian-family systems and /var/log/secure on RHEL-family systems, where Accepted publickey lines record the key fingerprint that identifies which key authenticated.
A honeypot generates zero false positives by definition — any interaction is unauthorized — which makes Cowrie session transcripts and Dionaea malware captures unusually high-value evidence.
Router and switch configuration is volatile: the running configuration lives only in RAM, so a reboot destroys attacker changes unless the config was captured live or archived off-device.
Last updated: September 2026
13.6 Network Device & Service Log Forensics: Firewall, IDS, Honeypot, Router, DHCP, Switch, VPN, DNS & SSH
Quick Answer: Blueprint Domain 5 requires analyzing firewall, IDS, honeypot, router, and DHCP logs , then Cisco switch, VPN, and DNS server logs , then investigating SSH logs , and analyzing SMTP and SNMP traffic . Each device answers a different investigative question. Firewall and IDS logs answer what was attempted . DHCP logs answer who owned an IP address at a point in time — the single most important attribution step in any network case. Router and switch logs answer how traffic moved . VPN logs answer who was remote . DNS logs answer what the host tried to reach . SSH logs answer which credential or key authenticated .
Syslog: The Common Container
Almost every network device exports through syslog, so the format is worth memorizing.
- Standard Structure
- RFC 3164 (BSD, legacy) <PRI>TIMESTAMP HOSTNAME TAG: MESSAGE — no year, no time zone, second granularity
RFC 5424 (modern) <PRI>VERSION TIMESTAMP HOSTNAME APP-NAME PROCID MSGID [STRUCTURED-DATA] MSG — ISO 8601 timestamp with offset and fractional seconds
PRI = Facility × 8 + Severity . Severity runs 0 Emergency, 1 Alert, 2 Critical, 3 Error, 4 Warning, 5 Notice, 6 Informational, 7 Debug .
Important
RFC 3164's missing year and time zone is a recurring forensic trap. A legacy syslog line reads Sep 14 03:21:44 with no year and no offset. Correlating it against a UTC-stamped web log requires knowing the device's configured time zone and the year, both of which must be documented from the device configuration — not assumed.
Firewall and IDS/IPS Logs
Firewall logs record the connection decision: 5-tuple, action (permit/deny/drop), interface, rule or ACL identifier, and byte/packet counts on session teardown.
Platform Characteristic record
Cisco ASA %ASA-6-302013 built inbound TCP connection; %ASA-6-302014 teardown with duration and bytes; %ASA-4-106023 deny by access-group
- iptables/netfilter Kernel IN= OUT= SRC= DST= PROTO= SPT= DPT= lines in kern.log
- pfSense/OPNsense filterlog CSV with rule number, interface, action, and full tuple
- Palo Alto / Fortinet Comma- or key-value traffic logs with application identification and bytes-sent/received
The forensically decisive field is usually bytes . A teardown record showing 4 GB sent outbound to an unfamiliar destination on port 443 is exfiltration evidence even when payload was never captured.
IDS/IPS logs record signature matches. Snort and Suricata write alert entries carrying the SID (signature ID), GID , revision, classification, priority, and the triggering 5-tuple; Suricata's eve.json additionally emits protocol, TLS/JA3, HTTP, DNS, and file-extraction records that make it a partial substitute for full packet capture.
An IDS alert is a signature match , not proof of compromise. Validate it against the packet capture or the destination host's own logs.
Tuned-out or disabled signatures explain silence. Always retrieve the ruleset state at the time of the incident , not the current one.
Honeypot Logs
A honeypot has no production purpose, so every interaction is unauthorized by construction — the false-positive rate is effectively zero, which is why honeypot evidence carries disproportionate weight.
Honeypot Captures
Cowrie Full SSH/Telnet session transcripts, keystroke timing, credentials tried, files downloaded via wget / curl , TTY replay logs
- Dionaea Malware binaries dropped over SMB, HTTP, FTP, MSSQL
- Conpot ICS/SCADA protocol interaction (Modbus, S7comm)
- T-Pot Multi-honeypot platform aggregating the above with Elastic dashboards
Cowrie's TTY replay files reconstruct the attacker's session keystroke-by-keystroke, including typing errors and pauses — evidence of live human interaction rather than automation, which matters for both attribution and sentencing.
DHCP Logs: The Attribution Keystone
An IP address in a web log is meaningless on a dynamic internal network without the lease record that bound it to a host.
Server Location and format
Windows DHCP Server %SystemRoot%\System32\dhcp\DhcpSrvLog-<Day>.log — comma-delimited: ID, Date, Time, Description, IP Address, Host Name, MAC Address
ISC dhcpd (Linux) /var/log/syslog or /var/log/messages — DHCPDISCOVER , DHCPOFFER , DHCPREQUEST , DHCPACK , DHCPNAK , DHCPRELEASE
Infoblox/appliances Syslog export plus a queryable lease history database
Windows DHCP event IDs to know: 10 new lease assigned, 11 lease renewed, 12 lease released, 13 IP found in use on network, 14 lease request could not be satisfied, 15 lease denied (NACK), 24 database cleanup.
Warning
Windows DHCP logs rotate weekly by file name ( DhcpSrvLog-Mon.log … DhcpSrvLog-Sun.log ), overwriting the same weekday file each week. An incident discovered eight days late may have already lost its lease record. Preserve DHCP logs in the first hour of any network investigation.
The correlation chain is: web/proxy log (IP + timestamp) → DHCP lease (IP + MAC + hostname at that timestamp) → switch CAM/MAC address table or 802.1X authentication (MAC + physical port) → asset inventory (host + assigned user) .
Router and Switch Logs
Cisco IOS syslog format: %FACILITY-SEVERITY-MNEMONIC: message-text , for example %SEC-6-IPACCESSLOGP: list 101 denied tcp 203.0.113.44(4221) -> 10.0.2.15(3389), 1 packet .
Forensically valuable IOS messages:
- Message Meaning
- %SEC-6-IPACCESSLOGP ACL permit/deny with full tuple
- %LINK-3-UPDOWN / %LINEPROTO-5-UPDOWN Interface state change — physical device connect/disconnect
- %SYS-5-CONFIG_I Configuration changed , with the user and source (console/vty)
- %SYS-5-RESTART / %SYS-5-RELOAD Reboot, which destroys the running configuration
- %PORT_SECURITY-2-PSECURE_VIOLATION Unauthorized MAC on a secured port — rogue device indicator
- %DOT1X-5-FAIL 802.1X authentication failure
Switch-specific evidence: the CAM/MAC address table ( show mac address-table ) maps MAC to physical port — but it is volatile , aging out in about 5 minutes by default. Capturing it requires live collection during the incident. The ARP cache ( show ip arp ) maps IP to MAC with a default 4-hour timeout.
Important
The running configuration exists only in RAM. show running-config reflects live state; show startup-config reflects NVRAM. An attacker who modifies the running config without writing it leaves evidence that a reboot silently erases. Live capture of show running-config , show mac address-table , show ip arp , show users , and show logging is the network equivalent of a RAM dump, and it must precede any remediation reboot.
VPN Logs
VPN concentrators answer who was remote, from where, for how long, and with what internal address .
Essential fields: username, authentication result and method (password, certificate, MFA token), public source IP with geolocation, assigned internal tunnel IP , session start and end, bytes transferred, and client posture.
The pivot that matters: the assigned tunnel IP is what appears in every internal log. Attribution requires joining the internal activity to the VPN session that held that tunnel IP at that moment. Because tunnel addresses are recycled from a pool, the timestamp is as essential as the address .
Characteristic findings: impossible travel (two authentications from distant countries minutes apart), a single account with concurrent sessions from different sources, and authentication success from a source that never appears in the account's history.
DNS Server Logs
DNS is the highest-yield low-volume telemetry in an investigation because nearly every attacker action begins with a name resolution.
- Source Content
- Windows DNS debug log / Analytical ETW Per-query client IP, query name, type, response code
- BIND querylog client 10.0.2.15#54321: query: evil.example.com IN A +
- Passive DNS / resolver telemetry Historical name-to-address mappings for pivoting
Detection patterns:
DNS tunneling — abnormally long labels, high-entropy subdomains, heavy TXT / NULL query volume, and sustained query rate to a single second-level domain. Exfiltration over DNS is encoded in the query name , so query length distribution is the tell.
DGA (domain generation algorithm) — bursts of NXDOMAIN responses for high-entropy names as malware cycles candidate domains before finding the live one. The domain that finally resolves is the C2.
DNS hijacking/spoofing — responses for a known domain returning an unexpected address, or an endpoint querying a resolver that is not the sanctioned one (a rogue resolver configured by malware).
Fast flux — very low TTLs with a rapidly rotating address set for one name.
SSH Logs
- Distribution family Authentication log
- Debian/Ubuntu /var/log/auth.log
- RHEL/CentOS/Fedora /var/log/secure
- systemd journal journalctl -u sshd (binary; export with journalctl -o export )
- Record types to parse: Accepted password for jsmith from 203.0.113.44 port 51422 ssh2
Accepted publickey for root from 198.51.100.7 port 40112 ssh2: RSA SHA256:8Lc9k...
- Failed password for invalid user admin from 203.0.113.44 port 51388 ssh2
- Disconnected from authenticating user root 203.0.113.44 port 51390 [preauth]
Accepted publickey ... SHA256:<fingerprint> is the highest-value line in the file: the fingerprint identifies which key authenticated, which can be matched against ~/.ssh/authorized_keys entries across the estate to trace attacker key implantation.
Failed password for invalid user X means the account does not exist — automated scanning. Failed password for X on a real account is targeted.
Correlate with wtmp / btmp / lastlog (parsed via last , lastb ), shell history files, and ~/.ssh/authorized_keys modification times.
SMTP and SNMP Traffic
SMTP traffic analysis reveals mass outbound mail from a non-mail host (compromised spam relay), MAIL FROM values inconsistent with the organization's domains, and large attachments leaving on port 25/587 as an exfiltration channel. Capture of the DATA phase yields full message content including headers and attachments.
SNMP is frequently overlooked. Community strings in SNMPv1/v2c travel in cleartext , so a capture containing public or private exposes device enumeration and potential configuration write access. A host performing SNMP GETBULK walks across the address space is conducting network reconnaissance; SNMPv3 with authPriv is the remediation, and its absence is itself a finding.