Sensitive fields. Consistent policy. Evidence of what was governed.
Find unsafe logging, apply policy at selected application or OTLP log boundaries, and retain recorded outcomes. CerbiShield runs in your Azure tenant, beside your existing observability stack.
Synthetic demo data. Unavailable services are shown explicitly. This redesigned UI is not included in Marketplace 74.
Policy findings, terminal outcomes, and retained evidence are shown with scope and source context. Scroll the image or open full resolution to inspect the complete screen.Explore the dashboard preview
Catch the risk. Explain the decision.
The control is only useful if you can see what it did.
Find the sensitive field, review the policy outcome, and follow the retained evidence. These examples show the questions Cerbi helps your team answer.
01 / Prevent exposure
Know what policy let through.
Separate passed, redacted, blocked, and error outcomes before you investigate a workload.
CerbiShieldIllustrative example
Policy outcome review
What reached the log?
120sample events four illustrated outcomes
64 passed32 redacted16 blocked8 errors
Inspect the decision
customer.emailREDACTED[REDACTED]
authorizationBLOCKEDEvent held at policy boundary
Illustrative reporting example · sample data, not a dashboard capture. Actions depend on the integration and policy.
Redesigned UI previews are outside Marketplace 74. Screens use synthetic or illustrative data. Select a phone capture to inspect its full, uncropped source.
Keep the stack. Add the governance layer.
Your observability platform may already offer processing and redaction. Cerbi is relevant when a logging-control or evidence gap remains: inconsistent policy across teams, sensitive fields escaping controls, or no record of which policy governed a workload. Keep Splunk, Datadog, Azure Monitor, OpenTelemetry, and your existing destinations.
01One logging-governance lifecycle
Policy with a runtime record.
For platform and security teams facing a customer-assurance or audit deadline: discover unsafe logging, define versioned policy, enforce it at supported boundaries, and prove what happened. Preserve useful debugging context where policy allows.
Discover → Define policy → Enforce → Prove
Enforce it. Relax it deliberately. Keep the evidence.
CerbiShield manages policy versions, rollout, observed coverage, and evidence over time. CerbiStream applies policy in selected applications; Gateway applies it on explicitly configured OTLP log paths. Available actions depend on the integration and policy.
Review findings alongside the application, environment, policy version, recorded outcome, and observation window where that context is available. Missing evidence cannot establish control coverage.
Bring policy outcomes, configuration changes, and authorization history into a reviewable evidence story.
Runtime evidence. Operational context. A record of change.
Reporting summarizes observed governance activity. Audit records help explain who changed configuration and when. Deployments and Service Health show the state of the governance plane itself.
Evidence supports governance reviews and audit readiness. It is not certification or a guarantee of regulatory compliance.
Synthetic demo data. Unavailable services are shown explicitly. This redesigned UI is not included in Marketplace 74.
Healthy summaries and detailed evidence remain distinct. The current Reporting projection supports CSV and hashed JSON manifest export; stored package inventory remains unavailable. Scroll the image or open full resolution to inspect the complete screen.
04Governed Applications
Identity stays with Entra. Control lives with the workload.
Register the application. Authorize the workload. Make access revocable and the lifecycle auditable.
01
Register
Create a stable, tenant-scoped governed application.
02
Authorize
Associate existing Entra workload principals; assign viewer or editor access.
03
Govern
Validate the workload token and active installation entitlement for governed access.
04
Observe
Read back governance profiles and review the recorded lifecycle.
05
Revoke
Revoke an assignment or disable the application; authorization fails closed.
06
Audit
Retain the authorization lifecycle, including changes and denials.
Microsoft Entra remains your identity authority. Cerbi validates real workload tokens and tenant-scoped assignments, backed by an active installation entitlement. Revocation and disablement invalidate authorization caches.
AI-related logs can carry sensitive fields too. Apply the same logging-governance lifecycle to supported provider, model, agent, and tool metadata emitted through connected logging paths.
See the logged context
Systems, providers, models, dependencies, and agent/tool context where supported and emitted.
Inspect exposure and usage
Data classifications, protected-field evidence, request/token metadata, and estimated cost where supplied.
Keep policy evidence
Review recorded runtime outcomes. Raw prompts, responses, and secrets are not collected by default.
Visibility depends on instrumentation and emitted log metadata. This does not authorize agent actions, govern model behavior, or provide universal AI estate coverage.
Boundary study / Cerbi editorial artwork
Customer-hosted architecture
Your Azure tenant. Your operating boundary.
CerbiShield deploys as an Azure Managed Application into the customer’s tenant. Managed identities, server-side tenant isolation, and governed access support architectural control.
Policy, deployment, service health, and evidence in the customer’s operating environment.
Build-time signal + runtime evidence
Find the gap before it ships.
Run the free Scanner independently. Review findings against your existing controls; if a recurring gap remains, evaluate CerbiShield on one workload with an agreed policy and evidence requirement.
Bring a Scanner finding, a sensitive-field concern, or an evidence requirement. Compare existing controls first. If a gap remains, agree one workload, one policy, an evaluation window, and evidence to review before deciding on a recurring CerbiShield deployment.
As AI systems take more actions across enterprise applications, teams need evidence of what happened and how policies were applied. Cerbi helps engineering teams govern application telemetry and review recorded policy outcomes, alongside their existing security and observability tools.
