Topic starter
12/06/2026 9:35 pm
TL;DR: Enterprises cannot safely scale AI on chips, models, and compute alone because trust depends on what AI can see and do, according to Cyera’s Series G announcement. Data classification, identity controls, DLP, and AI usage governance are now the practical boundary between enablement and uncontrolled exposure.
Editorial analysis by NHI Mgmt Group, based on content published by Cyera: “Building The Trust Layer for Enterprise AI”.
By the numbers:
- Cyera says it shipped more than 100 new product capabilities across DSPM, privacy, identity, DLP, and agentic security over the last year.
Key questions
Q: What breaks when AI security is treated only as model security?
A: Model-only security misses the part of the system that actually touches tools, data, and workflows in production.
Q: Why do AI agents and automated accounts need separate identity controls from human users?
A: AI agents act at machine speed, can scale actions quickly, and often hold access across multiple systems.
Q: How should security teams govern employee AI use without blocking productivity?
A: Start with visibility into sanctioned and shadow AI use, then apply runtime policies that inspect intent and context rather than only keywords.
Practitioner guidance
- Define AI trust boundaries by data class Map each AI use case to the sensitive data classes it may read, summarise, or return, then block any workflow that cannot be matched to an approved classification policy.
- Inventory AI runtime identities separately Catalogue the service accounts, tokens, and delegated credentials used by AI applications and agents, then review them as non-human identities rather than as part of human access reviews.
- Apply usage governance at the workflow boundary Set rules for prompts, outputs, and action triggers so AI systems cannot move from authorised access into unrestricted data handling or downstream business actions.
Bottom line: Enterprise AI security is moving from model-centric thinking to trust-boundary control across data, identity, and usage.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
12/06/2026 11:47 pm
AI trust now functions as an identity and data governance problem, not a model-quality problem. Cyera's framing is important because it shifts the centre of gravity away from infrastructure scale and toward controlled exposure. Enterprises do not fail AI trust because the model is unavailable; they fail when the AI can see more data than the governance model can justify. The practitioner conclusion is that AI security now starts with identity-scoped data access.
A few things that frame the scale:
- AI-related credential leaks surged 81.5% year-over-year in 2025, with the surrounding AI infrastructure leaking 5x faster than core LLM providers, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: How do identity and cloud teams share responsibility for agentic AI risk?
A: Identity teams own the privileges, connected accounts, and review process, while cloud teams own exposure, reachability, and workload context. Neither view is sufficient alone. Shared responsibility means validated AI findings must flow into the same governance records used for access decisions, so exposure, privilege, and evidence stay aligned.
👉 Read our full editorial: AI trust layers and identity controls now anchor enterprise AI security