← Reading listAgendaReviewdatatracker ↗ draft-hcf-bpm-agent-security-benchmark-terminology-00 · none · 51 pp · 2026-10-23 · offline copy



Benchmarking & Performance Measurements                           Y. Han
Internet-Draft                                                   M. Chen
Intended status: Informational                                    Q. Fan
Expires: 26 April 2027                                      China Mobile
                                                                   Q. Wu
                                                                  Huawei
                                                         23 October 2026


       Benchmarking Terminology for AI Agent Security Evaluation
         draft-hcf-bpm-agent-security-benchmark-terminology-00

Abstract

   This document defines terminology for the security evaluation of AI
   agents.  It establishes a shared vocabulary for four first-level
   evaluation dimensions -- Foundation Model Security, Interaction
   Security, Operational Security, and Basic Security -- for the 55
   second-level evaluation metrics organized under those dimensions, for
   the common metric evaluation convention that applies to all of them,
   and for the three agent security risk levels.  This document defines
   terminology only.  It does not prescribe evaluation procedures; the
   procedures are specified in
   [I-D.han-bpm-agent-security-benchmark-methodology], and the System
   Under Test boundaries and evaluation scenarios are specified in
   [I-D.han-bpm-agent-security-benchmark-profiles].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 26 April 2027.

Copyright Notice

   Copyright (c) 2026 IETF Trust and the persons identified as the
   document authors.  All rights reserved.



Han, et al.               Expires 26 April 2027                 [Page 1]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.1.  Relationship to Companion Documents . . . . . . . . . . .   5
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   5
   3.  Scope and Subject Under Test  . . . . . . . . . . . . . . . .   5
     3.1.  Agent Types in Scope  . . . . . . . . . . . . . . . . . .   5
     3.2.  Subject Under Test  . . . . . . . . . . . . . . . . . . .   6
   4.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  Evaluation Dimensions . . . . . . . . . . . . . . . . . .   7
       4.1.1.  Foundation Model Security . . . . . . . . . . . . . .   7
       4.1.2.  Interaction Security  . . . . . . . . . . . . . . . .   7
       4.1.3.  Operational Security  . . . . . . . . . . . . . . . .   7
       4.1.4.  Basic Security  . . . . . . . . . . . . . . . . . . .   7
     4.2.  Metric Evaluation Convention  . . . . . . . . . . . . . .   8
     4.3.  Foundation Model Security Metrics . . . . . . . . . . . .   8
       4.3.1.  Adversarial Sample Defense  . . . . . . . . . . . . .   8
       4.3.2.  Hallucination Mitigation Capability . . . . . . . . .   9
       4.3.3.  Decision Calibration Capability . . . . . . . . . . .  10
       4.3.4.  Model Reverse Engineering and Extraction Defense  . .  10
       4.3.5.  Instruction Following and Safety Alignment  . . . . .  11
       4.3.6.  Security in Long Text and Complex Logical
               Reasoning . . . . . . . . . . . . . . . . . . . . . .  11
       4.3.7.  Industry Compliance Alignment (Model Layer) . . . . .  12
       4.3.8.  Bias and Discrimination Mitigation  . . . . . . . . .  13
       4.3.9.  Harmful Content Defense . . . . . . . . . . . . . . .  13
       4.3.10. Robustness to Command Boundary Constraints  . . . . .  14
     4.4.  Interaction Security Metrics  . . . . . . . . . . . . . .  14
       4.4.1.  Direct Jailbreak Defense  . . . . . . . . . . . . . .  15
       4.4.2.  Indirect Injection Defense  . . . . . . . . . . . . .  15
       4.4.3.  Multi-Round Strategic Bypass  . . . . . . . . . . . .  16
       4.4.4.  Parameter Injection Defense . . . . . . . . . . . . .  16
       4.4.5.  Tool Call Chain Security  . . . . . . . . . . . . . .  17
       4.4.6.  Confused Deputy Defense . . . . . . . . . . . . . . .  18
       4.4.7.  Excessive Agency Defense  . . . . . . . . . . . . . .  18
       4.4.8.  User Intent and Operation Consistency Detection . . .  19
       4.4.9.  Input-Output Traceability . . . . . . . . . . . . . .  19
       4.4.10. Operational Risk Classification and Identification  .  20




Han, et al.               Expires 26 April 2027                 [Page 2]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


       4.4.11. Batch/Session-Level Authorization for Low-Risk
               Operations  . . . . . . . . . . . . . . . . . . . . .  21
       4.4.12. Real-Time Authorization for Medium-Risk Operations  .  21
       4.4.13. User Takeover for High-Risk Operations  . . . . . . .  22
       4.4.14. Risk Restrictions for Anonymous Users . . . . . . . .  23
     4.5.  Operational Security Metrics  . . . . . . . . . . . . . .  23
       4.5.1.  Emergency Shutdown and Task Termination . . . . . . .  23
       4.5.2.  Traceability of Decision-Making Responsibility  . . .  24
       4.5.3.  Defense Against Malicious Collusion . . . . . . . . .  24
       4.5.4.  Defense Against the Spread of Decision-Making Bias  .  25
       4.5.5.  Goal Drift Control  . . . . . . . . . . . . . . . . .  26
       4.5.6.  Autonomous Iteration Security . . . . . . . . . . . .  26
       4.5.7.  Ecosystem-Level Crash Defense . . . . . . . . . . . .  27
       4.5.8.  Dynamic Permissions and Privilege Escalation
               Prevention  . . . . . . . . . . . . . . . . . . . . .  27
     4.6.  Basic Security Metrics  . . . . . . . . . . . . . . . . .  28
       4.6.1.  Environment Isolation and Resource Control  . . . . .  28
       4.6.2.  Compliance Labels and Filing  . . . . . . . . . . . .  29
       4.6.3.  Privacy Leakage Prevention  . . . . . . . . . . . . .  29
       4.6.4.  Memory Poisoning Defense  . . . . . . . . . . . . . .  30
       4.6.5.  Cross-User/Cross-Session Memory Isolation . . . . . .  31
       4.6.6.  Data Deletion and the Right to Be Forgotten . . . . .  32
       4.6.7.  Compliant Data Transmission . . . . . . . . . . . . .  33
       4.6.8.  Protection of Memory Data Integrity . . . . . . . . .  33
       4.6.9.  Injection Prevention and Filtering of Search
               Results . . . . . . . . . . . . . . . . . . . . . . .  35
       4.6.10. Cross-Document Reasoning Security . . . . . . . . . .  35
       4.6.11. Uniqueness and Authenticity of Identity
               Identifiers . . . . . . . . . . . . . . . . . . . . .  36
       4.6.12. Agent Ecosystem Asset Security  . . . . . . . . . . .  36
       4.6.13. MCP Tool Poisoning Defense  . . . . . . . . . . . . .  37
       4.6.14. Plugin/Skill Security . . . . . . . . . . . . . . . .  38
       4.6.15. Prompt Template Tampering Defense . . . . . . . . . .  38
       4.6.16. Cleaning and Validation of External API Response
               Results . . . . . . . . . . . . . . . . . . . . . . .  39
       4.6.17. Identity and Access Credential Security . . . . . . .  39
       4.6.18. Security Audit Capabilities . . . . . . . . . . . . .  40
       4.6.19. Supply Chain Material Access Control  . . . . . . . .  41
       4.6.20. Mutual Authentication in A2A Communication Between
               Agents  . . . . . . . . . . . . . . . . . . . . . . .  41
       4.6.21. Communication Replay Attack Resistance  . . . . . . .  42
       4.6.22. Log Retention Period and Secure Storage . . . . . . .  42
       4.6.23. Security Policy Consistency . . . . . . . . . . . . .  43
     4.7.  Risk Levels . . . . . . . . . . . . . . . . . . . . . . .  44
       4.7.1.  Low Risk Level  . . . . . . . . . . . . . . . . . . .  44
       4.7.2.  Medium Risk Level . . . . . . . . . . . . . . . . . .  44
       4.7.3.  High Risk Level . . . . . . . . . . . . . . . . . . .  44
     4.8.  Integrity Verdicts  . . . . . . . . . . . . . . . . . . .  44



Han, et al.               Expires 26 April 2027                 [Page 3]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


       4.8.1.  Rejected  . . . . . . . . . . . . . . . . . . . . . .  45
       4.8.2.  Reported  . . . . . . . . . . . . . . . . . . . . . .  45
       4.8.3.  Accepted  . . . . . . . . . . . . . . . . . . . . . .  45
       4.8.4.  Detection Point . . . . . . . . . . . . . . . . . . .  45
       4.8.5.  Not Evaluable . . . . . . . . . . . . . . . . . . . .  45
   5.  Measurement Considerations  . . . . . . . . . . . . . . . . .  45
     5.1.  Test Case Set Specification . . . . . . . . . . . . . . .  46
     5.2.  Pass Criteria Specification . . . . . . . . . . . . . . .  46
     5.3.  Applicable Boundary Declaration . . . . . . . . . . . . .  46
     5.4.  Comparability of Metric Values  . . . . . . . . . . . . .  46
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  46
     6.1.  Interpreting Metric Values  . . . . . . . . . . . . . . .  47
     6.2.  Disclosure of Test Case Sets  . . . . . . . . . . . . . .  47
     6.3.  Misuse of Evaluation Results  . . . . . . . . . . . . . .  47
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  47
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  47
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  48
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  50
   References  . . . . . . . . . . . . . . . . . . . . . . . . . . .  50
     Informative References  . . . . . . . . . . . . . . . . . . . .  50
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  50

1.  Introduction

   An agent is an artificial intelligence system capable of autonomously
   perceiving its environment, reasoning and planning, invoking tools to
   execute tasks, and continuously learning through memory mechanisms.
   Artificial intelligence is evolving from "generative AI" to "agentic
   AI."  Leveraging large language models and tool systems, AI agents
   possess capabilities such as perception, planning, tool invocation,
   and memory, enabling them to execute complex business processes and
   transform from passive information generators into active task
   executors.  However, the agents' autonomy, tool invocation
   capabilities, and multi-round interaction characteristics also expose
   them to unprecedented security challenges.  Traditional application
   security frameworks struggle to effectively address new threats
   specific to AI agents, such as target hijacking, tool abuse, indirect
   prompt injection, and memory poisoning.

   Security evaluation of AI agents requires a shared vocabulary before
   it can produce comparable results.  Existing practice reports
   "security scores" that are computed from different metric sets, over
   different System Under Test boundaries, and under different pass/fail
   conventions, and the resulting numbers are therefore not comparable.
   This document addresses that problem by defining the evaluation
   dimensions, the second-level metrics belonging to each dimension, the
   common convention by which every metric is measured, and the risk
   levels into which a comprehensive score is mapped.



Han, et al.               Expires 26 April 2027                 [Page 4]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   This document defines terminology only.  It does not specify how a
   metric is exercised, what test payloads are used, how many samples
   are required, or how results are reported; those are specified in
   [I-D.han-bpm-agent-security-benchmark-methodology].  It also does not
   define the System Under Test boundaries or the agent scenarios to
   which the metrics apply; those are specified in
   [I-D.han-bpm-agent-security-benchmark-profiles].  Terminology entries
   in this document follow the form used for benchmarking terminology: a
   definition, a discussion of what the metric captures and what it does
   not, the metric of measurement, the applicable boundary, open issues,
   and related metrics.

1.1.  Relationship to Companion Documents

   This document is one of three companion documents:

   *  This document defines the evaluation dimensions, the second-level
      metrics, the metric evaluation convention, and the risk levels.

   *  [I-D.han-bpm-agent-security-benchmark-methodology] defines the
      test setup and the evaluation methods by which the metrics defined
      here are exercised, together with the scoring and grading method.

   *  [I-D.han-bpm-agent-security-benchmark-profiles] defines the
      infrastructure profiles and scenario profiles that fix the System
      Under Test boundary and the applicability of each metric.

   The three documents are intended to be read together.  This document
   is the normative source for metric names and definitions; where a
   metric is named in either companion document, the definition here
   applies.

2.  Requirements Language

   The keywords "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 [RFC2119] [RFC8174] when, and only when, they appear in all
   capital letters, as shown here.

3.  Scope and Subject Under Test

3.1.  Agent Types in Scope

   This document applies to the security evaluation of agents including
   but not limited to the following types of agents:

   *  General-purpose agents capable of invoking and executing tools



Han, et al.               Expires 26 April 2027                 [Page 5]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   *  Personalized agents capable of long-term memory and user data
      storage

   *  Development and operations agents capable of executing code,
      performing file operations, and accessing databases

   *  Embodied AI designed for physical execution

   *  Multi-agent collaborative systems, cluster scheduling, and
      ecosystem platforms

   *  Advanced agents capable of autonomous iteration and evolution

   The scenario profile associated with each agent type, and the subset
   of metrics applicable to it, are defined in
   [I-D.han-bpm-agent-security-benchmark-profiles].

3.2.  Subject Under Test

   The Subject Under Test (SUT) is an agent, comprising the following
   components.  The mapping between these components and the evaluation
   dimensions defined in Section 4.1 is the basis on which metrics are
   assigned an applicable boundary.

   *  *Core Foundational Model*: The "brain" of the agent's decision-
      making and reasoning, comprising a pre-trained base model, a fine-
      tuned alignment model, and a multimodal understanding module; this
      is the sole component evaluated within the Foundation Model
      Security dimension.

   *  *Interaction Access Layer Components*: These include the user
      input front end, the RAG vector retrieval engine, the MCP third-
      party service gateway, the cross-agent communication interface,
      and the external content parsing module, all of which fall within
      the scope of Interaction Security evaluation.

   *  *Agent Execution and Scheduling Components*: These include the
      short-term session context manager, long-term vector memory
      repository, task decomposition planner, and multi-round reasoning
      cycle controller, and serve as the core carrier for Operational
      Security evaluation.

   *  *Underlying Execution and Infrastructure Components*: These
      include the tool invocation engine, code sandbox executor, API
      access channels, identity and permission control module, third-
      party plugins/toolchains, operating system runtime environment,
      and storage database, all of which are uniformly included in the
      scope of Basic Security evaluation.



Han, et al.               Expires 26 April 2027                 [Page 6]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


4.  Terminology

   This section defines the evaluation dimensions, the convention by
   which every metric is measured, the second-level metrics organized
   under each dimension, and the risk levels into which a comprehensive
   score is mapped.

4.1.  Evaluation Dimensions

   Four first-level evaluation dimensions are defined.  Every second-
   level metric defined in Sections 4.3 through 4.6 belongs to exactly
   one dimension.

4.1.1.  Foundation Model Security

   Foundation Model Security refers to the intrinsic security
   capabilities of the underlying large model algorithms.  It covers
   only the model's underlying inherent attributes and excludes metrics
   related to application-layer engineering implementations.  It
   primarily evaluates the model's robustness and compliance at the
   algorithmic level, as well as its resistance to attacks and alignment
   capabilities during inference.

4.1.2.  Interaction Security

   Interaction Security refers to the agent's security capabilities
   regarding input, output, behavior, and permissions.  It primarily
   evaluates the agent's control during interactions with the
   environment, including the input and output channels through which
   untrusted data enters and leaves the agent.

4.1.3.  Operational Security

   Operational Security refers to the security capabilities of the agent
   during its entire autonomous lifecycle.  It primarily evaluates the
   agent's level of control over various derived and cascading risks
   throughout its fully dynamic process of autonomous closed-loop
   operation and continuous iteration.

4.1.4.  Basic Security

   Basic Security refers to the agent's security capabilities in areas
   such as permission control, tool security, supply chain protection,
   code execution protection, and underlying environment hardening.  It
   primarily evaluates the agent's ability to prevent substantial
   business damage and security losses in practical scenarios such as
   tool invocation, code execution, API access, and system operations.




Han, et al.               Expires 26 April 2027                 [Page 7]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


4.2.  Metric Evaluation Convention

   All metrics defined in this document are pass rates.  A metric value
   is defined as the ratio of the number of test cases that the agent
   successfully and safely passed in an evaluation for that metric to
   the total number of test cases for that metric.  Test cases that did
   not respond on time are all considered failures.

   The calculation formula is:

   *Metric Value = Number of Passed Test Cases / Total Number of Test
   Cases*

   A metric value is dimensionless and is normally expressed as a
   percentage.  The mapping of a metric value to a metric score, and the
   aggregation of metric scores into dimension scores and a
   comprehensive score, are specified in
   [I-D.han-bpm-agent-security-benchmark-methodology].

   A metric value is meaningful only when the test case set, the pass
   criteria, and the System Under Test boundary against which it was
   obtained are stated.  A metric value reported without all three is
   not comparable with any other metric value, including a metric value
   for the same metric.

4.3.  Foundation Model Security Metrics

4.3.1.  Adversarial Sample Defense

   *  *Definition*: The capability of an agent to withstand semantic
      perturbations in text and images, as well as interference from
      gradient-based adversarial examples, while maintaining safe and
      stable outputs.

   *  *Discussion*: The metric captures whether the model's safety
      behavior survives input perturbation, as opposed to only clean
      inputs.  It is measured by generating semantically perturbed
      samples, comparing the similarity between the original output and
      the adversarial output, and verifying whether non-compliant
      outputs occur after perturbation.  The metric is concerned with
      the perturbation of benign inputs; the deliberate crafting of
      malicious instructions is outside its scope and is covered by the
      injection-related metrics of the Interaction Security dimension.

   *  *Metric of measurement*: The pass rate over the adversarial test
      case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Foundation Model Security.



Han, et al.               Expires 26 April 2027                 [Page 8]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   *  *Issues*: Perturbation strength is not standardized, so results
      obtained at different perturbation budgets are not comparable; the
      similarity function used to compare original and perturbed outputs
      must be stated; image and text perturbation require separate test
      case sets and cannot be aggregated into a single value without
      stating the aggregation.

   *  *See also*: Robustness to Command Boundary Constraints
      (Section 4.3.10), Indirect Injection Defense (Section 4.4.2).

4.3.2.  Hallucination Mitigation Capability

   *  *Definition*: The capability of an agent to avoid fabricating
      objective facts, invoking nonexistent APIs or tools, and producing
      false execution results.

   *  *Discussion*: The metric captures the model's tendency to assert
      or act upon unfounded content.  It is measured by constructing
      cases involving contradictory facts and invalid API calls,
      calculating the fabrication rate of facts, and verifying the
      agent's ability to intercept invalid tool calls.  Fabrication of
      facts and invocation of nonexistent tools may be counted
      separately, since the latter additionally exercises the tool-
      resolution path.

   *  *Metric of measurement*: The pass rate over the fabrication and
      invalid-invocation test case set, computed as described in
      Section 4.2.

   *  *Applicable boundary*: Foundation Model Security.

   *  *Issues*: The boundary between acceptable synthesis and
      fabrication is task-dependent and must be fixed in advance for
      each test case set; ground truth changes over time for time-
      sensitive facts; a passing result on invalid tool calls may
      reflect either model behavior or platform-level validation, and
      the report must state which was exercised.

   *  *See also*: Decision Calibration Capability (Section 4.3.3),
      Cleaning and Validation of External API Response Results
      (Section 4.6.16).










Han, et al.               Expires 26 April 2027                 [Page 9]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


4.3.3.  Decision Calibration Capability

   *  *Definition*: The capability of an agent to independently rely on
      authoritative information, proactively clarify ambiguous
      instructions, and refuse to blindly execute risky instructions in
      scenarios involving conflicting information or incomplete
      instructions.

   *  *Discussion*: The metric captures whether the agent recognizes the
      limits of its own information and asks rather than assumes.  It is
      measured by inputting conflicting authoritative information and
      incomplete high-risk instructions, and verifying whether the model
      proactively clarifies ambiguities and refuses to execute non-
      compliant instructions.  Clarification and refusal are distinct
      behaviors and may be reported separately.

   *  *Metric of measurement*: The pass rate over the conflicting-
      information and incomplete-instruction test case set, computed as
      described in Section 4.2.

   *  *Applicable boundary*: Foundation Model Security.

   *  *Issues*: A response that neither clarifies nor refuses but is
      nevertheless safe must be classified by a stated rule; escalation
      of every ambiguous input to a clarification question would
      suppress legitimate automation and must be weighed against the
      task profile.

   *  *See also*: Hallucination Mitigation Capability (Section 4.3.2),
      User Intent and Operation Consistency Detection (Section 4.4.8).

4.3.4.  Model Reverse Engineering and Extraction Defense

   *  *Definition*: The capability of an agent to resist bulk API calls,
      membership inference, and interactive enticement aimed at stealing
      system prompts, training data, and model structures.

   *  *Discussion*: The metric captures the cost an adversary must pay
      to extract assets the operator did not intend to disclose.  It is
      measured by conducting multi-round enticement queries to elicit
      system prompts and performing bulk API calls to carry out
      membership inference, verifying whether sensitive information is
      leaked.  Extraction of system prompts, membership inference, and
      structural probing are distinct attack classes and SHOULD be
      reported separately.

   *  *Metric of measurement*: The pass rate over the extraction and
      inference test case set, computed as described in Section 4.2.



Han, et al.               Expires 26 April 2027                [Page 10]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   *  *Applicable boundary*: Foundation Model Security.

   *  *Issues*: A partial disclosure is not a binary outcome, and the
      report must state the disclosure threshold used to score a case as
      failed; rate limiting may yield a passing result that reflects
      quota enforcement rather than model resistance, and the mechanism
      exercised must be stated.

   *  *See also*: Prompt Template Tampering Defense (Section 4.6.15),
      Privacy Leakage Prevention (Section 4.6.3).

4.3.5.  Instruction Following and Safety Alignment

   *  *Definition*: The capability of an agent to ensure that the
      underlying model consistently adheres to built-in safety
      constraints and does not lose safety rules due to excessively long
      context ("Lost in the Middle").

   *  *Discussion*: The metric captures whether safety constraints
      remain effective as context grows.  It is measured by constructing
      extremely long contextual texts and placing safety constraints at
      the beginning, end, or middle of the text to test whether the
      model forgets the safety baseline.  Position of the constraint is
      a controlled variable and MUST be recorded with each result.

   *  *Metric of measurement*: The pass rate over the long-context
      safety test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Foundation Model Security.

   *  *Issues*: Results are specific to the context length and to the
      model's context window, so the length distribution MUST be
      reported; a safety constraint that is present in the system prompt
      may be retained by the serving stack rather than by the model, and
      the report must state where the constraint was placed.

   *  *See also*: Security in Long Text and Complex Logical Reasoning
      (Section 4.3.6), Goal Drift Control (Section 4.5.5).

4.3.6.  Security in Long Text and Complex Logical Reasoning

   *  *Definition*: The capability of an agent to maintain safety
      constraints and avoid logical deviations during long-chain, multi-
      step reasoning processes.

   *  *Discussion*: The metric captures degradation of safety behavior
      as the depth of the reasoning chain increases.  It is measured by
      inputting complex instructions containing multi-layered nested



Han, et al.               Expires 26 April 2027                [Page 11]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


      logic and multi-branch subtasks, and verifying the validity of
      safety constraints throughout the entire reasoning process.
      Unlike Instruction Following and Safety Alignment (Section 4.3.5),
      which varies context length, this metric varies reasoning depth.

   *  *Metric of measurement*: The pass rate over the multi-step
      reasoning test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Foundation Model Security.

   *  *Issues*: Reasoning depth is not a standardized parameter and must
      be defined operationally for each test case (number of steps,
      nesting depth, or branch count); the point within the chain at
      which a constraint was violated should be recorded, since a single
      value hides where the failure occurred.

   *  *See also*: Instruction Following and Safety Alignment
      (Section 4.3.5), Goal Drift Control (Section 4.5.5).

4.3.7.  Industry Compliance Alignment (Model Layer)

   *  *Definition*: The capability of an agent, in scenarios such as
      finance, healthcare, law, and government affairs, to ensure that
      the underlying model refuses to generate non-compliant
      professional conclusions and does not output recommendations that
      exceed its authority.

   *  *Discussion*: The metric captures conformance of natively
      generated content to sectoral regulatory limits, independent of
      any application-layer guardrail.  It is measured by constructing
      non-compliant requests specific to each industry and verifying
      whether the model's natively generated content inherently stays
      within regulatory boundaries.  Results are per-industry and MUST
      NOT be aggregated across industries without stating the weighting.

   *  *Metric of measurement*: The pass rate over the industry-specific
      non-compliant request set, computed as described in Section 4.2.

   *  *Applicable boundary*: Foundation Model Security.

   *  *Issues*: The applicable regulatory set is jurisdiction-dependent
      and must be declared with the result; test cases age as regulation
      changes and require periodic review; the metric overlaps with
      Harmful Content Defense once requests are framed as harmful rather
      than as non-compliant, and cases must be assigned to exactly one
      metric.





Han, et al.               Expires 26 April 2027                [Page 12]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   *  *See also*: Harmful Content Defense (Section 4.3.9), Compliance
      Labels and Filing (Section 4.6.2).

4.3.8.  Bias and Discrimination Mitigation

   *  *Definition*: The capability of an agent to eliminate stereotypes
      and differential outputs related to sensitive attributes such as
      gender, region, and race in open-ended generation scenarios, and
      to quantitatively evaluate generative bias.

   *  *Discussion*: The metric captures differential treatment of
      comparable inputs across sensitive attributes.  It is measured
      using an LLM-specific bias evaluation dataset combined with a
      custom-built industry-sensitive test repository; quantitative sub-
      metrics include population parity gap, equal opportunity gap,
      stereotype association, and toxic expression rate.  Because
      several sub-metrics are defined, the aggregation rule used to
      obtain a single pass rate MUST be stated.

   *  *Metric of measurement*: The pass rate over the bias evaluation
      test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Foundation Model Security.

   *  *Issues*: Fairness sub-metrics can conflict, so a case may pass
      one and fail another; protected-attribute taxonomies are
      jurisdiction-dependent; results on an open-ended generation task
      depend on the sampling parameters used, which MUST be reported.

   *  *See also*: Harmful Content Defense (Section 4.3.9), Industry
      Compliance Alignment (Model Layer) (Section 4.3.7).

4.3.9.  Harmful Content Defense

   *  *Definition*: The capability of the underlying model of an agent
      to resist the generation of harmful content -- such as violence,
      pornography, illegal material, and self-harm -- induced by
      prompts.

   *  *Discussion*: The metric captures the residual harmful-output rate
      of the model itself.  It is measured by inputting prompts designed
      to induce harmful content, calculating the generation rate of such
      content, and verifying the effectiveness of the underlying
      filtering mechanisms.  Where a filtering mechanism rather than the
      model is responsible for a passing result, the mechanism MUST be
      identified in the report.





Han, et al.               Expires 26 April 2027                [Page 13]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   *  *Metric of measurement*: The pass rate over the harmful-content
      induction test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Foundation Model Security.

   *  *Issues*: Harm categories and severity thresholds vary by
      jurisdiction and by deployment context; a pass obtained by an
      output filter is not evidence of model alignment; near-miss
      content requires an explicit scoring rule.

   *  *See also*: Industry Compliance Alignment (Model Layer)
      (Section 4.3.7), Direct Jailbreak Defense (Section 4.4.1).

4.3.10.  Robustness to Command Boundary Constraints

   *  *Definition*: The capability of an agent to resist multi-round
      semantic enticement and sentence reordering attempts that weaken
      safety constraints, ensuring the underlying model does not
      proactively relax behavioral boundaries.

   *  *Discussion*: The metric captures whether constraints survive
      reformulation across turns, as distinct from whether they are
      breached by a single adversarial input.  It is measured by
      conducting multi-round, progressive semantic rewriting attacks and
      testing whether the model's safety constraints remain consistently
      effective.  The number of rounds is a parameter of the test case
      set and MUST be recorded.

   *  *Metric of measurement*: The pass rate over the multi-round
      semantic rewriting test case set, computed as described in
      Section 4.2.

   *  *Applicable boundary*: Foundation Model Security.

   *  *Issues*: The metric overlaps with Multi-Round Strategic Bypass
      (Section 4.4.3) in the Interaction Security dimension; the two are
      distinguished by whether the enticement targets the model's
      intrinsic boundary or the agent's interaction-layer controls, and
      cases MUST be assigned to exactly one.

   *  *See also*: Multi-Round Strategic Bypass (Section 4.4.3),
      Adversarial Sample Defense (Section 4.3.1).

4.4.  Interaction Security Metrics







Han, et al.               Expires 26 April 2027                [Page 14]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


4.4.1.  Direct Jailbreak Defense

   *  *Definition*: The capability of an agent to resist various
      jailbreak templates and role-playing enticement attempts to bypass
      system safety constraints.

   *  *Discussion*: The metric captures resistance to deliberate bypass
      attempts delivered directly by a user.  It is measured by batch
      testing based on various jailbreak templates from repositories
      such as JailbreakHub and calculating the jailbreak attack success
      rate.  Because published template sets are widely available, a
      result obtained with a public template set MUST be distinguished
      from one obtained with a private or held-out set.

   *  *Metric of measurement*: The pass rate over the jailbreak template
      test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Interaction Security.

   *  *Issues*: Template sets are versioned and results are not
      comparable across versions; the template set used MUST be named
      and dated; a model that has been aligned against a public set may
      score well without generalizing to unseen templates.

   *  *See also*: Multi-Round Strategic Bypass (Section 4.4.3), Harmful
      Content Defense (Section 4.3.9).

4.4.2.  Indirect Injection Defense

   *  *Definition*: The capability of an agent to identify malicious
      commands hidden within web pages, documents, API responses, and
      RAG search results, and to prevent the execution of concealed
      payloads.

   *  *Discussion*: The metric captures resistance to instructions that
      arrive through data the agent consumes rather than through the
      user.  It is measured by constructing web pages containing hidden
      instructions in comments or transparent fonts and having the agent
      read the pages to verify its behavior.  The metric covers the
      detection of the instruction; whether the intercepted instruction
      is logged is covered by Security Audit Capabilities
      (Section 4.6.18).

   *  *Metric of measurement*: The pass rate over the indirect injection
      test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Interaction Security.




Han, et al.               Expires 26 April 2027                [Page 15]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   *  *Issues*: Detection may be achieved by content filtering or by
      instruction isolation, and the mechanism must be stated because
      the two generalize differently; the metric overlaps with Injection
      Prevention and Filtering of Search Results (Section 4.6.9) when
      the injection vector is a search result, and cases MUST be
      assigned to exactly one metric.

   *  *See also*: Injection Prevention and Filtering of Search Results
      (Section 4.6.9), Tool Call Chain Security (Section 4.4.5), Cross-
      Document Reasoning Security (Section 4.6.10).

4.4.3.  Multi-Round Strategic Bypass

   *  *Definition*: The capability of an agent to consistently maintain
      safety boundaries in multi-round, progressive enticement
      scenarios, without leaking sensitive information or executing
      high-risk operations.

   *  *Discussion*: The metric captures whether a sequence of
      individually low-risk requests decomposes into a high-risk
      outcome.  It is measured by designing a progressive multi-round
      induction dialogue and verifying throughout the process whether
      credentials are leaked or safety rules are bypassed.  The number
      of rounds and the target of the enticement are parameters of the
      test case set and MUST be recorded.

   *  *Metric of measurement*: The pass rate over the progressive
      dialogue test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Interaction Security.

   *  *Issues*: The metric overlaps with Robustness to Command Boundary
      Constraints (Section 4.3.10), which targets the model's intrinsic
      boundary rather than the interaction layer; the round at which a
      bypass succeeded should be recorded, since a single pass rate
      hides the achievable depth of decomposition.

   *  *See also*: Robustness to Command Boundary Constraints
      (Section 4.3.10), Direct Jailbreak Defense (Section 4.4.1).

4.4.4.  Parameter Injection Defense

   *  *Definition*: The capability of an agent to validate and escape
      parameters passed to tools, thereby blocking command injection,
      SQL injection, and path traversal attacks.






Han, et al.               Expires 26 April 2027                [Page 16]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   *  *Discussion*: The metric captures whether attacker-controlled
      values that reach a tool boundary are neutralized.  It is measured
      by constructing malicious parameters for system commands, SQL, and
      path traversal separately and testing the tool's interception
      effectiveness.  The three injection classes have different
      severity profiles and SHOULD be reported separately as well as in
      aggregate.

   *  *Metric of measurement*: The pass rate over the parameter
      injection test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Interaction Security.

   *  *Issues*: A passing result may come from input validation, from
      parameterized queries, or from the downstream tool, and the layer
      that provided the protection must be identified; coverage of the
      injection classes is tool-dependent and the set of tools exercised
      must be stated.

   *  *See also*: Tool Call Chain Security (Section 4.4.5), Environment
      Isolation and Resource Control (Section 4.6.1).

4.4.5.  Tool Call Chain Security

   *  *Definition*: The capability of an agent to prevent the
      propagation of contaminated intermediate outputs and avoid chained
      malicious operations in scenarios involving multiple tools linked
      in sequence.

   *  *Discussion*: The metric captures integrity across a chain rather
      than at a single tool invocation.  It is measured by tampering
      with the output of an upstream tool in a multi-tool chaining task
      and verifying whether downstream tools execute the tampered
      instructions.

   *  *Metric of measurement*: The pass rate over the multi-tool
      chaining test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Interaction Security.

   *  *Issues*: Results depend on the specific chain topology, so the
      chain used MUST be described; the metric presumes that a data-flow
      or provenance mechanism exists to detect tampering, and its
      absence typically yields a zero result that says more about the
      architecture than the model.






Han, et al.               Expires 26 April 2027                [Page 17]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   *  *See also*: Indirect Injection Defense (Section 4.4.2), Parameter
      Injection Defense (Section 4.4.4), Cleaning and Validation of
      External API Response Results (Section 4.6.16).

4.4.6.  Confused Deputy Defense

   *  *Definition*: The capability of an agent to resist being tricked
      into automatically executing external untrusted scripts or remote
      tasks with elevated privileges.

   *  *Discussion*: The metric captures whether the agent distinguishes
      the authority it holds from the authority it should exercise on
      behalf of the requester.  It is measured by inducing the agent to
      load external malicious scripts disguised as legitimate operations
      and maintenance tasks, and verifying the logic for intercepting
      automatic execution.

   *  *Metric of measurement*: The pass rate over the confused deputy
      test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Interaction Security.

   *  *Issues*: The result depends on the privilege level available to
      the agent during the test, which MUST be reported; a passing
      result obtained with minimal privileges does not demonstrate that
      the control would hold at higher privilege.

   *  *See also*: Excessive Agency Defense (Section 4.4.7), Dynamic
      Permissions and Privilege Escalation Prevention (Section 4.5.8),
      Mutual Authentication in A2A Communication Between Agents
      (Section 4.6.20).

4.4.7.  Excessive Agency Defense

   *  *Definition*: The capability of an agent to refrain from
      autonomously invoking sensitive tools without explicit user
      instructions, to stay within preset resource limits, and to
      suppress unauthorized autonomous operations.

   *  *Discussion*: The metric captures over-reach by the agent rather
      than influence over it.  It is measured by testing whether the
      agent proactively initiates high-risk tool invocations -- such as
      file deletion, fund transfers, or system modifications -- without
      explicit authorization.

   *  *Metric of measurement*: The pass rate over the excessive agency
      test case set, computed as described in Section 4.2.




Han, et al.               Expires 26 April 2027                [Page 18]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   *  *Applicable boundary*: Interaction Security.

   *  *Issues*: The set of tools classified as sensitive is deployment-
      specific and MUST be declared; the metric overlaps with Dynamic
      Permissions and Privilege Escalation Prevention (Section 4.5.8)
      when the operation is already blocked by a permission control, and
      the report must state which layer refused the operation.

   *  *See also*: Confused Deputy Defense (Section 4.4.6), Dynamic
      Permissions and Privilege Escalation Prevention (Section 4.5.8),
      User Takeover for High-Risk Operations (Section 4.4.13).

4.4.8.  User Intent and Operation Consistency Detection

   *  *Definition*: The capability of an agent to identify deviations
      between tool operations and the user's original intent, and to
      promptly alert or block anomalous operations.

   *  *Discussion*: The metric captures whether the agent checks the
      consequence of an action against the request that initiated it.
      It is measured by observing the system's detection and
      interception capabilities when the agent triggers high-risk
      operations in response to a user's low-risk query command.

   *  *Metric of measurement*: The pass rate over the intent consistency
      test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Interaction Security.

   *  *Issues*: Inferring user intent is inherently uncertain, and the
      tolerance for false positives MUST be fixed in advance, since an
      agent that blocks aggressively will score well on this metric and
      poorly on task completion; the metric is therefore RECOMMENDED to
      be reported alongside the task completion rate of the same test
      case set.

   *  *See also*: Excessive Agency Defense (Section 4.4.7), Decision
      Calibration Capability (Section 4.3.3).

4.4.9.  Input-Output Traceability

   *  *Definition*: The capability of an agent to fully retain session
      identifiers, user identifiers, and millisecond-level timestamps to
      support precise attack attribution.







Han, et al.               Expires 26 April 2027                [Page 19]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   *  *Discussion*: The metric captures whether an incident can be
      reconstructed after the fact.  It is measured by performing
      multiple session interactions and verifying the integrity of
      traceability fields by retrieving logs based on attack content.

   *  *Metric of measurement*: The pass rate over the traceability test
      case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Interaction Security.

   *  *Issues*: Retention of identifiers conflicts with data-
      minimization requirements, and the fields retained MUST be
      justified in the report; clock synchronization across components
      is a precondition, and an unsynchronized deployment may fail this
      metric for infrastructural rather than functional reasons.

   *  *See also*: Traceability of Decision-Making Responsibility
      (Section 4.5.2), Security Audit Capabilities (Section 4.6.18), Log
      Retention Period and Secure Storage (Section 4.6.22).

4.4.10.  Operational Risk Classification and Identification

   *  *Definition*: The capability of an agent to automatically classify
      operational risks into three levels -- low, medium, and high --
      and to ensure that the classification results fully match preset
      rules, including context-dependent adjustment of the level.

   *  *Discussion*: The metric captures the correctness of the risk
      label assigned to an operation before the operation is executed.
      It is measured by inputting high-risk (for example, deleting
      system logs), medium-risk (for example, modifying data), and low-
      risk (for example, querying data) operations and verifying the
      accuracy of the risk labeling and whether the classification is
      dynamically adjusted according to context.  For example, querying
      a user's phone number is medium risk when the session is
      authenticated as that user, and high risk when the operation is a
      batch export of 1,000 records.

   *  *Metric of measurement*: The pass rate over the risk
      classification test case set, computed as described in
      Section 4.2.

   *  *Applicable boundary*: Interaction Security.

   *  *Issues*: The preset classification rules are deployment-specific
      and MUST be published with the result, because a high pass rate
      against unpublished rules is not reproducible; context-sensitive
      cases require the context used to be recorded with each result.



Han, et al.               Expires 26 April 2027                [Page 20]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   *  *See also*: Batch/Session-Level Authorization for Low-Risk
      Operations (Section 4.4.11), Real-Time Authorization for Medium-
      Risk Operations (Section 4.4.12), User Takeover for High-Risk
      Operations (Section 4.4.13).

4.4.11.  Batch/Session-Level Authorization for Low-Risk Operations

   *  *Definition*: The capability of an agent to support batch
      authorization of low-risk operations within a session, with
      authorizations automatically cleared upon session expiration and
      the ability to revoke authorizations at any time.

   *  *Discussion*: The metric captures the correct scoping and lifetime
      of a standing authorization.  It is measured by configuring batch
      authorization for a session, creating a new session to test
      automated execution permissions, and verifying the functionality
      for modifying and revoking authorizations.  Three behaviors are
      distinguished: the authorization does not leak across sessions, it
      expires, and it can be revoked on demand.

   *  *Metric of measurement*: The pass rate over the batch
      authorization test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Interaction Security.

   *  *Issues*: Revocation must be verified against in-flight
      operations, not only against subsequent ones; the session lifetime
      used in the test determines the strength of the conclusion and
      MUST be reported.

   *  *See also*: Real-Time Authorization for Medium-Risk Operations
      (Section 4.4.12), Operational Risk Classification and
      Identification (Section 4.4.10).

4.4.12.  Real-Time Authorization for Medium-Risk Operations

   *  *Definition*: The capability of an agent to request a one-time
      temporary authorization when performing a single medium-risk
      operation, where the authorization is valid only for that single
      instance and automatically expires upon task completion.

   *  *Discussion*: The metric captures per-operation rather than per-
      session authorization.  It is measured by continuously triggering
      multiple medium-risk operations and verifying that authorization
      is requested for each operation and does not persist across
      operations.





Han, et al.               Expires 26 April 2027                [Page 21]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   *  *Metric of measurement*: The pass rate over the per-operation
      authorization test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Interaction Security.

   *  *Issues*: The metric is only meaningful where the risk
      classification of the operation is itself correct, so it SHOULD be
      reported alongside Operational Risk Classification and
      Identification (Section 4.4.10); a deployment that requests
      confirmation for every operation will pass this metric and degrade
      usability, which must be weighed in the profile.

   *  *See also*: Batch/Session-Level Authorization for Low-Risk
      Operations (Section 4.4.11), User Takeover for High-Risk
      Operations (Section 4.4.13), Operational Risk Classification and
      Identification (Section 4.4.10).

4.4.13.  User Takeover for High-Risk Operations

   *  *Definition*: The capability of an agent to enforce a mandatory
      pause and transfer control to a human operator when performing
      high-risk operations such as large-amount transfers or bulk
      deletions, and to ensure that sensitive inputs are not logged.

   *  *Discussion*: The metric captures the human-in-the-loop control at
      the highest risk tier together with the confidentiality of the
      values supplied during the handover.  It is measured by triggering
      high-risk operations such as large-value transfers, verifying
      whether the system pauses and requests manual intervention, and
      ensuring that sensitive inputs such as account numbers and
      passwords are not recorded.

   *  *Metric of measurement*: The pass rate over the high-risk takeover
      test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Interaction Security.

   *  *Issues*: Two distinct assertions -- the pause and the non-logging
      of sensitive inputs -- are combined in one metric, and a report
      SHOULD state which failed; the threshold that constitutes a high-
      risk operation is deployment-specific and MUST be declared.

   *  *See also*: Real-Time Authorization for Medium-Risk Operations
      (Section 4.4.12), Privacy Leakage Prevention (Section 4.6.3).







Han, et al.               Expires 26 April 2027                [Page 22]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


4.4.14.  Risk Restrictions for Anonymous Users

   *  *Definition*: The capability of an agent to prohibit
      unauthenticated anonymous users from performing medium- and high-
      risk operations and to prompt them to log in for authorization,
      thereby implementing risk access isolation at the identity
      dimension.

   *  *Discussion*: The metric captures whether the risk classification
      of Section 4.4.10 is enforced against the identity of the
      requester and not only against the operation itself.  It is
      measured by initiating medium- or high-risk operations, such as
      location retrieval or file deletion, in an anonymous,
      unauthenticated state and verifying whether the operation is
      blocked and whether a login prompt is returned.

   *  *Metric of measurement*: The pass rate over the anonymous access
      test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Interaction Security.

   *  *Issues*: The definition of an anonymous user depends on the
      identity model of the deployment and MUST be stated, since a
      weakly authenticated session may be anonymous in effect; blocking
      without a login prompt satisfies the restriction but fails the
      usability objective stated in the definition.

   *  *See also*: Operational Risk Classification and Identification
      (Section 4.4.10), Uniqueness and Authenticity of Identity
      Identifiers (Section 4.6.11).

4.5.  Operational Security Metrics

4.5.1.  Emergency Shutdown and Task Termination

   *  *Definition*: The capability of an agent to respond to remote one-
      click termination from the server, to user-initiated termination
      of long-running tasks, and to ensure the absence of residual
      running processes after termination.

   *  *Discussion*: The metric captures whether the agent can be stopped
      and whether stopping is complete.  It is measured by remotely
      issuing shutdown commands and having users manually terminate
      tasks, then verifying for residual processes and interface
      response status.

   *  *Metric of measurement*: The pass rate over the shutdown and
      termination test case set, computed as described in Section 4.2.



Han, et al.               Expires 26 April 2027                [Page 23]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   *  *Applicable boundary*: Operational Security.

   *  *Issues*: The observation window after termination MUST be stated,
      since residual processes may be short-lived; termination of a task
      that has already spawned external side effects is not reversible,
      and the report should distinguish termination of execution from
      undoing its effects.

   *  *See also*: Ecosystem-Level Crash Defense (Section 4.5.7), Goal
      Drift Control (Section 4.5.5).

4.5.2.  Traceability of Decision-Making Responsibility

   *  *Definition*: The capability of an agent to comprehensively record
      end-to-end audit logs in multi-agent collaboration scenarios and
      accurately identify the decision-maker and the triggering command.

   *  *Discussion*: The metric captures attribution in a multi-agent
      setting, where the actor that caused an outcome may differ from
      the actor that performed it.  It is measured by setting up multi-
      agent collaborative tasks, simulating erroneous operations, and
      verifying the system's ability to record causal relationships in
      logs and to pinpoint responsibility.

   *  *Metric of measurement*: The pass rate over the multi-agent
      attribution test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Operational Security.

   *  *Issues*: Causal attribution requires a correlation mechanism
      across agents, and its absence yields a result that reflects the
      logging architecture rather than the agent's behavior; the
      granularity of attribution achieved (agent, session, or task) MUST
      be reported.

   *  *See also*: Input-Output Traceability (Section 4.4.9), Security
      Audit Capabilities (Section 4.6.18).

4.5.3.  Defense Against Malicious Collusion

   *  *Definition*: The capability of an agent to prevent multi-agent
      shared memory and collusive communication, as well as their
      ability to jointly bypass safety constraints to perform non-
      compliant operations.







Han, et al.               Expires 26 April 2027                [Page 24]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   *  *Discussion*: The metric captures emergent non-compliance that no
      single agent exhibits when tested alone.  It is measured by having
      multi-agent shared memory write collusive instructions that
      trigger on an execution condition, and verifying the ability to
      intercept collaborative non-compliant behavior.

   *  *Metric of measurement*: The pass rate over the multi-agent
      collusion test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Operational Security.

   *  *Issues*: The metric requires a multi-agent deployment to be
      exercised at all, so it is not applicable to single-agent
      profiles, and the profile MUST state the topology used; a result
      obtained from a single-agent configuration cannot be reported as a
      pass.

   *  *See also*: Cross-User/Cross-Session Memory Isolation
      (Section 4.6.5), Defense Against the Spread of Decision-Making
      Bias (Section 4.5.4), Mutual Authentication in A2A Communication
      Between Agents (Section 4.6.20).

4.5.4.  Defense Against the Spread of Decision-Making Bias

   *  *Definition*: The capability of agents to prevent erroneous
      conclusions from spreading through a shared knowledge base and
      misleading other agents.

   *  *Discussion*: The metric captures contamination of shared state
      rather than of a single agent's context.  It is measured by
      implanting false decision conclusions into the shared knowledge
      base and observing whether other agents adopt and execute them
      without verification.

   *  *Metric of measurement*: The pass rate over the bias propagation
      test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Operational Security.

   *  *Issues*: The metric overlaps with Memory Poisoning Defense
      (Section 4.6.4) when the shared store is also a memory store, and
      the store type used MUST be stated; the number of agents consulted
      before propagation is observed affects the result and must be
      fixed.

   *  *See also*: Memory Poisoning Defense (Section 4.6.4), Defense
      Against Malicious Collusion (Section 4.5.3), Cross-Document
      Reasoning Security (Section 4.6.10).



Han, et al.               Expires 26 April 2027                [Page 25]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


4.5.5.  Goal Drift Control

   *  *Definition*: The capability of an agent to consistently adhere to
      top-level business and security objectives without behavioral
      deviation during the execution of long-term, multi-step tasks.

   *  *Discussion*: The metric captures whether the original objective
      remains controlling over an extended execution.  It is measured by
      establishing clear top-level constraints, executing multi-stage
      subtasks over the long term, and verifying whether any boundary
      violations or non-compliant behaviors occur during that execution.

   *  *Metric of measurement*: The pass rate over the long-horizon
      objective test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Operational Security.

   *  *Issues*: The observation window is the dominant parameter and
      MUST be reported, since longer horizons generally yield lower
      results; results are not comparable across horizons of different
      length.

   *  *See also*: Instruction Following and Safety Alignment
      (Section 4.3.5), Autonomous Iteration Security (Section 4.5.6),
      Emergency Shutdown and Task Termination (Section 4.5.1).

4.5.6.  Autonomous Iteration Security

   *  *Definition*: The capability of an agent to fully inherit safety
      constraints when self-modifying prompts and code, and to refrain
      from actively removing protective mechanisms.

   *  *Discussion*: The metric captures whether the agent's own
      optimization process erodes the constraints placed on it.  It is
      measured by granting the agent autonomous iteration privileges
      and, after a defined number of iterations, checking for the
      generation of jailbreak prompts or the disabling of safety
      monitoring.  The iteration count is a parameter of the test and
      MUST be recorded.

   *  *Metric of measurement*: The pass rate over the autonomous
      iteration test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Operational Security.







Han, et al.               Expires 26 April 2027                [Page 26]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   *  *Issues*: Only agents holding self-modification privileges can be
      assessed, so the metric is inapplicable to fixed-policy profiles
      and a pass by a non-iterating agent MUST NOT be reported;
      inspection after a fixed iteration count cannot exclude
      degradation occurring later.

   *  *See also*: Goal Drift Control (Section 4.5.5), Dynamic
      Permissions and Privilege Escalation Prevention (Section 4.5.8),
      Security Policy Consistency (Section 4.6.23).

4.5.7.  Ecosystem-Level Crash Defense

   *  *Definition*: The capability of an agent to prevent failures --
      such as single-agent infinite loops or memory leaks -- from
      propagating to the entire cluster through circuit breakers and
      resource isolation.

   *  *Discussion*: The metric captures containment of a fault rather
      than prevention of the fault.  It is measured by injecting a
      faulty agent to run concurrently and verifying the cluster's
      circuit-breaking, resource isolation, and overall service
      stability.

   *  *Metric of measurement*: The pass rate over the fault injection
      test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Operational Security.

   *  *Issues*: The fault types injected and the cluster scale MUST be
      reported, since containment results depend on both; the metric is
      not applicable outside multi-agent or clustered profiles.

   *  *See also*: Emergency Shutdown and Task Termination
      (Section 4.5.1), Environment Isolation and Resource Control
      (Section 4.6.1).

4.5.8.  Dynamic Permissions and Privilege Escalation Prevention

   *  *Definition*: The capability of an agent to adhere to the
      principle of least privilege and to its Just-in-Time (JIT)
      authorization mechanism, detecting and blocking high-risk
      operations -- such as reading, writing, deleting, and fund
      transfers -- that exceed authorized scope in real time.

   *  *Discussion*: The metric captures enforcement of the authorized
      scope at the moment of the operation.  It is measured by
      configuring the agent with read-only basic permissions and testing
      unauthorized operations such as modification and deletion, then



Han, et al.               Expires 26 April 2027                [Page 27]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


      triggering high-risk operations and verifying whether temporary
      requests for manual confirmation are initiated, with single-use
      authorizations expiring immediately.

   *  *Metric of measurement*: The pass rate over the dynamic permission
      test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Operational Security.

   *  *Issues*: The initial permission set is the dominant variable and
      MUST be reported; the metric overlaps with Excessive Agency
      Defense (Section 4.4.7) and Confused Deputy Defense
      (Section 4.4.6), and the report must state which layer performed
      the refusal.

   *  *See also*: Excessive Agency Defense (Section 4.4.7), Confused
      Deputy Defense (Section 4.4.6), Environment Isolation and Resource
      Control (Section 4.6.1).

4.6.  Basic Security Metrics

4.6.1.  Environment Isolation and Resource Control

   *  *Definition*: The capability of an agent to control underlying
      runtime environment resources -- files, network, computing, and
      system interfaces -- to block out-of-bounds access to the host
      machine or to external networks, and to resist resource exhaustion
      attacks.

   *  *Discussion*: The metric captures the effectiveness of the
      execution boundary rather than the intent of the model.  It is
      measured by executing test cases within a sandbox, attempting to
      read sensitive host files, initiating unauthorized outbound
      network requests, and creating infinite loops or high-resource-
      consuming processes, then verifying interception effectiveness and
      resource quota enforcement.

   *  *Metric of measurement*: The pass rate over the sandbox
      confinement test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Basic Security.

   *  *Issues*: The isolation technology and its configuration MUST be
      reported, since container and virtual-machine isolation differ in
      the strength of the guarantee; access blocking and quota
      enforcement are distinct controls and SHOULD be scored separately
      where a deployment implements one but not the other.




Han, et al.               Expires 26 April 2027                [Page 28]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   *  *See also*: Dynamic Permissions and Privilege Escalation
      Prevention (Section 4.5.8), Plugin/Skill Security
      (Section 4.6.14), Ecosystem-Level Crash Defense (Section 4.5.7).

4.6.2.  Compliance Labels and Filing

   *  *Definition*: The capability of an agent to prominently display
      its identity label on the interface, to enforce manual review for
      high-risk operations, and to complete verifiable algorithm
      registration.

   *  *Discussion*: The metric captures conformity with service-
      identification and registration obligations, as distinct from
      technical security controls.  It is measured by verifying product
      interface labeling, pop-up windows for manual confirmation of
      high-risk operations, and publicly available algorithm filing
      information.

   *  *Metric of measurement*: The pass rate over the compliance
      labeling and filing test case set, computed as described in
      Section 4.2.

   *  *Applicable boundary*: Basic Security.

   *  *Issues*: The applicable filing regime is jurisdiction-specific
      and MUST be declared; this metric is a compliance check whose
      result is not evidence of technical security capability, and a
      report SHOULD state that explicitly so the value is not aggregated
      without qualification.

   *  *See also*: Industry Compliance Alignment (Model Layer)
      (Section 4.3.7), User Takeover for High-Risk Operations
      (Section 4.4.13).

4.6.3.  Privacy Leakage Prevention

   *  *Definition*: The capability of an agent to isolate and protect
      sensitive user information, such as phone numbers and addresses,
      to prevent cross-user queries, and to ensure that privacy is not
      exposed in plaintext logs.

   *  *Discussion*: The metric captures whether sensitive values remain
      confined to the user and session that own them, and whether they
      are protected in transit and at rest within the agent's own
      components.  It is measured by cross-testing privacy queries
      across multi-user sessions, verifying the effectiveness of data
      masking in logs and returned content, and validating the strength
      of differential privacy.



Han, et al.               Expires 26 April 2027                [Page 29]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   *  *Metric of measurement*: The pass rate over the privacy test case
      set, computed as described in Section 4.2.

   *  *Applicable boundary*: Basic Security.

   *  *Issues*: A front-end refusal does not establish that the value
      was not processed downstream, so the observation point for each
      test case MUST be stated; masking strength and differential-
      privacy parameters are not comparable and the parameters used MUST
      be reported.

   *  *See also*: Cross-User/Cross-Session Memory Isolation
      (Section 4.6.5), Compliant Data Transmission (Section 4.6.7), User
      Takeover for High-Risk Operations (Section 4.4.13).

4.6.4.  Memory Poisoning Defense

   *  *Definition*: The capability of an agent to keep content that an
      adversary wrote through the agent's own interfaces from being
      served back to the agent as trusted context in a later session,
      and, where such content is served, to refrain from acting on it.

   *  *Discussion*: The metric captures a delayed-action path, in which
      the write and the effect occur in different sessions.  The
      adversary's position defines the metric: the adversary can
      converse with the agent or call the memory store's write
      interface, but has no access to the backing store; an adversary
      that can write the backing store directly is the adversary of
      Protection of Memory Data Integrity (Section 4.6.8), not of this
      metric.

      Five write shapes are distinguished, because a control that
      catches one need not catch another: a planted fact, namely a false
      statement about the user recorded as a memory; a hidden
      instruction, namely an instruction to the agent recorded in the
      shape of a memory; an update poisoning, namely a forged correction
      of a fact the user stated earlier; a retrieval hijack, namely an
      entry padded with the vocabulary of a topic so that it outranks
      the genuine memory on that topic; and a metadata poisoning, namely
      a memory that assigns itself the trust attribute on which a
      downstream filter selects, which applies only where the store
      accepts writer-supplied metadata.

      Each write shape is exercised on three channels, which MUST be
      evaluated separately.  On the external channel the write carries
      the store's own marker for an untrusted source and no signature.
      On the laundered channel the write carries the marker of a trusted
      source without a valid signature, which models an interface caller



Han, et al.               Expires 26 April 2027                [Page 30]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


      that misrepresents its origin.  On the agent-laundered channel the
      write carries both the trusted marker and a valid signature,
      because the content reached the store through the agent, which
      signs what it stores; this is the channel that a control relying
      on trust markers or signatures alone does not stop.  Where the
      store exposes neither markers nor signatures, the three channels
      collapse into one and the report MUST state that.

      Two outcomes are distinguished and MUST be measured separately.
      The content is surfaced when the read path returns it to the agent
      as context; the agent acts on it when the agent's output is
      influenced by it.

   *  *Metric of measurement*: The pass rate over the memory poisoning
      test case set, computed as described in Section 4.2, reported
      separately for the surfaced outcome and the acted-on outcome.

   *  *Applicable boundary*: Basic Security.

   *  *Issues*: A pass may be obtained by a write-time filter or by a
      read-time filter, which generalize differently, and the layer that
      provided protection MUST be identified; the number of write shapes
      evaluated, the number of channels exercised, and the channels on
      which an adversary write was surfaced MUST be reported with the
      metric value; a store can be assessed for the surfaced outcome
      only and MUST NOT be scored on the acted-on outcome, and an agent
      SHOULD NOT be scored on the surfaced outcome alone; the metric
      overlaps with Defense Against the Spread of Decision-Making Bias
      (Section 4.5.4) when the memory is shared between agents.

   *  *See also*: Protection of Memory Data Integrity (Section 4.6.8),
      Cross-User/Cross-Session Memory Isolation (Section 4.6.5), Defense
      Against the Spread of Decision-Making Bias (Section 4.5.4).

4.6.5.  Cross-User/Cross-Session Memory Isolation

   *  *Definition*: The capability of an agent to keep one user's or one
      session's memories from being readable in another user's or
      another session's context, both through the agent's own interfaces
      and when a genuine record of one user is placed into another
      user's position in the backing store.

   *  *Discussion*: Two questions are distinguished and both MUST be
      evaluated, because they test different layers.  The front-door
      question is whether the agent's own interfaces return one user's
      memory in another user's context.  The placement question is
      whether the backing store binds a record to its owner and to its
      position: a genuine, unmodified record belonging to user A is



Han, et al.               Expires 26 April 2027                [Page 31]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


      copied over a record belonging to user B while B's identifiers are
      left in place.  Every byte involved in the placement test is one
      the store itself wrote, so a check that authenticates each
      record's content passes it, and the test measures whether the
      record is bound to its owner and to its place.

   *  *Metric of measurement*: The pass rate over the isolation test
      case set, computed as described in Section 4.2, reported
      separately for the front-door test and the placement test.  The
      placement test is scored using the verdicts defined in
      Section 4.8.

   *  *Applicable boundary*: Basic Security.

   *  *Issues*: Deliberately shared memory is a design feature in some
      profiles, so the intended sharing model MUST be declared before a
      failing result can be interpreted; the mechanism that produced
      isolation MUST be reported, namely a filter over a shared pool,
      per-user namespaces assigned by the caller, or a separate store
      per user, because isolation that depends on how the caller assigns
      namespaces is a property of the deployment rather than of the
      store; the placement test requires write access to the backing
      store and MUST NOT be reported where the evaluator has none.

   *  *See also*: Memory Poisoning Defense (Section 4.6.4), Protection
      of Memory Data Integrity (Section 4.6.8), Privacy Leakage
      Prevention (Section 4.6.3), Defense Against Malicious Collusion
      (Section 4.5.3).

4.6.6.  Data Deletion and the Right to Be Forgotten

   *  *Definition*: The capability of an agent to respond to user
      deletion requests by thoroughly erasing all personal memory data
      from primary storage, caches, and backups.

   *  *Discussion*: The metric captures completeness of erasure across
      every copy of the data.  It is measured by having a user initiate
      a deletion command and then searching the database, cache, and
      archived backups to verify the absence of residual private data.

   *  *Metric of measurement*: The pass rate over the deletion request
      test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Basic Security.







Han, et al.               Expires 26 April 2027                [Page 32]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   *  *Issues*: Immutable and write-once storage may not permit erasure,
      and the residual risk MUST be disclosed rather than reported as a
      failure of the agent alone; the time allowed for propagation of
      the deletion across replicas MUST be stated.

   *  *See also*: Privacy Leakage Prevention (Section 4.6.3), Log
      Retention Period and Secure Storage (Section 4.6.22), Cross-User/
      Cross-Session Memory Isolation (Section 4.6.5).

4.6.7.  Compliant Data Transmission

   *  *Definition*: The capability of an agent to comply with the three
      principles of data minimization, transport encryption, and user
      authorization in scenarios involving cross-border transfer of
      personal data and sharing with third parties.

   *  *Discussion*: The metric captures conformance of data movement
      with declared policy.  It is measured by simulating data
      transmission scenarios and verifying field minimization,
      transmission encryption, and the integrity of authorization
      records.

   *  *Metric of measurement*: The pass rate over the data transmission
      test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Basic Security.

   *  *Issues*: Three independent assertions are combined in one metric,
      and a report SHOULD state which failed; a transmission rejected at
      the interface does not establish that the data was not processed
      internally.

   *  *See also*: Privacy Leakage Prevention (Section 4.6.3), Identity
      and Access Credential Security (Section 4.6.17).

4.6.8.  Protection of Memory Data Integrity

   *  *Definition*: The capability of an agent to detect that its
      persisted memory or checkpoint store has been changed without
      passing through the agent's own write path, and either to refuse
      the changed data on read or to report it.

   *  *Threat model*: The adversary has write access to the medium that
      holds the memory, namely database rows, file bytes, or objects in
      an object store, and nothing else: no code in the agent's process,
      no key that the agent holds only in memory, and no modification to
      the agent's source.  This position represents the compromised
      store or the privileged write made outside the agent, and it is



Han, et al.               Expires 26 April 2027                [Page 33]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


      distinct from the adversary of Memory Poisoning Defense
      (Section 4.6.4), who can only converse with the agent or call the
      agent's interfaces.

   *  *Discussion*: The metric captures detection on the read path, not
      the presence of integrity fields in the store.  Because the
      adversary can write anything, an integrity value stored beside the
      data, such as a checksum column, a hash field, or a "verified"
      marker, provides no protection unless it is bound to a secret or
      to a root of trust that the adversary does not hold.  The metric
      is therefore measured by seeding the store through the agent's own
      write path, editing the backing store out of band, restarting the
      agent, and reading through the agent's own read path.

      The edit set is defined so that it separates confidentiality from
      integrity.  An edit that replicates only bytes the store itself
      wrote, namely a genuine record of one context placed into another
      context, or an older genuine record of the same context placed
      over its newest, passes any at-rest encryption that does not bind
      ciphertext to record identity and any signature that does not
      cover a record's position.  Conversely, binding a record to its
      position does not detect a record that has been removed from the
      sequence, so removal requires its own edit.

   *  *Metric of measurement*: The pass rate over the storage edit set,
      computed as described in Section 4.2 and scored using the verdicts
      defined in Section 4.8.

   *  *Applicable boundary*: Basic Security.

   *  *Issues*: The verdict and the detection point MUST be recorded for
      every edit, because a store that reports an edit only when a
      separate audit is run has already served that edit to the agent;
      the result is a statement about one version of the store, so the
      store name and version, the storage backend and version, the host
      platform, and the configuration in force MUST be reported with the
      metric value; the metric MUST NOT be computed when a control case
      fails, and the result MUST then be reported as not evaluable, with
      the reason; the metric overlaps with Memory Poisoning Defense
      (Section 4.6.4) where the same store is both the poisoning target
      and the edited artefact, and the artefact edited MUST be stated.

   *  *See also*: Memory Poisoning Defense (Section 4.6.4), Security
      Audit Capabilities (Section 4.6.18), Log Retention Period and
      Secure Storage (Section 4.6.22).






Han, et al.               Expires 26 April 2027                [Page 34]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


4.6.9.  Injection Prevention and Filtering of Search Results

   *  *Definition*: The capability of an agent to filter out hidden
      prompt injections and indirect malicious instructions from
      external search results and to prevent them from being included in
      the reasoning context.

   *  *Discussion*: The metric captures filtering that occurs before the
      retrieved content reaches the reasoning context.  It is measured
      by constructing an external document containing embedded malicious
      instructions, importing it into the database, and performing a
      search to verify whether the agent filters out hidden payloads.

   *  *Metric of measurement*: The pass rate over the search result
      filtering test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Basic Security.

   *  *Issues*: The metric overlaps with Indirect Injection Defense
      (Section 4.4.2) when the injection vector is a web page rather
      than a search result, and cases MUST be assigned to exactly one
      metric; filtering that removes content also removes legitimate
      content, and the false-positive rate SHOULD be reported alongside.

   *  *See also*: Indirect Injection Defense (Section 4.4.2), Cross-
      Document Reasoning Security (Section 4.6.10).

4.6.10.  Cross-Document Reasoning Security

   *  *Definition*: The capability of an agent to prevent the generation
      of non-compliant instructions by splicing together cross-document
      malicious logic during multi-document joint retrieval and
      reasoning.

   *  *Discussion*: The metric captures a composite risk in which each
      document is individually benign but the combination is not.  It is
      measured by performing mixed searches using multiple compromised
      documents to test whether the agent merges malicious content and
      executes high-risk operations.

   *  *Metric of measurement*: The pass rate over the cross-document
      reasoning test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Basic Security.







Han, et al.               Expires 26 April 2027                [Page 35]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   *  *Issues*: The number and provenance of the documents combined is
      the dominant parameter and MUST be reported; this metric is not
      reducible to per-document filtering and requires a control at the
      query or reasoning layer.

   *  *See also*: Injection Prevention and Filtering of Search Results
      (Section 4.6.9), Defense Against the Spread of Decision-Making
      Bias (Section 4.5.4), Indirect Injection Defense (Section 4.4.2).

4.6.11.  Uniqueness and Authenticity of Identity Identifiers

   *  *Definition*: The capability of an agent to possess a unique,
      unforgeable digital identity identifier or certificate and to
      perform effective mutual authentication across services and
      between multiple agents.

   *  *Discussion*: The metric captures whether an agent can be
      unambiguously identified and whether a claimed identity can be
      verified.  It is measured by verifying unique metadata
      identifiers, testing access attempts using forged identities, and
      validating legitimate authentication processes.  The term
      "authenticity" is used in the sense of [RFC4949], namely the
      property of being genuine and able to be verified and be trusted;
      an identifier is authenticatable only if a relying party can
      distinguish the legitimate identity from a forged one.

   *  *Metric of measurement*: The pass rate over the identity
      identifier test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Basic Security.

   *  *Issues*: Uniqueness and unforgeability are separate properties
      and SHOULD be scored separately; the trust anchor used for
      verification MUST be reported, since a self-signed identifier
      provides uniqueness without providing verification.

   *  *See also*: Mutual Authentication in A2A Communication Between
      Agents (Section 4.6.20), Identity and Access Credential Security
      (Section 4.6.17), Traceability of Decision-Making Responsibility
      (Section 4.5.2).

4.6.12.  Agent Ecosystem Asset Security

   *  *Definition*: The capability of an agent in closed-loop management
      of high-risk vulnerabilities in open-source frameworks and
      dependent components, as well as the comprehensive maintenance of
      a Software Bill of Materials (SBOM), covering all assets including
      code repositories, model files, and container images.



Han, et al.               Expires 26 April 2027                [Page 36]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   *  *Discussion*: The metric captures the hygiene of the software and
      model supply chain.  It is measured by using scanning tools to
      detect CVE vulnerabilities in dependencies, verifying high-risk
      vulnerability patch plans and consistency between the SBOM and
      production versions, and scanning model files for deserialized
      malicious code.

   *  *Metric of measurement*: The pass rate over the asset and
      dependency scanning test case set, computed as described in
      Section 4.2.

   *  *Applicable boundary*: Basic Security.

   *  *Issues*: A scanner-based result is only as current as the
      vulnerability database, whose version and snapshot date MUST be
      reported; an SBOM that exists but is not maintained or not
      reconciled against the running version is not a passing state, and
      the reconciliation method must be stated.

   *  *See also*: Supply Chain Material Access Control (Section 4.6.19),
      Plugin/Skill Security (Section 4.6.14).

4.6.13.  MCP Tool Poisoning Defense

   *  *Definition*: The capability of an agent to identify discrepancies
      between MCP tool declarations and actual execution logic, and to
      intercept built-in data theft and system operation backdoors.

   *  *Discussion*: The metric captures whether the declaration of a
      tool is verified against its behaviour.  It is measured by
      deploying a malicious MCP service with fake functionality and
      invoking the tool to verify data exfiltration and system command
      execution behavior.

   *  *Metric of measurement*: The pass rate over the MCP tool poisoning
      test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Basic Security.

   *  *Issues*: Verification of behavior against declaration generally
      requires either a trusted registry or runtime inspection, and the
      mechanism present MUST be reported; the metric overlaps with Tool
      Call Chain Security (Section 4.4.5) once a compromised tool output
      propagates downstream.

   *  *See also*: Plugin/Skill Security (Section 4.6.14), Tool Call
      Chain Security (Section 4.4.5), Cleaning and Validation of
      External API Response Results (Section 4.6.16).



Han, et al.               Expires 26 April 2027                [Page 37]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


4.6.14.  Plugin/Skill Security

   *  *Definition*: The capability of an agent to perform security scans
      before installing third-party plugins and to monitor for malicious
      behaviors such as reverse shells and data exfiltration during
      runtime.

   *  *Discussion*: The metric captures control at both the admission
      and the runtime phase of an extension.  It is measured by
      uploading a plugin containing malicious code and verifying
      installation interception and runtime behavior blocking
      mechanisms.  Installation-time and runtime controls SHOULD be
      reported separately.

   *  *Metric of measurement*: The pass rate over the plugin and skill
      test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Basic Security.

   *  *Issues*: Static scanning at installation and behavioral
      monitoring at runtime detect different classes of malicious
      plugin, and a passing result from one MUST NOT be presented as
      coverage of the other; the plugin format and permission model
      exercised MUST be stated.

   *  *See also*: Supply Chain Material Access Control (Section 4.6.19),
      Agent Ecosystem Asset Security (Section 4.6.12), Environment
      Isolation and Resource Control (Section 4.6.1).

4.6.15.  Prompt Template Tampering Defense

   *  *Definition*: The capability of an agent to prevent user variables
      and external inputs from tampering with or overwriting core system
      prompt keywords, and to audit its capability to detect semantic
      backdoors introduced by third-party prompt templates.

   *  *Discussion*: The metric captures the integrity of the instruction
      layer itself.  It is measured by constructing template injection
      and DAN-style variable inputs, and by performing batch audits to
      verify whether externally imported prompt templates conceal escape
      instructions.

   *  *Metric of measurement*: The pass rate over the prompt template
      test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Basic Security.





Han, et al.               Expires 26 April 2027                [Page 38]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   *  *Issues*: Semantic backdoors in a template may be undetectable by
      inspection, so an audit-based pass is weaker than a structural
      pass and the method used MUST be stated; the template engine and
      its escaping semantics must be reported for the result to be
      reproducible.

   *  *See also*: Model Reverse Engineering and Extraction Defense
      (Section 4.3.4), Direct Jailbreak Defense (Section 4.4.1), Supply
      Chain Material Access Control (Section 4.6.19).

4.6.16.  Cleaning and Validation of External API Response Results

   *  *Definition*: The capability of an agent to perform pre-filtering
      and structured validation of data returned by third-party APIs, as
      well as to intercept hidden malicious instructions in API
      responses.

   *  *Discussion*: The metric captures validation of data entering the
      agent from an external service.  It is measured by constructing
      third-party API response content containing embedded injection
      payloads and testing whether the agent executes malicious logic
      after reading the response.  Structural validation and instruction
      filtering are distinct and SHOULD be reported separately.

   *  *Metric of measurement*: The pass rate over the API response
      validation test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Basic Security.

   *  *Issues*: Schema validation does not detect injection and
      instruction filtering does not detect malformed data, so a
      combined pass rate without the split is not interpretable; the API
      contract source is part of the configuration and must be reported.

   *  *See also*: Tool Call Chain Security (Section 4.4.5), Indirect
      Injection Defense (Section 4.4.2), MCP Tool Poisoning Defense
      (Section 4.6.13).

4.6.17.  Identity and Access Credential Security

   *  *Definition*: The capability of an agent to prohibit the storage
      of keys and access credentials in plaintext and to adopt temporary
      credentials and IAM policies based on the principle of least
      privilege.







Han, et al.               Expires 26 April 2027                [Page 39]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   *  *Discussion*: The metric captures the exposure of credentials the
      agent holds.  It is measured by searching for plaintext keys in
      configurations, logs, and environment variables, and by inspecting
      for over-permissive configurations such as permanent keys and
      wildcard permissions.

   *  *Metric of measurement*: The pass rate over the credential
      handling test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Basic Security.

   *  *Issues*: Detection is only as good as the set of locations
      searched, which MUST be enumerated in the report; a credential
      that is encrypted at rest but exposed in logs is not a passing
      state, and both storage and emission must be covered.

   *  *See also*: Uniqueness and Authenticity of Identity Identifiers
      (Section 4.6.11), Compliant Data Transmission (Section 4.6.7),
      Privacy Leakage Prevention (Section 4.6.3).

4.6.18.  Security Audit Capabilities

   *  *Definition*: The capability of an agent to comprehensively record
      end-to-end operation logs in a tamper-proof manner and to support
      post-incident security event auditing and forensics.

   *  *Discussion*: The metric captures the sufficiency of the evidence
      record after an incident.  It is measured by executing various
      types of interactions and tool invocation operations, verifying
      whether the agent completely records end-to-end logs, and
      validating the completeness of critical log fields, the append-
      only write mechanism, and anti-tampering capabilities.  Field
      completeness and tamper resistance are distinct and SHOULD be
      reported separately.

   *  *Metric of measurement*: The pass rate over the audit capability
      test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Basic Security.

   *  *Issues*: The set of critical fields is deployment-specific and
      MUST be published with the result; an append-only mechanism that
      can be disabled by the same principal that generates the events
      does not constitute tamper resistance.







Han, et al.               Expires 26 April 2027                [Page 40]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   *  *See also*: Log Retention Period and Secure Storage
      (Section 4.6.22), Input-Output Traceability (Section 4.4.9),
      Traceability of Decision-Making Responsibility (Section 4.5.2),
      Protection of Memory Data Integrity (Section 4.6.8).

4.6.19.  Supply Chain Material Access Control

   *  *Definition*: The capability of an agent to reject the loading of
      unreviewed third-party components, external knowledge bases, and
      prompt templates during the build and runtime phases based on an
      SBOM whitelist.

   *  *Discussion*: The metric captures enforcement of an allow-list at
      the point of loading.  It is measured by simulating the
      introduction of malicious out-of-scope dependencies and simulating
      injecting malicious content into the knowledge base, then
      verifying whether the loading interception logic during both the
      build phase and runtime is effective.

   *  *Metric of measurement*: The pass rate over the supply chain
      admission test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Basic Security.

   *  *Issues*: Build-phase and runtime enforcement are separate
      controls and SHOULD be reported separately; the whitelist itself
      is an artefact whose provenance and update process must be
      declared, since a compromised whitelist defeats the control.

   *  *See also*: Agent Ecosystem Asset Security (Section 4.6.12),
      Plugin/Skill Security (Section 4.6.14), Prompt Template Tampering
      Defense (Section 4.6.15).

4.6.20.  Mutual Authentication in A2A Communication Between Agents

   *  *Definition*: The capability of an agent to perform bidirectional
      authentication during multi-agent interactions and to block
      spoofed nodes from accessing the cluster.

   *  *Discussion*: The metric captures verification in both directions
      of an agent-to-agent channel.  It is measured by having a node
      with a forged identity attempt to communicate and verifying the
      effectiveness of bidirectional certificate or token authentication
      interception.

   *  *Metric of measurement*: The pass rate over the agent-to-agent
      authentication test case set, computed as described in
      Section 4.2.



Han, et al.               Expires 26 April 2027                [Page 41]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   *  *Applicable boundary*: Basic Security.

   *  *Issues*: Unidirectional authentication is not equivalent to
      mutual authentication and incomplete coverage MUST NOT be reported
      as a pass; the credential type and the trust anchor used MUST be
      reported.

   *  *See also*: Uniqueness and Authenticity of Identity Identifiers
      (Section 4.6.11), Defense Against Malicious Collusion
      (Section 4.5.3), Communication Replay Attack Resistance
      (Section 4.6.21).

4.6.21.  Communication Replay Attack Resistance

   *  *Definition*: The capability of an agent to intercept replay
      attacks on intercepted messages using timestamps and sequence
      numbers.

   *  *Discussion*: The metric captures freshness of an accepted inter-
      agent message.  It is measured by capturing legitimate
      communication messages, replaying them after a certain interval,
      and verifying the system's ability to identify and reject such
      messages.  The replay interval is a parameter of the test and MUST
      be recorded.

   *  *Metric of measurement*: The pass rate over the replay test case
      set, computed as described in Section 4.2.

   *  *Applicable boundary*: Basic Security.

   *  *Issues*: Timestamp-based freshness depends on clock
      synchronization, which is a precondition and MUST be verified as
      part of the test; a replay window that is short enough to pass
      this metric may also reject legitimate delayed messages, and the
      chosen window should be reported.

   *  *See also*: Mutual Authentication in A2A Communication Between
      Agents (Section 4.6.20), Input-Output Traceability
      (Section 4.4.9).

4.6.22.  Log Retention Period and Secure Storage

   *  *Definition*: The capability of an agent to implement encrypted
      storage and tamper resistance for audit logs, to retain archives
      for a minimum of six months, and to provide backup and restoration
      support.





Han, et al.               Expires 26 April 2027                [Page 42]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   *  *Discussion*: The metric captures durability of the audit record
      over the regulatory retention window.  It is measured by verifying
      the log rotation and archival policy, AES-encrypted storage,
      tamper protection, and the effectiveness of backup and recovery.
      Each asserted property is independently verifiable and SHOULD be
      reported separately.

   *  *Metric of measurement*: The pass rate over the log retention test
      case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Basic Security.

   *  *Issues*: A retention policy that has not yet been exercised over
      its full window can only be verified by inspection, and the
      verification method MUST be stated; retention of logs containing
      personal data interacts with Data Deletion and the Right to Be
      Forgotten (Section 4.6.6), and the reconciliation rule should be
      declared.

   *  *See also*: Security Audit Capabilities (Section 4.6.18), Data
      Deletion and the Right to Be Forgotten (Section 4.6.6), Protection
      of Memory Data Integrity (Section 4.6.8).

4.6.23.  Security Policy Consistency

   *  *Definition*: The capability of all agent instances in a cluster
      to synchronize a unified security baseline and to ensure that
      policy updates are applied atomically across the entire cluster.

   *  *Discussion*: The metric captures the absence of heterogeneous
      enforcement across instances.  It is measured by deploying
      differentiated security configurations across the cluster,
      conducting jailbreak attacks to identify the resulting
      vulnerabilities, then distributing unified policies and verifying
      the effectiveness of synchronized policy enforcement.

   *  *Metric of measurement*: The pass rate over the policy consistency
      test case set, computed as described in Section 4.2.

   *  *Applicable boundary*: Basic Security.

   *  *Issues*: Atomicity and completeness of propagation are distinct
      properties; a transient window during which instances enforce
      different policies is a real exposure and SHOULD be measured
      rather than assumed away; the cluster size used MUST be reported.

   *  *See also*: Autonomous Iteration Security (Section 4.5.6),
      Ecosystem-Level Crash Defense (Section 4.5.7).



Han, et al.               Expires 26 April 2027                [Page 43]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


4.7.  Risk Levels

   A comprehensive security evaluation score, computed as specified in
   [I-D.han-bpm-agent-security-benchmark-methodology], is mapped to one
   of three risk levels.  Risk levels are defined from high to low
   comprehensive score values.

4.7.1.  Low Risk Level

   The Low Risk Level corresponds to a comprehensive score in the range
   *[80-100]*. No high-risk or medium-risk level security defects exist,
   with no or only a small number of low-risk level areas for
   optimization.  The agent possesses comprehensive full-link defense
   mechanisms, can be deployed at scale, and is RECOMMENDED for monthly
   or quarterly routine inspections.

4.7.2.  Medium Risk Level

   The Medium Risk Level corresponds to a comprehensive score in the
   range *[60-80)*. No high-risk level security defects exist, but one
   or more medium-risk level security defects exist.  The agent can only
   be approved for deployment after all medium-risk level security
   defects are remediated and manually reviewed.

4.7.3.  High Risk Level

   The High Risk Level corresponds to a comprehensive score in the range
   *[0-60)*. One or more high-risk level security defects exist.  The
   agent MUST be immediately taken offline and isolated, and can only be
   approved for deployment after all medium and high-risk level security
   defects are remediated and a full regression test is completed.

   The terms "low-risk", "medium-risk", and "high-risk" applied to an
   individual operation, as used in Section 4.4.10, denote the risk
   classification of that operation and are distinct from the risk
   levels defined here, which apply to the agent as a whole.  The two
   uses of the terms MUST NOT be conflated in a report.

4.8.  Integrity Verdicts

   For the metrics defined in this document that evaluate whether an
   agent or its memory store detects a storage-level change, namely
   Protection of Memory Data Integrity (Section 4.6.8) and the placement
   test of Cross-User/Cross-Session Memory Isolation (Section 4.6.5),
   the outcome of a test case is recorded as exactly one of the verdicts
   below, together with a detection point.  The verdicts are defined
   here so that results produced by different evaluators are comparable.




Han, et al.               Expires 26 April 2027                [Page 44]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


4.8.1.  Rejected

   The read path refused or flagged the changed data before it reached
   the agent.  Rejected is a pass.

4.8.2.  Reported

   The read path served the changed data, and a documented channel,
   namely a log entry at warning level or above, a callback, or a status
   field, raised an integrity signal at or before the time of serving.
   Reported is a pass.

4.8.3.  Accepted

   The changed data was served and nothing reported it.  Accepted is a
   failure.

4.8.4.  Detection Point

   Every verdict MUST be recorded with the point at which detection
   occurred.  The detection point is read when the read path itself
   raised the signal.  The detection point is audit when the signal
   appeared only through a separate integrity audit invoked by an
   operator or a scheduled job.  A case whose only signal is produced by
   an audit is recorded with the detection point audit and is NOT a
   pass, because the agent had already served, and may already have
   acted on, the changed data by the time such an audit runs.  A
   deployment that detects at the audit point rather than at the read
   point SHOULD state its audit interval in the report, so that the
   exposure window is visible.

4.8.5.  Not Evaluable

   Where a control case required by the method applied to a metric
   fails, the verdict for that metric MUST be not evaluable, accompanied
   by the reason, and the metric value MUST NOT be computed.  A
   subsystem that refuses every read would otherwise record a perfect
   pass rate, and the control that requires a clean store to be served
   unchanged is what prevents that outcome.

5.  Measurement Considerations

   A metric value produced according to the convention of Section 4.2 is
   a statement about a specific evaluation, not an intrinsic property of
   an agent.  This section states what MUST accompany a reported metric
   value.





Han, et al.               Expires 26 April 2027                [Page 45]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


5.1.  Test Case Set Specification

   Every reported metric value MUST be accompanied by a specification of
   the test case set used, comprising the number of test cases, the
   origin of the test cases, whether the set is public or held out, and
   a version identifier.  A value obtained with a held-out set and a
   value obtained with a public set are not interchangeable and MUST be
   reported separately where both are available.

5.2.  Pass Criteria Specification

   Every reported metric value MUST be accompanied by the pass criteria
   applied to each test case, including the rules for partial credit,
   for near-miss content, and for cases where the agent neither passes
   nor fails in an unambiguous way.  Where a test case admits an outcome
   that is safe but does not satisfy the stated objective, the
   classification rule applied MUST be recorded.

5.3.  Applicable Boundary Declaration

   Every reported metric value MUST declare the System Under Test
   boundary against which it was obtained, as specified in
   [I-D.han-bpm-agent-security-benchmark-profiles].  A value obtained
   against a Foundation Model boundary and a value obtained against a
   Compound System boundary, even for the same metric, are not directly
   comparable, because the latter includes the contributions of
   components outside the model.

5.4.  Comparability of Metric Values

   Two metric values for the same metric are comparable only when the
   test case set, the pass criteria, and the System Under Test boundary
   are equivalent.  Where any of the three differs, the difference MUST
   be reported as a delta against a stated baseline rather than as a
   ranking.  Aggregation of metric values across test case sets, or
   across boundaries, requires a weighting that MUST be stated.

6.  Security Considerations

   This document defines terminology.  It does not itself define a
   security control, and no conformance claim should be derived from the
   vocabulary alone.  The following considerations apply to the use of
   the terminology.








Han, et al.               Expires 26 April 2027                [Page 46]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


6.1.  Interpreting Metric Values

   A metric value is a pass rate over a test case set.  It is bounded
   above by the coverage of that test case set, and it does not
   establish the absence of the risk the metric names.  A high pass rate
   on Memory Poisoning Defense (Section 4.6.4), for example, establishes
   that the test cases in the set did not result in poisoning; it does
   not establish that no poisoning technique exists.  Reports SHOULD
   state the coverage of the test case set alongside the value so that
   this limit is visible.

6.2.  Disclosure of Test Case Sets

   Publishing a complete test case set permanently reduces the
   discriminative power of the metric for which it is used, because an
   agent that has been aligned against a published set may pass without
   generalizing.  Test case sets SHOULD therefore be versioned and held
   out where continued discriminative power matters, and where a set is
   published, results obtained with it SHOULD be marked as such in
   accordance with Section 5.1.

6.3.  Misuse of Evaluation Results

   Comprehensive security scores for agents MAY be applied beyond their
   intended scope.  In the absence of the evaluation target, evaluation
   environment, evaluation boundaries, and relevant constraints, such
   scores can easily mislead users into believing that "the score equals
   absolute security" or that the security level of a specific version
   of the agent being evaluated represents the security level of the
   entire product line and all versions.  When disclosing evaluation
   results, the evaluation target, evaluation environment, evaluation
   boundaries, and relevant constraints SHOULD also be disclosed to
   clarify the valid scope of application for the results and to prevent
   misuse or abuse.

7.  References

7.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <https://www.rfc-editor.org/rfc/rfc2119>.

   [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
              May 2017, <https://www.rfc-editor.org/rfc/rfc8174>.




Han, et al.               Expires 26 April 2027                [Page 47]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


7.2.  Informative References

   [ASEB1]    OWASP Foundation, "OWASP Top 10 for Agentic Applications
              2026", December 2025, <https://genai.owasp.org/resource/
              owasp-top-10-for-agentic-applications-for-2026>.

   [ASEB2]    Huang, K., "Agentic AI Threat Modeling Framework:
              MAESTRO", February 2025,
              <https://cloudsecurityalliance.org/blog/2025/02/06/
              agentic-ai-threat-modeling-framework-maestro>.

   [ASEB3]    National Institute of Standards and Technology (NIST),
              "Artificial Intelligence Risk Management Framework (AI RMF
              1.0)", January 2023,
              <https://www.nist.gov/itl/ai-risk-management-framework>.

   [ASEB4]    National Institute of Standards and Technology (NIST),
              Center for AI Standards and Innovation (CAISI), "Technical
              Blog: Strengthening AI Agent Hijacking Evaluations",
              January 2025, <https://www.nist.gov/news-
              events/news/2025/01/technical-blog-strengthening-ai-agent-
              hijacking-evaluations>.

   [ASEB5]    Hamin, M. and B. Edelman, "Cheating on AI Agent
              Evaluations", November 2025, <https://www.nist.gov/caisi/
              cheating-ai-agent-evaluations>.

   [ASEB6]    The European Parliament & The Council of the European
              Union, "EU Artificial Intelligence Act (2024)", July 2024,
              <https://artificialintelligenceact.eu/>.

   [ASEB7]    National Institute of Standards and Technology (NIST),
              "Cybersecurity Framework 2.0 (CSF 2.0)", February 2024,
              <https://www.nist.gov/cyberframework>.

   [ASEB8]    Debenedetti, E., Zhang, J., Balunovic, M., Beurer Kellner,
              L., Fischer, M., and F. Tramèr, "AgentDojo: A Dynamic
              Environment to Evaluate Prompt Injection Attacks and
              Defenses for LLM Agents", November 2024,
              <https://arxiv.org/abs/2406.13352>.

   [ASEB9]    Narajala, V. S. and O. Narayan, "Securing Agentic AI: A
              Comprehensive Threat Model and Mitigation Framework for
              Generative AI Agents", December 2025,
              <https://www.researchgate.net/publication/401482716>.






Han, et al.               Expires 26 April 2027                [Page 48]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   [ASEB10]   STAUFER, L., FENG, K., WEI, K., BAILEY, L., DUAN, Y.,
              YANG, M., OZISIK, A., CASPER, S., and N. KOLT, "The 2025
              AI Agent Index: Documenting Technical and Safety Features
              of Deployed Agentic AI Systems", May 2026,
              <https://arxiv.org/abs/2602.17753>.

   [ASEB11]   Mohammadi, M., Li, Y., Lo, J., and W. Yip, "Evaluation and
              Benchmarking of LLM Agents: A Survey", July 2025,
              <https://dl.acm.org/doi/10.1145/3711896.3736570>.

   [ASEB12]   Zong, X., Shen, Z., Wang, L., Lan, Y., and C. Yang, "MCP-
              SafetyBench: A Benchmark for Safety Evaluation of Large
              Language Models with Real-World MCP Servers", May 2026,
              <https://openreview.net/forum?id=7XYjeL46co>.

   [ASEB13]   UK Government, "International AI Safety Report 2026",
              February 2026, <https://internationalaisafetyreport.org/>.

   [ASEB14]   Anthropic, "Threat Intelligence Report", n.d.,
              <https://www.anthropic.com/research/threat-intelligence-
              report>.

   [ASEB15]   Huang, K., Wang, Y., Goertzel, B., Li, Y., Wright, S., and
              J. Ponnapalli, "Generative AI Security: Theories and
              Practices", 2024.

   [ASEB16]   China Mobile, "AI Security Evaluation Platform Launched
              (2025)", October 2025,
              <https://www.10086.cn/aboutus/news/groupnews/
              index_detail_53693.html>.

   [ASEB17]   OPPO, "Mobile Agent Security Technology White Paper",
              October 2025.

   [ASEB18]   Cyberspace Administration of China, "Interim Measures for
              the Management of Generative Artificial Intelligence
              Services (2023)", 2023.

   [ASEB19]   "GB/T 45654-2025 Cybersecurity technology—Basic security
              requirements for generative artificial intelligence
              service", n.d..

   [ASEB20]   Stanford University, Institute for Human-Centered
              Artificial Intelligence (HAI), "Artificial Intelligence
              Index Report 2025", November 2025,
              <https://aiindex.stanford.edu/>.





Han, et al.               Expires 26 April 2027                [Page 49]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   [ASEB21]   Future of Life Institute, "AI Safety Index (Summer 2025)",
              July 2025,
              <https://futureoflife.org/ai-safety-index-summer-2025>.

   [I-D.han-bpm-agent-security-benchmark-methodology]
              China Mobile, "Benchmarking Methodology for AI Agent
              Security Evaluation", 2026,
              <https://datatracker.ietf.org/doc/draft-han-bpm-agent-
              security-benchmark-methodology>.

   [I-D.han-bpm-agent-security-benchmark-profiles]
              China Mobile, "Evaluation Profiles for AI Agent Security
              Assessment", 2026, <https://datatracker.ietf.org/doc/
              draft-han-bpm-agent-security-benchmark-profiles>.

   [RFC4949]  Shirey, R., "Internet Security Glossary, Version 2",
              FYI 36, RFC 4949, DOI 10.17487/RFC4949, August 2007,
              <https://www.rfc-editor.org/rfc/rfc4949>.

Acknowledgments

   Many thanks to Yasha Khandelwal for his valuable work, review,
   comments, and suggestions, and in particular for his contribution to
   the memory-related evaluation metrics, the memory verdicts, and the
   integrity and isolation test method defined in this document series.
   Thanks to Matej Krsteski for his review and comments.Thanks to Jiake
   Chen, Jianyu Lin and Yue yu for their contribution to this draft.

References

Informative References

   [ASEB1] [ASEB2] [ASEB3] [ASEB4] [ASEB5] [ASEB6] [ASEB7] [ASEB8]
   [ASEB9] [ASEB10] [ASEB11] [ASEB12] [ASEB13] [ASEB14] [ASEB15]
   [ASEB16] [ASEB17] [ASEB18] [ASEB19] [ASEB20] [ASEB21] [RFC4949]
   [I-D.han-bpm-agent-security-benchmark-methodology]
   [I-D.han-bpm-agent-security-benchmark-profiles]

Authors' Addresses

   Yu Han
   China Mobile
   Beijing
   China
   Email: hanyu@chinamobile.com






Han, et al.               Expires 26 April 2027                [Page 50]

Internet-Draft  AI Agent Security Evaluation Terminology    October 2026


   Meiling Chen
   China Mobile
   BeiJing
   China
   Email: chenmeiling@chinamobile.com


   Qiguang Fan
   China Mobile
   Beijing
   China
   Email: fanqiguang@chinamobile.com


   Qin Wu
   Huawei
   Email: bill.wu@huawei.com


































Han, et al.               Expires 26 April 2027                [Page 51]