Operations | Monitoring | ITSM | DevOps | Cloud

Bryan Peace Leon Adato break down what exactly security-minded IT folks - whether they work in SRE, dev, networking, or more esoteric disciplines - should do when a new, critical, apocalyptic vulnerability is announced. They walk you step by step through research, analysis, and how to protect your company if a patch isn't out yet. Along the way they muse about the nature of the industry, the sudden spike in CVEs, and where to find the best hard cidr to take the edge off.

The timeline between vulnerability disclosure and active weaponization has collapsed. Threat actors no longer wait weeks or months—in many cases, security and IT teams have 72 hours or less to identify exposure, prioritize risk, and deploy countermeasures before exploitation begins.

"CFEngine: The agent is in" is our monthly webinar series, where we show new features, teach best practices, and keep the community informed about everything CFEngine.

Cribl gives security teams control over their data: what they collect, where to send it and how much to keep. The rest of the SecOps stack hasn’t kept pace. Detections, parsers and configurations spread across SIEMs, pipelines and data lakes still change by hand, so every cost cut, migration or new source turns into weeks of manual validation, and plenty of planned changes never happen at all. SecOps as Code closes that gap: every change ships like software, with testing, version control and rollback across the entire infrastructure.