Cloud-native application protection is shifting toward AI and access control

At a glance

What this is: Forrester’s CNAPP evaluation places access control, AI visibility, and runtime action at the centre of cloud security buying criteria.

Why it matters: For IAM, PAM, and NHI teams, the signal is that cloud protection now has to follow identities into workloads and AI paths, not stop at posture reporting.

Context

Forrester’s latest CNAPP evaluation treats cloud-native security as an access and action problem, not just a visibility problem. The primary issue is how security teams connect identity, workload telemetry, and policy enforcement across cloud environments that now include AI-heavy application paths.

That shift matters because CNAPP buyers are being asked to judge whether a platform can analyse risk across identities, data sensitivity, external exposure, code origins, and real-time threats. In practice, that pushes CNAPP deeper into IAM, CIEM, and workload governance rather than leaving it as a posture-only control layer.

The article’s core message is that cloud security tooling is converging around runtime decisions as much as findings. That makes the topic directly relevant to organisations governing machine identities, cloud roles, and agentic AI access flows.

Key questions

Q: How should teams respond when CNAPP is expected to govern both cloud access and runtime risk?

A: Treat CNAPP as part of the identity control plane, not just a posture tool. The practical question is whether entitlement visibility, workload context, and enforcement actions are connected enough to reduce excessive access and constrain blast radius when risky activity appears in production.

Q: Why does CIEM matter more when cloud workloads include AI and third-party integrations?

A: Because access graphs become useful only when they explain how identities actually interact with workloads, data, and external dependencies. Without that context, entitlement data is descriptive rather than operational, and teams cannot tell which permissions create the largest runtime risk.

Q: What are the signs that a CNAPP programme is still posture-only?

A: The clearest signs are good visibility but weak response, limited entitlement context, and no clear path from detection to enforcement. If the platform can list issues but cannot prioritise risk across identities, data sensitivity, and runtime activity, it is not governing behaviour.

Q: What does the move toward agentic AI support mean for cloud security architecture?

A: It means cloud security tools must understand AI-driven execution paths as part of the same governance model used for workloads and identities. Teams need correlation across access, integrations, and runtime signals so AI behaviour is assessed in context, not treated as a separate silo.

Technical breakdown

CIEM and access graphs in CNAPP

CIEM, or cloud infrastructure entitlement management, maps who and what can reach cloud resources and then highlights excessive or risky entitlements. In this article, Forrester’s scoring language shows that access graphs are becoming a core part of CNAPP evaluation because they reveal relationships between machine and human identities, data assets, and privilege sprawl. The practical value is not the graph itself but the ability to see where standing access is broader than the workload really needs. That matters when cloud roles, service identities, and third-party access all intersect in one platform.

Practical implication: treat entitlement visibility as a control surface, not a reporting feature, and use it to drive privilege reduction in cloud estates.

Agentless cloud workload protection versus sensor-based runtime control

Agentless cloud workload protection inspects cloud resources without installing software agents, which helps teams gain rapid coverage and reduce operational overhead. The article also notes Orca Sensor’s agent-based protections, showing that CNAPP vendors are balancing lightweight coverage with deeper runtime enforcement. In practice, this is a governance decision about how much behavioural control the platform can exert once workloads start executing. The issue is especially relevant when runtime privilege escalation or unusual network activity must be detected and contained before cloud blast radius expands.

Practical implication: validate whether your CNAPP strategy can move from detection into enforcement at runtime, especially for workloads that cannot tolerate heavy agents.

Agentic AI and third-party integrations as a CNAPP requirement

Agentic AI in this context means security tooling is being evaluated on whether it can understand and support AI-driven workloads as they run in cloud environments. The article pairs that criterion with depth and breadth of third-party integrations, which is a reminder that AI-related risk is now embedded in broader platform interoperability. CNAPP cannot remain a silo if it is expected to correlate identity, code origin, network behaviour, and runtime signals across cloud and AI workloads. That makes integration depth part of identity governance, not just a procurement feature.

Practical implication: confirm that AI workload telemetry and access data can be correlated across the tools already governing cloud identities and workload activity.

Breaches seen in the wild

• Kubeflow cryptomining attacks 2020: Exposed Kubeflow dashboards and a notebook's mounted Kubernetes service account let attackers run cryptominers on tens of ML clusters.

Read and download The State of NHI & AI Agent Breach Report 2026, covering 200+ breaches impacting Non-Human Identities including AI Agents.

NHI Mgmt Group analysis

CNAPP is being evaluated as an identity and action control plane. The significance of this wave is that cloud security platforms are no longer judged mainly on what they can observe. They are being compared on how well they connect entitlement context, workload behaviour, and enforcement decisions across cloud and AI workloads. For identity practitioners, that means CNAPP is moving into the same governance conversation as CIEM, runtime policy, and workload authorisation.

Agentic AI support changes the buying criteria for cloud security. Once AI-driven workloads become part of the estate, static posture checks are not enough to explain risk. Security teams now need telemetry that ties access, data exposure, and runtime behaviour together so they can understand how an AI-enabled workload is using privilege in context. That raises the bar for identity governance across cloud and automation programmes.

Privilege visibility is becoming inseparable from workload protection. The article’s emphasis on machine and human identity relationships reflects a broader shift in CNAPP: entitlement data is now operationally useful only when it is attached to workload behaviour. That makes CIEM, cloud workload protection, and identity analytics part of the same decision loop. Practitioners should expect cloud protection to be judged on whether it can reduce privilege and contain blast radius, not simply enumerate assets.

Cloud security platforms are converging on governed execution rather than passive detection. The report’s criteria point to a market where the useful CNAPP stack is the one that can prioritise, correlate, and act across identities, code, and runtime signals. That is a meaningful change for NHI and cloud IAM teams because it pushes governance closer to the moment privilege is used. The operational implication is that control ownership must be shared across cloud security, identity, and platform teams.

Named concept: identity-aware runtime CNAPP. This article illustrates a category shift in which CNAPP is expected to reason over identities as part of runtime protection, not as an adjacent inventory field. That is a more demanding model than posture management because it binds access, execution, and response into one control loop. Practitioners should treat identity-aware runtime CNAPP as a design requirement when cloud estates include AI workloads and third-party integrations.

From our research library:

• 88% of organisations have embedded AI agents in their workflows, according to KPMG's 2026 report.
• Read next: Agentic AI Identity Maturity Model

What this signals

Identity-aware runtime CNAPP: Cloud protection is shifting toward platforms that can evaluate entitlement context and runtime behaviour together, which is a better fit for estates where workloads, service identities, and AI paths overlap. That should prompt cloud and IAM teams to review whether their current controls can still distinguish visibility from enforceable governance.

For programme owners, the practical question is whether access graphs, workload telemetry, and policy enforcement share the same decision loop. If they do not, the organisation may see risk clearly but still be unable to contain it before it becomes operational.

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. That gap suggests CNAPP buyers should test AI workload support against real governance workflows, not marketing claims.

For practitioners

• Audit entitlement graphs for cloud blast radius Review whether your CNAPP can expose excessive access across human users, service accounts, and third-party identities, then tie those findings to remediation ownership.
• Test runtime enforcement on high-risk workloads Validate that the platform can do more than alert by enforcing policy against privilege escalation, suspicious process activity, or unusual network behaviour in live workloads.
• Map AI workload telemetry into identity governance Check whether AI-related workload events, access grants, and integrations flow into the same governance workflow used for cloud roles and machine identities.
• Separate detection coverage from enforcement coverage Document where agentless visibility ends and where agent-based or sensor-driven enforcement is required, especially for workloads that handle sensitive data or AI logic.

Key takeaways

• CNAPP is moving beyond visibility toward identity-aware runtime control, which makes entitlement data and enforcement capability equally important.
• The article shows that Forrester now rewards platforms that connect cloud posture, CIEM, agentless coverage, and AI workload awareness in one operating model.
• Practitioners should verify whether their CNAPP can reduce privilege and act on runtime risk, especially where AI and third-party integrations expand the attack surface.

Key terms

• Cloud Infrastructure Entitlement Management: Cloud Infrastructure Entitlement Management focuses on who has access to what in cloud systems, especially excessive or unused permissions. It helps reveal overprivileged identities, but it does not automatically remove them. In practice, it is most useful when tied to policy enforcement and access expiry mechanisms.
• Agentless Workload Protection: Agentless workload protection observes cloud workloads without installing a host agent on each system. It is useful for rapid coverage and low operational overhead, but it depends on cloud control-plane and metadata visibility, which means it can miss some runtime behaviors inside the workload itself.
• Agentic AI: Autonomous AI systems capable of planning, deciding, and taking actions, including calling APIs, writing code, and orchestrating other agents, with minimal human oversight. Agentic AI introduces new NHI risks as agents must authenticate to external services.
• Identity-Aware Runtime Control: Identity-aware runtime control is a governance pattern where access, workload behaviour, and enforcement decisions are evaluated together during execution. It matters when cloud or AI workloads can alter their own privilege use in ways that static posture checks cannot reliably capture.

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 building or maturing an IAM programme, it is worth exploring.