Identity security lessons from WEF 2026: why identity is the control plane

At a glance

What this is: This analysis argues that the World Economic Forum’s 2026 outlook points to identity as the control plane because AI misuse, fraud, supply-chain compromise and cloud disruption all converge on identity abuse.

Why it matters: It matters because IAM, PAM and NHI programmes can no longer treat identity as a downstream control layer; they have to govern trust continuously across humans, service accounts and AI-enabled access paths.

By the numbers:

• 94% of organisations identify AI as the most significant driver of cyber risk.
• 87% cite AI-related vulnerabilities as the fastest-growing threat.
• 73% of respondents were personally affected by cyber-enabled fraud.
• 64% of organisations claim they meet minimum cyber resilience requirements.

Context

The core problem is not simply more attacks. It is that the identity controls many programmes still rely on were designed for a world where trust was easier to contain, access paths were fewer, and humans were the main subjects of governance. That assumption no longer holds when AI, cloud, vendors and machine accounts all participate in the same access fabric.

In identity security terms, the control plane has shifted. If identities are the mechanism through which most legitimate access now flows, then any weakness in authentication, authorization, inventory, lifecycle control or monitoring becomes a direct security exposure, not just an operational issue. That is why the article frames identity as the place where systemic risk now concentrates.

The article is a broad analysis, not a breach report. Its starting position is typical of current enterprise environments: fragmentation, implicit trust and uneven governance across human and non-human identities are now common rather than exceptional.

Key questions

Q: What breaks when organisations rely on static credentials for agentic AI and other non-human identities?

A: Static credentials create durable access that is hard to control in automated environments. They increase the chance of credential reuse, secret leakage, and excessive persistence after a task is complete. That makes it harder to contain compromise, rotate access cleanly, and prove that AI systems only had the permissions needed for a specific action.

Q: Why do service accounts and other non-human identities increase breach impact?

A: Service accounts and other non-human identities increase breach impact because they often carry broad, persistent access and bypass interactive controls like MFA. When those identities are not tightly scoped, rotated, and retired, attackers can reuse them to move quietly across systems, pipelines, and cloud environments. The issue is not the token alone, but the authority attached to it.

Q: What are the signs that traditional identity governance is not keeping up with access risk?

A: Traditional governance is lagging when it can only tell who has access, not whether that access is being used appropriately. Common signs include large certification backlogs, reviewers approving access without context, dormant or orphaned accounts going unnoticed, and excessive or rogue entitlements persisting across peer groups. These patterns show that governance is recording access, not managing risk.

Q: Should organisations prioritise identity visibility or access automation first?

A: Visibility comes first. If teams cannot see who has access, how that access is used, and where sensitive data lives, automation simply accelerates incomplete governance rather than improving it.

Technical breakdown

Why identity becomes the control plane in AI-heavy environments

Identity becomes the control plane when access decisions, rather than network location, determine whether action is allowed. In AI-heavy environments, that means humans, service accounts, APIs, bots and AI agents all depend on the same trust fabric, even if they behave very differently. The technical problem is not just authentication. It is that authorization, context, monitoring and lifecycle control must now operate continuously across heterogeneous identities. When the article says identity is the new control plane, it is describing a shift from perimeter enforcement to runtime governance of who or what can act.

Practical implication: treat identity inventory, trust signals and access policy as shared runtime controls rather than separate admin functions.

How AI-driven attacks accelerate credential abuse and privilege escalation

AI does not need to invent a new attack path to be effective. It can scale existing ones such as phishing, impersonation, credential harvesting and privilege escalation with much higher speed and realism. The article’s point is that AI amplifies identity abuse because many environments still depend on static credentials, weak step-up checks and broad standing access. Once a credential is obtained, the attacker often behaves like a legitimate user or workload, which makes detection harder if telemetry only looks for obvious malware or perimeter intrusion. That is why identity verification must extend beyond initial login into behaviour and context.

Practical implication: move detection and policy enforcement closer to credential use, privilege elevation and anomalous session behaviour.

Why third-party and machine identities inherit trust too easily

Supply-chain access is often granted through service accounts, vendor logins and machine credentials that remain valid long after the business need changes. That creates inherited trust, where a partner or managed service is trusted because the relationship was approved once, not because the access is still appropriate today. Technically, the risk comes from long-lived secrets, broad permissions and weak lifecycle offboarding. The article is right to focus on this because these identities are not peripheral exceptions; they are part of the operational backbone. Once one trusted identity is compromised, the attacker can move through systems without needing to break the perimeter.

Practical implication: inventory third-party identities, enforce time-bounded access and remove standing trust from vendor authentication paths.

Threat narrative

Attacker objective: The attacker wants to convert legitimate identity trust into broad access that supports fraud, lateral movement, supply-chain compromise or cloud disruption.

1. Entry begins when an attacker uses AI-assisted phishing, impersonation or credential harvesting to obtain legitimate access rather than forcing a perimeter breach.
2. Escalation follows when the attacker abuses over-privileged service accounts, APIs, bots or AI agents to raise access or extend reach into connected systems.
3. Impact occurs when trusted identities are used to execute fraud, compromise supply chains or disrupt cloud environments while blending into normal authentication traffic.

Breaches seen in the wild

• reviewdog Action compromise 2025: A stolen maintainer token poisoned reviewdog/action-setup, leaking CI secrets including the tj-actions bot token used in the next attack.
• BeyondTrust breach 2024: A stolen BeyondTrust Remote Support API key let a China state-sponsored actor reset accounts and reach US Treasury workstations in 2024.

Read our 52 NHI Breaches Analysis report for a comprehensive view of breaches impacting Non-Human Identities including AI Agents.

NHI Mgmt Group analysis

Identity trust has become the dominant attack surface because access control now matters more than perimeter control. The article reinforces a structural shift that many programmes still understate: attackers increasingly bypass systems by using valid identities, not by breaking infrastructure first. That means authentication, authorization and lifecycle governance are now first-order security controls, not back-office administration. Practitioners should treat every access path as a security boundary.

AI has turned identity abuse into a scale problem, not a novel problem. The important change is not that AI created new categories of identity risk, but that it accelerated phishing, impersonation and credential abuse across human and non-human identities. This makes implicit trust a failing assumption because the same access patterns can now be generated faster, at higher volume and with more convincing context. Practitioners need to rethink where validation occurs, not just how strong a login is.

Inherited trust in third-party access is now a governance liability, not a procurement detail. When vendors, partners and managed services authenticate through service accounts or other NHIs, the identity becomes part of the organisation’s operational trust chain. If that chain is not actively governed, compromise can arrive through a route that looks authorised on paper but is no longer justified in practice. Practitioners should align identity governance with contract, business and offboarding lifecycles.

Ephemeral risk in static control models creates an identity visibility gap. The article shows that resilient organisations assess identity risk continuously, yet many programmes still certify access on review cycles that assume stable entitlements. That assumption is no longer sufficient in environments where machine identities, cloud services and AI-driven access paths change faster than governance cadence. The implication is that identity assurance has to move closer to issuance and use.

Identity security is becoming the coordination layer between IAM, fraud, cloud and resilience programmes. The article connects disparate threats that are often handled in separate teams, but they share the same root condition: trust in identities that are insufficiently governed. That convergence is where the discipline is heading. Practitioners should expect identity controls to become the common language for cross-domain risk reduction.

From our research library:

• 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to the Ultimate Guide to NHIs.
• Read next: NHI Lifecycle Management Guide

What this signals

Identity-first governance will increasingly define resilience programmes. Organisations that keep treating identity as an admin layer will struggle to see where trust is being inherited, reused or overextended. The programme shift is toward continuous identity assurance, not periodic entitlement review.

Supply-chain risk is now an identity lifecycle problem. The 92% figure for third-party NHI exposure is a warning that vendor access can no longer be treated as a static onboarding issue. Practitioners need governance that tracks access from issuance through offboarding, because inherited trust survives far longer than most contracts.

AI is compressing the time between credential theft and business impact. That changes the operating model for IAM, PAM and fraud teams alike. Security leaders should expect identity telemetry, behavioural context and lifecycle control to sit closer together in the same response path.

For practitioners

• Map every trusted identity path Inventory humans, service accounts, APIs, bots and AI agents together so the programme reflects the full access fabric rather than only employee accounts.
• Replace implicit trust with continuous validation Use adaptive access decisions, context-aware step-up checks and behaviour monitoring so authentication is not the end of the security decision.
• Shrink standing privilege across third parties Review vendor and partner access for broad, persistent permissions and enforce time-bounded access wherever business operations allow.
• Align identity lifecycle with business lifecycle Offboard vendor identities, service accounts and unused machine credentials when the relationship or purpose ends, not only during periodic clean-up.
• Build a living access graph Maintain a current view of which identities exist, what they can reach and where inherited trust creates exposure across cloud and legacy systems.

Key takeaways

• The report ties AI-driven attacks, fraud and supply-chain compromise to the same root condition: identity trust is too broad and too static.
• Resilience depends on seeing humans, service accounts and AI-enabled access paths as one governed identity fabric, not separate domains.
• Programmes that keep perimeter assumptions while leaving standing trust in place will remain exposed to both opportunistic abuse and systemic compromise.

Key terms

• Identity Control Plane: An identity control plane is the governance layer that decides who or what can access systems and under what conditions. In practice, it coordinates authentication, authorization, privilege review, and lifecycle management across human and machine identities so access policy is enforced consistently across environments.
• Inherited Trust: Access or authority an agent effectively receives from a surrounding workflow, upstream agent, or human process rather than from its own direct permissions. This can make the agent appear properly scoped while its real operational reach is broader than the entitlement record suggests.
• Standing Privilege: Standing privilege is access that remains active even when no immediate task requires it. For NHI programmes, it is a common failure mode because long-lived credentials and persistent roles create unnecessary exposure. Reducing standing privilege usually means tighter expiry, on-demand access, and clearer review of who or what still needs access.
• Continuous validation: Continuous validation is the practice of re-checking user, device, or session risk after login instead of trusting access indefinitely. It recognizes that identity assurance can drift during a session, especially when endpoint state or user context changes after authentication.

Deepen your knowledge

NHI governance, agentic AI identity, and machine identity lifecycle are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are responsible for identity security strategy or NHI governance in your organisation, it is worth exploring.