Softlander Book a call
Agent security and cybersecurity

Security release assurance

Decide what security evidence is required before an agent release

Security findings and feature readiness are being combined without clear blocking rules. The decision is how to decide what security evidence is required before an agent release. 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 release authorities and engineering 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 agent security relationship

  1. Starting evidenceThreat models

    Establish the basis for release delta.

  2. Decision boundaryBlocking finding

    Keep unresolved consequential behaviour visible.

  3. Decision artefactSecurity release evidence pack

    Retain the scoped finding and its unresolved dependencies.

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

Decision

Frame the decision around release delta

Questions and the evidence they need

Criterion / evidenceRelease delta
Inspect threat models for the relevant constraint or observation.
Criterion / evidenceBlocking finding
Inspect control tests for the relevant constraint or observation.
Criterion / evidenceException decision
Inspect unresolved findings 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 decide what security evidence is required before an agent release. This is relevant to security release authorities and engineering owners when security findings and feature readiness are being combined without clear blocking rules. 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 signed review for an earlier version is reused after tools or permissions change. 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

Release evidence must cover the changed security surface

Relationships within agent security

Source or conditionRelease delta
Map changed components to threat assumptions.
Crossing or choiceBlocking finding
Keep unresolved consequential behaviour visible.
Consequence or decisionException decision
Assign residual issues and the required retest.
Observe the control and resulting business effect. Each relationship needs evidence in the actual scope.

What this specialty examines

Security release assurance needs evidence attached to the current configuration and authority. Identify material changes since the last review and the controls they affect. Prior approval should not silently cover an added tool, permission or data source.

The review should map current release changes to required evidence and define blocking, exception and retest decisions. 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, consistent security gates improve clarity while exception handling must retain named accountability. 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 release delta

Illustrative working format

BasisThreat models
Bound the starting influence, protected effect, authorised surface, and stopping rule.
ContextControl tests
Check its relationship to the relevant workflow and expose missing context.
ObservationUnresolved findings
Name the custodian and the conditions requiring a refreshed version.
DependencyRelease changes
Identify provenance and the specific decision this material can inform.
Illustrative preparation record. Availability, revision, and handling need confirmation.

Start with threat models, control tests, unresolved findings and release changes. 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 a signed review for an earlier version is reused after tools or permissions change 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 release delta through to an accountable finding

From the scoped material to a decision record

  1. Establish conditionsThreat models

    Define the hypothetical attacker’s starting influence.

  2. Examine the relationshipBlocking finding

    Apply the scoped check to exception decision.

  3. Retain the findingSecurity release evidence pack

    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 threat models, control tests, unresolved findings and release changes with security release authorities and engineering owners. 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

Define blockers, exceptions, reviewer competence and required retests. Preserve residual findings with named disposition and conditions. Technical evidence supports the release authority; it does not transfer accountability for accepting business risk.

Select a control response and retest

Build a security release evidence pack with scope, residual findings and accountable disposition 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 security release evidence pack usable by its owner

Security release evidence pack

Illustrative working format

Annotated fieldSecurity release evidence pack
Link observations and counterevidence to the case, configuration, and conclusion limit.
Annotated fieldScope
Link supporting and contrary observations to inspectable evidence.
Annotated fieldResidual 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 security release evidence pack with scope, residual findings and accountable disposition. 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 exception decision through a constructed exception

A constructed case and its decision paths

Illustrative scenario

  1. SituationRelease delta

    A new connector is released using security evidence from the earlier tool set.

  2. Question to examineBlocking finding

    Map the new connector's permissions and threats against retained tests.

  3. Conditional next actionException decision

    Require evidence for the changed surface before the release decision.

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

Consider a fictional situation: a previously reviewed assistant adds a write-capable connector immediately before launch. The scenario is illustrative, with no client engagement, executed test or measured improvement implied.

For the new connector, examine its write actions and affected threat paths before reusing earlier evidence. A narrower release may remain possible without the connector. The decision record should state exactly which configuration and limitations were accepted.

Scope and next action

Keep the conclusion within the agreed threat scenario

Confirm fit before the next commitment

Included boundaryRelease delta
This review is limited to the agreed threat scenario.
PrerequisiteThreat models
The relevant owner must confirm access and the intended operating conditions.
Claim limitSecurity release evidence pack
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 security findings and feature readiness are being combined without clear blocking rules; 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.

Can a prior security review cover a changed agent release?

Only to the extent that its scope and assumptions still apply. New tools, permissions, data or dependencies may invalidate relevant evidence. Review the change and record the exact configuration covered by the next decision.

Which changes invalidate earlier security evidence?

Start with threat models, control tests, unresolved findings and release changes. 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 release blockers and exceptions be defined?

Map current release changes to required evidence and define blocking, exception and retest decisions. 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 belongs in a security release pack?

The proposed output is a security release evidence pack with scope, residual findings and accountable disposition. 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 a new connector delay part of a release?

Delay the affected release scope when a new connector introduces unevaluated consequential actions or invalidates prior controls. A narrower configuration may still be considered if its evidence remains applicable and the decision boundary is explicit.

What if existing evidence already answers the question?

Review its scope, provenance and configuration before proposing new work. Existing work from security release authorities and engineering 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 threat models, control tests, unresolved findings and release changes 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

Agentic AI threat modelling

Prioritise credible attack paths against the agent's business authority. The review connects data-flow diagrams, actor assumptions, assets and action privileges to a bounded review of agent security, giving the security decision owner a clearer basis for the next action.

Secure agent architecture assessment

Assess where security controls should sit in an agent architecture. The review connects component diagrams, identity flows, policy enforcement and data paths to a bounded review of agent security, giving the security decision owner a clearer basis for the next action.

Prompt-injection testing

Test whether direct instructions can redirect an agent beyond its approved task. The review connects instruction hierarchy, protected behaviours, synthetic prompts and tool audit records to a bounded review of agent security, giving the security decision owner a clearer basis for the next action.