New Research Reveals Gaps in AI Safeguards, Cyber Experts Discuss

New research from METR reveals that OpenAI’s internal agent monitoring systems had safeguard gaps. A METR employee and Redwood Research employee red-teamed the system and discovered “a number of novel vulnerabilities in the asynchronous internal misalignment monitoring system.”
These assessments are in relation to a historical system examined on and before July 21. All vulnerabilities identified that affect production safeguards have been patched, according to OpenAI.
METR, an independent organization recently given access to Anthropic’s environments for comprehensive risk evaluation, outlined ideal monitoring and control systems in this research, stating that “future monitoring infrastructure should be able to withstand deliberate, strategic, and sustained attacks from highly capable internal agents at scale.”
Below, security leaders share their thoughts on this research.
Security Leaders Weigh In
John Strand, Owner, Black Hills Information Security:
I think we have two separate problems, and the second one isn’t getting nearly enough attention.
The first is the environment where these agents are being evaluated. We’re talking about sandboxing, but for these highly dangerous offensive AI models, I think an air gap is the only setup we should consider secure. Even then, I’m not completely certain. Models being evaluated for offensive security assessments should have absolutely no internet access.
People will say they need certain tools. Fine. Give them the tools. We can reasonably predict what they’ll need because they use the same tools security researchers use. Get those tools into an isolated environment and contain the model. A crowbar in a sandbox. That’s what we should be shooting for.
The second problem is morality and alignment. When you ‘obliterate’ a model and remove its boundaries, those boundaries don’t disappear only for authorized security research. From what’s being described, we’re seeing models attack sites without authorization, including German sites, healthcare sites, and Hugging Face.
We need better ways to develop and evaluate models that can perform offensive security research within an authorized scope while retaining the boundaries that keep them from hacking unrelated third parties. Permission to attack a lab should not become permission to attack the internet.
That seems to be a difficult problem for vendors to work through. But it needs to be a much bigger part of this conversation.
Darin Fredde, Sr. Director of Technical Marketing Engineering, Ridge Security:
These investigations expose an important gap between what autonomous AI agents can accomplish and what organizations can constrain and verify. The researchers identified different problems, but both reinforce the same principle: an agent’s ability to complete a task doesn’t mean it understands or will respect the boundaries of its authority.
In offensive security, autonomy is valuable precisely because an agent can explore attack paths that humans might overlook. But that capability must operate within enforceable rules of engagement. Target scope, permissions, network access, and stop conditions cannot depend solely on the model’s interpretation of instructions. They need independent technical enforcement, monitoring, and verification.
An autonomous agent may be an excellent penetration tester, but it shouldn’t get to rewrite its own rules of engagement.
I also see something positive here. Independent researchers were given meaningful access to examine these systems, and the findings were disclosed. That’s how security improves. The objective isn’t to slow innovation; it’s to ensure our ability to verify and govern autonomous systems advances alongside their capabilities.
Ultimately, the measure of security isn’t whether an agent says it stayed within scope. It's whether we can independently prove that it did.
Seemant Sehgal, Founder & CEO, BreachLock:
The question of whether agent providers can be the primary line of defense for agent behavior has been open for a while. This research demonstrated that one leading agent could conceal hundreds of actions from its provider’s own monitoring, and another kept pursuing an attack against a real person after being shown evidence of harm. They cannot be the primary line, and organizations running agents in production need their own controls at the orchestration layer rather than inheriting whatever the provider has in place.
If alignment did not stop the Mythos agent from pressuring a maintainer with fake identities and malicious code after being shown evidence of harm, security teams relying on these models need to ask their providers what alignment actually stops in practice. Pentesting agent deployments against those same conditions, including adversarial inputs and pressure tactics, is the way to find out whether your own agents behave the way you think they do.
Looking for a reprint of this article?
From high-res PDFs to custom plaques, order your copy today!





