Security boundaries
CMP Core operator protection and managed Cloud authorization remain distinct.
CMP context repositories may contain sensitive knowledge. Access control and evidence authorization must be validated before responding to clients or writing records.
Self-hosted CMP Core
The current open-source reference server is development-only. It requires a locally configured bearer token, binds to loopback, and refuses production mode. This is not multi-user OAuth, tenant isolation or production-ready deployment security. Do not make it publicly reachable.
CMP Cloud
Managed OAuth, accounts, organizations, per-repository permissions, external source credentials, Connect, agent identity, WebSocket streams, session archive policy and retention belong to the proprietary Cloud backend.
Cloud integrations must not return evidence that the authorized requester cannot access. Session capture needs both managed policy approval and a host-side opt-in; deletion, encryption, audit and retention require verified end-to-end controls.
The presence of an SDK call does not bypass Cloud authorization or imply the backend is deployed.