Softlander Book a call
Agent sandbox assurance

Escape-resistance assessment

Assess evidence for resisting escape from a defined execution environment

A platform owner needs to understand the limits of an environment running untrusted code. The decision is how to assess evidence for resisting escape from a defined execution environment. The work begins with your actual workflow and looks for the evidence that separates intended behaviour from a consequential exception. It is particularly relevant to qualified platform security reviewers and infrastructure owners. A useful outcome is an explicit account of what was examined, what remains uncertain, and which decision the evidence can support.

Book a 30 minute readiness callBrowse this capability group

The runtime isolation relationship

  1. Starting evidenceRuntime versions

    Establish the basis for runtime interface.

  2. Decision boundaryChallenge scope

    Constrain nonproduction cases and stop conditions.

  3. Decision artefactBounded escape-resistance assessment

    Retain the scoped finding and its unresolved dependencies.

Proposed working model. Untested surfaces remain outside the conclusion.

Decision

Frame the decision around runtime interface

Questions and the evidence they need

Criterion / evidenceRuntime interface
Inspect runtime versions for the relevant constraint or observation.
Criterion / evidenceChallenge scope
Inspect privilege configuration for the relevant constraint or observation.
Criterion / evidenceUnexamined surface
Inspect host interfaces for the relevant constraint or observation.
Read each criterion against the available evidence before deciding that additional work is needed.

The decision is how to assess evidence for resisting escape from a defined execution environment. This is relevant to qualified platform security reviewers and infrastructure owners who need to understand the limits of an environment running untrusted code. Name the affected workflow, the consequence of a wrong decision, and the owner who can act on the result. The initial discussion should establish which evidence is already available and which uncertainty is material enough to investigate.

The specific failure hypothesis is that a broad escape-resistant claim is made without examining exposed host or management interfaces. It remains a hypothesis until examined in the deployment. Existing internal tests or operating records may already resolve it; identify the uncovered question before commissioning additional work.

Mechanism

Escape assessment is bounded by the authorised surface

Relationships within runtime isolation

Source or conditionRuntime interface
Identify exposed host and privilege mechanisms.
Crossing or choiceChallenge scope
Constrain nonproduction cases and stop conditions.
Consequence or decisionUnexamined surface
Keep unsupported escape conclusions visible.
Compare effective controls with harmless test observations. Each relationship needs evidence in the actual scope.

What this specialty examines

Escape-resistance assessment begins with a qualified threat model and explicit testing authority. Identify privilege, exposed host interfaces, management operations and runtime assumptions. The assessment should distinguish architecture concerns, known dependency questions and behaviour actually exercised in the agreed environment.

The review should review the specified attack surface and execute only explicitly approved nonproduction challenge cases. Identify the normal route, relevant exceptions and the authoritative record of the outcome. Inspect the relevant business-system record, enforcement event or process evidence alongside any reported status. Keep incomplete cases visible, with an explanation of what their absence prevents the owner from concluding.

The tradeoff to make explicit

For this decision, strong claims require deep specialist evidence and cannot be inferred from a few blocked attempts. Compare the available design or operating choices against the same intended outcome. If one option removes a required control or changes the task boundary, describe that difference before treating its apparent simplicity, speed or lower effort as an improvement. The decision should expose the tradeoff instead of burying it in an aggregate score.

Preparation

Connect the working inputs to the boundary being examined

Evidence packet for runtime interface

Illustrative working format

BasisRuntime versions
Match this description to the deployed or proposed boundary being examined.
ContextPrivilege configuration
Match this description to the deployed or proposed boundary being examined.
ObservationHost interfaces
Match this description to the deployed or proposed boundary being examined.
DependencyAuthorised threat model
Bound the starting influence, protected effect, authorised surface, and stopping rule.
Illustrative preparation record. Availability, revision, and handling need confirmation.

Start with runtime versions, privilege configuration, host interfaces and an authorised threat model. Identify the owner, revision and operating context of each source. Sanitised examples may support initial design, but differences from actual conditions should remain explicit. Where direct access is unsuitable, a customer-controlled evidence or execution route may be considered, with agreed handling and retention.

The scope also needs the runtime owner, agreed expectations for a representative boundary test, and the authority to inspect the relevant boundary. Specify what evidence would distinguish the failure in which a broad escape-resistant claim is made without examining exposed host or management interfaces from acceptable behaviour. If stakeholders disagree about intended behaviour, resolve the interpretation before classifying the observed difference as a defect.

How the work proceeds

Carry runtime interface through to an accountable finding

From the scoped material to a decision record

  1. Establish conditionsRuntime versions

    Declare the permitted environment and resources.

  2. Examine the relationshipChallenge scope

    Apply the scoped check to unexamined surface.

  3. Retain the findingBounded escape-resistance assessment

    Record the evidence, open dependencies, and the owner’s next decision.

Proposed sequence; resolve interpretation or access gaps before relying on the next step.

Prepare the runtime boundary and fixtures

Use runtime versions, privilege configuration, host interfaces and an authorised threat model to identify the exact runtime and boundary claimed by qualified platform security reviewers and infrastructure owners. Mark permitted resources and protected resources in a controlled fixture, including shared services where they are relevant. Define observable success, denial and incomplete setup before execution. The preparation output is a boundary map and fixture manifest that lets reviewers distinguish effective isolation from a test that never reached its target.

Exercise and inspect the boundary

Avoid extrapolating from a small number of blocked attempts to impossibility of escape. Record untouched surfaces and limits imposed by access or specialist competence. Potentially disruptive exploration belongs in a separately controlled test plan with clear stopping conditions.

Choose containment or configuration changes

Translate the observations into a bounded escape-resistance assessment with tested conditions and unresolved dependencies. Locate each issue in the worker, shared service, policy rollout or cleanup path rather than attributing every symptom to the sandbox as a whole. Decide which configuration change, narrower resource exposure or specialist investigation is warranted. Retest the affected boundary and inspect residual state before treating the changed environment as equivalent to the intended design.

Indicative artefact

Make the bounded escape-resistance assessment usable by its owner

Bounded escape-resistance assessment

Illustrative working format

Annotated fieldBounded escape-resistance assessment
Identify the assessed workflow, revision, and decision boundary.
Annotated fieldTested conditions
Link supporting and contrary observations to inspectable evidence.
Annotated fieldUnresolved dependencies
Name the missing evidence, responsible owner, and condition for revisiting the decision.
Illustrative artefact structure, not a completed engagement or an observed result.

A useful decision artefact is a bounded escape-resistance assessment with tested conditions and unresolved dependencies. Supporting material may include selected cases, configuration or process records, evidence references, a disagreement log and prioritised actions. Retain the case selection rationale and material disagreements alongside the result; otherwise the result may be mistaken for complete coverage.

Illustrative scenario

Examine unexamined surface through a constructed exception

A constructed case and its decision paths

Illustrative scenario

  1. SituationRuntime interface

    A runtime exposes a host interface outside the stated challenge scope.

  2. Question to examineChallenge scope

    Map the exposed host interface to the authorised test surface.

  3. Conditional next actionUnexamined surface

    Request a separately scoped review before making claims about that surface.

Fictional example. No executed test, customer engagement, or measured outcome is implied.

Consider a fictional situation: a proposed coding worker has restricted filesystem access but can reach a powerful local management endpoint. The scenario is illustrative, with no client engagement, executed test or measured improvement implied.

For the management endpoint, determine its accessibility and authorised functions before any challenge. Removing unnecessary exposure may be the first design decision. A configuration review can identify that concern without inventing an executed exploit or universal conclusion.

Scope and next action

Keep the conclusion within the authorised runtime boundary

Confirm fit before the next commitment

Included boundaryRuntime interface
This review is limited to the authorised runtime boundary.
PrerequisiteRuntime versions
The relevant owner must confirm access and the intended operating conditions.
Claim limitBounded escape-resistance assessment
Untested surfaces remain outside the conclusion.
Bring the triggering change and existing evidence; resolve the dependency that could alter the decision.

Testing is confined to explicitly authorised environments and non-destructive cases. A bounded assessment cannot establish that escape or cross-boundary access is impossible. Any engagement depends on an agreed scope, qualified team, authorised access and confirmed availability. Bring the affected workflow, its current configuration or process, the triggering change and the evidence already available. The immediate scope question is which missing observation would change the owner’s understanding of the environment’s limits.

Ways to engage

Related engagement scopes

AI Agent Runtime Security Review

Make every delegation explicit. Examine who the agent acts for, where it can execute and which tools it can reach when instructions alone are not enough.

Read about this offer

AI Agent Red Team

Challenge the boundaries that matter to your workflow. Test agreed attack scenarios against agent instructions, tools and data access.

Read about this offer

AI Agent Sandbox Assurance

Examine the boundary between agent execution and the systems around it, including files, networks, secrets and cleanup.

Read about this offer

Continue exploring

Related insights and resources

Agent security6 MIN READ

The permission boundary behind every agent action

An agent can only be evaluated in the context of what its tools allow. Examine identity, delegated authority and action boundaries before you put a workflow in motion.

Whitepaper5 MIN READ

Before your agent can act, define its authority

A working paper for the moment an AI system moves from advice to action. Map identity, permissions, approvals and recovery into an authority model your team can review and test.

A little more clarity

Questions to consider.

Start with the questions that shape a better decision.

Can this assessment prove that escape is impossible?

No. The proposed assessment can describe tested conditions, architecture concerns and limitations. It cannot establish that every escape path is impossible. Stronger conclusions require an explicitly scoped qualified assessment and still need bounded wording.

Which runtime records support an escape-resistance scope?

Start with runtime versions, privilege configuration, host interfaces and an authorised threat model. Record their revision, owner and relationship to the intended workflow. Missing context should be identified before interpreting outcomes; a sanitised fixture is useful only when its relevant differences from the operating case are understood.

How should host-interface concerns be investigated?

Review the specified attack surface and execute only explicitly approved nonproduction challenge cases. Retain effective runtime configuration and observations from the relevant boundary. Distinguish an enforced denial from failed setup or an operation that never reached the resource. Use controlled markers and preserve residual-state evidence.

What should a bounded escape assessment disclose?

The proposed output is a bounded escape-resistance assessment with tested conditions and unresolved dependencies. Include the selected conditions, supporting observations, unresolved differences and next decision. A reviewer should be able to follow each important conclusion back to its evidence and understand the limits without depending on an undocumented explanation from the author.

When is deeper specialist testing needed?

Deeper specialist work is needed when the decision depends on unexamined host interfaces, privilege transitions or attack surfaces beyond current competence and scope. Keep the limitation explicit rather than extending the claim.

What if existing evidence already answers the question?

Review its scope, provenance and configuration before proposing new work. Existing work from qualified platform security reviewers and infrastructure owners may already be sufficient. In that case, capture the decision, unresolved limitations and the change that would require another review. Additional assessment should address a real gap.

What would make the findings inconclusive?

Missing runtime versions, privilege configuration, host interfaces and an authorised threat model can prevent a reliable interpretation, depending on the case. Record the specific missing observation and its implication. The owner can supply evidence, narrow the claim or defer the dependent decision; an incomplete case should not silently be counted as a pass.

Start with the decision you need to make.

Tell us about the agent workflow you want reviewed, and where you need greater clarity. Scope and availability are confirmed together.

Book a 30 minute readiness call Get the agent release checklist

Connected disciplines

Filesystem-access testing

Verify what files an agent execution environment can read or change. The review connects mount maps, path permissions, symlink rules and synthetic sensitive-file markers to a bounded review of execution boundaries, giving the runtime owner a clearer basis for the next action.

Network-egress control review

Define and validate where a sandbox may send network traffic. The review connects destination policies, DNS behaviour, proxy routes and connection logs to a bounded review of execution boundaries, giving the runtime owner a clearer basis for the next action.

Secret-exposure testing

Check whether sandboxed work can expose credentials or other secret material. The review connects secret-injection design, redaction rules, access paths and synthetic canary values to a bounded review of execution boundaries, giving the runtime owner a clearer basis for the next action.