The White House has finalized its voluntary cybersecurity framework for frontier AI models, giving leading AI developers a process to submit advanced models for government security evaluations before public release. The framework is intended to address the growing cybersecurity risks posed by increasingly capable AI systems (after recent testing incidents involving frontier models).
Zach Wasserman, co-founder, Fleet Device Management (and one of the creators of OSquery) had this to say:
“The White House is focused on whether frontier AI models are safe. Enterprises must consider whether AI can safely operate inside their own environments. A model can perform well in testing but still create risk if it’s connected to production systems without the right controls. Before AI is managing thousands of endpoints, organizations need an operating model where every change is version controlled, auditable and easy to roll back.
The takeaway from the recent OpenAI and Anthropic testing incidents is that autonomous systems need guardrails. We’ve spent years building software development processes around code review, version control and rollback. AI making infrastructure changes should follow the same principles. Infrastructure as code gives AI a safe, structured way to make changes while keeping people in control.
Our recent research found that almost half of organizations are prioritizing AI automation, but fewer than a third are prioritizing infrastructure as code. That’s a problem because AI is only as safe as the systems it’s allowed to change. AI also shortens the time between finding a vulnerability and acting on it, whether that’s patching it or exploiting it. Organizations relying on manual processes simply won’t keep up.”
Also with The White Houre, they have told AI developers it will not include open-weight AI models in its new voluntary cybersecurity testing program, according to Reuters.
The policy was discussed during a White House meeting with representatives from Meta, Google, Nvidia, OpenAI and Anthropic, according to sources familiar with the discussions. Open-weight models, such as Meta’s Llama and Nvidia’s Nemotron, make their core model weights publicly available, unlike closed models from OpenAI and Anthropic.
The voluntary testing program is intended for advanced AI models with sophisticated cyber capabilities and follows recent disclosures that AI systems from OpenAI and Anthropic breached other organizations during controlled security evaluations.
Jacob Krell, Senior Director: Secure AI Solutions & Cybersecurity, Suzu Labs:
“The US government already knows how to test open-weight models for cyber capability. Before Moonshot released Kimi K3’s weights on July 27, AISI and NIST ran a joint evaluation of its offensive capabilities, measuring exploit development, code execution, and network intrusion performance. That methodology works. The White House chose not to apply it.
“Publicly disclosed incidents that prompted this framework all involved closed-model companies. OpenAI’s models exploited Artifactory vulnerabilities to escape a test environment, then compromised Hugging Face through a separate attack path. Claude models gained unauthorized access to three companies during security evaluations. Under these guidelines, Meta and Nvidia walked out of the August 4 briefing with zero obligations while OpenAI and Anthropic accepted a voluntary pre-release review of up to 30 days.
“Kimi K3 trails US frontier models on cyber tasks today, but in a simulated enterprise attack it completed a full intrusion chain in one of ten attempts, against an intentionally vulnerable network, with initial access provided. China has made open-weight release a strategic priority, and each generation closes ground on the previous one. A framework that categorically exempts open weights has no mechanism to adapt when that gap narrows.”
I would give everything a read because if you use AI related anything, you are affected.




NVIDIA-led alliance proposes AI cybersecurity incident reporting framework
Posted in Commentary with tags NVIDIA on August 5, 2026 by itnerdNVIDIA and the Open Secure AI Alliance have proposed a new industry framework called Shared AI Findings Exchange (SAFE) to standardize how organizations report and share AI-related cybersecurity incidents.
Published through the Linux Foundation as a Request for Comments, the guidelines are intended to help organizations share information on AI attacks, vulnerabilities and near misses to improve collective cyber defenses.
The alliance also announced new open-source contributions, including AI security models, datasets, evaluation tools and research designed to improve the security of AI systems and agents.
NVIDIA said the Open Secure AI Alliance has grown to more than 120 member organizations, including technology companies, cybersecurity firms and open-source foundations collaborating to develop shared AI security tools and best practices.
Jacob Krell, Senior Director: Secure AI Solutions & Cybersecurity, Suzu Labs had this to say:
“SAFE is required because AI agent failures don’t fit existing vulnerability disclosure. When a model finds and uses access it shouldn’t have reached, there’s no patch to issue and no vulnerability identifier to publish. Agent failures are often behavioral and non-deterministic, with no signature to match and no fix to deploy.
“Aviation’s safety reporting system has been running since 1976, the financial sector’s threat-sharing body since 1999. Both protect reporters from liability and operate at industry speed. AI threats outpace government coordination, making private-sector self-organization the right model.
“Identity is the piece that makes the rest of the defensive stack enforceable. The alliance’s work on agent identity and access controls lets organizations verify what an agent is before it acts. SAFE adds information sharing on top of that identity and runtime layer. Together, organizations learn from each other’s agent failures fast enough to defend proactively.
“The highest value will come from near-misses. Breaches make headlines, but an agent that probes a boundary and fails never gets published. That behavioral pattern is exactly the intelligence other organizations running similar systems need, and SAFE creates the channel for sharing what would otherwise stay invisible.”
Jeremiah Fowler, Researcher for Black Hills Information Security, Inc. follows with this:
“I believe this is a positive step in the right direction. Organizations that experience AI related attacks gain valuable insights that could help protect others but only if that information is shared. Establishing a framework for responsible information sharing promotes transparency, peer review, and independently evaluated security findings. The more organizations that contribute real-world evidence, the more effectively we can identify emerging attack patterns, common vulnerabilities, and evolving threats while reducing duplicated defensive efforts that waste valuable time and resources.
“As AI becomes increasingly integrated into everyday life, business operations, and critical infrastructure, developing standardized security guidance now is a proactive investment rather than waiting to retrofit a defense after incidents occur. Sharing information about unsuccessful attacks is just as valuable as documenting confirmed compromises, because near misses can often expose weaknesses, configuration issues, or emerging attack tactics before they evolve into critical security incidents. I used to always say “it is not if you will have a data incident, it is when you will have a data incident”. AI has supercharged the threat landscape in ways we couldn’t have imagined just a few years ago. Reporting and sharing AI related cybersecurity incidents is a great first step. I am happy to see organizations take the initiative instead of waiting around for regulators or lawmakers.”
Standards are good. But I will have to see this in action to get an idea of how well this works. Because there’s nothing worse than a standard that nobody uses.
Leave a comment »