Developer Packages
Start with CerbiStream, then add integrations, analyzers, runtime enforcement, or signature packs based on how your team adopts telemetry governance.
Cerbi works with existing logging frameworks and helps teams govern telemetry before ingestion. Use CerbiStream as a native logger, or add Cerbi governance to your existing framework.
Start here
- –New to Cerbi→
- –Using Serilog, MEL, or ASP.NET Core integrations→
- –Want enforcement in CI→
- –Want runtime governance inside the app→
- –Want faster adoption→
Start Here
Recommended first installFramework Integrations
Add Cerbi governance to the frameworks teams already use.
Cerbi.AspNetCore.Governance
Add Cerbi governance to ASP.NET Core applications.
Cerbi.Serilog.Governance
Apply Cerbi governance policies to Serilog pipelines.
Build-Time Enforcement
Catch governance issues during development and CI before telemetry is emitted.
CerbiStream.GovernanceAnalyzer
Build-time governance validation for CerbiStream-based logging.
Runtime Governance
Govern telemetry inside the application process before it leaves the service.
Signature Packs
Accelerates adoptionPrebuilt signature packs help teams standardize logging faster without inventing every event shape from scratch.
Cerbi.Signatures.Security
Prebuilt security logging signatures for authentication, authorization, access violations, and sensitive actions.
Cerbi.Signatures.Api
Standard API logging signatures for requests, responses, failures, dependencies, and endpoint activity.
Cerbi.Signatures.Audit
Audit-focused signatures for record changes, approvals, access tracking, and compliance-sensitive events.
Cerbi.Signatures.Pii
Signatures for logging events that involve personally identifiable information — with field-level classification and masking guidance.
Cerbi.Signatures.Financial
Logging signatures for financial transactions, payment events, fraud signals, and monetary operations.
Cerbi.Signatures.Observability
Structured signatures for traces, metrics, dependency calls, and system health events aligned to observability best practices.
Cerbi.Signatures.Hipaa
Prebuilt logging signatures aligned to HIPAA requirements — covering PHI access, disclosures, and audit trail events.
Cerbi.Signatures.Gdpr
Signatures for GDPR-governed logging — data subject requests, consent events, retention triggers, and processing records.
Cerbi.Signatures.Soc2
Logging signatures mapped to SOC 2 trust service criteria — availability, security, confidentiality, and change management.
Cerbi.Signatures.Pci
Signatures for PCI DSS logging requirements — cardholder data access, authentication events, and network activity.
Cerbi.Signatures.FedRamp
Logging event signatures aligned to FedRamp control families — access control, audit and accountability, and incident response.
Cerbi.Signatures.Iso27001
Signatures covering ISO 27001 Annex A control logging requirements — asset management, access control, and cryptographic events.
Cerbi.Signatures.Ferpa
Prebuilt signatures for FERPA-governed logging in education systems — student record access, disclosures, and consent tracking.
How to choose
- 1.Start with CerbiStream if you are adopting Cerbi directly.
- 2.Add framework integrations if you already use Serilog, MEL, or ASP.NET Core adapters.
- 3.Add analyzers to shift governance left into development and CI.
- 4.Add runtime governance when you want in-process enforcement and tagging.
- 5.Use Signature Packs to accelerate adoption with prebuilt event shapes.
Ready to get started?
Install CerbiStream from NuGet and configure your first governance profile in minutes.