Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Snapshot-Based Cloud Forensics?

Snapshot-based cloud forensics uses the platform’s own disk snapshot APIs to capture a compromised instance in seconds, then analyses the copy in an isolated forensic account.

Illustration for the cybersecurity term Snapshot-Based Cloud Forensics
Home / Blog / Cybersecurity Terms / What Is Snapshot-Based Cloud Forensics?
17 November 2026

What Is Snapshot-Based Cloud Forensics?

What Is Snapshot-Based Cloud Forensics?

Snapshot-based cloud forensics is the practice of preserving a compromised virtual machine by calling the cloud provider’s own snapshot API rather than attaching a write blocker to a physical disk. The operation takes seconds, needs no access to the guest operating system, and produces a copy that can be analysed in a separate account while the original is left untouched or destroyed as the business requires.

It is the one area where cloud forensics is genuinely easier than the on-premises equivalent. Everything else about cloud investigation is harder, but acquisition is not.

The Order of Operations

Sequence matters more than tooling, and getting it wrong destroys evidence irrecoverably.

  1. Isolate without stopping. Replace the instance’s security group with one that denies all traffic, remove it from load balancer target groups and auto-scaling groups so nothing terminates it, and revoke or replace the IAM instance profile so any stolen role credentials stop working.
  2. Capture memory first. Run AVML or an equivalent through the management agent and write the output to object storage in the forensic account. Stopping or terminating the instance destroys RAM permanently, and that is usually where the implant lives.
  3. Snapshot every attached volume. On AWS, create-snapshots captures all volumes of an instance together, which matters for multi-volume consistency. Azure and Google Cloud offer equivalent managed disk and persistent disk snapshots.
  4. Copy into the forensic account and re-encrypt with a key that only the investigation team controls, so that a compromise of the production account cannot reach the evidence.
  5. Collect the context. Instance metadata, tags, the launch template, attached role policies, VPC flow logs, CloudTrail or Activity Log records, and load balancer logs are all part of the evidence and are frequently more valuable than the disk.

Two Ways to Analyse the Snapshot

The straightforward route is to create a volume from the snapshot, attach it to a hardened analysis instance in an isolated VPC with no internet gateway, and mount it read-only. This is fast and familiar, but it means a live operating system is touching evidence, so mount options must be set carefully.

The cleaner route on AWS uses the direct block read APIs, ListSnapshotBlocks and GetSnapshotBlock, to stream the snapshot into a raw image file without ever attaching it. The result is an ordinary disk image that can be hashed, stored, and opened in Autopsy, X-Ways, or the Sleuth Kit exactly like any other. For evidential work this is preferable, because the image is immutable and its hash is meaningful.

Known Limitations

Chain of Custody Is Built In

Every API call is recorded by the platform itself. CloudTrail, Azure Activity Log, and Google Cloud audit logs show who created the snapshot, from where, and exactly when, which produces a stronger custody record than a paper exhibit form. Keep those logs for the duration of the investigation and export them with the evidence.

The preparation that makes this work is organisational rather than technical: a dedicated forensic account or subscription with a pre-agreed cross-account role, a key management service key reserved for evidence, and an automated capture function that an analyst can trigger without raising a change request. AWS publishes a reference solution for exactly this pattern, and the equivalent in Azure and Google Cloud is straightforward to build.

Where the compromised workload is a SaaS tenant rather than an instance, there is nothing to snapshot and the approach changes entirely; see SaaS evidence collection. We set up and rehearse both paths as part of Investigation and Incident Response Services.

FAQ – Frequently Asked Questions

Should I Stop the Instance Before Snapshotting It?

No, not before capturing memory. Stopping or terminating an instance discards its RAM, taking with it running processes, decrypted payloads, and network state that often constitute the only evidence of a fileless intrusion. Isolate the instance at the network and identity layer first, acquire memory through the management agent, then snapshot the volumes while it is still running.

Is a Cloud Snapshot Forensically Sound?

It is accepted practice, with caveats that should be stated. The snapshot is crash-consistent rather than a clean point-in-time image, and it has no inherent hash value. The usual approach is to materialise the snapshot into a raw image, hash that image, and rely on the provider’s own audit log to evidence who created the snapshot and when.

Why Copy the Snapshot to a Separate Account?

Because the account under investigation may still be under the attacker’s control. Copying the snapshot into a dedicated forensic account, re-encrypted with a key that only the investigation team can use, means that continued compromise of production cannot delete or alter the evidence. It also keeps investigative access separate from the operational permissions in the affected environment.

Can You Recover Deleted Files From a Snapshot?

Files deleted from blocks that were previously written are usually recoverable, exactly as on a physical disk, because the data remains until the blocks are reused. Blocks that were never written at all are not stored in a thin-provisioned snapshot, so carving across unallocated space returns less than it would from a traditional image of a fully written drive.

Related Terms

You May Be Interested In These

What Is Role-Based Access Control (RBAC)?

Cybersecurity Terms

17 November 2026

What Is Role-Based Access Control (RBAC)?

Read More
What Is a Personal Data Inventory?

Cybersecurity Terms

17 November 2026

What Is a Personal Data Inventory?

Read More
What Is a Timestamping Authority?

Cybersecurity Terms

17 November 2026

What Is a Timestamping Authority?

Read More