01
Isolated workspace
Agents run where mistakes have no reach.
ESACA · Security
Security
ESACA is built by engineers and attacked by our own security team at mgm security partners. This page shows the architecture behind it – and how we help you build, review or prove your own.
Security · Reference architecture
Want to build it yourself? Here is what has to hold.
Some organisations want to run ESACA; others want to build their own agentic platform with it as a blueprint. Either way, the same security architecture has to hold. We call it four walls and a gate: isolated workspaces, a controlled egress gateway, a managed harness, a vetted supply chain – and a human gate before anything reaches production. We have built it, tested it and run it on real enterprise projects. We help you build yours, review what you already have, or prove it to your auditors.
02
Controlled egress
Default-deny, secretless, logged.
03
Managed harness
Rights, policies and context outside the model’s control.
04
Vetted supply chain
Skills, MCP servers and models admitted by review.
05
Human gate
Scanned, scoped, attributed changes reviewed by qualified people.
Security in every tool
Where each control lives
The same architecture, seen from each part of ESACA. Every card leads to the detail on the tool page.
Sandbox →
SA
Containment
Three ingredients make an agent dangerous. We control the one that matters.
SB
Secrets & supply chain
Nothing to steal. Nothing smuggled in.
Benchmark →
BA
Security measured
Measure security, not just speed.
BB
Sovereign models & data
Sovereign means: you know where the model came from, and your code stays yours.
Workbench →
WA
Harness Security
The model suggests. The harness decides.
WB
Checked & accountable
Every change is checked, has a name, and gets a real review.
