# Edison | AI Data Leak Prevention

AI data leak prevention. Govern how agents access your data so you can adopt AI (Claude, ChatGPT, Cursor) and connect securely to real data, without data leaks.

## What is Edison?

Edison is AI data leak prevention for agentic AI: one place to govern how every agent accesses your data. Traditional RBAC and data security break down when AI agents connect to enterprise software via MCP and other tool protocols. Edison sits between any agent and your data sources, assigning a live risk score to every agent action, so security leaders get the observability, runtime enforcement, and unified control they need to adopt AI without data leaks.

## Key Capabilities

- **Real-time session monitoring** - See every tool call, every data flow, every external service contact
- **Deterministic policy enforcement** - Runtime controls at the tool-call level, not probabilistic guardrails
- **Shadow MCP discovery** - Detects unauthorized tool servers the moment they appear on devices running the Edison Watch daemon
- **Secure AI on any device** - Applies continuous monitoring and enforcement on enrolled endpoints
- **Complete audit trails** - System of record for all agentic actions: who did what, when, and why
- **SIEM integration** - Streams audit events to Splunk HEC and custom HTTP endpoints
- **Policy automation** - Auto-enforces company data policy, reducing IT tickets for agentic actions

## The Problem

59% of business and IT leaders say AI risks outpace their expertise. Agentic AI breaks traditional data security by connecting to existing software through tools, bypassing access controls designed for humans. Security leaders lack holistic visibility into how AI agents interact with company data.

## MCP Client Coverage

Stable coverage includes Claude Code, Cursor, VS Code, and Codex CLI. Beta coverage includes Claude Desktop, Claude Cowork, Windsurf, Zed, and JetBrains IDEs.

## Proof-Oriented Docs

- MCP quarantine: https://docs.edison.watch/en/docs/admin-guide/mcp-quarantine
- MCP server management: https://docs.edison.watch/en/docs/admin-guide/managing-servers
- Access control: https://docs.edison.watch/en/docs/admin-guide/access-control
- Policy rules: https://docs.edison.watch/en/docs/admin-guide/policy-rules
- Monitoring sessions: https://docs.edison.watch/en/docs/admin-guide/monitoring-sessions
- SIEM integration: https://docs.edison.watch/en/docs/enterprise/siem-integration
- Security posture: https://docs.edison.watch/en/docs/security/self-serve-security
- MCP dependency pinning: https://docs.edison.watch/en/docs/security/mcp-dependency-pinning

## Machine-Readable Product Card

Product capability card: /.well-known/agent-card.json

Edison has MCP support for gateway/proxy, server management, daemon-based MCP configuration monitoring, and MCP server quarantine. Edison does not currently publish a public API or OpenAPI specification.

## Scope Notes

MCP quarantine covers declared MCP servers; non-MCP plugins and native extensions are outside MCP quarantine scope. MCP quarantine requires the Edison Watch daemon to be installed and persistently running on the user device.

## Team Experience

Applying cybersecurity and AI experience from Wayve, Synopsys, Oxford University, CrowdStrike, and Citadel Securities.

## Get Started

Email: hello@edison.watch
Demo: https://edison.watch/#cta

## Links

- Documentation: https://docs.edison.watch
- Blog: blog.edison.watch
- LinkedIn: https://www.linkedin.com/company/edisonwatch/
- X/Twitter: https://x.com/edison_watch

## Legal

- [Terms of Service](https://edison.watch/terms-of-service)
- [Privacy Policy](https://edison.watch/privacy-policy)
- [Subprocessors](https://edison.watch/subprocessors)

## Company

EdisonWatch (GPU-EVM LTD)
3rd Floor, 86-90 Paul Street, London EC2A 4NE, United Kingdom