Config Baselines
Lock a known-good snapshot as a baseline, then track how far your tenant has drifted since then. Use baselines to watchdog for unauthorized changes after audits or security incidents. Works across tenants too — MSPs can enforce one standard across every client.
Post-SOC2 Audit Baseline (Feb 2026)
LockedConfig locked the day we passed our SOC 2 Type II audit. Use this as the reference point for compliance drift.
Hardened Reference (April 2026)
LockedOur target-state config after the Q2 hardening sprint. Locked to prevent accidental drift from this known-good state.
MSP Standard Client Baseline
EditableOur managed-service standard config. Every new client tenant is bootstrapped from this baseline.
Demo tip: click the first baseline to see drift tracked against the Feb 2026 audit-pass config. That's the single-tenant narrative — how much has your tenant drifted since the day you were compliant? For MSPs, the same screen scores every managed client against one golden standard.
