Security
Trust boundaries for governed act: metadata-first audit, residency by tier, and honest compliance wording for procurement.
This page is the trust chapter in Operate. Hand it to security and procurement after Audit & metrics and Threat signals & approvals. Proof and policy still share one compileHash thread with Runs and Runtime policy.
Governance boundary
Blekline governs agent boundaries: IDE hooks, MCP proxy, SDK, API ingress, and cluster cells. Enforcement runs before model and tool side effects. Ingress mask and response handling reduce sensitive content in flight; default audit is metadata, not a prompt archive.
Metadata by default
Workspace audit log, compliance export, and default POST /api/events ingest are designed for metadata-only records. See Audit & metrics for investigations and Events API for automation.
| Stored (default) | Not stored (default) |
|---|---|
| kind, action, verdict, entitiesMasked, riskTier | Raw prompt body |
| mcpToolName, clientSurface, requestId, compileHash | Full tool argument payloads (default) |
| Mask provider and phase labels | Durable cloud PII payload archive |
Mask and ingress in transit
Mask and enforce calls send prompt or tool summaries over TLS to the control plane for evaluation. The response returns masked text or a verdict. Original prompt bodies are not written to the default audit stream. Tool enforcement evaluates policy locally or via API without storing full argument bodies in default ingest.
For workloads that must not leave the cluster, use sidecar or local fast paths documented in Spin up cells (VPC sidecar). Client wiring lives in Connect agents and clients.
Act run residency
Residency splits between hosted act and customer VPC cells. Metering vs placement is in Billing & limits; attach and profiles are in Spin up cells.
| Tier | Act execution | Control plane |
|---|---|---|
| Platform Team | Hosted act pool (EEA-first SaaS posture). | app.blekline.com control plane and audit metadata. |
| Platform Production | cells in your VPC. | Orchestration and metadata on the control plane. |
Tokenization archive
Open Monitor → Tokenization Archive for retention policy, archive metadata, and legal hold KPIs. Full tokenize and hydrate runs in your VPC when the Trust Vault sidecar is deployed. Endpoint credentials are configured on Endpoints; workspace tokens are on API keys.
Workspace access
Configure sign-in methods and primary identity on Workspace → Authentication. Scope automation tokens in API keys (mask:write, events:write, runs:write, and others). Rotate keys on a regular cadence.
Evidence and export
| Surface | Use |
|---|---|
| Audit log | Per-event proof with compileHash and verdict filters. |
| Compliance export | Batch metadata extracts for GRC and committee packs. |
| Evidence integrations | Forward metadata to SIEM when your plan includes webhooks. |
| Tokenization Archive | Retention policy and archive metadata in Monitor; Trust Vault sidecar tokenize in your VPC. |
Forwarding to SIEM is metadata-oriented by default. Field shapes are in Telemetry and events. Configure webhooks on Evidence integrations when your plan includes them.
Compliance posture
Diligence packs may reference subprocessors and privacy policy on blekline.com/subprocessors and blekline.com/privacy. Static cluster posture audits can use the OSS @blekline/cluster-posture CLI (POSTURE rules). That is not a shadow MCP registry.
| Capability | Status | Note |
|---|---|---|
| Mask and enforce at client ingress | Shipped | Hooks, MCP proxy, SDK, and API paths. |
| Metadata-only audit and export | Shipped | Audit log and compliance export default. |
| Trust Vault sidecar | Shipped v1 | In-cluster tokenize and hydrate when entitled. |
| Cluster posture CLI | Shipped (OSS) | Static cluster audit; not a fleet MCP registry. |
| SAML SSO | Enterprise program | OIDC and sign-in methods in workspace today. |
| SOC 2 Type II | Roadmap | Contact sales for questionnaire status. |
What Blekline is not
- A WAF or network packet firewall.
- A full CASB or cross-SaaS DLP estate.
- A certification claim unless your org letter says otherwise.