Connect one runtime.
Verify one control.

Choose the adapter for your logger. Follow its installation guide, attach a governance profile, send a synthetic test event through the supported path, and inspect the recorded outcome and downstream result.

Runtime coverage

Choose the integration.
Verify its behavior.

Cerbi is .NET-first, with Java, Node.js, and Go integrations. Sharing a governance model does not imply identical enforcement support in every adapter.

Implementation documentation for the integration you choose.
RuntimeIntegrationScope
.NETCerbiStream, MEL, Serilog, NLogApplication/runtime governance and compiler or IDE analysis through the applicable package.
JavaLogback, Log4j2Structured logging and MDC governance through the relevant filter or adapter. SLF4J usage depends on the logging backend.
Node.jsPino, WinstonGovernance-aware transport/evaluator paths. Check the adapter’s enforcement and transformation semantics.
GoZap, ZerologGovernance integrations for structured logger events; verify the selected adapter’s supported actions.
NEXTChoose your next proof

Review a Scanner finding or logging requirement against your existing controls. If a recurring gap remains, scope one CerbiShield workload, policy, evaluation window, and evidence review.

One initial workload/Customer-hosted in Azure/Existing destinations remain
Runtime Governance — Cerbi Docs