Softlander Book a call
Agent sandbox assurance

Browser sandbox evaluation

Verify the browser state and access boundaries used by an agent

An agent navigates authenticated sites and downloads external content. The decision is how to verify the browser state and access boundaries used by an agent. 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 browser automation engineers and security 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 evidenceBrowser profile settings

    Establish the basis for profile identity.

  2. Decision boundaryNavigation scope

    Review origins, popups, downloads, and extensions.

  3. Decision artefactBrowser sandbox evaluation

    Retain the scoped finding and its unresolved dependencies.

Proposed working model. Untested surfaces remain outside the conclusion.

Decision

Frame the decision around profile identity

Questions and the evidence they need

Criterion / evidenceProfile identity
Inspect browser profile settings for the relevant constraint or observation.
Criterion / evidenceNavigation scope
Inspect cookie stores for the relevant constraint or observation.
Criterion / evidenceState cleanup
Inspect extension inventory 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 verify the browser state and access boundaries used by an agent. This is relevant to browser automation engineers and security owners when an agent navigates authenticated sites and downloads external content. 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 sessions, downloaded files or cross-site state persist beyond the authorised task. 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

Browser state can cross the intended task boundary

Relationships within runtime isolation

Source or conditionProfile identity
Separate cookies and authenticated accounts.
Crossing or choiceNavigation scope
Review origins, popups, downloads, and extensions.
Consequence or decisionState cleanup
Check retained sessions when profiles are reused.
Compare effective controls with harmless test observations. Each relationship needs evidence in the actual scope.

What this specialty examines

Browser sandbox evaluation examines profile state, navigation and file exchange. Cookies, extensions, downloads and authenticated origins can persist beyond one interaction. Define which state is intentional for the task and which should be separated across users or sessions.

The review should test profile separation, origin changes, downloads, popups and session cleanup with synthetic accounts. 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, persistent profiles improve continuity while isolation and cleanup become harder to demonstrate. 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 profile identity

Illustrative working format

BasisBrowser profile settings
Identify provenance and the specific decision this material can inform.
ContextCookie stores
Check its relationship to the relevant workflow and expose missing context.
ObservationExtension inventory
Match this description to the deployed or proposed boundary being examined.
DependencyNavigation policies
Confirm the applicable revision and who resolves disputed interpretation.
Illustrative preparation record. Availability, revision, and handling need confirmation.

Start with browser profile settings, cookie stores, extension inventory and navigation policies. 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 sessions, downloaded files or cross-site state persist beyond the authorised task 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 profile identity through to an accountable finding

From the scoped material to a decision record

  1. Establish conditionsBrowser profile settings

    Declare the permitted environment and resources.

  2. Examine the relationshipNavigation scope

    Apply the scoped check to state cleanup.

  3. Retain the findingBrowser sandbox evaluation

    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 browser profile settings, cookie stores, extension inventory and navigation policies to identify the exact runtime and boundary claimed by browser automation engineers and security 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

Exercise redirects, new windows, downloads and abnormal termination under controlled conditions. Observe state in a subsequent session to verify cleanup. Browser privacy modes may alter some storage behaviour, but the deployment needs evidence for its particular isolation claim.

Choose containment or configuration changes

Translate the observations into a browser sandbox evaluation with state and navigation boundary findings. 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 browser sandbox evaluation usable by its owner

Browser sandbox evaluation

Illustrative working format

Annotated fieldBrowser sandbox evaluation
Identify the assessed workflow, revision, and decision boundary.
Annotated fieldState
Link supporting and contrary observations to inspectable evidence.
Annotated fieldNavigation boundary findings
Link observations and counterevidence to the case, configuration, and conclusion limit.
Illustrative artefact structure, not a completed engagement or an observed result.

A useful decision artefact is a browser sandbox evaluation with state and navigation boundary findings. 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 state cleanup through a constructed exception

A constructed case and its decision paths

Illustrative scenario

  1. SituationProfile identity

    A later task inherits cookies from an earlier synthetic account.

  2. Question to examineNavigation scope

    Run paired synthetic accounts through profile reuse and cleanup.

  3. Conditional next actionState cleanup

    Treat inherited cookies as a session-boundary finding.

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

Consider a fictional situation: a browser agent completes a customer task but leaves authenticated state available to the next queued session. The scenario is illustrative, with no client engagement, executed test or measured improvement implied.

For the queued session, inspect whether the next task inherits authentication or downloaded content. The response may involve dedicated profiles, reset verification or refusing reuse after failure. A closed browser window is not the same observation as removed state.

Scope and next action

Keep the conclusion within the authorised runtime boundary

Confirm fit before the next commitment

Included boundaryProfile identity
This review is limited to the authorised runtime boundary.
PrerequisiteBrowser profile settings
The relevant owner must confirm access and the intended operating conditions.
Claim limitBrowser sandbox evaluation
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 prompted by the situation in which an agent navigates authenticated sites and downloads external content; confirm which missing observation would change the owner’s next action.

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.

Is private browsing a complete agent isolation strategy?

No. Private browsing behaviour is only part of a deployment's state and access model. Evaluate profiles, authentication, downloads, extensions and session reuse under the actual configuration.

Which browser state needs isolation?

Start with browser profile settings, cookie stores, extension inventory and navigation policies. 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 navigation and session reuse be exercised?

Test profile separation, origin changes, downloads, popups and session cleanup with synthetic accounts. 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 belongs in a browser boundary assessment?

The proposed output is a browser sandbox evaluation with state and navigation boundary findings. 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 should persistent profiles be avoided?

Avoid persistent profiles when cross-user reuse, sensitive state or unreliable cleanup creates an unacceptable boundary for the intended task. Persistence can be deliberate, but needs ownership, scope and reset evidence.

What if existing evidence already answers the question?

Review its scope, provenance and configuration before proposing new work. Existing work from browser automation engineers and security 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 browser profile settings, cookie stores, extension inventory and navigation policies 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

Sandbox architecture review

Decide whether the proposed execution boundary matches the agent's privileges. The review connects deployment diagrams, mount configuration, network routes and privilege settings to a bounded review of execution boundaries, giving the runtime owner a clearer basis for the next action.

Isolation-boundary testing

Verify the resource boundaries an execution environment is meant to enforce. The review connects approved boundary claims, synthetic fixtures, runtime policies and host observations to a bounded review of execution boundaries, giving the runtime owner a clearer basis for the next action.

Code-execution sandbox certification readiness

Prepare evidence for a separately defined sandbox certification assessment. The review connects target scheme requirements, scope statements, architecture evidence and control-test records to a bounded review of execution boundaries, giving the runtime owner a clearer basis for the next action.