TL;DR: AI governance becomes a runtime control problem across employees and autonomous agents, according to Lumia Security. Security teams need policies that reflect business context if they want AI rules to be enforceable in real work.
Editorial analysis by NHI Mgmt Group, based on content published by Lumia Security: “Lumia Security Named as a Cool Vendor in the 2026 Gartner Coolest Vendor Innovations in Securing AI”.
By the numbers:
- The company emerged from stealth in December 2025 with $18 million in seed funding.
Key questions
Q: Why do static data classifications fall short for AI governance?
A: Because many AI risks are not about a single data type, but about the meaning of the request in a specific business context.
Q: What breaks when organisations monitor AI but cannot intervene in real time?
A: They get visibility without control.
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 policy in business terms Write rules around the tasks, topics and outcomes that matter to the organisation, not just around broad data classes or generic acceptable-use language.
- Map where AI actions are actually enforced Inventory the applications, browsers, coding environments and agent workflows where AI interactions occur, then identify where policy can be applied before a decision completes.
- Separate human and agent authority Document which actions may be taken by people, which may be delegated to agents, and which require explicit approval or intervention before execution.
Bottom line: The article frames AI governance as a runtime control problem that spans both employee usage and autonomous agent activity.
Glossary terms: Agentic AI, Runtime Policy Enforcement, Business Context Rules, Agent Authority
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
AI governance is becoming an access-control problem, not a content-moderation problem. The article’s central shift is from classifying prompts after the fact to controlling what AI is allowed to do in the moment. That is closer to identity governance than traditional DLP because the question is not only what data was seen, but whether the acting entity, human or agent, had legitimate authority to use it. Security teams should treat AI policy as a runtime authorization layer, not as a reporting layer.
A few things that frame the scale:
- According to Gartner, worldwide spending on generative AI is set to reach $644 billion in 2025, a nearly 77% year-over-year increase.
A question worth separating out:
Q: What is the difference between governing human AI use and autonomous agent actions?
A: Human use is usually bounded by awareness and direct accountability, while agent actions can execute independently across systems with delegated authority. That means agent governance has to focus on permission scope, revocation, and runtime controls. If an agent can act without supervision, it should be governed like an identity with tightly constrained authority.
👉 Read our full editorial: Governing AI use across employees and autonomous agents