Cybersecurity & Information Security

Order of Volatility in Digital Forensics: What to Collect First and Why

6 min readPublished: August 5, 2026

Professional visual illustration on the order of volatility in Incident Response and DFIR

Quick answer

The order of volatility is a controlled process that balances damage containment with evidence preservation. Document the source, time, and tool, save the Hash, build a Timeline, and separate fact, interpretation, and decision.

Incident Response and DFIR require a balance between speed, evidence preservation, business continuity, and documentation. A correct action is an action that can be explained, reproduced, and reviewed after the incident. This article focuses on the order of volatility and is intended for junior DFIR analysts and investigators. The goal is to provide a working methodology that can be applied in practice, in a professional interview, and in a work environment, without settling for a dictionary definition.

The main challenge is that data is almost always incomplete. Volatile memory, network state, and running processes can point to a direction, but their meaning depends on the time, asset, user, and expected activity. Therefore, we will build the examination around an investigation question, required evidence, and a clear criterion for completion.

The practical scenario in the article is: sorting evidence sources by urgency. All examples are lab data or process descriptions. When dealing with Penetration Testing, Web, or Cloud, one must work only with explicit permission, a defined Scope, and the ability to stop the test.

What is Volatility

The topic 'What is Volatility' is a central part of working on the order of volatility. It is recommended to break it down into three questions: What is the input, what decision do you want to make, and what evidence is sufficient to justify it. These questions prevent automatic tool usage without understanding the purpose.

In practice, record volatile memory, network state, running processes, disk image, hash, compare to expected behavior, and define at least one Pivot. The result should be verifiable by another analyst, including limitations and next steps.

Data Types by Change Rate

At this stage, define what evidence is needed to answer the investigation question. For the order of volatility, the basic points are the evidence source, collection time and time zone, Hash and Chain of Custody, tool and version. For each source, document owner, retention range, time zone, ingestion delay, and fields that may be missing.

Collection quality is not measured by the log 'arriving'. Completeness, Latency, Parsing, Duplicate events, and time synchronization should be checked. A Canary test or a known lab event allows verifying that the action appeared in the source, passed through the Pipeline, and is searchable in the correct fields.

Trade-offs in Live Collection

Impact of Isolation and Shutdown

The topic 'Impact of Isolation and Shutdown' is a central part of working on the order of volatility. It is recommended to break it down into three questions: What is the input, what decision do you want to make, and what evidence is sufficient to justify it. These questions prevent automatic tool usage without understanding the purpose.

Documenting Process Deviations

The order of volatility process is built in stages with stopping points. Define the goal, Scope, sources, permitted actions, required evidence, roles, and completion criteria. In attack scenarios, add Stop conditions and an emergency channel.

Each stage should have a clear Output: an asset map, Timeline, Finding, Rule, Playbook, or report. Moving to the next stage only occurs when the Output is sufficient and reliable; this prevents random work or Scope expansion without approval.

Unique Inspection Focuses

For this topic, it is recommended to build a focused evidence map in advance. The main inspection focuses are: volatile memory, network state, running processes, disk image, hash, collector/time. The list is not an automatic Checklist; each item is chosen because it can link an entity, action, and time or explain legitimate behavior.

volatile memory: Define the expected value, what would be considered anomalous, and what additional source would verify the finding.
network state: Define the expected value, what would be considered anomalous, and what additional source would verify the finding.
running processes: Define the expected value, what would be considered anomalous, and what additional source would verify the finding.
disk image: Define the expected value, what would be considered anomalous, and what additional source would verify the finding.
hash: Define the expected value, what would be considered anomalous, and what additional source would verify the finding.
collector/time: Define the expected value, what would be considered anomalous, and what additional source would verify the finding.

When one of the focus points is unavailable, the gap should be documented, and an alternative selected. For example, if a Process identifier is unstable, time, Host, User, and Parent can be used; if a Payload is encrypted, Metadata, volume, frequency, and TLS/DNS context are used.

Recommended Workflow

Define a Scope and one working question regarding the order of volatility.
List the data sources and required evidence: volatile memory, network state, running processes, disk image.
Create a short Baseline of normal behavior or expected outcome.
Perform the minimal test in a lab environment and save time, input, and output.
Build a Timeline or comparison table and separate fact from interpretation.
Pivot to an additional source to confirm or refute the initial explanation.
Summarize the decision, limitations, recommended action, and Retest criterion.

Practical Scenario

The chosen scenario is sorting evidence sources by urgency. The purpose of the exercise is not to prove attack capability, but to practice safe collection, comparison, and documentation. Before starting, define dummy data, a time window, and an expected outcome.

At the end of the exercise, a product should be submitted that another analyst or reviewer can critique: a screenshot or Export of the evidence, a short Timeline, an initial assumption, validating evidence, a limitation, and a recommendation. When there is insufficient evidence, the correct conclusion is that the scenario has not been proven.

Stage	What to perform	Output
Preparation	Define Scope, time, and objective. List which fields or evidence from volatile memory, network state, running processes are expected to appear.	Short test plan
Data Generation	Perform a safe, simulated action related to the order of volatility, without real information or impact on a production system.	Controlled event/Request/Flow
Collection	Collect the raw evidence and context from an additional source. Verify Time zone, identifiers, and completeness.	Two linked pieces of evidence
Analysis	Write what each piece of evidence proves, what it does not prove, and what the possible legitimate explanation is.	Interim conclusion
Completion	Choose closure, escalation, Finding, or Tuning; add a recommendation and Retest.	Documented product

Practical Checklist

Check and document: Evidence source.
Check and document: Collection time and time zone.
Check and document: Hash and Chain of Custody.
Check and document: Tool and version.
Check and document: Response actions taken.
Check and document: Timeline and working assumptions.
Note Time zone, tool version, and collection time.
Save raw data before filtering or modification.
Write what the finding proves and what is still unknown.
Define owner and next action with a due date.

Common Mistakes

Modifying the system before preserving evidence.
Not documenting the time zone.
Not calculating Hash.
Mixing fact and hypothesis.
Not documenting who possessed the evidence.
Prioritizing theoretical completeness over immediate damage containment.

Summary and CTA

The order of volatility in digital forensics: what to collect first and why, is a topic that connects technical knowledge with work discipline. Start with a question, collect only relevant evidence, maintain context and time, and choose an action that can be justified and re-examined.

In HPI's Cybersecurity & AI program, these principles are practiced using systems, logs, and labs. A natural progression is to move to the linked articles, perform the lab exercise, and save the output as part of a professional portfolio.

FAQ

Does the order of volatility alone prove an attack or vulnerability?

No. It provides a signal or finding that requires context, validation, and an additional source. A professional conclusion relies on a chain of evidence and alignment with expected behavior.

What to do when some data is missing?

Document the missing data, check for an alternative source, and reduce the level of certainty. Do not complete fields based on speculation or present Unknown as normal.

How long should evidence be retained?

Retention time depends on policy, regulation, cost, and the type of incident. It is important to define Retention, Legal hold, and the ability to export evidence in a verifiable format in advance.

How to practice without risking a real system?

Use virtual machines, dummy data, CTF, or a dedicated lab. In authorized tests, define Scope, Stop conditions, and backup before starting work.