TL;DR: Claude governance has moved beyond prompt oversight to files, connectors, agent actions and model choice, Lumia Security says. Policies now need runtime enforcement because entitlement alone cannot decide whether a specific AI action is acceptable.
Editorial analysis by NHI Mgmt Group, based on content published by Lumia Security: “AI Governance for Claude: How to Secure Code, Cowork, and Agents”.
Key questions
Q: Why do permissions alone not control risky AI use?
A: Permissions only answer whether access exists.
Q: How should security teams govern personal AI assistants that act on behalf of employees?
A: Treat each assistant as a distinct non-human actor with its own identity, policy scope, and audit trail.
Q: How should organisations govern AI assistants that can read and act on inbox messages?
A: They should define those assistants as delegated non-human identities with explicit message scope, action scope, and escalation limits.
Practitioner guidance
- Define acceptable Claude use by workflow, not by product alone Specify approved products, accounts, data types, connected tools and agent actions, plus when premium models require justification or approval.
- Enforce policy before data leaves the environment Use runtime controls to inspect prompts and files, block prohibited transfers, and redact sensitive values such as credentials or payment data.
- Separate corporate and personal usage decisions Require the system to identify which account is in use and apply different rules to enterprise-approved and personal access paths.
Bottom line: Claude governance has expanded from prompt oversight to control of files, connectors, agent actions and model choice.
Glossary terms: AI Governance, Agentic workflow, Context-aware Enforcement, Model Routing Layer
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Claude governance is now an AI access problem, not just a prompt-safety problem. Once an AI system can read files, reach business tools and act through agents, the governance question shifts from content moderation to decision control. That means security teams have to govern account state, data classification, action scope and approval context together. The useful unit of control is no longer the prompt; it is the end-to-end interaction.
A few things that frame the scale:
- 63% of organisations surveyed lacked AI governance policies to manage AI or prevent shadow AI, according to IBM's 2025 Cost of a Data Breach Report.
A question worth separating out:
Q: How should organisations enforce AI policy compliance across employee and agent use?
A: Start by classifying AI usage by identity type, data sensitivity, and execution context, then enforce policy at runtime rather than only through written rules. Human users, enterprise copilots, and autonomous agents should not share the same control path if they can process different data or take different actions. The goal is visible, auditable behaviour control.
👉 Read our full editorial: Governing Claude across chat, code and agents needs runtime controls