Iranian-linked hackers reportedly breached California Water Service by pivoting through an open-source GPS correction tool to then access billing systems. The alleged intrusion laid bare security failures that federal inspectors had already flagged across hundreds of U.S. water systems.
Security teams are caught between a rapidly expanding attack surface and accelerating adversarial use of AI. Thirty-two percent of security teams see automated, AI-fueled attacks as the single greatest driver reshaping their offensive security strategies.
A trio of fresh flaws highlights the heightened vulnerability of the entire enterprise software stack, as the combination of automated scanning, the availability of exploit code, and patching delays is cited as a factor in the rise of vulnerability exploitation as a preferred entry point.
The normalization of ransomware in industrial systems, along with an operating culture that treats downtime as unacceptable, is an uncomfortable tension that's not likely to go away soon.
Salesforce knew its platform was being systematically exploited. Charter's customers are paying the price. The gaps that enabled these intrusions are largely the same. Here's what enterprises and platform providers should have done and still need to do.
A voice phishing call compromised one identity. Millions of records followed. The Charter breach is the latest evidence that the gap between identity security and SaaS governance isn't a gap enterprises can afford to keep ignoring.
NIST releases its first concrete OT recovery playbook and it looks nothing like an IT runbook. The document is formally aimed at manufacturing, but the problem it addresses is structural across every operational technology environment where stopping production has physical consequences.
AI security scanners promise to reduce AppSec workload, but Contrast Labs' testing shows they systematically multiply it, turning a $315 API fee into an estimated $128,000 triage burden, before fixing a single vulnerability.
An 18-year-old heap overflow in NGINX's rewrite engine is now under active exploitation. Patches exist, but attackers moved faster than most organizations can respond.
Organizations spend real money on penetration testing and too often walk away afterwards with the same vulnerabilities they started with. The test happened. The report landed. The checkbox got checked. Nothing significant has changed.
Traditional security operations: CTI feeds piped into a SIEM, alerts routing into a ticket queue, and analysts triaging the resulting flood is running out of road. A new operational model is emerging in its place, and it doesn’t look much like what most security teams currently have in place.
Federal agencies and tech providers are accelerating AI security programs but organizations responsible for water systems, emergency services, and local government operations are struggling to keep pace. (Article includes an infographic to help security teams understand the operational challenges.)
New survey results show that medical device procurement standards are tightening and budgets are growing, yet organizations are not keeping pace with threat actors as their attacks become more frequent. And the security gap between legacy and newly deployed devices isn’t closing.
With NIST's National Vulnerability Database now triaging only a fraction of incoming CVEs, security teams must diversify beyond NVD while rethinking patch SLAs and risk scoring.
There's an all-too-common frustration that shows up in enterprise security survey results when the gap between a security team’s intentions and its execution leaves an opening for attackers to succeed.
Executives think their teams are fixing critical vulnerabilities. Their security practitioners disagree by 42 percentage points.
