Observability that stays local: lessons from CyberSentinel
What building a zero-telemetry security hub taught me about signal, noise, and keeping audit trails on the machine.
CyberSentinel started as a simple question: why does catching a Windows anomaly still mean crossing Event Viewer, process lists and network connections by hand?
The constraint that shaped everything
Nothing leaves the machine. That single rule killed cloud SIEM shortcuts, third-party enrichers, and "we'll add a collector later" thinking. Every heuristic had to earn its place against a local CPU budget.
What I would change
Separate collection from heuristics before the first false-positive cycle. Mixing them made iteration slower than it needed to be — debt you only see once the system is running.
Local-first is not a feature flag. It is a topology decision.