Into the Expanse: A Security Leader’s Guide to the Agent Frontier
Read more
Get a demo
Reco
Claude
ECOSYSTEM INTEGRATIONS > CLAUDE

Accelerate
Claude Adoption. Secure the Reach.

Deploy Claude across your enterprise with continuous environment visibility, pre-inference inspection, and reach containment. Reco governs agent identities, MCP tool permissions, and third-party data reach surrounding Claude across Claude Enterprise, Claude Platform, native inference hooks, and local Model Context Protocol (MCP) connections.

The Bi-Directional Integration Architecture

Complete AI governance in both directions: Reco governs the environment surrounding Claude, and Claude queries Reco’s normalized context graph.

Reco Governs the Environment Surrounding Claude

Reco connects out-of-band via read-only APIs and native platform hooks to inspect Claude administrative, execution, and development surfaces (supported for Anthropic-hosted deployments; does not apply to third-party hosted cloud instances such as AWS Bedrock or Google Vertex AI):

01

Claude Enterprise (via Claude’s Compliance API)

Continuous visibility into user directories, enterprise workspaces, project data boundaries, conversation content inspection, and user activity feeds. Enforces centralized off-boarding, MFA policies, and prevents sensitive data exfiltration.

02

Pre-Inference Prompt & Transcript Inspection (via Native Inference Hooks)

Moves security enforcement directly onto Anthropic infrastructure. Reco acts as your configured security evaluation server: prompts, prior tool calls, and session transcripts are evaluated against corporate policy and cleared or blocked before Claude ever sees them—stopping PII, payment card numbers, or proprietary code leaks across Claude Chat, Cowork, and Claude Code sessions.

03

Claude Platform (Developer Console & Workspaces)

Complete governance over developer API keys, workspace memberships, and activity/audit logs. Tracks assigned tools, service accounts, and permission policies back to human owners without citing or restricting underlying model execution.

04

Local & Remote MCP Protocol Governance

Inspects and governs Model Context Protocol (MCP) client-server connections across local developer endpoints (`stdio`) and remote services (`SSE`). Prevents tool poisoning, tool drift, and unauthorized tool invocation surrounding Claude.

Claude Queries Reco

Reco exposes a native Model Context Protocol (MCP) server that enables Claude to query enterprise security posture:

  • Natural-Language Identity & Posture Investigations: Security analysts can query Claude directly to inspect toxic permission combinations, cross-app access paths, and dormant service tokens.
  • Normalized Context Graph Telemetry: Claude queries Reco’s real-time identity graph, pulling live telemetry across 285+ native third-party integrations to trace agent blast radius in seconds.
Claude queries Reco’s context graph

The 6 Critical Risk Categories Reco Governs

Risk Category
Enterprise Threat
Reco Integration Control
Risk Category

1. Shadow Agent & Account Sprawl

Enterprise Threat

Unsanctioned Claude accounts, rogue projects, and unvetted MCP servers deployed by business units.

Reco Integration Control

Continuous discovery across endpoints, identity providers, and network egress; classifies every Claude workspace automatically.

Risk Category

2. Sensitive Data Extraction

Enterprise Threat

Unregulated transfer of customer records, PII, intellectual property, or source code into Claude prompts.

Reco Integration Control

Real-time data exposure mapping via Claude Enterprise and pre-inference blocking via native inference hooks before data reaches the model.

Risk Category

3. Prompt Injection & Tool Poisoning

Enterprise Threat

Malicious instructions embedded in untrusted external data (memory/RAG poisoning or compromised MCP responses).

Reco Integration Control

Runtime MCP tool-call inspection, schema validation, and third-party data reach boundary enforcement around Claude.

Risk Category

4. Developer API Key Exposure

Enterprise Threat

Long-lived Claude Platform API keys hardcoded in codebases, CI/CD pipelines, or local scripts.

Reco Integration Control

Instant detection of leaked, dormant, or over-scoped API keys with automated revocation workflows.

Risk Category

5. Excessive Agent Agency

Enterprise Threat

Autonomous agents granted broad read/write access beyond their immediate task scope.

Reco Integration Control

Enforces least-privilege boundaries and maps transitive blast radius across all downstream third-party API connections surrounding Claude.

Risk Category

6. Off-Boarding & Orphaned Identities

Enterprise Threat

Departing engineers or contractors leaving behind active Claude Platform API keys, projects, or autonomous agents.

Reco Integration Control

Correlates IdP lifecycle status (Okta, Azure AD, Ping) to immediately revoke orphaned tokens and reassign agent ownership.

The CISO’s Guide to Claude Risk in the Enterprise
The CISO’s Guide to Claude Risk in the Enterprise

Secure Claude Risk in the Enterprise

Get the guide
The Reco Graph connecting identities, agents and third-party appsThe Reco Graph connecting identities, agents and third-party apps

The Reco Graph: Context Beyond the Claude Boundary

While point AI security tools treat Claude as an isolated silo, Reco analyzes the broader environment:

  • Multi-Hop Reach Analysis: An Agent reading a customer support ticket in Zendesk might access an embedded token leading to your Snowflake warehouse. Reco maps every multi-hop path surrounding Claude before execution occurs.
  • Hundreds of Native Third-Party Connectors: Pre-built, agentless API connectors across Salesforce, Google Workspace, GitHub, Slack, AWS, Workday, and Microsoft 365.
  • Toxic Combination Management: Surfaces dangerous intersections—such as an Agent with broad third-party write permissions owned by a deactivated employee.

Compliance & Audit Readiness

Framework
Applicable Claude Control
Reco Audit Evidence
Framework

SOC 2 Type II

Applicable Claude Control

CC6.1, CC6.2, CC6.3 (Access control, least privilege, off-boarding)

Reco Audit Evidence

Verifiable inventory of all Claude users, active Claude Platform API keys, inference policy logs, and automated de-provisioning records.

Framework

ISO / IEC 27001

Applicable Claude Control

A.9.2, A.9.4 (User access management and system access restriction)

Reco Audit Evidence

Continuous configuration drift detection and RBAC enforcement across Claude Enterprise.

Framework

NIST AI RMF 1.0

Applicable Claude Control

GOVERN 1.2, MAP 1.5, MEASURE 2.6 (AI risk mapping and reach containment)

Reco Audit Evidence

Multi-hop blast-radius mapping and continuous non-human identity lifecycle monitoring across the Claude environment.

Framework

CIS Controls v8

Applicable Claude Control

Control 5 (Account Management) & Control 6 (Access Control Management)

Reco Audit Evidence

Full discovery of shadow Claude accounts, unapproved workspaces, and stale API tokens.

Deploy Claude with Confidence. Govern What Claude Can Reach.