Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Turns out the scariest thing about SSL certificates isn’t when they expire. It’s when they don’t. I wrote about the CA/Browser fight that led to the 47-day certificate mandate. CAs crying about lost revenue, browsers flexing their root program authority, enterprises stuck in the middle. But nobody talks about the security research that started it all: BygoneSSL at DEFCON 2018. Two researchers mining Certificate Transparency logs found something surprising.

When AWS’s US-East-1 region went down again this month, it reminded the industry of an uncomfortable truth: even the most trusted cloud platforms can fail. From streaming services to SaaS providers, many businesses were caught off guard, not because they lacked backups, but because they lacked redundancy. In a Kubernetes world, redundancy isn’t just about having data snapshots.

The recently published 2025 Latio Cloud Security Market Report, authored by industry analyst James Berthoty, captures a major transformation: cloud security is leaving behind static visibility tools and moving toward runtime-driven risk reduction. The report traces five years of evolution – from dashboards full of misconfigurations to platforms that can detect, prioritize, and mitigate threats in real time. Six key insights define this new era.

Prompt guardrails are a common first line of defense against client-level LLM application attacks, such as prompt injection and context poisoning. They’re also a critical component of a full defense-in-depth strategy for LLM security at the infrastructure, supply chain, and application level. The specific guardrails that teams implement depend highly on use case, but they are typically designed to.

I've spent the last few months talking to partners and prospects across EMEA about the upcoming Cyber Security and Resilience Bill, and there's a common theme: everyone knows it's coming, but most aren't sure where to start. The conversations usually begin with "Is this just another compliance checkbox?" and end with "How do we actually implement this without ripping out our entire infrastructure?" Here's what I've learnt from these discussions.