Identity Graph Hero Bottom Background

Identity Graph

Runtime Identity Graph for Sensitive Data

Aurva connects Agents, NHIs, Services, workloads, database users, permissions, queries, sensitive data, and downstream movement into one runtime graph.

Runtime Identity Graph
Runtime Access ChainLive
Real-time view of how identities access and move data
View full graph ↗
authenticates
AI Agent / Serviceagent-paymentsManaged
runs inside
IAM Role / Service Accountpayments-agent-roleAssumed
queries
Workload / Applicationpayments-api-v3Verified
queries
Database Userapp_db_userActive
touches
Table / Columncustomers.piiAccessed
sends to
Sensitive Datacustomer_piiHigh Risk
External Destinationus-east-1Untrusted
Access chain observed · 2 min ago
High-risk data exfiltration path detectedSensitive data is being sent to an untrusted external destination.
View alert →
Active Identities1,248↑ 8.2% vs 7d ago
Sensitive Reads347↑ 23% vs 7d ago
Risky Destinations18↑ 5 vs 7d ago
Cleanup Opportunities47↑ 12 vs 7d ago
Monitoring live⏱ Data refreshed 30s ago

Identity meets runtime. Reality beats entitlements.

Permissions tell you what could happen. Aurva's runtime identity graph tells you what actually happened — linking every identity to the sensitive data it touched and where that data moved next.

Full Identity Chain

From AI agent or service account to DB user to sensitive column — every hop mapped.

Runtime Over Entitlements

Not what was allowed, but what was executed, what was touched, and what moved.

Context Drift Detection

Flag when access falls outside expected scope — by agent, workload, or data type.

Static graphs show what could happen.
Aurva shows what did.

Identity graphs map possible access. Data graphs map sensitive data. Aurva connects identity, workload, query, data touched, and movement at runtime.

Identity Graph

Who can access what

Maps identities, roles, permissions, and entitlement paths.

PermissionsRolesEntitlements
Data Graph

Where sensitive data lives

Maps data stores, classifications, and sensitive fields.

DatabasesPIIPCI
Aurva Runtime Graph

What actually happened

Shows which service, NHI, or agent touched sensitive data, what it queried, whether it was expected, and where the data moved next.

IdentityWorkloadQuerySensitive dataMovement

From possible access to runtime evidence. Built for service, NHI, and agent-driven access across production environments.

Four layers. One runtime graph.

Aurva builds a runtime graph connecting identity, permissions, data sensitivity, queries, behavior, and movement — across cloud, databases, and downstream services.

01

Identity Chain

Who acted, and through what.

Aurva maps the full identity stack: service account, IAM role, workload, pod, application, database user, AI agent, and delegated identity. Not just the surface — the whole chain of who or what executed the access.

  • Service accounts and IAM roles
  • Workloads, pods, and applications
  • Database users and session identities
  • AI agents and delegated identities
02

Access and Entitlement Graph

What the identity could do.

Map what every identity is allowed to access — including inherited permissions, unused entitlements, excessive scopes, toxic combinations, and cross-environment reach. Understand the full blast radius before an incident happens.

  • Inherited and effective permissions
  • Unused and excessive entitlements
  • Toxic permission combinations
  • Cross-environment access reach
03

Runtime Activity Graph

What the identity actually did.

Track every query executed, every database, schema, table, and column touched. Surface volume, frequency, new access patterns, first-time access, and unusual behavior. This is the gap between entitlement and execution.

  • Queries executed per identity and workload
  • Database, schema, table, and column accessed
  • Volume, frequency, and behavioral patterns
  • First-time and anomalous access detection
04

Data and Movement Graph

Where sensitive data went.

Classify the sensitive data that was touched, understand its business context, and trace where it moved next — internal services, external destinations, AI tool calls, API responses, and agent context windows. Detect egress and context drift before they become incidents.

  • Sensitive data classification and business context
  • Downstream services and external destinations
  • Egress, AI tool calls, and API movement
  • Context drift and intent mismatch detection

Questions security teams can finally answer

Static identity graphs show what is configured. Aurva shows what actually happened — and gives you the evidence to act on it.

01

Which service touched PCI data for the first time?

Detect first-time access to regulated data by any identity — and flag it before it becomes a compliance finding.

02

Which AI agent accessed customer data outside its expected scope?

Surface context drift when an agent's data access falls outside its declared intent or operational boundary.

03

Which role has broad access but only uses 5% of it?

Quantify the gap between entitlement and execution. Shrink permissions to what is actually needed.

04

Which identity moved sensitive data outside the approved path?

Trace data movement from query to destination. Detect unauthorized egress before it becomes a breach.

05

Which database user maps back to which cloud role or workload?

Close the attribution gap. Map every DB session identity back to its cloud principal and originating workload.

What the runtime identity graph enables

From least privilege to agentic governance, every capability is grounded in what actually happened at runtime.

Least Privilege Enforcement

Close the gap between what identities are allowed and what they actually use. Reduce permissions to what runtime evidence supports.

NHI Governance

Govern non-human identities — service accounts, API keys, and machine credentials — with visibility into their actual data behavior.

Agentic Access Monitoring

Track what every AI agent accessed, what sensitive data it touched, and whether its behavior matched its declared intent.

Data Access Investigation

Reconstruct any access event end-to-end: which identity, which workload, which query, which sensitive data, where it went.

Blast-Radius Analysis

Before an incident, understand how far a compromised identity could reach. After one, understand exactly how far it did.

Context Drift Detection

Alert when access deviates from expected patterns — new data types, unusual destinations, or access outside normal operating windows.

Evidence-Backed Remediation

Remove permissions with evidence, not guesswork. Every recommendation is grounded in observed runtime activity.

See the full identity-to-data chain in your environment

Watch how Aurva maps runtime access across your services, NHIs, and AI agents.

You now know who touched sensitive data, and whether it was appropriate.

Identity + Runtime + Data. The full chain is connected.

Agent Access Data

Agents access data through chains, apart from queries.

Every chain is attributable.

AI-SPMRuntime Protection
Try Now
Sensitive Data Access

Sensitive data moves after every access.

Every Access is traceable.

DAMDSPM
Try Now
aurva-logo

USA

AURVA INC. 1241 Cortez Drive, Sunnyvale, CA, USA - 94086

India

Aurva, 4th Floor, 2316, 16th Cross, 27th Main Road, HSR Layout, Bengaluru – 560102, Karnataka, India

aicpa-logoiso-logo

© 2025 Aurva. All rights reserved.Terms of ServicePrivacy Policy

twitterlinkeding