TL;DR: Access, data quality and governance gaps are slowing enterprise AI rollout, with Protecto citing 88% adoption in at least one function. Data, connectors and runtime permissions need tighter governance before wider deployment.
Editorial analysis by NHI Mgmt Group, based on content published by Protecto: “Top Enterprise AI Adoption Challenges”.
By the numbers:
- 88% of businesses use AI in at least one business function.
- Poor data quality can result in organizations incurring average losses of $12.9 million every year.
Key questions
Q: When should organisations prioritise AI identity governance over new AI deployments?
A: They should prioritise it before broad deployment, because the first wave of AI usage often creates the largest blind spots.
Q: What are the signs that an AI project has become shadow AI?
A: The main signs are orphaned agents, unmanaged MCP connections, and AI logic appearing in branches or services without a clear owner or approved governance path.
Q: What breaks when AI systems can access data without context-aware controls?
A: What breaks is the governance model.
Practitioner guidance
- Define AI data classification rules Specify which data types can enter prompts, vector stores and model training, then apply masking or blocking before ingestion rather than after output review.
- Register every AI use case and connector Build a central inventory of copilots, LLMs, agents, RAG pipelines and third-party integrations so ownership, approval status and data access are visible.
- Scope agent access by task and context Require runtime decisions to consider business purpose, data sensitivity and workflow step, so an agent does not inherit broad standing access.
Bottom line: Enterprise AI adoption is constrained less by model capability than by weak control over data, connectors and runtime access.
Glossary terms: AI Governance, Context-based access control, Retrieval-augmented Generation, Shadow AI
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Enterprise AI governance is now an access-control problem, not just a model-risk problem. Once AI systems can retrieve enterprise data, the key question becomes who or what is allowed to see, pull and transform information at runtime. That shifts the governance centre of gravity toward policy enforcement, data classification and auditability. Practitioners should treat AI workflows as governed access paths, not as isolated productivity tools.
A few things that frame the scale:
- Only 13% of organisations feel extremely prepared for the reality of agentic AI despite the majority racing toward autonomous adoption, according to the 2026 Infrastructure Identity Survey.
- Enterprise AI use rose from 55% of organisations in 2023 to 88% in 2025, according to McKinsey’s Global Surveys on the State of AI.
A question worth separating out:
Q: How should security teams govern LLM apps that use RAG and agents?
A: They should treat retrieval, generation, and action as separate trust zones with separate policy checks. The right model is least privilege for context and tools, plus evidence-rich logging for every runtime decision. That approach aligns AI security with identity governance because it limits what the system can read, reveal, and do.
👉 Read our full editorial: AI governance failures are slowing enterprise rollout at scale