Home/Refreshers/An analysis machine that cannot reach production: refresher
An analysis machine that cannot reach production
A clean-room virtual machine for looking at suspicious files, with no route to anything live, on four clouds.
Remember
- Evidence arrives: a disk snapshot or files in the evidence bucket.
- The isolated workstation: no route to production or the internet.
- Analysis: reached through a broker, never a public address.
- Anything reaching out is refused: and alerted, at Standard.
| Platform | Uses | The part that catches people |
|---|---|---|
| AWS | An isolated VPC with no internet gateway, reached through Session Manager only | Without Standard's DNS Firewall, the workstation can still look up any name through the VPC resolver, which security groups do not filter and flow logs do not record. |
| Azure | An isolated virtual network with a workstation reached only through Azure Bastion | Network security groups do not filter DNS to Azure's resolver, and flow logs do not record it, so a sample could leak data through lookups. |
| Google Cloud | An isolated VPC network with no internet route, reached through Identity-Aware Proxy | DNS lookups go to the metadata server, which firewall rules do not cover, so in the quick start public names still resolve and a sample could leak data through lookups. |
| Oracle Cloud | An isolated VCN with no internet route, reached through a Bastion port-forwarding session | Oracle's resolver answers public names for instances with no internet access, by design, so a sample under examination can carry data out in a name lookup. |
Run the quick start
| Download providers | terraform init |
| Preview | terraform plan |
| Apply | terraform apply |
Watch out
- Malware under examination may try to call home.
- Evidence comes in through snapshots and the evidence bucket, and nothing goes out.
Check it worked
From the workstation, try to reach a production subnet. It should fail.