Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

A few weeks ago, we wrote about Project Glasswing and what we observed when we pointed cyber frontier models at our own code. Since then, we’ve seen that the part of the post that has resonated most deeply is the argument that the architecture around the vulnerability matters more than the speed of the patch.

The recent wave of announcements surrounding Claude Mythos and Project Glasswing has certainly filled our feeds. While these developments are technically interesting, the real story for me lately has been what they reveal about where the cybersecurity market is heading and how quickly that evolution is reshaping the risk conversation.

Co-founder and COO If you're running an MSSP or preparing for an audit, lc-compliance automatically documents relevant compliance evidence directly into your case records as they're created. Service providers work in a regulated environment, and already know compliance is a grind. Audits produce a pile of evidence requests. Your team pulls logs, traces detections back to controls, and writes documentation that no one reads until the QSA asks for it. Then you do it again next year.

As Japan navigates the mid-point of the decade, its cybersecurity landscape is undergoing a fundamental transformation. Driven by escalating geopolitical tensions and the rapid proliferation of agentic AI, the nation is shifting its focus from purely technical defenses to a broader strategy of "Cognitive Security" and national resilience. The emergence of a hybrid workforce - where human employees work alongside autonomous AI agents - has redefined the traditional enterprise perimeter.

AI demos are easy. AI you’d actually trust near your control environment is not. If you’ve sat through a few of these pitches lately, you’ve probably landed on the same four questions every CISO we talk to is asking. And you’re right to ask them.

ThreatSpike exhibited at Infosecurity Europe 2026 at ExCeL London from 2–4 June this year. Three days, ten expert sessions presented on our stand and more conversations about AI than we’ve had at any event in recent memory. This is our round-up: what we saw on the floor, what we presented, and what the industry is clearly wrestling with right now.

Network security stacks are stronger than ever: visibility is high, threat detection is improving, and AI adoption is widespread, with 99% of SOCs using it in some capacity. But despite these advances, network security teams face many of the same operational challenges as before. Incidents still escalate. Responses are slow. Analysts remain overwhelmed and burnt out. The issue isn’t detection – it’s what happens next.

Open-source virtualization is moving fast, and many IT teams are standardizing on KVM running the latest Linux distributions and Proxmox VE 9.1 to balance performance, flexibility, and cost.

What recent AI security developments should change and what they should not—for security leaders and vulnerability management teams The question is no longer whether AI will affect vulnerability discovery. It is whether exposure management programs can keep up with a faster clock.

Cyber reporting to the board has a consistency problem: updates arrive regularly but rarely deliver the forward-looking intelligence executives need to act. This piece breaks down why the disconnect exists, how it affects CEOs, CFOs, and CISOs differently, and what decision-ready threat intelligence should actually look like at board level.