Volatile vs Non-Volatile Evidence
You'll learn how to prioritize evidence collection based on data volatility—what disappears first and why it matters during incident response.
When collecting digital evidence during an incident, some data evaporates the moment you power down a system, while other data persists on disk. This critical distinction drives your entire collection strategy.
Understanding Data Volatility
Volatile evidence exists only in active memory (RAM) or temporary system states. The instant a machine reboots or loses power, this data vanishes forever. Examples include:
- Running processes and their command-line arguments
- Network connections currently established
- Contents of RAM (encryption keys, passwords, malware code)
- Clipboard contents
- User sessions and authentication tokens
Non-volatile evidence survives reboots because it's stored on persistent media like hard drives, SSDs, or backups. This includes:
- Files on disk
- System logs written to storage
- Registry entries
- Email archives
- Database contents
The Order of Volatility
Think of evidence like melting ice cubes of different sizes. Small cubes (volatile data) melt in seconds; large blocks (non-volatile data) last hours. The RFC 3227 volatility order guides responders:
- CPU registers, cache (most volatile)
- Memory (RAM)
- Network state and connections
- Running processes
- Disk storage
- Remote logs and backups (least volatile)
During incident response, collect from top to bottom—capture memory and network connections before pulling the plug, because a hard drive image is useless without the encryption keys that were only in RAM.
Key Takeaway: Always prioritize collecting volatile evidence first during incident response, following the order of volatility, because this data disappears on reboot while disk-based evidence remains accessible later.