Current scope / future direction
Evidence first.
Scope made explicit.
Application logging governance is the current commercial focus. Workload authorization supports governed access; AI-related logs use the same supported policy and evidence lifecycle. Agent execution control is outside this product scope.
| Status | Capability |
|---|---|
| Shipped | Governed Applications: Entra-backed identity validation, tenant-scoped viewer/editor assignments, governance-profile access, entitlement checks, revocation, disablement, fail-closed authorization, and lifecycle audit. |
| Current platform | Scanner and supported runtime integrations; policies, violations, deployments, reporting, service health, and audit evidence. |
| Optional / Pro++ | AI Logging Governance for explicitly connected sources: observed logging context, provider/model and agent/tool metadata where logged, exposure classifications, policy evidence, and token/cost metadata where supplied. |
| Future direction | Broader autonomous agent-action enforcement, universal tool-call enforcement, and model-behavior governance. No delivery date or universal coverage claim. |
Future direction is not a purchase commitment. Runtime behavior depends on the chosen integration and release.
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.