AI • PRELIMINARY RECONSTRUCTION
The Sandbox Was
Not the Boundary
What the incident exposed about software delivery and defense
Ted Tschopp / August 13, 2026 / Public Workbench
ASSUMPTION | WHAT REMAINED REACHABLE | ENTERPRISE TEST | CONTROL QUESTION |
No direct internet | Package proxy and cache | Trace delegated egress | What can fetch for the agent? |
Fresh run | Shared files and directories | Inventory persistent state | What survives the run? |
One foothold | Service identities and metadata | Map lateral paths | What can this identity become? |
Patched | Alternate protocol and path | Retest the whole boundary | What did we not close? |
Restored | Model and data lineage | Separate closure evidence | What learned or persisted? |
QUESTION | ANSWER NEEDED | EVIDENCE | RED FLAG |
Exposed? | Endpoint, protocol, path | Runtime + network | Scan mismatch |
Running? | Version, configuration, drift | Deployment + asset records | Stale state |
Owner? | Primary, backup, approver | Catalog + on-call | No owner |
Dependencies? | Upstream, downstream, vendor | Telemetry + service map | Hidden break |
Stop path? | Isolation, kill switch, outage limit | Tested runbook | No safe stop |