Security and compliance teams can now monitor Claude Enterprise activity directly in Pluto, bringing Claude into the same governance workflows they already use for the rest of their AI estate.

AI assistants like Claude are now part of how every team works. As Claude Enterprise rolls out across organizations, security and compliance teams need the same level of visibility, control, and audit evidence they already have for the rest of their SaaS and AI stack. Without it, Claude usage stays in a parallel universe: vital to the business, opaque to security.

Pluto has built an integration with Anthropic’s Compliance API that brings Claude Enterprise activity directly into the Pluto platform. Customers now see Claude users, projects, and data flows as first-class entities in their AI inventory, governed by the same policies and audit timeline as every other application Pluto covers.

Discovering and mapping Claude across your environment

Through the Compliance API, Pluto continuously ingests:

  • The full roster of Claude Enterprise users, their roles, and role bindings
  • Projects, owners, and privacy settings, including which projects are private and which are shared org-wide
  • Attachments and datasets connected to each project, with content-aware classification
  • Permission changes, membership changes, and administrative actions, fed into Pluto’s audit timeline

Every resource is mapped onto the Pluto AI security graph and correlated with the rest of the organization’s identity, endpoint, and data context. The result is a centralized Claude Enterprise inventory: one place to ask who is using Claude, what they are working on, what data is connected, and how it has changed over time.

Visibility for teams across the organization

Pluto Top Risky Sessions list ranking Claude users by severity and number of detected risks
Pluto ranks Claude Enterprise sessions by risk, so teams start with the activity that matters most.

Security engineers get immediate visibility when a Claude project connects to a sensitive system, when a dataset contains regulated data, or when permissions drift outside policy. Pluto also scores each Claude session for risk and flags threat patterns – prompt injection, credential leakage, and data exfiltration – so a dangerous sequence of actions is surfaced, not buried in logs. Claude shows up in the same graph as the systems it touches, so blast radius is something they can see, not infer.

Pluto session risk summary flagging a credential-staging exfiltration pattern, with the agent activity timeline showing a prompt-injection attempt and a cat ~/.aws/credentials command
A single session, fully reconstructed: Pluto correlates the prompt, the tool calls, and the data accessed to explain why a session is critical.

Compliance leads get audit-ready evidence of how generative AI is governed: by user, by project, and by date. When an auditor asks who had access to what and when it changed, the answer is a record in Pluto, not a screenshot from an admin console.

Platform and IT teams can monitor Claude Enterprise for misconfigurations, dormant projects, and over-privileged users across the organization without having to log into Claude to investigate every alert.

Built into the ‘workflows’ you already use

Because Claude Enterprise is now a native entity in Pluto, all the tooling customers already rely on works for Claude out of the box: alerts, policies, automations, Slack notifications, and more. There is no second pane of glass to maintain and no separate process for getting Claude into the compliance program.

Get started

Pluto connector card for Claude.ai Enterprise with a Connect button
Connect Claude Enterprise to Pluto to begin monitoring usage and enforcing governance policies across your org.

The Pluto integration with Anthropic’s Compliance API is available in Private Preview for organizations using both Pluto and Claude Enterprise.