Join our Newsletter — 33% off our NHI Course

Does the 2025 readiness report show agents are the hardest risk class?

 

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

TL;DR: The 2025 AI Data Security Readiness report says autonomous AI agents are the hardest to secure for 76% of respondents, according to Cyera's analysis. Teams need tighter links between identity, data classification, and runtime policy if discovery at scale is going to translate into real governance.

Editorial analysis by NHI Mgmt Group, based on content published by Cyera: “Cyera Becomes One of the Top 10 Fastest-Growing Companies, Powering the New Era of AI and Data Security”.

By the numbers:

  • Cyera says its platform has protected more than 530 million identities.

Key questions

Q: Why do AI coding agents make application security harder to govern?

A: AI coding agents increase risk because they can generate large volumes of code quickly, often optimised for function over security.

Q: What breaks when data classification is incomplete in AI environments?

A: When classification is incomplete, policy enforcement becomes unreliable because the security stack is operating without a trustworthy view of the data estate.

Q: How should security teams govern sensitive data used by AI systems?

A: Security teams should treat AI as a data consumer that needs policy boundaries, not just authentication.

Practitioner guidance

  • Map AI agent data interactions Inventory which models and agents can reach sensitive data, which prompts they process, and which downstream workflows they trigger.
  • Bind authorisation to agent purpose Define acceptable agent actions by business purpose, data class, and workflow context, then enforce those rules where the agent requests or transforms data.
  • Unify classification with runtime detection Correlate data classification signals with agent telemetry, prompt activity, and access events so inappropriate use patterns can be seen in context.

Bottom line: AI agents change the control problem because they act on data, not just access it.

Glossary terms: Data Security Posture Management, AI Agent Governance, Agent-Use Ambiguity, Runtime Policy Enforcement

Explore further

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


This topic was modified 2 weeks ago by NHI Mgmt Group

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

AI agent growth exposes a data control boundary problem, not just a visibility problem: The article shows that enterprises can now discover and classify enormous data estates, yet still struggle to govern what autonomous systems do with that data. That gap matters because AI agents create risk through use, not just storage or location. The practitioner conclusion is that data security programmes have to account for runtime behaviour, not only static exposure.

A few things that frame the scale:

A question worth separating out:

Q: Should AI security be managed separately from IAM and data protection?

A: No. AI security becomes practical only when it is absorbed into existing identity and data governance. The same entitlement reviews, access approvals, and data classification rules that govern other sensitive systems need to apply to AI retrieval paths as well.

👉 Read our full editorial: AI agent growth is exposing the limits of data security controls



   
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.