Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

I’ve been following ransomware since the first one, the AIDS Cop Trojan, was released in December 1989. It locked up victim computers and asked for $300 to be sent to a Panama P.O. Box. A lot has changed since then. The invention of cryptocurrencies, particularly Bitcoin in January 2009, was largely responsible for the explosion of ransomware by 2013. This was when CryptoLocker ransomware was released to the world. Ransomware gangs have been making many billions of dollars per year ever since.

Software-as-a-Service adoption is exploding, but security teams are struggling to keep up. The Cloud Security Alliance’s 2025 SaaS Security Survey has revealed that while investment in and attention to SaaS security are on the rise, genuine control remains elusive, especially when it comes to configuration management, identity governance, and visibility.

For decades now we’ve been locked in this game of cat-and-mouse where attackers develop a new technique and defenders catch up, or defenders introduce a new control and attackers adapt. From the evolution of network security to identity and access control, many of our technical controls have matured into strong and reliable defences. Yet as we continue to see in the media, attackers continue to get in, compromising even the most mature and secure of environments, in seemingly simple way.

In our 1,200-plus Sentinel deployments, we've seen the same pattern play out repeatedly. Security teams forced to choose between comprehensive visibility and manageable costs. Logs getting aged out just when they become most valuable for investigations. Compliance requirements colliding with retention budgets. The pressure to do more with less doesn't come with a pause button. And until now, that pressure has meant making hard choices about what security data to keep and what to let go.

In our latest report Data Pirates' Toolkit (Leveraging SQLmap for Unearthing Digital Gold), we take a comprehensive look at a tried-and-tested cyberattack methodology that threat actors can use to unlock sensitive and critical data from unsecured databases: SQL injection (SQLi) attacks.

Fireblocks has officially launched support for the Sui, the blockchain built for mass adoption, enabling institutional clients to securely custody SUI assets and access the growing range of applications built on the network via WalletConnect. Sui joins the expanding list of blockchains supported by Fireblocks, reinforcing our commitment to bring our customers the ability to participate in the industry’s most exciting protocols.

Federal agencies and contractors today are disproportionately targeted by cyber attackers as they store and manage sensitive public and government data. As a result, their data security standards need to be the most stringent, and software providers who partner with them must attest to the highest standards.

At Netskope, we are relentlessly focused on empowering our customers to stay ahead of the curve in the face of the increasingly dynamic threat landscape. We’re thrilled to announce the expansion of our technology partner ecosystem through innovative new integrations. These strategic alliances with industry-leading companies are designed to deliver even more comprehensive protection and unparalleled visibility across your critical cloud environments. These new integration areas include.

Today, we’re excited to announce a preview of the Model Context Protocol (MCP) Server for Nucleus. This marks an important step towards AI-native workflows for vulnerability and exposure management. Model Context Protocol (MCP) is an emerging industry standard enabling seamless integration between enterprise applications and AI models. Backed by leading organizations like OpenAI, Microsoft, and Google, MCP servers are quickly becoming the foundation for AI-enablement across the enterprise.

If you’re building AI systems with agents, plugins, and orchestration layers and you’re only thinking about how to route traffic, you’re halfway to being pwned. Everyone’s rushing to build a Model Context Protocol (MCP) — and that’s great. But almost no one’s talking about MoCoP — the Model Control Plane, which is just as important and arguably where the riskiest stuff happens. (Also, side note, who the hell keeps making these damn acronyms so confusing?