SecOps as Code

How to ship SecOps changes like software

SecOps as code means your detections, parsers, and automations ship like software, with validation, testing version control and rollback. Everyone agrees it's the right way to work. But few teams manage to actually make it happen. There's new fires to put out and alerts in the queue...

John Port, Sr. Detection Engineer at Clear got there by building in stages. He'll walk through the SecOps as code maturity model and progression with Fig Co-Founder and CEO Gal Shafir: what to build first, what can wait, and how to keep the work moving when nothing is on fire and it's nobody's top priority but yours.

No SecOps team knows what their SOC will be defending against in six months. That's the argument for starting to build towards resilience today.

What we'll cover:

• A maturity model you can place your own team on
• Why the order matters: detections, parsers, agents
• The process and review habits that made it stick
• How to justify the work against everything else in the queue