01
Policy lifecycle
Author, validate, version, target, publish, and review governance policy without treating scattered logger or Collector configuration as the authoritative control plane.
Available in Azure MarketplaceCerbiShield · control + evidence plane
Operate telemetry governancefrom one control plane.
Define policy, target enforcement, publish signed runtime policy, investigate findings, verify Gateway readiness, and retain evidence while your existing logging and observability destinations stay in place.
Customer-hosted in AzureStream + Gateway policy lifecycleBounded governance evidence
Interactive proof01
Governance input
Runtime Policy Bundle v18
02
Control-plane state
SIGNED
payments-prodSIGNED
Policy version, hash, target, and owner retained
What CerbiShield owns
The lifecycle around enforcement is the product.
Logger filters and OpenTelemetry processors can execute individual transformations. CerbiShield provides the authoritative lifecycle around policy, targeting, deployment, investigation, evidence, and operational review.
02
Deployment control
Publish signed Runtime Policy Bundles to intended targets and keep deployment state and history tied to the policy lifecycle.
03
Governance operations
Track posture, findings, enforcement state, workload risk, validation, Gateway readiness, and service health from one operating surface.
04
Evidence and audit
Retain policy, deployment, finding, exception, reporting, and audit records that help teams review what the control was expected to do and what happened.
05
AI telemetry logging evidence
A separate deployment option from the Cerbi AI assistant. The scope is AI telemetry metadata, scanner findings, runtime log observations, settings, and redacted evidence, with raw prompt and response storage off by default.
01Operate
Start from governance posture, not a pile of raw logs.
The Governance Command Center brings policy coverage, enforcement posture, governed activity, findings, workload risk, and readiness into one operating view. It is the place to decide what needs attention next, not another destination for raw telemetry.
02Validate
Test governance behavior before enforcement.
Validation Console lets teams evaluate a representative structured event against the active governance model and review the result before applying enforcement to production telemetry.
03Deploy
Publish policy to an explicit runtime target.
Deploy Center is where signed Runtime Policy Bundles move from governed policy into a target-specific rollout. The capture shows the clean first-deployment state rather than fabricated deployment history.
04Investigate
Turn findings into an investigation workflow.
Violations Explorer is organized around severity, rate, top rules, distribution, and trend so a team can move from posture into the workload and policy behavior that needs remediation.
05Verify
Check the customer-local platform as one system.
Service Health verifies the deployed control-plane services, reports current connectivity, and gives operators a direct view of platform readiness inside the customer environment.
06Prove
Build evidence from the records the control plane already owns.
Evidence Center scopes policy versions, hashes, coverage, violations, deployments, exceptions, and audit records into a reviewable evidence package. It supports governance review and audit preparation without claiming a compliance certification.
Two enforcement boundaries
One governance program without forcing every workload into the same runtime model.
Use CerbiStream when policy should execute inside a selected application process. Use Cerbi Gateway when existing OTLP workloads are better governed at a customer-hosted telemetry boundary. Both paths keep downstream observability in place.
CerbiStream
In-process enforcement
Apply governance before the application's first network hop when closest-to-emission control is the right tradeoff.
Cerbi Gateway
Available with CerbiShieldOTLP-boundary enforcement
Route selected OpenTelemetry traffic through a customer-hosted governance boundary without requiring a Cerbi SDK in workloads that already emit OTLP.
Bounded pilot
Prove one governance control against one real workload first.
A useful evaluation should prove policy activation, enforcement behavior, evidence, and operational visibility against representative telemetry. It should not stop at proving that a dashboard screen loads.