Security Considerations for Intent-Based Requests in Agentic SystemsHuaweijiangyuning2@h-partners.comHuaweililun20@huawei.comHuaweisongyurong1@huawei.comHuaweiliufei19@huawei.com
Security
intentAI Agentsagentic systemsdelegationtransaction contextdrift
Intent-based requests enable users, applications, and agents to express goals and constraints without
specifying step-by-step procedures. Such intents are commonly translated into executable directives
and propagated across multiple entities (clients, agents, authorization components, orchestration
functions, and execution endpoints). This multi-hop processing expands the attack surface for
tampering, privilege escalation, constraint bypass, and intent drift.
This document provides a solution-agnostic security analysis for intent-based requests across
agentic systems. It introduces a reference model and scenarios to guide
protocol and system design, and also presents threats and requirements. The document emphasizes constraint validation, invocation validation,
multi-hop chain-of-custody, and policy-driven responses to drift, while remaining independent
of any specific deployment domain.
Introduction
Intent-based interaction is increasingly adopted in automation, orchestration, and agentic systems,
where a request expresses desired outcomes and constraints rather than explicit procedures.
A receiving system (or a chain of systems) translates the intent into executable directives and
invokes tools or services to achieve the intended outcome.
Multi-hop processing (client-to-agent, agent-to-agent, agent-to-tool/service) introduces security
risks beyond traditional single-hop APIs, including: (1) integrity and substitution attacks against
derived directives, (2) privilege escalation during tool/service invocation, (3) constraint bypass,
and (4) multi-hop intent drift where constraints degrade or diverge over transformations.
This document does not define a new protocol. Instead, it provides a security-oriented reference
model, threat analysis, requirements, and scenarios to support future standardization and
interoperable designs.
Scope
This document focuses on security considerations for intent-based requests in multi-hop agentic
systems. While examples may reference telecom or networking contexts, the analysis applies
broadly to any domain where intent processing spans multiple trust boundaries.
Terminology and ConventionsConventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
"RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted
as described in BCP 14 when, and only when,
they appear in all capitals, as shown here.
Definitions
This document uses the following terms:
Intent:
A declarative expression of desired operational goals and outcomes, without
specifying how to achieve or implement them. This definition is aligned with
intent-based networking (IBN) guidance .
Intent Translation:
The process of transforming an intent into more concrete representations,
such as constraints, objectives, candidate procedures, or executable directives.
Constraint:
A condition that limits acceptable outcomes or actions. Constraints may include
invariants, policy rules, safety boundaries, and compliance requirements.
Constraint Validation:
Verifying whether an intent and/or its derived artifacts comply with
applicable constraints, invariants, policy rules, and safety boundary requirements.
Invocation:
A request to a tool or service intended to fulfill an intent (e.g., API call,
workflow step, actuation command).
Invocation Validation:
Determining whether an invoker holds the required privileges to invoke
a tool or service and whether invocation parameters satisfy the requirements
and constraints specified by the intent.
Observation:
Telemetry, events, measurements, or other signals used for monitoring and assurance.
Drift:
A divergence between the intent (including its constraints) and the realized
plan or actions over time or across multi-hop transformations.
Derived Directive:
An executable or enforceable artifact generated from an intent through translation,
such as an allowed rule set, capability token, or authorization grant.
Acronyms
IBN:
Intent-Based Networking
IBS:
Intent-Based System
Problem Statement and Threat Model
In many agentic systems, an intent is translated into executable directives (e.g., an
allowed rule set) that must be propagated across multiple entities and enforced at
execution endpoints. However, existing designs often lack end-to-end mechanisms that
jointly ensure: (1) directives remain within authorized boundaries across transformations
and propagation, (2) constraints are validated before execution, (3) invocations are
privilege-checked and constraint-checked at each call boundary, and (4) drift is detected
and handled under policy.
Threats
This document considers the following representative threats in multi-hop intent processing:
T1 (Directive Tampering/Substitution):
A malicious or compromised intermediary modifies or replaces derived directives
(e.g., allowed rule sets) to expand privileges or bypass constraints.
An agent or client invokes tools/services without the required privileges, or
smuggles parameters that violate intent constraints.
T3 (Constraint Bypass):
Constraints, invariants, or safety boundaries are dropped, weakened, or misapplied
during translation, planning, or execution.
T4 (Multi-Hop Drift):
Across repeated transformations, delegations, and tool invocations, the realized
actions diverge from the original intent boundary (accidentally or adversarially).
T5 (Monitoring Evasion / False Observations):
Attackers evade detection by suppressing, forging, or selectively presenting
observations used for assurance and drift detection.
Requirements
Based on the threats above, this document identifies the following security requirements:
R1 (Provenance and Authorization Boundary Binding):
The system provides a verifiable binding between the intent, derived directives,
and the applicable authorization boundary, such that unauthorized expansion can be
detected or prevented.
R2 (Chain-of-Custody for Derived Directives):
The system protects derived directives against tampering and substitution
across multi-hop propagation.
R3 (Constraint Validation):
The system validates the intent and/or derived artifacts against applicable
constraints, invariants, policy rules, and safety boundaries before accepting or
executing actions.
R4 (Invocation Validation):
The system validates that an invoker holds the required privileges to invoke
a tool/service and that invocation parameters satisfy intent constraints prior to
and/or at invocation time.
R5 (Non-Bypass Enforcement):
The execution endpoint enforces constraints and authorization boundaries such
that direct/side-path invocation cannot bypass required checks.
R6 (Observability and Auditability):
The system provides sufficient observations and audit evidence to support
compliance assessment, drift detection, and incident investigation.
R7 (Policy-Driven Drift Response):
Upon drift detection or constraint violation, the system supports policy-driven
responses (e.g., deny, degrade, re-confirm, re-negotiate, fallback).
Reference Model
This section introduces a technology-neutral reference model for intent-based requests.
The model is aligned with intent-based system decomposition commonly used in IBN guidance
, while remaining applicable to non-networking domains.
Reference Model for Multi-Hop Intent Processing| Intent Processing Func |
| Originator | Artifact | |
| |---------->| +---------+ +---------+ |
| Intent | | | Intent | |Constrain| |
| Client | | |Transform| |Validate |-+-> Policy/
+--------------+ | +---------+ +---------+ | Constrain
| | Authority
| +---------+ |
| |Invocate | |
| | Gate |--------------+-> Tool/
| +---------+ | Service
+---------------------------+ Provider
^ |
| Observe|
| v
+---------------------------+
| Observer (Monitoring) |
+---------------------------+
]]>
The figure separates User Space from IBS Space for clarity. Deployments may collapse
functions into fewer components or distribute them across multiple agents and services.
Reference Model Entities
The following entities are defined in the reference model:
Intent Originator:
The party whose goals and constraints are to be satisfied (e.g., human user,
application owner, operator, or delegated principal).
Intent Client:
The component that submits intents to an IBS and may carry contextual signals.
Intent Processing Function:
A logical function that performs translation, validation, and orchestration
for intent fulfillment. This function encompasses the Intent Transformer,
Constraint Validator, and Invocation Gate.
Intent Transformer:
A function that transforms intent representations (e.g., natural language to
structured intent, structured intent to constraints/objectives, objectives to
derived directives).
Constraint Validator:
A function that enforces R3 by validating intents and derived artifacts against
constraints, invariants, policy rules, and safety boundaries.
Invocation Gate:
A function that enforces R4 and R5 by privilege-checking and constraint-checking
each tool/service invocation and preventing bypass of required checks.
Policy/Constraint Authority:
A logical source of constraints and policy boundaries (e.g., organizational policy,
compliance rules, safety invariants, subscription/contract limits).
Tool/Service Provider:
A system that executes actions (APIs, workflows, actuators, management functions,
data services).
Observer (Monitoring Function):
A function that collects observations (telemetry, events, measurements)
used for assurance, compliance assessment, and drift detection (R6 and R7).
Operational Overview
This section provides an informative lifecycle overview to contextualize constraint
validation, invocation validation, observation, and drift handling.
The Intent Originator expresses an intent via the Intent Client.
The Intent Client submits an intent artifact to the IBS.
The IBS performs intent translation (Intent Transformer) to derive constraints,
objectives, and candidate directives.
The IBS performs constraint validation (R3) in consultation with the
Policy/Constraint Authority.
The IBS determines one or more tool/service invocations needed for fulfillment.
Prior to each invocation, the IBS performs invocation validation (R4), including
privilege checks and parameter/constraint checks.
The Tool/Service Provider executes the invocation and returns results; side effects
may be irreversible.
The Observer produces observations used by the IBS for assurance and drift detection (R6).
If drift or violations are detected, the IBS applies a policy-driven response (R7),
such as deny, degrade, re-confirm, re-negotiate, or fallback.
Security Scenarios
This section describes representative security scenarios using a consistent template:
Setting, Actors, Assets, Attack Sketch, Impact, and Relevant Requirements. These scenarios
are not exhaustive but illustrate key threat patterns in multi-hop intent processing.
Scenario 1: Directive Tampering and Authorization Boundary ExpansionSetting:An IBS translates an intent into derived directives (e.g., allowed rules) that traverse
multiple intermediaries before reaching an execution endpoint.
Actors:
Intent Originator, Intent Client, IBS, one or more intermediaries (agents/clients),
Tool/Service Provider.
Assets:
Authorization boundary, constraints/invariants, protected resources, audit evidence.
Attack Sketch:
An intermediary modifies derived directives to add operations or widen resource scope.
The modified directives are forwarded to the execution endpoint without effective detection.
The endpoint performs out-of-bound operations (e.g., modifying account state,
accessing other parties' data, disabling safety rules).
Impact:
Privilege escalation, policy bypass, unauthorized side effects, compliance violations.
Relevant Requirements:
R1 (Provenance and Authorization Boundary Binding), R2 (Chain-of-Custody for Derived
Directives), R3 (Constraint Validation), R5 (Non-Bypass Enforcement), R6 (Observability
and Auditability).
Security Considerations
This section provides solution-agnostic security considerations mapped to the scenarios
and requirements. Implementations may realize these considerations using different security
mechanisms (tokens, signatures, attestation, policy engines, or protocol-level bindings).
Scenario-to-Requirement Mapping summarizes the primary mappings between the elaborated scenarios
and security requirements. Note that these mappings are non-exhaustive; additional
requirements may apply depending on deployment context.
Scenario to Requirement Mapping
Scenario
Primary Threats
Key Requirements
1 (Directive Tampering)
T1, T3
R1, R2, R3, R5, R6
Considerations for Scenario 1 (Directive Tampering)
Scenario 1 highlights that derived directives are often more operationally powerful
than the original intent text. Therefore, systems should treat derived directives as
security-relevant artifacts whose integrity and authorization boundary binding should be
protected across hops.
Overview
The core challenge is ensuring that derived directives cannot be tampered with or
substituted in transit, and that execution endpoints can verify the authenticity and
authorization boundary of received directives.
Binding and Custody (R1, R2):
Derived directives should be bound to the intent context and authorization boundary
such that unauthorized expansion or substitution is detectable or preventable across hops.
Pre-Execution Constraint Validation (R3):
Even if directives appear intact, the receiver should validate that the intended
actions remain within constraints and invariants before execution.
Non-Bypass Enforcement (R5):
Execution endpoints should enforce checks such that direct calls cannot bypass
required validation gates.
Audit Evidence (R6):
Systems should produce evidence linking execution decisions to validated directives
and constraints.
Illustrative Procedure
The following procedure is informative and solution-agnostic. Implementations may use
various mechanisms (e.g., signed tokens, cryptographic binding, attestation) to achieve
these objectives.
Directive Derivation and Binding: The IBS derives directives from an intent and
associates them with the applicable authorization boundary. The IBS generates a
cryptographically-protected artifact (e.g., signed token, sealed directive) that
binds the directives to the intent context and authorization scope.
Integrity Protection for Multi-Hop Propagation: Before forwarding directives across
trust boundaries, the system attaches integrity and binding evidence (e.g., digital
signature, MAC, or attestation token) sufficient for downstream verification. This
evidence includes the authorization boundary, constraint set, and issuer identity.
Reception and Verification: Upon receipt, the execution-side gate verifies the
integrity and binding evidence of the received directives. This verification
confirms: (a) the directives have not been tampered with or substituted, (b) the
directives originate from an authorized IBS, and (c) the authorization boundary
matches expected scope.
Constraint Re-Validation: The execution endpoint re-validates the directives against
local constraints, invariants, and policy rules. This step provides defense-in-depth
even if upstream validation was bypassed or compromised.
Enforcement and Audit: If verification or validation fails, the system denies or
degrades execution under policy and records audit evidence. If successful, the system
proceeds with execution and logs the binding evidence, execution decision, and outcomes
for compliance assessment.
This procedure addresses T1 (Directive Tampering/Substitution) and T3 (Constraint Bypass)
by establishing end-to-end integrity and validation across multi-hop processing.
General Security Considerations
Beyond the scenario-specific considerations, the following general principles apply to
intent-based systems:
Trust Boundary Awareness: systems explicitly identify trust boundaries and
apply appropriate security controls at each boundary crossing.
Defense in Depth: validation occur at multiple layers (translation, propagation,
invocation, execution) to provide resilience against bypass or compromise of individual
layers.
Least Privilege: derived directives and invocations are scoped to the minimum
privileges necessary for intent fulfillment.
Fail-Safe Defaults: when validation fails or drift is detected, systems default
to denying actions rather than permitting potentially unsafe operations.
Auditability: all security-relevant decisions and events are logged with
sufficient context to support post-incident investigation and compliance assessment.
IANA ConsiderationsThis document has no IANA actions.Normative ReferencesInformative ReferencesAcknowledgmentsTODO