The Governance Layer That Existing
Security Tools Don't Cover
CyberArk governs credentials. SailPoint governs identity. HashiCorp governs secrets. These tools address different layers from a release decision. AI agents or people request sensitive data or an action. At least M of N named human approvers must approve, and any single denial permanently vetoes the request. After the configured veto window, CAM makes one signed call to your system, delivers the result once to the approved destination, and discards it. CAM does not store the released data, and every step is recorded in a tamper-evident, hash-chained audit log.
Request details you submit, such as endpoint URLs and metadata, are kept with the audit record. Do not place sensitive data in them.
Why CAM Protocol Exists
Average US enterprise breach cost
IBM Cost of Data Breach Report 2025
Of enterprises have adequate AI agent governance
Gartner 2025
Global cybercrime cost in 2025
Cybersecurity Ventures Official Cybercrime Report 2025
Of AI-related breaches had no AI access controls
IBM Cost of Data Breach Report 2025
Review the controls in your stack.
CAM adds human approval for sensitive data access and actions.
CAM governs sensitive data access and actions requested by AI agents or people. At least M of N named human approvers must approve, any denial permanently vetoes the request, and the configured veto window must pass before CAM sends one signed call to the customer's system, which releases data or executes the action. CAM does not execute actions. CAM does not store the released data.
Network Security
Palo Alto · Zscaler · Cloudflare
Identity & SSO
Okta · Microsoft Entra · Ping Identity
Identity Governance
SailPoint · Saviynt · One Identity
Privileged Access (PAM)
CyberArk · BeyondTrust · Delinea
Secrets Management
HashiCorp Vault · AWS Secrets · Azure Key Vault
Endpoint / XDR
CrowdStrike · SentinelOne · Microsoft Defender
SIEM & Detection
Splunk · Microsoft Sentinel · IBM QRadar
Data Loss Prevention
Microsoft Purview · Forcepoint · Symantec DLP
Cloud Security Posture
Wiz · Prisma Cloud · Orca Security
AI Agent Request Governance
No dedicated release approval workflow shown
Human Approval for Sensitive Data and Actions
AI Agent Data and Action Requests
AI agents and people can request sensitive data access or actions.
M-of-N Human Approval
Thresholds define how many named human approvers must approve.
Built-In Denial Veto
Any one denial permanently vetoes the request.
Requests from AI Agents and People
Requests can come from AI agents or people.
Signed Call to Customer System
CAM sends one signed call to the customer's system.
Tamper-Evident Audit Log
CAM records each decision in a tamper-evident, SHA-256 hash-chained audit log.
CAM Protocol vs. Leading Security Platforms
Security platforms address credentials, identity, and secrets. CAM addresses sensitive data and action requests from AI agents and people.
| Capability | CAM Protocol | CyberArk | SailPoint | BeyondTrust | HashiCorp | Okta |
|---|---|---|---|---|---|---|
| Primary Purpose | Sensitive data access and action requests with named human approval | Privileged credential mgmt | Identity lifecycle mgmt | Endpoint privilege control | Secrets management | Identity & SSO |
| Release Authorization | Named human approval and denial veto | Yes: one admin credential grants privileged access | Yes: single workflow approver can grant access | Yes: single approver controls privilege escalation | Yes: stolen token grants full secret access, no human gate | Yes: one compromised identity reaches all SSO-connected systems |
| AI Agent Data Access and Action Requests | Requests routed to named human approvers | None | None | None | None | None |
| Named Human Approval Threshold | Named human approval threshold | Single approver | Sequential workflow | Single approver | None (token-based) | None |
| Denial / Veto Rights | Any denial permanently vetoes the request | None | None | None | None | None |
| Configured Veto Window | Window must pass before signed call | Session-based | Role expiration | Session-based | Token TTL | Session-based |
| Signed Call to Customer System | One signed call after approval and veto window | No | No | No | No | No |
| Governed Data Not Stored by CAM | Customer system handles governed releases | Identity/credentials only | Identity/roles only | Endpoint/credentials only | Secrets only | Identity only |
| Tamper-Evident Decision Log | Each decision recorded in a tamper-evident, SHA-256 hash-chained log | Session/credential logs | Role change logs | Session logs | Audit log | System log |
| Healthcare Data Release Requests | M-of-N human approval; any denial vetoes; window must pass | Via configuration | Via configuration | Via configuration | Via configuration | Via configuration |
Competitive data is based on publicly available documentation.
How CAM Is Built
Website data protection
The website is served over HTTPS/TLS. Encryption at rest for the contact database is managed by the infrastructure provider. See our trust page for the current data-handling details.
Purpose Limitation
CAM processes governance metadata, including request details and decision events.
Signed Call to Customer System
The customer's system handles each release or action.
See what is in place today and what remains on our roadmap.
Trust and data handlingReady to Integrate CAM Into Your Stack?
Priority onboarding for healthcare, financial services, and AI infrastructure teams.