An unauthorized data access attempt occurs when an AI agent requests a resource, action, or scope that falls outside its assigned permissions. This differs from a security breach: the request may be blocked before execution, but the attempt itself is a measurable event. OWASP's Top 10 for LLM Applications names this pattern "Excessive Agency," describing systems that take actions beyond their intended scope. OWASP's agentic AI guidance extends this to tool misuse, privilege escalation, and unauthorized action execution, framing these as risks that require enforcement at runtime rather than detection after the fact. Establishing a clear, per-agent authorized-scope baseline before deployment is a prerequisite for measurement. Without a documented baseline referencing least-privilege principles, there is no reliable way to distinguish an authorized exploratory action from a genuine policy violation.
Technical Signals That Indicate Unauthorized Access
Several signal types recur across access-control literature and are directly applicable to agent runtimes. Scope mismatch occurs when a requested resource or action exceeds the permission scope granted to the agent's credential or token, a pattern well suited to detection through OAuth 2.0 or OpenID Connect scope-based authorization models that bind tool calls to defined permissions. Denied or blocked API and tool calls, visible in IAM or gateway logs, represent explicit attempted actions that exceeded authorization and were stopped. Anomalous sequencing, such as an agent accessing data stores unrelated to its assigned task, signals deviation from intended scope even when individual calls are technically permitted. A related complication is credential or token reuse across sessions or multiple agents, which makes it difficult to attribute a specific unauthorized attempt to a single agent identity. Assigning unique, non-shared identities per agent instance addresses this directly and is a precondition for attributable audit trails.
Implementing Measurement at the Runtime Layer
Runtime Architecture for Capturing Access Attempts
Mapping Metrics to Governance Frameworks
No standards body has yet published an agent-specific KPI standard for unauthorized access attempt rates. Current practice adapts general IT audit controls to agent identities. NIST's AI Risk Management Framework includes a "Measure" function intended for quantifying AI system risks, including unauthorized behavior, as part of a lifecycle governance approach, with the 2024 Generative AI Profile (NIST AI 600-1) addressing risks such as data leakage and unauthorized information access more specifically. Mapping agent access logs to the AI RMF's Measure and Manage functions, alongside NIST SP 800-53's AU and AC control families, gives security teams a defensible basis for governance documentation without inventing a nonstandard measurement scheme. Cloud-provider audit logging services such as AWS CloudTrail, Azure Activity Log, and Google Cloud Audit Logs already record identity, action, resource, and outcome data at the API level, and MITRE ATLAS catalogs adversarial techniques such as prompt injection and tool exploitation that inform which access patterns warrant closer scrutiny.