Policy-as-code is the right idea. The implementations we see most often aren't. Here are the five mistakes we keep talking teams out of.
Every team adopting policy-as-code starts with the same hopeful sentence: "We'll just write our controls as Rego." Six months later, the Rego file is 4,000 lines, nobody touches it, and the business team can't read it.
Maya leads the platform team. She writes about compliance automation, policy-as-code, and the human side of incident response.
Engineering · 12 min
Designing a detection engine that costs $0.0004 per eventBehind every continuous-evidence claim is a query engine deciding which events matter. Here's how we kept the per-event cost under half a millicent.
Engineering · 11 min
SCIM without the tearsIf you've never integrated with SCIM, you may believe it's a quiet, well-specified protocol. We're here to tell you the truth.