Topic starter
11/07/2026 8:47 pm
TL;DR: Enterprises are embedding AI into core workflows while security teams struggle to see prompts, tools, MCP-connected agents, and data flows, according to SentinelOne. The key issue is not just detection speed, but whether governance can keep pace with AI systems that reason, delegate, and act across multiple control planes.
Editorial analysis by NHI Mgmt Group, based on content published by SentinelOne: “AI Security: Defining and Defending Cybersecurity’s Next Frontier”.
Key questions
Q: How should security teams govern AI use in developer tooling?
A: Security teams should govern AI use as a data and access problem, not only a productivity feature.
Q: Why do AI models create governance risk even without retraining?
A: Because behaviour can change at inference time when the model sees new context, examples, or instructions.
Q: What are the signs that AI security controls are lagging behind AI deployment?
A: Common warning signs include broad AI use with limited governance, unclear ownership for risk decisions, weak visibility into model usage, and inconsistent security testing before deployment.
Practitioner guidance
- Inventory AI tools, assistants, and agent connections Create a live register of sanctioned and shadow AI tools, including browser assistants, developer copilots, and agent-to-agent links.
- Enforce policy at the prompt and action layer Apply controls that inspect prompts, outputs, and tool calls before sensitive data is exposed or an agent executes a downstream action.
- Map agent authority to identity governance records Record which user, service, or workflow owns each AI agent and what data sources or tools it can reach on their behalf.
Bottom line: AI has become a broad attack surface because employees, developers, and agents use it across ordinary workflows without consistent visibility or governance.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/07/2026 9:14 pm
AI security governance now depends on the control plane, not just the model. The article’s central point is that organisations are trying to govern AI with tools that cannot see prompts, connected assistants, agent actions, or downstream data movement. That creates a governance gap where policy exists in theory but cannot be enforced at the point of use. For identity teams, this means AI usage has to be tied to access control, ownership, and auditability if it is to remain governable.
A few things that frame the scale:
- Only 23% of IT leaders were very confident in their organisation's ability to manage security and governance for GenAI deployments, according to a 2025 Gartner survey of 360 IT leaders.
A question worth separating out:
Q: How do AI security programmes differ from traditional endpoint or cloud security programmes?
A: Traditional programmes focus on devices, workloads, and network paths. AI security also has to govern context, intent, and delegated action across prompts, tools, models, and agent chains. The difference is that the control boundary moves from infrastructure alone to the full decision path that AI systems use to access and transform data.
👉 Read our full editorial: AI security’s governance gap is visibility, context, and control