Table Of Content
Agents in a Box: What Windows Execution Containers Solve, and What Still Needs Endpoint Telemetry
-
November 3, 2026
-
Kitecyber | Data & Gen AI Security
Containment answers “what can this agent reach?” Security teams also have to answer “what did it do, and what was it holding when it did it?”
On 7 October, Microsoft laid out its vision for Windows as a platform for “hybrid intelligence”: AI agents that run locally when needed, call the cloud when appropriate, and operate with built-in security and manageability. A headline item was that Microsoft Execution Containers (MXC) are now generally available on Windows, alongside identity and manageability capabilities meant to help organizations control what agents can access and understand which agent performed an action.
This is a meaningful step. Running an agent inside a boundary is exactly the right instinct. It also raises a question every security team should ask before declaring the problem solved: what does a container tell you, and what does it leave out?
What containment does well
Where the gaps remain
- Data inside the permitted boundary still moves. An agent allowed to read a project folder and call an approved tool can still carry sensitive content into a prompt, a summary or an outbound request. The container permits the access; it does not judge whether the data should travel. Classification of what the agent actually handled is a separate question.
- Not every agent will be in the box. Developers install coding assistants, desktop AI apps, browser extensions and local model runtimes on their own. Many fleets are mixed across Windows, macOS and Linux. A control that applies to agents launched through the sanctioned path says little about the ones that were not.
- Containment is a prevention layer, not an evidence layer. After an incident, the first questions are what ran, what it read, what it sent, and who was logged in. Those answers come from process, file, network and user activity on the device, recorded consistently across every agent, contained or not.
- Local and cloud intelligence blur together. Hybrid designs route work to a local model or the cloud depending on the task. For governance, the useful unit is the data flow: what left the device, what stayed, and why. That is visible at the endpoint.
A practical way to layer the controls
- 1. Contain what you sanction. Use platform containment for agents you deploy deliberately.
- 2. Inventory what you did not. Discover every AI app, agent, extension, MCP server and local model on each device, whether or not it was launched through the approved path.
- 3. Classify the data in motion. Tie agent activity to data classification so a policy can distinguish a draft memo from customer records.
- 4. Record the activity as evidence. Keep a device-level timeline of process, file, network and user events for every agent, so investigations start from facts.
- 5. Enforce on the device. Apply allow, warn, redact or block decisions where the action happens, including for agents outside the container.