Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Let’s catch up on the more interesting vulnerability disclosures and cyber security news gathered from articles across the web this week. This is what we have been reading about on our coffee break! If you’re reading this and not already patched your WordPress, you might well have been breached…

Every conversation our team has with security leaders begins the same way. Nobody is backing off on AI in the SOC. The direction of the lean is what’s shifting. Torq’s 2026 AI SOC Leadership Report surveyed more than 450 CISOs and SOC leaders. The data confirms what those conversations were already telling me. We’ve left the adoption phase. The market is now in the architecture phase and the implications for how teams plan, buy, and build are significant.

The final part of CYJAX's rail cybersecurity series sets out a practical, five-step roadmap for building a rail-specific threat intelligence capability, covering regulation, coverage, and where to start regardless of maturity.

This briefing analyzes verified developments over two horizons: the Past Week (July 15–21, 2026) and the Past Month (June 22–July 21, 2026). It draws exclusively from contemporaneous incident disclosures, threat research, and authoritative reporting. Analysis emphasizes material business risk, control effectiveness gaps, residual exposure in software supply chains, cloud/IaC environments, identity-adjacent vectors, and AI-adjacent workloads.

Omdia once again named Acronis a Champion in its Global Managed BDR Leadership Matrix for backup and disaster recovery. Acronis was one of only four vendors in 2026 to retain its Champion status from the previous edition of the matrix. For managed service providers (MSPs), the honor provides recognition from an independent analyst firm of Acronis’ consistency, continued innovation and sustained commitment to partner success. Analyst report Omdia Global Managed BDR Leadership Matrix.

Your audit passed last quarter because the screenshots matched the baseline. Then someone pushed an emergency firewall tweak, a legacy admin account came back, and no one recorded the exception. By the time operations noticed the drift, the environment no longer matched the documentation, and the control that was supposed to prove stability had become part of the problem.