Order of Volatility
What to collect first, what it answers, and what collecting it costs.
Most of this site parses evidence somebody already collected. This page is about that step. RFC 3227 says collect in decreasing order of volatility, because the fastest-decaying evidence is gone while you decide.
Take memory before disk. Memory holds injected code, decrypted config, credentials and network state, and it is gone at the next reboot. A reboot is not a neutral act.
9 rows.
| Source | Lifetime | What it answers |
|---|---|---|
| CPU registers and cache | Nanoseconds | Nothing you can practically use. |
| Network connections and routing state | Seconds to minutes | Who the host is talking to right now. Established C2, an open reverse shell, the port a backdoor is listening on. |
| Running processes and loaded modules | Seconds to hours | What is executing, under which account, from which path, with which parent and command line. |
| Physical memory | Until reboot | Injected code, unpacked malware, decrypted configuration, cleartext credentials, deleted process artifacts, and the network and process state above in one consistent snapshot. |
| Temporary filesystems and swap | Minutes to days | Staged archives, dropped tooling, partially written exfiltration sets, paged-out memory contents. |
| Disk | Until overwritten | The filesystem timeline, Registry hives, event logs, browser history, prefetch, and every file-backed artifact the rest of this site parses. |
| Remote logs and monitoring data | Days to years, by retention policy | What the host did as seen from outside it. EDR telemetry, firewall and proxy logs, DNS, NetFlow, cloud control-plane records, IdP sign-ins. |
| Physical configuration and network topology | Stable | What the host is, where it sits, what it can reach, which VLAN and which segment. |
| Archival media and backups | Months to years | What the system looked like before the incident, which is how you establish when it changed. |