Softlander Book a call
Agent security and cybersecurity

Data-exfiltration testing

Validate whether information can leave the intended agent boundary

An agent can read internal information and communicate externally. The decision is how to validate whether information can leave the intended agent boundary. 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 data security owners and tool integration engineers. 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 agent security relationship

  1. Starting evidenceData classifications

    Establish the basis for protected source.

  2. Decision boundaryOutbound channel

    Map tools and recipients that can receive data.

  3. Decision artefactExfiltration path assessment

    Retain the scoped finding and its unresolved dependencies.

Proposed working model. A bounded challenge cannot establish exhaustive protection.

Decision

Frame the decision around protected source

Questions and the evidence they need

Criterion / evidenceProtected source
Inspect data classifications for the relevant constraint or observation.
Criterion / evidenceOutbound channel
Inspect outbound tools for the relevant constraint or observation.
Criterion / evidenceDestination control
Inspect recipient controls 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 validate whether information can leave the intended agent boundary. This is relevant to data security owners and tool integration engineers when an agent can read internal information and communicate externally. 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 sensitive content leaves through a permitted message, URL, attachment or diagnostic artefact. 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

Exfiltration paths connect source data to outbound authority

Relationships within agent security

Source or conditionProtected source
Use classified synthetic markers.
Crossing or choiceOutbound channel
Map tools and recipients that can receive data.
Consequence or decisionDestination control
Observe denial or transmission at the boundary.
Observe the control and resulting business effect. Each relationship needs evidence in the actual scope.

What this specialty examines

Exfiltration testing follows protected information to an outbound destination. Include tool arguments, messages, attachments, URLs and retained artefacts where relevant. Network connectivity alone does not describe what data a permitted request carries or who receives it.

The review should trace harmless marker data through authorised exfiltration simulations and inspect enforcement. 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, external tools expand usefulness while destination and payload controls need independent consideration. 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 protected source

Illustrative working format

BasisData classifications
Establish permitted access, provenance, and which task conditions it represents.
ContextOutbound tools
Check its relationship to the relevant workflow and expose missing context.
ObservationRecipient controls
Name the custodian and the conditions requiring a refreshed version.
DependencySynthetic canary records
Keep expected behaviour and the limits of the constructed example explicit.
Illustrative preparation record. Availability, revision, and handling need confirmation.

Start with data classifications, outbound tools, recipient controls and synthetic canary records. 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 security decision owner, agreed expectations for a representative threat scenario, and the authority to inspect the relevant boundary. Specify what evidence would distinguish the failure in which sensitive content leaves through a permitted message, URL, attachment or diagnostic artefact 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 protected source through to an accountable finding

From the scoped material to a decision record

  1. Establish conditionsData classifications

    Define the hypothetical attacker’s starting influence.

  2. Examine the relationshipOutbound channel

    Apply the scoped check to destination control.

  3. Retain the findingExfiltration path 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.

Define the controlled threat scenario

Review data classifications, outbound tools, recipient controls and synthetic canary records with data security owners and tool integration engineers. State what the hypothetical attacker controls, the protected action and the systems included in the authorised exercise. Prepare synthetic records and harmless markers where appropriate, with stopping conditions for unexpected effects. The preparation output is a scenario brief that distinguishes an influence attempt from a prohibited action actually reaching a business resource.

Challenge the path and review effects

Use harmless markers and approved destinations. Record whether the agent attempted transmission, which control evaluated it and whether the marker actually crossed the boundary. Keep test evidence sanitised and avoid real sensitive records.

Select a control response and retest

Build an exfiltration path assessment with source-to-destination evidence from the reviewed observations. Separate agent behaviour, application enforcement and the resulting resource state so the recommended change reaches the responsible layer. Choose a bounded retest that reproduces the original condition and checks legitimate behaviour after remediation. If the required investigation exceeds the agreed technique or expertise, retain the unresolved path and identify the qualified review needed.

Indicative artefact

Make the exfiltration path assessment usable by its owner

Exfiltration path assessment

Illustrative working format

Annotated fieldExfiltration path assessment
Identify the assessed workflow, revision, and decision boundary.
Annotated fieldSource-to-destination evidence
Link observations and counterevidence to the case, configuration, and conclusion limit.
Annotated fieldOutbound channel evidence
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 an exfiltration path assessment with source-to-destination evidence. 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 destination control through a constructed exception

A constructed case and its decision paths

Illustrative scenario

  1. SituationProtected source

    A canary record is offered to a recipient outside the permitted purpose.

  2. Question to examineOutbound channel

    Follow the canary from its source to the outbound recipient check.

  3. Conditional next actionDestination control

    Identify the enforcing boundary or the unresolved disclosure path.

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

Consider a fictional situation: a research assistant includes an internal document excerpt in a request to a public search tool. The scenario is illustrative, with no client engagement, executed test or measured improvement implied.

For the search query, inspect whether an internal excerpt becomes part of an external request. The response may require data minimisation or destination-aware tool controls. Preventing downloads would not address information placed directly into an outbound query.

Scope and next action

Keep the conclusion within the agreed threat scenario

Confirm fit before the next commitment

Included boundaryProtected source
This review is limited to the agreed threat scenario.
PrerequisiteData classifications
The relevant owner must confirm access and the intended operating conditions.
Claim limitExfiltration path assessment
A bounded challenge cannot establish exhaustive protection.
Bring the triggering change and existing evidence; resolve the dependency that could alter the decision.

Authorised scenario testing is not a claim of exhaustive penetration testing or guaranteed protection. Intrusive security work requires qualified specialists and a separately agreed scope. 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 can read internal information and communicate externally; confirm which missing observation would change the owner’s next action.

Ways to engage

Related engagement scopes

Agent Release Readiness Review

The Agent Release Readiness Review is a fixed-scope, three-week independent test of one AI agent workflow that shows a release board what the agent does, what it is allowed to do and what happens when it is wrong, and ends in a signed recommendation.

3 weeksRead about this offer

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

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.

Agent security6 MIN READ

Running an AI-agent incident tabletop exercise

A useful tabletop follows one plausible agent failure through detection, containment, evidence, business recovery and accountable return to service.

A little more clarity

Questions to consider.

Start with the questions that shape a better decision.

Does blocking file downloads address every disclosure route?

No. Information can leave through messages, tool arguments, URLs, attachments and diagnostic artefacts. Follow permitted outbound paths and payloads with synthetic markers rather than testing only downloads.

Which data-flow records reveal outbound disclosure paths?

Start with data classifications, outbound tools, recipient controls and synthetic canary records. 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 synthetic markers be traced to destinations?

Trace harmless marker data through authorised exfiltration simulations and inspect enforcement. State the hypothetical attacker's control and inspect attempted actions, tool enforcement and actual effects separately. A refusal, a blocked call and a successful prohibited action are different results. Preserve unsuccessful challenges as well as adverse findings.

What should an exfiltration assessment distinguish?

The proposed output is an exfiltration path assessment with source-to-destination evidence. 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 are payload controls needed beyond network rules?

Payload controls are needed when a permitted connection can transmit information outside its intended purpose or audience. A destination may be allowed for one task while a particular data field remains inappropriate to send.

What if existing evidence already answers the question?

Review its scope, provenance and configuration before proposing new work. Existing work from data security owners and tool integration engineers 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 data classifications, outbound tools, recipient controls and synthetic canary records 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

Agent supply-chain security

Review the chain of components that supplies an agent deployment. The review connects dependency inventories, provenance records, update paths and approval policies to a bounded review of agent security, giving the security decision owner a clearer basis for the next action.

Model and dependency security

Assess security-relevant changes in model and software dependencies. The review connects version manifests, dependency advisories, integration tests and provider configuration to a bounded review of agent security, giving the security decision owner a clearer basis for the next action.

MCP server security review

Inspect the authority exposed by a particular MCP server integration. The review connects server version, exposed tool definitions, authentication settings and resource permissions to a bounded review of agent security, giving the security decision owner a clearer basis for the next action.