Introducing the Glassbreak Blog

We're starting a blog. This is the first post, so it's short: what we plan to write about, and why.

What we'll cover

Break-glass and emergency access in practice. Most of what's written about break-glass procedures is abstract — a paragraph in a compliance checklist. We want to write about the parts that actually trip teams up: how to pick a trigger that isn't vague, why quorum approval changes the incentives around a shared credential, and what a good audit trail looks like once you've actually needed it.

Incident response. Break-glass access is usually one step inside a larger incident, not the whole story. We'll write about the surrounding process — on-call structure, escalation paths, playbooks that hold up under pressure — drawing on what we hear from teams using Glassbreak and from incident response practice more broadly.

Applied cryptography. Glassbreak's design leans on threshold cryptography and client-side encryption rather than a shared master password. We'll publish deeper technical explainers here than fit on the security page — design tradeoffs, the reasoning behind specific primitives, and where systems like ours have to be honest about their limits.

Compliance angles. Frameworks like SOC 2 and Cyber Essentials increasingly expect a defined emergency-access process, not an assumption that someone has the passwords written down somewhere. We'll cover how break-glass and audit trails map to those requirements in practice.

Where to start

If you're new to the term, Answers is our plain-language reference for questions like "what is a break-glass procedure?" If you're comparing tools, Compare walks through how different approaches to emergency access stack up.

We don't have a fixed publishing schedule to promise you — we'd rather post something worth reading than hit a cadence. New posts will show up here and in the sitemap.