TL;DR: Only 40% of organisations believe they are AI mature, but just 22% meet objective readiness standards, while 61% report unsanctioned AI tools and 74% remain worried about security risk, according to JumpCloud’s Q1 2026 IT Trends Report. The gap is not deployment speed but whether identity, access, and governance can scale with AI at all.
At a glance
What this is: JumpCloud’s Q1 2026 IT Trends Report finds a sharp mismatch between perceived AI maturity and the identity and access foundation needed to scale safely.
Why it matters: IAM teams need to treat AI readiness as an identity governance problem because shadow AI, fragmented access controls, and unmanaged bot access widen exposure across human and non-human programmes.
By the numbers:
- 40% of organizations believe they are AI mature, but only 22% possess the objective IT foundation required to scale safely.
- 61% of organizations report the use of unsanctioned AI tools, creating significant visibility and governance gaps.
- 74% remain concerned about security risks, specifically unauthorized data access and AI-generated phishing.
👉 Read JumpCloud's Q1 2026 IT Trends Report on AI maturity and readiness
Context
AI maturity is not the same as safe AI adoption. The article argues that enterprises are scaling AI faster than they are hardening the identity, access, and governance base underneath it, which leaves security teams with more automation, more unmanaged tools, and less control than the maturity narrative suggests.
For identity programmes, the practical issue is scope. Human IAM, NHI governance, and emerging agentic access patterns are being pulled into the same operational stack, but many organisations still manage them as separate problems. That separation makes it easier for shadow AI and bot access to slip through approval, review, and monitoring processes.
The starting position is typical rather than exceptional: confidence in AI progress is running ahead of measurable readiness across most enterprises.
Key questions
Q: How should security teams govern AI adoption when maturity scores look better than reality?
A: Security teams should anchor AI governance in identity and access controls, not self-assessed maturity. The practical test is whether the organisation can inventory AI-connected access, enforce approval, and revoke it cleanly. If those controls are fragmented, the maturity score is not a reliable indicator of safe scale.
Q: Why do shadow AI tools create an IAM problem instead of just an application risk?
A: Shadow AI creates an IAM problem because every unsanctioned tool introduces a new identity path, credential exposure point, or data connection that bypasses standard governance. The risk is not only the tool itself, but the fact that access may exist without ownership, review, or revocation.
Q: What breaks when AI access is governed separately from human and NHI access?
A: Separate governance creates inconsistent policy enforcement, slower revocation, and blind spots in review. When human, service account, and AI-linked permissions are managed in different workflows, teams cannot reliably answer who approved access, who owns it, or whether it still belongs in production.
Q: How do organisations know whether AI readiness is actually improving?
A: Improvement shows up when the organisation can reduce unsanctioned tool use, increase identity coverage for AI-linked access, and prove that permissions are reviewed and revoked on schedule. Readiness is measurable when identity controls can keep pace with how fast AI is adopted.
Technical breakdown
AI maturity versus AI readiness in identity governance
AI maturity describes organisational confidence and adoption momentum. AI readiness is the operational capacity to govern access, data, and controls safely as AI usage expands. The report’s core finding is that many enterprises equate usage with maturity, even when the underlying identity stack is fragmented. In practice, that means access governance, device policy, and application control are not aligned well enough to support AI workloads or the non-human identities behind them. Once AI becomes part of everyday operations, weak joiner-mover-leaver discipline, inconsistent entitlement review, and poor visibility across tools become governance failures rather than housekeeping issues.
Practical implication: assess AI readiness through identity control coverage, not adoption sentiment.
Shadow AI and unsanctioned access paths
Shadow AI is the use of AI tools outside approved governance channels. In identity terms, it creates unmanaged access paths that bypass inventory, policy, logging, and recertification. The article’s 61% figure matters because unsanctioned AI is not just an application issue. It is an access problem that can involve tokens, accounts, browser sessions, and data connections with no durable ownership. Once those connections exist, security teams lose the ability to answer basic questions about who approved access, what was touched, and whether the tool should still be trusted.
Practical implication: inventory unsanctioned AI tools as identity exposures, not only software sprawl.
Consolidated IAM for humans, bots, and agents
The report’s argument for unified IAM reflects a real structural problem: identity control planes are often split across users, service accounts, and new AI-driven workloads. That fragmentation makes policy inconsistent and slows response when privileges or tooling change. For non-human identities, especially AI-linked workloads, the issue is not only authentication but lifecycle ownership, permission scope, and revocation. When human and machine access are governed in different silos, the enterprise cannot enforce one trustworthy model of who or what may act on data and systems.
Practical implication: unify identity governance so human, NHI, and AI access share the same control baseline.
Breaches seen in the wild
- Cisco DevHub NHI breach — IntelBroker exploited exposed Cisco credentials, API tokens and keys in DevHub.
- ASP.NET machine keys RCE attack — 3,000+ exposed ASP.NET machine keys enabled remote code execution.
Read our 52 NHI Breaches Analysis report for a comprehensive view of breaches impacting Non-Human Identities including AI Agents.
NHI Mgmt Group analysis
AI maturity is an access-governance claim, not a deployment claim. JumpCloud’s data shows that organisations are treating AI adoption as proof of readiness even when only 22% meet objective standards. That gap matters because identity control, not model enthusiasm, determines whether AI can be introduced safely into production workflows. Practitioners should read AI maturity as a control-state question, not a roadmap milestone.
Shadow AI is the clearest sign that identity governance has lost the boundary. When 61% of organisations report unsanctioned AI tools, the problem is not simply unsanctioned software. It is unmanaged identity paths, unknown access grants, and broken accountability for data use. This is a governance failure across IAM, NHI oversight, and policy enforcement, and it shows why discovery has to precede any meaningful control discussion.
Secure AI scaling now depends on unified identity control across humans and bots. The report’s emphasis on IAM unification is directionally correct because separate control planes create inconsistent enforcement and blind spots. Human access reviews, NHI lifecycle governance, and AI-linked permissions cannot be managed as disconnected workflows if organisations want credible oversight. The practitioner conclusion is straightforward: identity governance must be treated as a shared operating layer for all actors that can touch data and systems.
Dynamic AI environments expose an identity readiness gap that many programmes have not named clearly. Shadow AI control gap: the enterprise assumes AI use can be governed through existing application and access processes, but unsanctioned tools move faster than approval, review, and offboarding cycles. That assumption fails when tool adoption happens outside sanctioned identity paths. The implication is that governance teams must rethink where the control boundary begins, because the old boundary no longer matches how access is actually created.
From our research:
- 59.8% of organisations see value in a solution that simplifies non-human access management and introduces dynamic ephemeral credentials, according to The 2024 Non-Human Identity Security Report.
- 88.5% of organisations acknowledge that their non-human IAM practices lag behind or are merely on par with their human identity and access management efforts.
- Ultimate Guide to NHIs , Why NHI Security Matters Now shows why identity programmes now have to treat machine and human access as one operating problem.
What this signals
Shadow AI has become an identity discovery problem as much as a software discovery problem. When tools appear outside approved channels, the programme loses sight of who can reach what, through which token or session, and for how long. That means AI governance should be measured by control coverage and revocation certainty, not by how many pilots have been approved.
With 59.8% of organisations already seeing value in simplifying non-human access management and using dynamic ephemeral credentials, per the 2024 Non-Human Identity Security Report, the market signal is clear: identity teams are moving toward shorter-lived, more governable access paths. That shift matters because static access models struggle to keep up with AI-linked and bot-mediated workflows. The programme implication is to close the gap between discovery, approval, and revocation before AI use becomes routine.
Unified identity control is becoming a baseline requirement for AI scale. If human IAM, NHI governance, and AI-linked permissions stay in separate process lanes, policy drift will keep widening. Security leaders should expect identity governance to absorb more of the operational burden as AI adoption expands.
For practitioners
- Measure AI readiness against identity control coverage Map where AI-connected access is authenticated, authorised, logged, and reviewed. Prioritise gaps in entitlement visibility, lifecycle ownership, and approval coverage over subjective maturity scores.
- Inventory shadow AI as an access problem Track unsanctioned AI tools, browser-based AI use, and service connections that can reach company data. Treat each connection as a governance object with an owner, a purpose, and a revocation path.
- Unify human and non-human governance workflows Bring user access reviews, service account oversight, and AI-linked permissions into one governance model so policy, recertification, and revocation follow the same operating standard.
- Require named ownership for AI-connected identities Assign accountable owners for every AI-enabled access path, including tokens, service accounts, and bot-linked sessions. Without ownership, review results become descriptive instead of actionable.
Key takeaways
- The report’s central warning is that AI confidence is running ahead of identity readiness.
- Shadow AI creates governance blind spots because every unsanctioned tool can introduce unmanaged access paths.
- IAM teams should treat AI scale as an identity consolidation problem across humans, bots, and agents.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Agentic AI Top 10 and OWASP Non-Human Identity Top 10 address the attack and risk surface, while NIST CSF 2.0 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Agentic AI Top 10 | AI tools and agents need governed runtime access paths. | |
| OWASP Non-Human Identity Top 10 | NHI-01 | Unsanctioned AI tools create unmanaged non-human identity paths. |
| NIST CSF 2.0 | PR.AA-01 | Identity governance and access control are central to safe AI scaling. |
Inventory AI-linked identities and constrain tool access with explicit approval and lifecycle ownership.
Key terms
- AI readiness: AI readiness is the practical ability to deploy and operate AI safely within existing security and governance constraints. It is not a sentiment score. In identity terms, readiness depends on who or what can access systems, how that access is approved, and whether it can be revoked without delay.
- Shadow AI: Shadow AI is the use of AI tools, models, or services outside approved organisational governance. It matters because unmanaged AI use can create hidden identity paths, data access points, and compliance gaps that security teams cannot review or offboard through standard processes.
- Non-human identity: A non-human identity is any digital identity used by a machine, workload, bot, token, service account, or AI system. These identities need lifecycle ownership, access scope control, and revocation discipline because they often operate faster and at larger scale than human accounts.
- Identity governance: Identity governance is the set of controls that define who or what should have access, who approves it, and how that access is reviewed over time. For AI and non-human systems, governance must cover discovery, ownership, recertification, and offboarding, not just authentication.
Deepen your knowledge
AI readiness, shadow AI governance, and non-human access control are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If your organisation is trying to scale AI on a fragmented identity base, this is the place to start.
This post draws on content published by JumpCloud: Q1 2026 IT Trends Report, The Dual Disconnect: Why Your AI Maturity Now Fails to Scale. Read the original.
Published by the NHIMG editorial team on 2026-02-10.
NHI Mgmt Group — the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org