Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Volatile data collection gathers the evidence that disappears when a system is powered down, in a defined order, with every command recorded so the method can be defended later.

What Is Volatile Data Collection?
Volatile data is anything that exists only while a system is running. Memory contents, running processes, open network connections, logged-on users, mounted shares, cached credentials, clipboard contents, and the routing table all vanish the moment the power goes. Volatile data collection is the disciplined gathering of that material before it is lost.
It is the point at which incident response differs most sharply from traditional computer forensics. The classical advice was to pull the plug and image the disk. Applied to a modern intrusion, that advice destroys the majority of the useful evidence.
RFC 3227, published in 2002 and still the cited reference, sets out the sequence by how quickly each source decays:
In practice this collapses into a simple rule for the field: take the memory image first, because it captures nearly everything in categories one and two; then run a short, scripted set of live commands to record system state in a readable form; then move to disk.
A memory image needs parsing before it yields answers, so a live state capture is still worth the few minutes it takes. On Windows the useful set includes the process list with full command lines and parent relationships, network connections with owning processes, logged-on sessions, local and domain group membership of active accounts, services and scheduled tasks, installed drivers, autoruns, open file handles, SMB sessions and shares, the ARP cache, and the DNS resolver cache.
On Linux the equivalents are the process tree with command lines, ss output for sockets, loaded kernel modules, mounted file systems, cron entries, systemd units, logged-in sessions, and the contents of /proc for any suspicious process, including its executable link and environment.
Cloud and container workloads add their own volatile layer: running container inventories, the instance metadata service response, and temporary role credentials that will expire within hours.
The tension in every live incident is that isolating a host protects the business while collecting from it preserves the evidence. The resolution is usually to isolate at the network layer first, using an EDR containment function or a switch port change, which stops the attacker interacting with the host while leaving it running, and then collect.
Where active destruction is under way, containment wins without argument. Where an attacker has an interactive session, assume they may notice the collection and act accordingly.
The common failure is improvisation: a first responder working out which commands to run while a director asks for updates every ten minutes. Build the collection script, test it on a representative build, store it on prepared media or deploy it through the EDR platform, and rehearse it in a tabletop exercise. Agree in advance who has authority to run it on a production system at three in the morning.
Done properly, this half hour of work is frequently what allows the subsequent memory and disk analysis to produce a definite answer rather than a range of possibilities, which is why it is the first operational step in our Investigation and Incident Response Services.
Anything that exists only while the system is powered on: memory contents, running processes and their command lines, open network connections, logged-on sessions, cached credentials, clipboard contents, the ARP and DNS caches, mounted shares, and temporary role credentials in cloud environments. All of it is lost on shutdown, and much of it changes significantly within minutes even while the system stays running.
The sequence set out in RFC 3227 for collecting evidence from most to least perishable: registers and cache, then memory, then network and process state, then temporary file systems, then disk, then remote logs, then archival media. Following it means capturing memory before running live commands, and running live commands before imaging the disk.
It changes the system, which is unavoidable and accepted. Executing any binary allocates memory, creates process artefacts, and may update file access times. The requirement is not to leave the system untouched but to document precisely what was run, when, and by whom, so the changes can be explained and distinguished from the attacker’s activity.
Isolate first at the network layer where possible, using endpoint detection containment or a switch configuration change, then collect. This stops the attacker interacting with the host while leaving it running so the evidence survives. Full shutdown or disconnection of power should be reserved for cases where destruction is actively occurring and evidence loss is the lesser harm.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.