CerbiShield / Product tour
From logging policy
to recorded evidence.
See what Cerbi records about governed activity: the decision made, the workload and policy in scope, the risk found, and the evidence retained. Availability follows the connected integration and data source.
Command Center
See recorded activity across connected logging paths.
The operating question
Policy coverage, governed events, findings, and runtime context guide the next investigation.
- 01 / Activity Six terminal outcomes account for governed events; findings remain separate.
- 02 / Risk Risk hotspots connect observed finding categories to workloads.
- 03 / Evidence Event-to-evidence flow shows what was summarized and what detail was retained.
- 04 / Confidence Unavailable policy and deployment signals are shown as unavailable, not zero.
AI Logging Governance
Review AI-related metadata emitted on connected logging paths.
The operating question
Provider, model, agent, and tool context where logged; policy and usage evidence where supplied. This is not agent-action authorization.
Governed Applications
Control which workloads are authorized to participate.
The operating question
Tenant-scoped application identity, Entra workload principals, viewer/editor assignments, revocation, and disablement.
Policies
Define governance before downstream ingestion.
The operating question
Governance profiles express policy. Runtime evidence records the resulting decision.
Violations Explorer
Investigate from signal to evidence.
The operating question
Follow a finding through application, environment, policy, time, and the recorded outcome.
Application Detail
Put identity and runtime evidence in context.
The operating question
Review the application, its environment, governance profile, activity, and associated evidence.
Reporting
Turn runtime activity into governance evidence.
The operating question
Review governance summaries and recorded policy outcomes within the selected scope and period.
Deployments
See where governance is active.
The operating question
Keep policy targets, deployment state, and rollout history connected to the control being operated.
Service Health
Check the governance plane itself.
The operating question
Inspect service readiness and health separately from workload activity and policy outcomes.
Audit / Evidence
Prove what happened and who changed it.
The operating question
Authorization and configuration lifecycle records support reviews alongside runtime evidence.
AI Exposure / Risk
Understand sensitive-data-to-AI exposure signals.
The operating question
Classification and protected-field evidence reveal exposure on explicitly connected AI telemetry paths.
Runtime / Language Coverage
Govern applications while keeping your stack.
The operating question
Choose a supported application integration or an OTLP governance boundary. Capabilities vary by integration.
Settings and governed access
Configure the installation and supported AI collection settings through governed access. Review changes alongside the audit lifecycle.
A founder-led logging-risk review
Find the control gap.
Test one workload.
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.