Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Every enterprise today runs on two kinds of infrastructure. One half lives on-premises: the company’s data centers, internal networks, DNS zones, DHCP scopes, IP address spaces, and the systems that help every device find and connect to the right service. The other half lives in the public cloud: where applications, databases, containers, and storage run on infrastructure delivered by providers like Amazon Web Services (AWS). This hybrid model is no longer a temporary phase.

We’ve long defined cybersecurity as the technical discipline of protecting networks, data and systems. But when viewed through a geopolitical lens, then this definition is no longer sufficient. What we are dealing with today goes beyond protecting organisational data, to protecting economies, sovereignty, and increasingly, human perception.

2026 has officially become the year of speed, scale and support The delta between a phishing email landing and a full organizational compromise has shrunk to mere seconds. The reality by the numbers: To close this window, your defense strategy must evolve into a two-step powerhouse of accuracy and automation.

With so many different security frameworks and standards that apply to different industries and businesses, it can be difficult to even know where to begin. Which ones do you need to use, at what levels, and when? Two frameworks in particular are closely related and important for many businesses, and thus are the cause of a lot of confusion. We wanted to address that confusion today. Those two are PCI DSS and SOC 2.

ATO fraud cost US adults $15.6 billion in 2024, yet most fraud teams are still measuring detection time from the moment an alert fires, not from the moment an attacker starts building infrastructure. That gap is where the damage happens. To reduce time to detect fraud, teams need to move detection upstream, to Stage 1 and Stage 2 of the fraud lifecycle, before phishing sites go live and before a single credential is submitted. Faster transaction monitoring won’t close this gap.

Security teams have a data problem. Not a shortage of data, but instead there is a growing data surfacing problem. The signals are there, the incidents are logged, and the classifications exist. But, getting from raw data to a prioritized action plan still requires close to an hour of manual querying, tab-switching, and context reconstruction, every single time. The Cyberhaven Analyst Plugin changes that.

What you need to know: MCP can evade traditional DLP, IAM, and SIEM controls because agent traffic looks like authorized API calls, sensitive data is semantically transformed before it leaves the perimeter, and exfiltration happens through tool invocations rather than file transfers.

A high-severity double-free vulnerability in Apache HTTP Server 2.4.66 allows low-privileged attackers to remotely crash vulnerable servers through a crafted HTTP/2 request sequence, with a demonstrated path to remote code execution on common Linux deployments. Tracked as CVE-2026-23918, the vulnerability exists in Apache’s mod_http2 module and affects deployments using multi-threaded MPMs such as worker and event.