Join our Newsletter — 33% off our NHI Course

Identity control or AI adoption: what drives multi-cloud risk?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20230
Topic starter  

TL;DR: Cloud exposure is being driven by identity, privilege and lifecycle control across multi-cloud estates, according to Orca Security’s 2025 State of Cloud Security Report. Multi-cloud governance has to account for standing access and weak remediation paths, or neglected assets and vulnerable AI packages stay exposed.

Editorial analysis by NHI Mgmt Group, based on content published by Orca Security: “What is Cloud Security?”.

By the numbers:

  • 55% of organisations use two or more cloud providers.
  • 84% use AI in the cloud.
  • 62% have at least one vulnerable AI package.

Key questions

Q: Why do standing cloud permissions increase attack paths?

A: Standing permissions increase attack paths because they remain usable long after the original business need has passed.

Q: What are the signs that non-human identity governance is failing in cloud environments?

A: Common warning signs include credential sprawl, long-lived API keys, unrotated certificates, unclear ownership, and workloads with more access than they need.

Q: How should security teams govern identity and configuration risk across multi-cloud environments?

A: Security teams should treat multi-cloud governance as a single operating problem, not a collection of isolated cloud projects.

Practitioner guidance

  • Map cloud entitlements across every provider Create a single inventory of cloud roles, service accounts, tokens, and workload permissions across all active cloud platforms.
  • Convert standing access to just-in-time access Reserve persistent permissions for only the smallest set of break-glass use cases.
  • Bind AI workloads to least-privilege credentials Treat AI packages and model-integrated services as access-bearing identities.

Bottom line: Cloud security exposure in this article is driven less by raw cloud adoption than by the difficulty of governing identity, privilege, and lifecycle across multiple providers and AI workloads.

Glossary terms: Cloud Security Posture Management, Cloud Infrastructure Entitlement Management, Just-in-Time Access Request, Attack path

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20712
 

Cloud security has become an identity governance problem before it is a tooling problem. The article’s own evidence shows that cloud estates are now defined by multi-provider complexity, AI adoption, and long-lived access paths. That combination pushes governance decisions into IAM, PAM, and NHI lifecycle control rather than leaving them in posture-only tooling. Practitioners should treat cloud security as the operational management of who or what can act, not just what is exposed.

A few things that frame the scale:

A question worth separating out:

Q: Should teams prioritise AI security posture or cloud identity controls first?

A: They should treat them as the same control problem when AI workloads run in cloud environments. Securing the package without constraining its identity leaves access risk in place, while tightening identity without understanding the model and dependency chain leaves operational blind spots. The right sequence is to govern both together.

👉 Read our full editorial: Cloud security is exposing identity gaps across multi-cloud estates



   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.