Improving access controls on AI models is the most obvious security gap to close, according to Kayne McGladrey, a senior member of IEEE, CISSP-certified cybersecurity advisor, and independent virtual CISO. “Treat your models and their APIs like crown jewels,” says McGladrey. “If you wouldn’t expose your database to the public internet without identity and access controls, why would you do that for your AI model?”

The pressure to fix this will not come only from threat reports. It is about to come through contracts. Kayne McGladrey, a senior member of the IEEE, told VentureBeat in an exclusive interview that enterprises are starting to push software security obligations onto the vendors and maintainers in their supply chains. "We're going to start seeing companies trying to contractually shift liability to other parties in their supply chain," he told VentureBeat. "We're using your technology, but we want you to do the security for it."

"The security leaders could totally walk into a board meeting with the Mythos hype sheet and walk out with some additional money. But I think that approach has got a shelf life," says McGladrey. "What the real play, if you're a CISO, is to look at quantified organizational risk. ... It's better than saying, 'Well, Anthropic just blew up the world and melted the internet,' because that doesn't work for anybody."

As an independent virtual CISO with a background in risk management, cybersecurity, and regulatory compliance, I prefer facts over marketing claims. For TechRound’s HealthTech44 2026, I ranked the submissions on five evidence-based dimensions: stated security maturity, AI claim substantiation, clinical validity, patient impact, and the team’s credibility. Companies that scored higher had provided named certifications, published benchmarks, regulatory clearance, quantified outcomes, and experienced clinical leaders named in their submission. By comparison, entries with visible AI instructions, placeholder content, or contradictory claims were disqualified, and submissions that were primarily unsubstantiated product marketing ranked poorly with me.

That figure makes the argument fundable. Kayne McGladrey, an IEEE Senior Member who has spent his career in identity security, told VentureBeat that security teams lose these fights by filing the exposure under the wrong heading. Companies "should be focused on business risks rather than some, you know, cybersecurity risk, because if it doesn't affect the business, like a loss or financial loss, in this case, predominantly, then nobody's going to pay any action to it, and they will not budget it appropriately, nor will they adequately put in controls to prevent it," he said. A destroyed model carries a known replacement cost, which is the version of this story a CFO acts on.

This AI security incident report is built for CISOs and security leaders operating AI agents today. Reviewed by hundreds of CISOs, this paper explains how the autonomous AI attack unfolded, what made it detectable, and what security teams should do next to secure agentic AI systems.

IEEE Senior Member Kayne McGladrey has argued in previous VentureBeat interviews that enterprises keep cloning human user accounts onto agents that then wield far more permission than any human would, and this is what that looks like when the agent is a frontier model and the target is a production database.

Finally, Schrems III is nigh: with the US Supreme Court's ruling undermining the independence of agencies like the FTC — the very foundation of the EU-US Data Privacy Framework — Max Schrems is poised to strike down transatlantic data transfer agreement number three.

No one expects a cybersecurity incident to begin in the cardboard industry. Yet as our guest Kayne McGladrey explains, cybercriminals don’t care what your company manufactures—they care about opportunity.

Independent vCISO, Senior member of the IEEE, author of the GRC Maturity Model and the upcoming book "Cyber Risk is a Myth", Kayne is a go-to voice on treating GRC as a core business competency rather than a one-time project. He has a rare gift for making complex risk feel simple and actionable in the boardroom.

Kayne McGladrey, an IEEE Senior Member, described the structural challenge in an exclusive interview with VentureBeat. “The CISO doesn’t have the budget. The CISO doesn’t have the staff. We can observe risks, we can advise on business risks, but we don’t own the business systems affected by those risks,” McGladrey said. When agent governance spans six departmental budgets, no single executive can confirm whether agents get the same access reviews as humans.

Kayne McGladrey, IEEE Senior Member, has confirmed the pattern across multiple published VentureBeat interviews. The structural gap in self-reported coverage is not new. What is new is that autonomous agents will act on it at machine speed without the institutional workarounds human analysts developed over years of experience.

Kayne McGladrey, a senior member of the IEEE, warned that organizations supporting major events often struggle with visibility across both IT and operational technology environments. He highlighted unmanaged connections between business systems and operational infrastructure as a significant security concern.

"Pre-event threat hunting and alert tuning can further help to reduce or remove known misconfigurations early, shrinking the decision space so analysts aren't drowning in noise when the clock starts ticking," he says. "Security leaders know that they can't expect analysts to review every alert, so they're prioritizing only high-confidence behavioral detections tied to big event milestones, like the opening ceremony or a high-profile matchup."

"Decisions in organisations don’t move because information exists. They move because the right people understand the consequences of acting, or not acting, in terms that connect to what they’re already responsible for. A risk described in technical language may be completely real and completely ignored, not because the people receiving it don’t care, but because no one has connected it to a problem they’re already losing sleep over. Revenue. Regulatory exposure. A board conversation happening next month. The gap between those two things isn’t a failure of evidence. It’s a failure of translation."

Kayne McGladrey, IEEE senior member, told VentureBeat why that governance gap persists. "Anything that seems to have a cybersecurity flavor is generally put into the cybersecurity risk category, which is a complete fiction. They should be focused on business risks, because if it doesn't affect the business, like a financial loss, then nobody's going to pay attention to it, and they will not budget it appropriately, nor will they adequately put in controls to prevent it," McGladrey told VentureBeat previously.

The fifty people on this list represent the most important voices in risk management across enterprise risk, governance, compliance, financial risk, operational resilience, and emerging technology risk. They range from pioneering academics whose frameworks now underpin global standards to active practitioners building and rebuilding risk functions inside major organisations right now. As of June 2026, risk management has never been more central to organisational survival.

To recognize the individuals rising to meet these challenges, we're spotlighting 50 CISOs and cybersecurity leaders making a meaningful impact. These professionals stand out not only for their career achievements, but for their influence on the broader cybersecurity community.

SOC 2 audits require organizations to demonstrate logical access controls, but most control mappings address only human users, such as engineers SSHing into servers, developers accessing Kubernetes clusters, or administrators approving access requests. But modern infrastructure now runs on non-human identities like CI/CD pipelines, AI agents, microservices, and automated bots. These entities request credentials, access databases, and move data, but they're frequently excluded from the same auditing rigor applied to human access.

Kayne McGladrey, senior IEEE member and independent cybersecurity advisor, describes what accountability looks like in practice today. "If and when an agent takes the wrong action, responsibility ends up distributed across the vendor, the security team that deployed it, and the owner of the impacted system, but liability is not clearly assigned. Frameworks like the NIST AI RMF and the EU AI Act focus on governance and oversight processes, not incident-level attribution."