TL;DR: AI systems stream data continuously and make decisions at machine speed, while most enterprises still govern access through human-paced approvals, creating bottlenecks, shadow access and compliance drift, according to Ethyca. The operating model must shift from exception handling to runtime, policy-driven control if AI is to scale safely.
Editorial analysis by NHI Mgmt Group, based on content published by Ethyca: “D a t a C o n s u m p t i o n a t A I S p e e d : W h y t h e E n t e r p r i s e O p e r a t i n g M o d e l M u s t B e R e - E n g i n e e r e d”.
Key questions
Q: How should organisations govern AI data access when requests happen continuously?
A: They should move from manual approval chains to runtime policy enforcement.
Q: Why do human approval workflows break down for agentic AI?
A: Because human approval assumes access persists long enough to be reviewed before an action completes.
Q: What are the signs that access governance is too static for AI-driven environments?
A: Common signs include review cycles that lag operational change, manual approvals for flows that already depend on runtime context, and decision records that explain outcomes poorly.
Practitioner guidance
- Map AI data consumption paths Identify where agents, applications and analytics pull data across domains, regions and systems, then trace where human approval still interrupts those flows.
- Replace queue-based approvals with runtime policy Move recurring access decisions into the data path so policy can be evaluated at the point of use instead of after a ticket is raised.
- Define ABAC and PBAC policy inputs Specify which attributes, context signals and purpose claims must be available before a request can be approved automatically or routed for exception handling.
Bottom line: AI systems expose a structural mismatch between human-paced approval models and continuous, machine-speed data consumption.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →