When an AI agent can act on your most sensitive data, one approval isn't enough. CAM requires a human quorum before anything executes, by design, not by policy.
Built for what you're governing
Choose Your Governed Surface
Mandatory quorum before any AI-initiated access to client accounts or portfolios
Before an AI agent or operator can access sensitive client data, portfolio positions, or execute asset movements, M-of-N approval from a configurable set of authorized principals is required. No single advisor or automated agent can unilaterally authorize access.
Coercion-resistant by design: veto evaluated before the approval counter
CAM's Single-Denial Veto gives compliance officers and risk managers a hard block that fires before quorum completes. A single flagged approver stops the action immediately, architecturally and not by policy.
Supports fiduciary accountability with a hash-chained audit log
Every authorization request, approval, denial, and execution is append-only and cryptographically-anchored. Both the advising firm and the compliance function hold independent read access. No operator has write capability post-commit.
Ephemeral access to account and position data
Sensitive client account data and position records are released only at the moment threshold conditions are satisfied, and only for the duration of a time-bound token. An attacker who defeats the governance layer finds no persistent data surface.
Featured Capabilities
How It Works
High-value transaction initiated
Governance layer evaluates the request against configured quorum policy.
M-of-N approvers authorize. Veto check runs first. Any denial blocks immediately.
Time-bound token issued. Data released only now. Immutable audit entry written.
All events → append-only bilateral audit log. Neither party has write access.
The threat landscape
A record of verified incidents where legitimate credentials, authorized integrations, or an AI agent itself became the path to sensitive data. Each entry states what the attacker was hunting, what CAM's architecture removes from a target like it, and what CAM does not cover.
Live count
Time since the last major breach where the perimeter failed and sensitive data was there to take.
Counting from July 16, 2026: HuggingFace autonomous-AI infrastructure breach. This is a measure of the threat landscape, not a claim about CAM. Source: HuggingFace disclosure.
The acceleration
reported AI breaches now involve autonomous agents, per HiddenLayer's 2026 AI Threat Landscape Report.
Roughly 89 percent year-over-year growth in AI-enabled attacks, per aggregated threat-intelligence reporting.
Source: HiddenLayer, 2026 AI Threat Landscape Report
Verified timeline · oldest to newest
Select an incident to read its detail
HuggingFace dataset-processing pipeline and cloud infrastructure
As HuggingFace disclosed it, an autonomous AI agent chained two remote-code-execution paths in the dataset-processing pipeline, harvested cloud and cluster credentials, and moved laterally over a weekend. A limited set of internal datasets and several credentials were accessed.
What the attacker was after
Infrastructure credentials first, then reach across the environment to whatever data those credentials opened.
What CAM's architecture removes
Lateral movement pays off only where reaching a system is the same as being allowed to release its data. Under CAM those are separate steps: a release requires an M-of-N human quorum, the data is released only inside a time-bound scoped token, and the governance layer retains no persistent sensitive-data payload between requests.
Scope, stated plainly
CAM governs the data-release and authorization boundary. It would not have stopped the initial remote-code-execution chain or the lateral movement. Attribution is still emerging, including the possibility that this was an AI model evaluation.
Source: HuggingFace disclosure
Live Protocol Demo
An AI agent requests access. A human Circle decides. Any member can veto. Watch all four patent-pending elements execute live.
Rotate device to landscape to view demo clearer
FINANCIAL SERVICES · HEALTHCARE · AI AGENT GOVERNANCE · ENTERPRISE & WORKFORCE · M-OF-N QUORUM · SINGLE-DENIAL VETO · EPHEMERAL RELEASE · BILATERAL AUDIT
Compliance Diagnostic
Answer 3 questions. Get an instant verdict on whether your enterprise needs CAM, and how it maps to your regulatory exposure.
Your industry
Go deeper
The Question Your Board Will Ask
The SEC now examines whether firms can prove human oversight of their AI, and EU AI Act Article 14 makes that same oversight enforceable law. Across finance, cybersecurity, and every regulated industry the question is the same: when a regulator asks what your AI did and who authorized it, CAM Protocol produces the auditable, multi-party human-oversight record for every AI-initiated action.
CAM Protocol is available via enterprise API licensing. Inquiries from financial services, wealth management, cybersecurity, and other regulated-industry teams welcome.