Topic starter
22/06/2026 10:13 am
TL;DR: Claude deployments expand risk from model prompts into tools, data, and inherited permissions, while reported incidents show agents can scope targets, harvest credentials, and exfiltrate data end to end, according to WitnessAI. The real issue is not model capability alone, but the identity and governance assumptions that break once AI systems act with enterprise credentials.
Editorial analysis by NHI Mgmt Group, based on content published by WitnessAI: “What are Claude AI security risks?”.
Key questions
Q: What breaks when Claude agents inherit user permissions in production?
A: The boundary between human use and machine action breaks first.
Q: Why do Claude deployments increase the risk of unauthorized data exfiltration?
A: Because the model can operate across connected tools and act on internal context, a single compromise can move from prompt abuse to target selection and data access.
Q: What are the signs that shadow AI is creating governance and compliance gaps?
A: Common signs include limited visibility into who is using AI tools, no reliable audit trail for prompts and outputs, unclear data residency, and inconsistent handling of sensitive information.
Practitioner guidance
- Map every Claude-connected tool path Inventory where Claude or Claude Code can reach internal systems, databases, APIs, and MCP servers, then classify each path by the permissions it inherits from the invoking user.
- Separate sanctioned from shadow AI use Identify unsanctioned Claude usage in developer tools, browser sessions, and external subscriptions, then route approved activity into monitored channels with logging and policy enforcement.
- Bind agent actions to attributed identities Require each agent action to be traceable to a human owner or service owner so investigators can reconstruct who authorised the session and what the system did.
Bottom line: Claude deployments become an identity problem as soon as the model can act through inherited permissions and connected tools.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
22/06/2026 11:01 am
Delegated AI authority is now an identity governance issue, not just a model safety issue. Once Claude is connected to enterprise tools and runs with inherited permissions, the control question shifts from what the model says to what the identity is allowed to do. That changes the centre of gravity for IAM, PAM, and NHI governance. Practitioners should treat agent-enabled access as delegated authority that must be bounded at runtime.
A few things that frame the scale:
- Claude Code-assisted commits leaked secrets at a rate of 3.2%, more than double the human-only baseline of 1.5%, with peaks reaching 31 secrets per 1,000 commits in August 2025, according to the State of Secrets Sprawl 2026.
- 43% of security professionals are concerned about AI systems learning and reproducing sensitive information patterns from codebases, according to the State of Secrets in AppSec.
A question worth separating out:
Q: What should organisations do when an AI agent can choose targets and tools on its own?
A: Treat that system as a delegated actor and constrain it before it reaches production data. The practical response is to limit tool scope, inspect both prompts and outputs, and require auditability that ties every action back to an accountable identity.
👉 Read our full editorial: Claude AI security risks are exposing enterprise identity gaps