Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

As we speak, bad actors are using AI agents to do their dirty work. Our own research tells us 85.8% of phishing attacks were AI-driven in the past 12 months. Agentic power is helping social engineering and malware get smarter, faster and harder to detect. But enough of what you probably already know. Let’s talk about how we can address these risks. Our CISO Advisor Dr. Martin Kraemer wrote recently about AI agents being used for good.

Enterprise AI agent adoption has created a massive blind spot: 83% of organizations have no visibility into what their AI agents are doing, while 86% lack visibility into their AI data flows. With 1 in 3 enterprise employees now using an AI assistant daily — mostly without security governance — this visibility gap has become a critical enterprise risk. The security industry's response splits into two distinct layers.

The next government security challenge isn’t AI models, it’s AI agents. Zenity and Carahsoft are helping agencies prepare. Across government agencies, AI agents are already interacting with sensitive data, mission-critical workflows, and public services. Yet most organizations still lack visibility into where these agents are deployed, what they can access, and how they behave once operational. The result is a growing governance gap between AI adoption and AI security.

The regulatory landscape for agentic AI is moving faster than most compliance programs are tracking. CISOs who wait for final guidance before building their compliance posture will find themselves in catch-up mode at exactly the wrong moment and, in some cases, already behind.

Security teams are spending more money than ever on offensive security, and getting less clarity than ever on what it buys using them. For a long time, the central debate was pentesting vs red teaming. That argument settled itself once buyers understood that the two serve different objectives. Now it’s slipping again due to autonomous pentesting vs red teaming.

Your SOC probably looks busy on paper and brittle in practice. Alerts land from email, endpoints, cloud workloads, identity providers, firewalls, and ticketing systems. Analysts swivel between consoles, copy indicators into chat, open cases by hand, and race to decide which events deserve containment and which ones are just noise. That model doesn't break because people are careless. It breaks because the volume, speed, and interdependence of modern environments outgrew manual response a long time ago.