01 / See
Start with the whole picture.
One overview of what was governed, what was found, and where to look first.
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.
The product, in the order a review happens
Six steps from policy
to proof.
01 Overview · 01/03
Headline countsGoverned events, policy findings, redactions and evidence reduction for the selected window. Active policies reads 0 because the assignment source is unavailable in this capture, and the view says so.Illustrative demo records, not customer results. Crops of the actual product; each view is in the full set below.
02 / Govern
Write the rule once.
Named governance profiles express policy before any downstream tool sees a log.
03 / Govern
Put it where it applies.
Bind a policy to an application, an environment and a mode, then keep the rollout record.
04 / Investigate
Go from signal to the exact finding.
Severity, trend and application breakdowns narrow review to a rule and a field.
05 / Prove
Show what was retained.
Distinguish a summary from the detailed evidence available to support a review.
06 / Prove
Keep the trail of who changed what.
Configuration and deployment events sit beside the evidence they relate to.
Nine views / One governance story
Choose the question.
Explore the evidence.
Actual product captures with illustrative demo data. Select a view to see what it shows, why it matters, and the limits of the captured evidence.
What you see
Reporting
Current and prior posture on a radar, alongside the overlap of blocked, redacted and processing-error outcomes.
Why it matters
Compare posture dimensions and identify application/environment pairs that need a closer review.
Overlap counts describe application/environment pairs, not event totals or same-event correlation. Missing observations are unknown, not zero. Scores and observed percentages measure different properties.
On smaller screens, use these controls or scroll to inspect each chart.
Apply the question to your own logging controls.
Bring one workload, a policy concern, or an evidence requirement. Review the available signals and agree what a useful evaluation should prove.
More product context and supporting views
01
Command Center
Review policy findings with their evidence.
The operating question
Policy findings, terminal outcomes, and retained evidence are shown with scope and source context.
Command Center / Product viewOpen full resolution ↗
- 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.
02
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.
AI Logging Governance / Illustrative previewOpen full resolution ↗
Illustrative AI preview. Example values are not tenant observations; this preview does not collect tenant AI telemetry.
03
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.
04
Policies
Define governance before downstream ingestion.
The operating question
Governance profiles express policy. Runtime evidence records the resulting decision.
05
Violations Explorer
Investigate from signal to evidence.
The operating question
Follow a finding through application, environment, policy, time, and the recorded outcome.
Violations Explorer / Product viewOpen full resolution ↗
06
Application Detail
Put identity and runtime evidence in context.
The operating question
Review the application, its environment, governance profile, activity, and associated evidence.
07
Reporting
Turn runtime activity into governance evidence.
The operating question
Review governance summaries and recorded policy outcomes within the selected scope and period.
Reporting / Product viewOpen full resolution ↗
08
Deployments
See where governance is active.
The operating question
Keep policy targets, deployment state, and rollout history connected to the control being operated.
09
Service Health
Keep current checks and historical telemetry distinct.
The operating question
Current connectivity checks appear beside Reporting history. Demo services are deliberately unreachable; unavailable queue and throughput data are identified explicitly.
10
Evidence Center
Understand what was retained.
The operating question
Healthy summaries and detailed evidence remain distinct. The current Reporting projection supports CSV and hashed JSON manifest export; stored package inventory remains unavailable.
Evidence Center / Product viewOpen full resolution ↗
11
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.
12
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.