Study guide
18.2 Virtualization, Container & Microservices Forensics, Bluetooth and Electron Chat Applications
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
18.2 Virtualization, Container & Microservices Forensics, Bluetooth and Electron Chat Applications
Key Takeaways Explain This Topic AI
Suspending a VMware virtual machine writes its entire RAM to a .vmem file next to the .vmss suspend state, which yields a complete memory image without running any acquisition agent inside the guest.
VMware snapshots create delta .vmdk files while Hyper-V checkpoints create .avhdx differencing disks; both mean the current disk state is a chain of parents and children that must be collected in full to be mountable.
Container filesystems are ephemeral union mounts over read-only image layers, so docker diff shows what changed, docker commit or docker export preserves it, and killing the container destroys the writable layer permanently.
Electron desktop applications such as Slack, Discord, and Microsoft Teams are Chromium processes that store message and workspace data in LevelDB directories under the user's AppData path, recoverable with LevelDB parsers and by carving .log and .ldb files.
Bluetooth pairing records prove device proximity and association: Windows stores paired device keys and identifiers under SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\Devices , and Linux under /var/lib/bluetooth/<adapter MAC>/<device MAC>/.
Last updated: September 2026
18.2 Virtualization, Container & Microservices Forensics, Bluetooth and Electron Chat Applications
Quick Answer: Blueprint Domain 4 lists virtualization forensics , forensic methodologies for containers and microservices , Bluetooth forensics , and Electron applications and chat application forensics among the investigative methodologies. The unifying theme is ephemerality : a container's writable layer, a suspended VM's memory file, and an Electron app's LevelDB cache all vanish or mutate quickly. The single highest-value trick in this section is that suspending a VMware virtual machine writes its full RAM to a .vmem file — a complete memory image obtained without touching the guest.
- Virtualization Forensics
- VMware File Types
Extension Contents Forensic value
.vmdk Virtual disk (monolithic, split, or thin) The guest's disk image; mountable read-only with standard tools
.vmx Plain-text configuration Hardware inventory, MAC addresses , attached devices, snapshot references, annotation field
- .vmem Guest RAM, paged out to disk A full memory image — analyze directly with Volatility
- .vmss Suspend state Accompanies .vmem ; written on suspend
.vmsn Snapshot state (includes memory when "snapshot the VM's memory" was selected) Point-in-time RAM plus disk state
- .vmsd Snapshot metadata and relationships The map of the snapshot chain
- .nvram Virtual BIOS/UEFI state Boot order and firmware settings
- vmware.log Hypervisor log Power on/off, snapshot operations, device connect/disconnect, guest crashes
Important
Suspending a VM is a memory acquisition technique. Suspend writes the entire guest RAM to .vmem , so an examiner can obtain a memory image with no agent inside the guest, no acquisition tool footprint, and no anti-forensic interference from the guest OS . Copy the .vmem and analyze it with Volatility as an ordinary raw memory image. Note the caveat: suspension is an intrusive act on a running system — it is a deliberate, documented decision, not a side effect.
Hyper-V and Others
Platform Disk Memory / state Configuration
Hyper-V .vhd , .vhdx , .avhdx (checkpoint differencing disk) .vmrs (runtime state), legacy .bin / .vsv .vmcx (binary), .vmgs
- VirtualBox .vdi (also .vmdk , .vhd ) .sav .vbox XML
- QEMU/KVM .qcow2 , raw virsh dump / virsh save output libvirt XML
- Proxmox/oVirt Backing storage volumes Managed snapshots Cluster configuration database
- The Snapshot Chain Problem
Both VMware snapshots and Hyper-V checkpoints work by freezing the parent disk read-only and writing all subsequent changes to a child delta file . The live state is therefore the parent plus every child in order .
Collect the entire chain. A delta .vmdk or .avhdx copied alone is unusable — it contains only changed blocks and has no base. Conversely, a base disk copied alone reflects the state before the incident, which is why an examiner who grabs only the largest file often ends up with the wrong point in time. Preserve .vmsd and the configuration file so the relationships can be reconstructed.
Forensic advantages of virtualization: snapshots give genuine point-in-time evidence; cloning a VM produces a working copy while the original stays untouched; the malware analysis lab depends entirely on snapshot-and-revert.
Forensic disadvantages: thin-provisioned disks may never write deleted blocks to physical storage, so unallocated-space carving yields less; storage deduplication at the datastore level breaks the assumption that a logical block maps to one physical location; and a shared datastore means the physical medium holds other tenants' data, which constrains what may lawfully be imaged.
Container and Microservices Forensics
Containers are processes on the host kernel , isolated by namespaces and cgroups, running on a union filesystem : read-only image layers with a thin writable layer on top.
The Evidence Model
- Layer Persistence How to collect
- Image layers Immutable, reproducible from the registry docker save , registry digest, docker history
Writable container layer Destroyed when the container is removed docker diff <id> , then docker commit or docker export
- Volumes / bind mounts Persist beyond the container Host filesystem collection
- Container logs Host-side, driver dependent /var/lib/docker/containers/<id>/<id>-json.log
Process memory Volatile Host-level memory acquisition — the container's processes are in the host's memory image
- Orchestrator records Control-plane database Kubernetes audit log, kubectl describe , etcd
- Live Container Triage Sequence docker ps -a # inventory including stopped containers
- docker inspect <id> > /evidence/inspect.json # config, mounts, network, env, start time
- docker diff <id> > /evidence/diff.txt # A=added C=changed D=deleted in writable layer
- docker logs <id> > /evidence/stdout.log # captured stdout/stderr
- docker top <id> > /evidence/procs.txt # processes with HOST pids
- docker export <id> > /evidence/fs.tar # flattened filesystem, no history
- docker commit <id> evidence/case123:t0 # preserves layers AND metadata
Warning
docker kill or docker rm destroys the writable layer irreversibly. In a GitOps or autoscaling environment the orchestrator may do this on its own within minutes (see Section 1.4). The first response action is to cordon the node, suspend reconciliation, and pause rather than kill the container. docker pause uses the cgroup freezer to stop the processes while leaving memory intact.
Kubernetes specifics: the audit log on the API server records every kubectl exec , create , delete , and secret access with the authenticated identity — the equivalent of a control-plane command history and usually the most important single artifact. crictl performs the same inspection where the runtime is containerd rather than Docker. Node-level evidence lives at /var/log/pods/ and in the kubelet journal, and etcd holds cluster state and secrets.
Microservices complications: a single transaction traverses many services, so the timeline must be assembled from distributed tracing (trace and span IDs) and centralized logging rather than from one host; service-mesh sidecars (Envoy) log every inter-service call; and secrets injected as environment variables appear in docker inspect output — which is itself a finding when a secret was never meant to be there.
Electron Application and Chat Application Forensics
Electron packages a Chromium renderer and a Node.js runtime into a desktop application. Slack, Discord, Microsoft Teams (classic), Signal Desktop, WhatsApp Desktop, Notion, and many others are Electron apps, which means they leave browser-style artifacts on the desktop .
Where the Data Lives
Base path: %AppData%\<AppName>\ on Windows, ~/Library/Application Support/<AppName>/ on macOS, ~/.config/<AppName>/ on Linux.
Sub-path Contents
Local Storage\leveldb\ LevelDB key-value store holding messages, workspace and channel metadata, and cached user objects — .ldb (SST) files, .log write-ahead files, MANIFEST-* , CURRENT
- IndexedDB\ Larger structured data, also LevelDB-backed
- Cache\ and Code Cache\ Chromium cache: downloaded images, avatars, and attachments
- Session Storage\ Per-session state
- Cookies SQLite database; authentication tokens
- logs\ Application-specific diagnostic logs with timestamps
- config.json / Preferences Account identifiers, workspace/server list, and in Signal Desktop the SQLCipher key
- Recovery Technique
Collect the entire application directory — a LevelDB store is only consistent as a set ( .ldb + .log + MANIFEST + CURRENT ).
Parse with a LevelDB reader ( plyvel , ccl_leveldb , Nirsoft/Magnet/Axiom LevelDB viewers). Never open the store with a writable client , which triggers compaction and destroys deleted-record remnants.
Carve the .log write-ahead files : deleted and superseded records frequently persist there until compaction, which is the richest source of "deleted" chat content.
strings over .ldb files recovers message fragments even where the structure is damaged.
Correlate the Chromium Cache for attachments and avatars, and the cookies database for the authenticated account.
Signal Desktop is the instructive special case: messages live in an SQLCipher-encrypted db.sqlite , and the decryption key sits in plaintext in config.json in the same directory (protected on newer builds by OS-level encryption such as DPAPI). Collecting the database without the configuration file yields an undecryptable blob.
Bluetooth Forensics
Bluetooth evidence proves proximity and association — that two specific devices were close enough to pair and that a user accepted the pairing.
Platform Artifact location
Windows SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\Devices\<MAC> — paired device MAC, name, and link-key material; plus Microsoft-Windows-Bluetooth-* operational logs
Linux /var/lib/bluetooth/<adapter MAC>/<device MAC>/info — device class, name, link key, and first/last-seen data
macOS /Library/Preferences/com.apple.Bluetooth.plist — paired devices with names, addresses, and last-connection timestamps
- Android /data/misc/bluedroid/bt_config.conf — paired devices, link keys, and timestamps
- iOS com.apple.MobileBluetooth.*.plist in the backup or full file system extraction
What it establishes: the device address (BD_ADDR) identifies a specific physical device; the friendly name often embeds the owner's name ("Sarah's AirPods"); pairing timestamps place the two devices in physical proximity at a specific moment. In vehicle infotainment forensics this is decisive — a head unit retains paired phone identities, contact lists, and call logs long after the phone is gone.
Attack-side terminology the exam expects: bluejacking (unsolicited message push), bluesnarfing (unauthorized data theft from a paired or vulnerable device), bluebugging (command execution over the device's control channel), and BlueBorne -class remote code execution in Bluetooth stacks. Address randomization in Bluetooth Low Energy (resolvable private addresses) complicates tracking, but a bonded device stores the identity resolving key, so paired-device records still resolve to a stable identity.