The Defender's Window: OpenAI's Greg Brockman on How to Secure Your Organization Before the AI Threat Window Closes

The OpenAI-Hugging Face incident changed how the security community thinks about AI-powered threats. An agentic collective autonomously penetrated not just OpenAI's research infrastructure but the production infrastructure of another company — chaining together vulnerabilities ranging from previously unknown security flaws to leaked user credentials found on the internet. In a new post, OpenAI's Greg Brockman breaks down what happened, what OpenAI is doing about it, and what every organization needs to do right now.

An Overview of the Moment

AI models are increasingly able to automate parts of real-world cyberattacks — making longstanding security gaps easier to find and exploit. Bugs buried deep in human-written software. Forgotten permissions. Misconfigured DNS records. Things that would take a skilled human attacker days to find, an AI agent can now surface in minutes.

The same capabilities, Brockman argues, give defenders an unprecedented edge — but only if they move now.

"It is increasingly clear that the tech debt of every company masks significant flaws, and defenders need to find and fix them before attackers do."

Earlier this year, OpenAI began releasing its cyber capabilities only to trusted defenders. Since then, open-weight models with comparable cyber capabilities have appeared — and the most recent, slated for release at the end of August, appears likely to significantly accelerate the threat landscape for everyone.

A Personal Anecdote

After the incident, Brockman decided to test the current moment himself. He asked ChatGPT Work — running publicly available GPT-5.6 Sol — to assess the security of his personal website, gregbrockman.com. A simple static site, hosted on AWS with Cloudflare as a front door. He expected minimal surface area.

In about 15 minutes, it uncovered 13 issues. DNS records not configured to prevent email forging. An insecure version of jQuery. Cloudflare forwarding requests to AWS over unencrypted HTTP.

He then asked it to fix the issues. Over the course of an hour, it opened the Cloudflare control panel in his browser and proceeded to click through DNS, TLS, and advanced security settings; dropped jQuery entirely; migrated the site off AWS onto Cloudflare Pages; and began a phased rollout of DMARC.

"This is a small example of how our existing models can operate as a cyberguardian — finding the long tail of issues that a human wouldn't have time or expertise to get to, and then fixing them with an appropriately tuned rollout plan."

What OpenAI Is Doing to Defend Itself

The Hugging Face incident, Brockman writes, showed that OpenAI underestimated the real-world cyber capabilities of its own AI models. The company is now investing across four major pillars:

Using models to secure code. Codex, including OpenAI's security plugin, validates code changes, identifies vulnerabilities, and helps developers fix issues before they ship. The goal is not to produce more security findings for humans to review — it is to catch real vulnerabilities before deployment and shorten the path from discovery to fix.

Defending infrastructure continuously. Almost all of OpenAI's initial security alerts are now triaged by AI before humans are looped in. This reduces toil for defenders, improves response time, and lets humans focus where their judgment matters most. Bounded automated responses are increasingly being connected to detections, with humans remaining responsible for the highest-impact decisions.

Continuously probing for attack paths. Frontier intelligence is used to enumerate, probe, and identify potential attack paths across OpenAI's products, infrastructure, and systems — finding vulnerabilities, misconfigurations, overly privileged identities, and unintentional trust boundaries before attackers can exploit them.

Investing in fundamentals at scale. Secure architecture, defense in depth, least privilege, network isolation, workload hardening, and safe patching and deployment — the classic controls — are more important than ever, not less.

What Defenders Should Do Now

Brockman's recommended steps, which he says need to be pursued at "turbo speed":

• Get organizational commitment. Ensure security and engineering teams have the support and resources to move quickly. Run tabletop exercises to simulate how AI-powered attacks might hit your specific organization.

• Give your security team an agent. Start using Codex, the Codex Security plugin, or another capable agentic tool. Give it approved access to codebases, infrastructure configurations, and technical documentation. Do not wait for a company-wide rollout.

• Equip the agent with security expertise. Start from community-supported skills covering static analysis, security-focused code review, vulnerability variant analysis, and supply-chain risk. Then build custom skills around your organization's own architecture, threat models, and playbooks.

• Run security assessments against your own systems now. Prioritize internet-facing services, authentication flows, infrastructure as code, deployment pipelines, and systems handling sensitive data first.

• Work through your existing vulnerability backlog. Feed your agent findings from code scanners, dependency alerts, security tickets, and bug bounty reports. Ask it to triage, distinguish exploitable issues from noise, and recommend what to fix first.

• Put security review directly into your development process. Use agents to review code changes before they merge. Look for authentication mistakes, access-control bypasses, exposed credentials, unsafe dependencies, and changes that expand access to production systems.

• Have the agent help fix what it finds. For validated issues, ask it to generate and verify a focused patch, write a regression test, and confirm the vulnerability no longer reproduces.

• Incrementally automate detection triage. Do not start by trying to build an autonomous security operations center. Start read-only. Let AI summarize evidence and recommend dispositions while humans make every decision. Expand autonomy gradually as confidence grows.

• Have an AI-assisted forensic investigation capability ready before you need it. Apply for Trusted Access for Cyber and get your team approved to use GPT-Daybreak-Blue for authorized defensive work — incident response, detection engineering, malware analysis.

• Experiment, run hack weeks, and iterate rapidly. Rapid incremental progress leads to compounding defensive results. Encourage your team to build new capabilities and expand autonomy as confidence grows.

The Window Is Open Now

Brockman closes with an appeal that goes beyond any single company. No organization can do this alone. His ask is that AI labs, security vendors, enterprises, and open-source maintainers share validated findings, fixes, and practical playbooks — so that one organization's discovery can strengthen the entire ecosystem.

"The defender's window is open now. Over the coming months, every organization will need to begin significantly automating its security program to stay secure."

The argument, stripped to its core, is that AI has not fundamentally changed the nature of the security problem — it is still a cat-and-mouse game — but it may be about to change the economics of that game in ways that favor defenders for the first time. Whether that window stays open long enough for most organizations to climb through it depends on how fast they move starting today.