Interactive Product Demo

Keep your logger. Add Cerbi governance.

Install the SDK, choose a governance profile, keep writing normal structured logs, and see what Cerbi changes before logs reach downstream tools.

Run the demo View SDK setup

SDK Setup

Two lines to add governance

CerbiStream is Cerbi's native governed logging pipeline. Cerbi.MEL.Governance adds runtime governance to Microsoft.Extensions.Logging. Other logger SDKs are shown as plugin coverage without exact setup snippets in this demo.

Verified SDK setup

dotnet add package CerbiStream

Before

var builder = WebApplication.CreateBuilder(args);

var app = builder.Build();

app.MapPost("/signup", (
    ILogger<Program> logger,
    SignupRequest request) =>
{
    logger.LogInformation(
        "User signup {email} {ssn}",
        request.Email,
        request.Ssn);

    return Results.Ok();
});

app.Run();

record SignupRequest(string Email, string Ssn);

After — one line added

using CerbiStream;

var builder = WebApplication.CreateBuilder(args);

builder.Logging.AddCerbiStream();

var app = builder.Build();

app.MapPost("/signup", (
    ILogger<Program> logger,
    SignupRequest request) =>
{
    logger.LogInformation(
        "User signup {email} {ssn}",
        request.Email,
        request.Ssn);

    return Results.Ok();
});

app.Run();

record SignupRequest(string Email, string Ssn);

Advanced production setup

builder.Logging.AddCerbiStream(options => options
    .ForProduction()
    .WithGovernanceProfile("myservice")
    .WithAesEncryption());

Expected result

Native governed logging enabled.
Sensitive fields can be redacted before logs leave the process.
Governance violations are attached to the event.
Downstream systems receive safer log data.

Editable Governance Profile

Profile name

Required field

******** field

Enforcement mode

AllowRelax

RequireTopic

Topic name

{
  "EnforcementMode": "Strict",
  "LoggingProfiles": {
    "Orders": {
      "FieldSeverities": {
        "userId": "Required",
        "email": "Required",
        "password": "********"
      },
      "AllowRelax": true,
      "RequireTopic": true,
      "AllowedTopics": ["Orders"]
    }
  }
}

Save as cerbi_governance.json and point the SDK at it.

Rule Playground

Change the rule. Re-run the log.

The expected dashboard outcome changes because the policy changed. Cerbi is policy-driven, not magic.

Input log

logger.LogInformation(
    "User info: {userId} {email}",
    "abc123",
    "test@example.com");

How the rule works

1.Required fields prove the log has enough context (e.g. userId).
2.******** fields prevent secrets from leaving the app (e.g. password).
3.Strict mode suppresses unsafe raw messages and emits governed output instead.
4.The SDK attaches governance metadata to the event.
5.CerbiShield turns governed events into findings, score changes, and remediation guidance.

Expected governed output

seeded demo data

{
  "Message": "User info",
  "userId": "abc123",
  "email": "test@example.com",
  "GovernanceViolations": [],
  "GovernanceRelaxed": false,
  "GovernanceProfileUsed": "Orders",
  "GovernanceMode": "Strict"
}

Expected dashboard update

seeded demo data

StatusAccepted

ProfileOrders

Dashboard updateAccepted governed log added to event stream

Suggested fixNo action needed.

Sample CerbiStream Scenario

Source-side redaction

The raw value never leaves the process.

Input log

logger.LogInformation(
    "User signup {email} {ssn}",
    "a@b.com",
    "111-11-1111");

Expected governed output — seeded demo data

{
  "message": "User signup",
  "email": "a@b.com",
  "ssn": "REDACTED",
  "GovernanceViolations": [
    {
      "Code": "********Field",
      "Field": "ssn"
    }
  ],
  "GovernanceProfileVersion": "1.0.0"
}

StatusViolation

Profilemyservice

Field actionssn redacted

Rule matched********Field:ssn

Dashboard updateViolation count increments, risky fields updated with ssn

Suggested fixRemove ssn from the log and use a safe identifier instead.

Event Stream

Expected event stream

Expected demo outcome from seeded events.

TimeSDKServiceLevelMessageResult

14:42:11CerbiStreamsignup-apiInformationUser signupViolation

14:42:18MELorder-apiInformationUser infoAccepted

14:42:26MELorder-apiInformationOnly email providedViolation

14:42:34MELorder-apiInformationPassword in logViolation

14:42:41MELorder-apiInformationEmergency diagnostic logRelaxed

Expected Dashboard Update

Expected CerbiShield dashboard update

Expected demo outcome from seeded events.

Total governed logs

Accepted logs

Violation events

Relaxed logs

Governance score

70 / 100

Top risky fields

ssn, password, userId

Top affected services

signup-api, order-api

Verified SDK setup

CerbiStream, MEL

Plugin SDK coverage

Serilog, NLog, Log4j2 + 4 more

What Cerbi Added

What Cerbi added to this event

Developer fix for selected scenario

No action needed.

Additional Logger Plugin SDK Coverage