Softlander Book a call
Agent sandbox assurance

Secret-exposure testing

Check whether sandboxed work can expose credentials or other secret material

Environment variables, logs or shared files contain sensitive integration material. The decision is how to check whether sandboxed work can expose credentials or other secret material. 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 security engineering and runtime 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 evidenceSecret-injection design

    Establish the basis for injection route.

  2. Decision boundaryExecution copies

    Inspect subprocess and temporary-file exposure.

  3. Decision artefactSecret exposure map

    Retain the scoped finding and its unresolved dependencies.

Proposed working model. Untested surfaces remain outside the conclusion.

Decision

Frame the decision around injection route

Questions and the evidence they need

Criterion / evidenceInjection route
Inspect secret-injection design for the relevant constraint or observation.
Criterion / evidenceExecution copies
Inspect redaction rules for the relevant constraint or observation.
Criterion / evidenceOutput boundary
Inspect access paths 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 check whether sandboxed work can expose credentials or other secret material. This is relevant to security engineering and runtime owners when environment variables, logs or shared files contain sensitive integration material. 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 secret excluded from prompts appears in process output, error traces or artefacts. 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

Secret handling includes logs and exported artefacts

Relationships within runtime isolation

Source or conditionInjection route
Use canaries to trace authorised secret placement.
Crossing or choiceExecution copies
Inspect subprocess and temporary-file exposure.
Consequence or decisionOutput boundary
Check logs and exports before retention.
Compare effective controls with harmless test observations. Each relationship needs evidence in the actual scope.

What this specialty examines

Secret-exposure testing should use synthetic canary values wherever possible. Trace how secrets enter workers, which processes can read them, and where outputs travel. Environment variables, errors, debug logs and generated artefacts each create distinct exposure paths.

The review should follow synthetic secret markers through environment, files, subprocesses, logs and exported outputs. 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, debug visibility supports troubleshooting while raw execution output needs controlled collection. 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 injection route

Illustrative working format

BasisSecret-injection design
Use nonsecret metadata to trace issuance, acceptance, and withdrawal responsibility.
ContextRedaction rules
Confirm the applicable revision and who resolves disputed interpretation.
ObservationAccess paths
Name the custodian and the conditions requiring a refreshed version.
DependencySynthetic canary values
Keep expected behaviour and the limits of the constructed example explicit.
Illustrative preparation record. Availability, revision, and handling need confirmation.

Start with secret-injection design, redaction rules, access paths and synthetic canary values. 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 secret excluded from prompts appears in process output, error traces or artefacts 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 injection route through to an accountable finding

From the scoped material to a decision record

  1. Establish conditionsSecret-injection design

    Declare the permitted environment and resources.

  2. Examine the relationshipExecution copies

    Apply the scoped check to output boundary.

  3. Retain the findingSecret exposure map

    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 secret-injection design, redaction rules, access paths and synthetic canary values to identify the exact runtime and boundary claimed by security engineering and runtime 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

Inspect collection and retention as well as initial access. A redaction rule may cover the main transcript but miss an attachment or subprocess log. Keep evidence sanitised so the test itself does not create the exposure it is meant to examine.

Choose containment or configuration changes

Translate the observations into a secret exposure map with reproducible paths and proposed containment changes. 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 secret exposure map usable by its owner

Secret exposure map

Illustrative working format

Annotated fieldSecret exposure map
Identify the assessed workflow, revision, and decision boundary.
Annotated fieldReproducible paths
Link supporting and contrary observations to inspectable evidence.
Annotated fieldContainment changes
Name the unresolved condition, next action, and accountable owner.
Illustrative artefact structure, not a completed engagement or an observed result.

A useful decision artefact is a secret exposure map with reproducible paths and proposed containment changes. 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 output boundary through a constructed exception

A constructed case and its decision paths

Illustrative scenario

  1. SituationInjection route

    A synthetic secret is hidden in output but remains in a debug artefact.

  2. Question to examineExecution copies

    Search approved logs and exported artefacts for the canary.

  3. Conditional next actionOutput boundary

    Treat any retained copy as part of the exposure and cleanup finding.

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

Consider a fictional situation: an agent’s test script prints its environment during debugging and the transcript is retained as a shareable artefact. The scenario is illustrative, with no client engagement, executed test or measured improvement implied.

For the environment dump, follow the marker into the retained transcript and any shared artefact. The design decision may involve limiting injection, suppressing raw diagnostics or filtering an export. Masking the final answer alone would leave other paths unresolved.

Scope and next action

Keep the conclusion within the authorised runtime boundary

Confirm fit before the next commitment

Included boundaryInjection route
This review is limited to the authorised runtime boundary.
PrerequisiteSecret-injection design
The relevant owner must confirm access and the intended operating conditions.
Claim limitSecret exposure map
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 environment variables, logs or shared files contain sensitive integration material; 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.

Can tests use real credentials to check secret exposure?

Use synthetic canary values wherever possible. Real credentials create unnecessary exposure during collection and reporting. Any exceptional need for sensitive material would require an approved handling route and explicit scope.

Which records map secret injection and output handling?

Start with secret-injection design, redaction rules, access paths and synthetic canary values. 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 canary secrets be traced through logs?

Follow synthetic secret markers through environment, files, subprocesses, logs and exported outputs. 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 secret exposure report preserve?

The proposed output is a secret exposure map with reproducible paths and proposed containment changes. 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 diagnostic visibility be reduced?

Reduce diagnostics when they expose secret material or unnecessary sensitive payloads. Preserve the minimum metadata needed to investigate behaviour, and test redaction across transcripts, subprocess output and exported artefacts.

What if existing evidence already answers the question?

Review its scope, provenance and configuration before proposing new work. Existing work from security engineering and runtime 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 secret-injection design, redaction rules, access paths and synthetic canary values 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

Resource-exhaustion testing

Establish what happens when agent execution consumes excessive resources. The review connects resource quotas, scheduler settings, workload limits and telemetry to a bounded review of execution boundaries, giving the runtime owner a clearer basis for the next action.

Malicious-code execution testing

Validate controls around potentially harmful generated code. The review connects execution policies, allowed interpreters, network limits and harmless test payloads to a bounded review of execution boundaries, giving the runtime owner a clearer basis for the next action.

Persistence and cleanup verification

Verify that finished agent sessions leave no unintended reusable state. The review connects session lifecycle events, volume policies, artefact lists and synthetic state markers to a bounded review of execution boundaries, giving the runtime owner a clearer basis for the next action.