Softlander Book a call
Agent security and cybersecurity

Model and dependency security

Assess security-relevant changes in model and software dependencies

A model provider, runtime package or inference configuration changes. The decision is how to assess security-relevant changes in model and software dependencies. 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 application security and ML platform 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 evidenceVersion manifests

    Establish the basis for version assumption.

  2. Decision boundaryChanged surface

    Identify affected task and enforcement behaviour.

  3. Decision artefactModel-and-dependency review

    Retain the scoped finding and its unresolved dependencies.

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

Decision

Frame the decision around version assumption

Questions and the evidence they need

Criterion / evidenceVersion assumption
Inspect version manifests for the relevant constraint or observation.
Criterion / evidenceChanged surface
Inspect dependency advisories for the relevant constraint or observation.
Criterion / evidenceRetest requirement
Inspect integration tests 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 security-relevant changes in model and software dependencies. This is relevant to application security and ML platform owners when a model provider, runtime package or inference configuration changes. 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 dependency swap is treated as behaviorally equivalent without checking new interfaces or permissions. 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

Dependency changes should trigger targeted control checks

Relationships within agent security

Source or conditionVersion assumption
Record model and library revisions in scope.
Crossing or choiceChanged surface
Identify affected task and enforcement behaviour.
Consequence or decisionRetest requirement
Select cases linked to the changed dependency.
Observe the control and resulting business effect. Each relationship needs evidence in the actual scope.

What this specialty examines

Model and dependency review should identify the integration assumptions affected by a change. These may include schemas, error behaviour, context handling and tool invocation. A newer version is not automatically equivalent to the configuration previously evaluated.

The review should review change surfaces and define targeted validation for affected task and control paths. 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, staying current can address known issues while every change has a deployment-specific impact. 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 version assumption

Illustrative working format

BasisVersion manifests
Match this description to the deployed or proposed boundary being examined.
ContextDependency advisories
Check its relationship to the relevant workflow and expose missing context.
ObservationIntegration tests
Name the custodian and the conditions requiring a refreshed version.
DependencyProvider configuration
Match this description to the deployed or proposed boundary being examined.
Illustrative preparation record. Availability, revision, and handling need confirmation.

Start with version manifests, dependency advisories, integration tests and provider configuration. 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 dependency swap is treated as behaviorally equivalent without checking new interfaces or permissions 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 version assumption through to an accountable finding

From the scoped material to a decision record

  1. Establish conditionsVersion manifests

    Define the hypothetical attacker’s starting influence.

  2. Examine the relationshipChanged surface

    Apply the scoped check to retest requirement.

  3. Retain the findingModel-and-dependency review

    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 version manifests, dependency advisories, integration tests and provider configuration with application security and ML platform 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

Use release information and the actual deployment manifest to define targeted checks. Avoid broad compatibility claims beyond the reviewed versions. Separate known dependency concerns from behavioural changes observed in the customer’s application.

Select a control response and retest

Build a model-and-dependency review with versioned assumptions and retest requirements 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 model-and-dependency review usable by its owner

Model-and-dependency review

Illustrative working format

Annotated fieldModel-and-dependency review
Name the missing evidence, responsible owner, and condition for revisiting the decision.
Annotated fieldVersioned assumptions
Distinguish verified conditions from assumptions that require confirmation before use.
Annotated fieldRetest requirements
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 model-and-dependency review with versioned assumptions and retest requirements. 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 retest requirement through a constructed exception

A constructed case and its decision paths

Illustrative scenario

  1. SituationVersion assumption

    A provider update changes an assumption used by an integration control.

  2. Question to examineChanged surface

    Map the changed provider behaviour to affected integration assumptions.

  3. Conditional next actionRetest requirement

    Retest those task and control paths before reusing earlier conclusions.

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

Consider a fictional situation: an inference library upgrade changes tool argument handling and existing validation no longer receives the expected shape. The scenario is illustrative, with no client engagement, executed test or measured improvement implied.

For changed argument handling, follow data from model output through parsing and validation to execution. If the expected shape changed, the adapter may need revision and regression evidence. The model’s general benchmark performance does not answer that integration question.

Scope and next action

Keep the conclusion within the agreed threat scenario

Confirm fit before the next commitment

Included boundaryVersion assumption
This review is limited to the agreed threat scenario.
PrerequisiteVersion manifests
The relevant owner must confirm access and the intended operating conditions.
Claim limitModel-and-dependency review
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 a model provider, runtime package or inference configuration changes; 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 selecting a newer model remove application security obligations?

No. Application security still depends on identity, data handling, tool wrappers, permissions and operating controls. A model change can require targeted revalidation rather than removing those obligations.

Which manifests identify model and dependency changes?

Start with version manifests, dependency advisories, integration tests and provider configuration. 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 changed integration assumptions be validated?

Review change surfaces and define targeted validation for affected task and control paths. 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 a dependency review disclose?

The proposed output is a model-and-dependency review with versioned assumptions and retest requirements. 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 does an upgrade require targeted regression tests?

Retest when an upgrade changes interfaces, argument handling, error behaviour, permissions or other assumptions used by existing controls. Focus on affected paths and preserve evidence tied to the actual dependency revision.

What if existing evidence already answers the question?

Review its scope, provenance and configuration before proposing new work. Existing work from application security and ML platform 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 version manifests, dependency advisories, integration tests and provider configuration 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

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.

Adversarial agent testing

Challenge a defined agent workflow using authorised adversarial scenarios. The review connects rules of engagement, threat hypotheses, synthetic data and stop conditions to a bounded review of agent security, giving the security decision owner a clearer basis for the next action.

AI incident-response planning

Prepare an operational response to agent-related incidents. The review connects system ownership, tool privileges, incident classes and evidence-retention controls to a bounded review of agent security, giving the security decision owner a clearer basis for the next action.