Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Security teams have never been better at finding problems. Discovery is broader, detection is sharper, and the volume of findings keeps climbing. But a finding is not a fix. When teams identify a risky AI agent, an exposed MCP server, or an active attack against an API, what happens next usually looks the same: someone triages it, someone opens a ticket, and someone on another team eventually makes the change. Until then, the risk stays exactly where it was.

When an auditor or an RFP asks how your organization handles AI risk, the OWASP Top 10 lists are often a core part of the checklist behind the question. Cato AI Security is built to address the risks on two lists.

Short answer: Do not assume an embedding is anonymous. An embedding can be matched back to the text it came from, and the text is usually stored right next to it. Treat each representation in a RAG pipeline as personal data when it can still be tied to a person, which is most of the time for chunk text. When the source record is deleted, every copy has to go. Your team builds a RAG assistant over HR policy and customer contracts. Documents go in, get chunked, get embedded, and land in a vector store.

Five days after PHP shipped the fix, CISA added both PHP2Shell flaws to its Known Exploited Vulnerabilities (KEV) catalog. Federal civilian agencies have until October 29 to remediate. Last week’s question was whether attackers could turn the flaws into working shells. This week’s question is which of your images and hosts still run an affected PHP build, and who can fix each one.

A report sitting in an inbox does little to protect a business.

Social engineering attacks differ from other cyberattacks most businesses face. In this type of attack, attackers exploit human trust rather than depending only on technical vulnerabilities. They impersonate employees or business partners to trick people into sharing sensitive information or transferring money. In some cases, they are also granted unauthorized access to company systems.

Every business with a website or email accounts has weak spots, and penetration testing helps you find them before an attacker does. Security experts try to break in the way a real hacker would, so you can see whether your defences hold up. The test itself is only the start. How often you test and what happens with what the testers find, decides whether a report makes you any safer. Both are worth knowing before you compare penetration testing services.

Somebody in the organization will eventually propose running documents through an AI text detector. The instinct is reasonable and the method is the one approach the published evidence rules out, for reasons a security or risk function should understand before the policy gets written. ‍ The organization that built the most widely used language model tried this and withdrew its own tool after six months. Its reason was accuracy, and the figures it published before withdrawing explain why. ‍

In the world of cyber incident response, experience teaches one truth over and over again: speed matters, precision matters, and coordination matters. But perhaps one of the most overlooked lessons, often learned the hard way, is this: Choosing the right legal counsel is just as critical as selecting the right Digital Forensics and Incident Response (DFIR) firm.

On October 21, 2026, Node.js released updates to address multiple vulnerabilities, including an issue in Brotli decoder (CVE-2026-111497). This critical buffer overflow vulnerability (CVSS score of 9.2) has become widely known as Node2Shell but has also been referred to Broccoli2Shell and HTTP2Shell. The issue exists in the Brotli decoder (c/dec/decode.c) in multiple Google Brotli versions, and products that rely on Brotli implementations are vulnerable.