Home/Refreshers/Evidence that survives termination: refresher
Evidence that survives termination
One tag or label keeps a machine alive, captures its disks and, on AWS, its memory, and cuts it off, in that order, on four clouds and Kubernetes.
Remember
- Someone tags or labels the machine: incident=<id>, from the console, the CLI, or a playbook.
- It is kept alive: protected from deletion, and out of its autoscaling group.
- Its disks are captured: snapshots at one instant, then memory where the cloud allows.
- It is cut off: a quarantine group, a firewall tag, or a network policy.
| Platform | Uses | The part that catches people |
|---|---|---|
| AWS | EventBridge and a Lambda responder, with memory captured by AVML through Systems Manager | The instance uploads its own memory image, using its own role, which will not mention the evidence bucket. |
| Google Cloud | A label-triggered function: deletion protection, disk snapshots, then a deny-all firewall rule by network tag | Google Cloud has no managed memory capture. |
| Azure | An Event Grid trigger and a Flex Consumption function, with a lock, disk snapshots, and a deny-all security group | Azure has no managed memory capture. |
| Oracle Cloud | An Events rule and a code-only function, with volume backups and a Zero Trust Packet Routing quarantine attribute | Oracle Cloud has no termination protection for an instance, and no managed memory capture. |
| Kubernetes | A quarantine network policy in every namespace, and a responder role that cannot change the evidence | Take the pod out of its controller before anything else. |
Run the quick start
| Download providers | terraform init |
| Preview | terraform plan |
| Apply | terraform apply |
Watch out
- Check what you downloaded with evidence-verify, a small Go program on the Verifying evidence page.
- The order follows the order of volatility, with one twist.
- Changing security groups does not always end connections that are already open.
Check it worked
Run the drill on a test machine: tag or label it incident=drill-1. Its disks are captured, it is cut off from the network, and deleting it is refused. The full page gives the exact commands for each platform.