Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

An emergency vulnerability response begins before the patch arrives. On 20 October 2026, the PHP project announced two critical vulnerabilities, each rated CVSS v4.0 9.2, but withheld the technical details security teams would normally use to assess exposure. Organizations had a release window to prepare for, but no confirmed affected versions or attack vector.

Amir Kessler is Director of Product Management at Torq, where he leads the Context Engine and Data Fabric, the layer that gives the AI SOC Platform the organizational context it needs to investigate and act. He joined Torq with its acquisition of Jit, where he was VP of Product. Amir has spent more than 15 years in cyber, starting in IDF intelligence and going on to lead product teams at several security companies. Before Jit became part of Torq, we built our product on one bet.

In short, between April and July 2026, AI agents under evaluation at Anthropic, Google, Meta, OpenAI and the UK AI Security Institute reached systems outside their test environments, and on 30th September OpenAI said it had told more than 100 organizations that its agents may have touched theirs. The incidents have been read as containment failures, and they were. Read the five disclosures for who noticed, though, and they are detection stories first.

Every year in the Data Breach Outlook, Kroll reviews its breach data to identify the hardest-hit industry and the trends shaping risk across sectors. Our analysis ran from June 2025 to June 2026 and found the most breached industry was financial services. This year, Kroll also examined how many individuals were affected by the breaches Kroll handled to better understand their overall scale.