Knowbe4 iconKnowbe4Sep 29, 2026 ~5 min source read

KnowBe4 Integrates Agent Risk Manager with Claude Compliance API to Monitor Claude Activity

KnowBe4’s Agent Risk Manager brings Claude activity into a single console for inventory, risk detection, and user-level visibility so security teams can treat AI agent activity like other human-driven risks.

Govern Claude AI with KnowBe4’s Agent Risk Manager

Share this story

Send the public story page.

Useful takeaways from this story.

Agent Risk Manager connects to the Claude Compliance API to collect Claude activity into KnowBe4’s AI Activity Log and User Activity views.

Detections evaluate prompt injection, sensitive data and PII exposure, privilege escalation, excessive agency, and unapproved access using full interaction context.

A single Compliance API key lets Agent Risk Manager discover every workspace tied to an organization’s Claude key with no per-agent setup.

# The problem: AI agents act where controls don't reach

# What the integration delivers Agent Risk Manager integrates with Anthropic's Claude Compliance API to bring Claude activity into the KnowBe4 Platform's Agent Risk Manager console. This places Claude alongside other monitored agents such as Microsoft Copilot Studio, ChatGPT, Google Gemini, and browser-based shadow AI. The integration provides:

  • A proactive inventory of Claude agents and tools tied to your organization's Compliance API key.
  • A unified AI Activity Log that centralizes detections and policy events instead of scattering them across multiple consoles.
  • User-level linkage that ties agent actions to the people behind them, helping security teams investigate incidents and assign responsibility.

# Detection capabilities

# Coverage and deployment model Only one Claude Compliance API key is required. Agent Risk Manager automatically discovers every workspace associated with that organization key, removing the need for per-team or per-agent configuration. What Agent Risk Manager can see depends on how Claude is deployed:

  • On Claude Enterprise, visibility can include conversation content such as chats and files.

Visibility follows the organization's deployment and the data available via the Compliance API.

# How organizations start activity. KnowBe4 outlines practical questions teams should be able to answer: How are you seeing AI activity? Do you know every agent and tool touching your systems or only those IT signed off on? If Claude connects to a shared drive, would someone notice by day's end? If something went wrong, could you trace it?

For organizations already using Agent Risk Manager, setting up the Claude integration is a one-time process:

  1. Add that key in Agent Risk Manager under Setup > Integrations using the Anthropic Claude Compliance tile.
  2. After connection tests healthy, Claude activity begins flowing into the AI Activity Log and User Activity views.

# Availability and context

# Practical next steps for security teams If Claude is in use at your organization, verify whether a Claude Compliance API key exists and who holds Primary Owner access. If you already run Agent Risk Manager, prepare to add the Compliance API key through the Integrations setup. If you do not yet have Agent Risk Manager, map where Claude activity currently appears in your environment so you can compare centralized logs and user linkage once the integration is active.

More context around this story.

Loading more related stories...

Keep reading in the app

Open the app view to save this story, compare related coverage, and continue from the same source.

Open in app