Type 1 or Type 2? The SOC 2 Decision Nobody Explains Properly
Founders ask me this early, usually right after a prospect’s procurement team sends over a security/vendor review questionnaire.
Writing
Practical lessons on security leadership, risk, compliance, and AI. Written from the work, for the people doing it.
Founders ask me this early, usually right after a prospect’s procurement team sends over a security/vendor review questionnaire.
AI has made writing code faster than it’s ever been. Pull requests that used to take a day now take an hour.
Welcome to a new thread. Over the last few years I’ve written about the DevOps, DevSecOps, Security and Compliance based on my everyday experience.
Security debt does not announce itself. It does not show up on a dashboard. It does not trigger an alert.
Every company I worked at made the same mistake. They hired someone for security, exhaled, and moved on.
Why activity-driven security programs produce effort without meaningful risk reduction.
Why CISOs, CTOs, CEOs, and CFOs need to evaluate security in terms of financial exposure, not just controls.
Why detection and response maturity define enterprise readiness more than any compliance framework. I’ve had versions of the same conversation many times.
A simple framework to assess whether your security posture will pass real-world scrutiny. Enterprise security reviews feel complicated from the outside.
Security doesn’t fail because teams don’t care. It fails because they’re optimizing for something else.