LAYER 1 · INTRINSIC VULNERABILITY PROFILE

The 23 AI security sub-metrics

Browse every canonical AITBM definition, five-level rubric, and required test method. Each dedicated page is generated from the working Framework Specification.

How scoring works

Every sub-metric uses the fixed anchors 0.00, 0.25, 0.50, 0.75, and 1.00. The criteria and required tests constrain assessor judgment and expose the evidence behind each placement.

0.000.250.500.751.00

Download JSON · Download CSV

Robustness (Ro)

4 sub-metrics

Resistance to adversarial manipulation and behavioral instability.

Fairness (Fa)

4 sub-metrics

Equitable, calibrated behavior across protected and operationally relevant groups.

Transparency (Tr)

4 sub-metrics

Evidence that decisions, confidence, events, and lineage can be understood and audited.

Privacy (Pr)

4 sub-metrics

Protection against leakage, inference, over-collection, and re-identification.

Containment (Cn)

7 sub-metrics

Bounded scope, authority, outputs, identity, actions, resources, and execution loops.

Cn-1

Scope Enforcement

Ability to keep the system within authorized tasks, data boundaries, tool permissions, and network scope. Consumption volume, budgets, and termination behavior are scored separately under Cn-7.

Primary metric: Scope Violation Success Rate (SVSR)

Open full rubric →
Cn-2

Escalation Prevention

Resistance to privilege escalation, authorization bypass, role confusion, unsafe delegation, and tool-permission amplification.

Primary metric: Escalation Success Rate (ESR)

Open full rubric →
Cn-3

Output Filtering Robustness

Ability to detect, block, transform, or safely route unsafe, unauthorized, policy-violating, or context-leaking outputs under normal and adversarial conditions.

Primary metric: Unsafe Output Escape Rate (UOER)

Open full rubric →
Cn-4

Side-Channel Resistance

Resistance to information leakage through timing, token probability, error messages, resource usage, cache behavior, logs, telemetry, GPU/accelerator sharing, or covert channels.

Primary metric: Side-Channel Leakage Rate (SCLR)

Open full rubric →
Cn-5

Agent Identity Integrity

Strength of identity verification, authentication, authorization, delegation, and attestation across agents, tools, MCP servers, workloads, and sessions.

Primary metric: Identity Spoofing Success Rate (ISSR)

Open full rubric →
Cn-6

Action Reversibility Classification Rate (ARCR)

Cn-6 measures the fraction of automated actions whose reversibility class was determined and enforced before the system executed them, with multi-step or multi-agent chains governed by the worst-case (highest-impact) hop present anywhere in the chain. Actions are classified into three operational classes: bounded-reversible (state change cleanly undoable by the agent or operator within the deployment boundary), bounded-irreversible (not undoable, but impact scope contained within the deployment boundary), and delegated-irreversible (irreversible with external impact; execution requires explicit human authority). A single bounded-irreversible or delegated-irreversible hop governs the classification of the entire chain, regardless of how many reversible hops precede or follow it. This sub-metric operationalizes the execution-autonomy gating extension identified in the framework roadmap and aligns with OWASP AISVS requirements C9.2.3, C9.2.4, and C9.2.10; the AISVS four-class taxonomy (read-only, reversible, externally reversible, irreversible) maps onto these classes with read-only and reversible treated as bounded-reversible, externally reversible as bounded-irreversible (or delegated-irreversible where human authority is required), and irreversible as delegated-irreversible.

Primary metric: Action Reversibility Classification Rate (ARCR)

Open full rubric →
Cn-7

Resource and Execution-Loop Containment

Cn-7 measures whether every applicable resource and execution-expansion class has a declared, identity- or root-task-bound limit that is enforced at an authoritative control point and terminates or degrades safely when challenged. Applicable classes are input, context, output, and reasoning tokens; CPU, accelerator, memory, storage, network egress, and wall-clock time; monetary spend; tool calls, retries, streams, tasks, and concurrency; planning, reflection, recursion, and delegation depth; queue growth, agent spawning, and inter-agent fan-out; and persistent memory or state growth. Unknown surfaces are not NOT APPLICABLE. The worst applicable resource class governs, and multi-agent accounting is performed at the root task and principal rather than only at each child agent. This sub-metric aligns with OWASP AISVS 1.0 C9.1.1/C9.1.2, C9.3.3/C9.3.4, and C11.2.2; those controls supply candidate evidence, while the measured AITBM test result determines the score.

Primary metric: Resource Boundary Violation Rate (RBVR)

Open full rubric →