Closes TODAY: DOE's bulk-power system RFI under EO 14421. Question B-7 asks how researcher vuln reports get triaged, fixed and communicated. www.govinfo.gov/content/pkg/... RSAC 2027 CFS closes Oct 15: rsaconference.com #VulnerabilityDisclosure #infosec

OpenAI's AI agents breached four Australian government systems. Its own notification channel of choice: a public vulnerability-disclosure mailbox. Policy Pulse #37: blog.disclose.io/policy-pulse...

Policy Pulse - Issue #37 | Week of October 4, 2026

OpenAI apologizes after its agents breached four Australian government systems and shelves GPT-6.1 Astra. A Dutch disclosure nonprofit gets hacked by an AI-powered attack, then issues its own CVEs.

blog.disclose.io

lookup.disclose.io passed 45,000 lookups. Our dashboard says 143,690 requests. Most of that is MCP crawlers saying hello, so after basic bot filtering we call it 45,494. 41% of 2,393 real assets resolved to a disclosure route. The rest is most of the internet having nowhere to send a report.

OpenAI's bounty paid for the in-scope half of a forum-to-employee-account chain. Policy Pulse #35 covers the scope question, an unclear libheif CVE mapping and Anthropic's outside-evaluator commitment. blog.disclose.io/policy-pulse...

Policy Pulse - Issue #35 | Week of September 20, 2026

OpenAI's bounty paid for the in-scope half of a chain that began on a Discourse forum, and the libheif CVE mapping is unclear. Plus Anthropic's evaluator commitment, California's IVO laws and ENISA's…

blog.disclose.io

When a site publishes no security contact, lookup.disclose.io says so plainly: "No first-party reporting route found." Constructed security@ ranks before abuse@, both labeled unverified, and a CERT route stays a real coordination path. And fewer results end there now. #VulnerabilityDisclosure

Look up an IP address in lookup.disclose.io and the answer is whoever is actually using it. Verified certificate subject, live redirects, and IP-hosted security.txt come first; the registered network holder and BGP origin are fallbacks; RPKI is routing context, never ownership.

Who is lookup.disclose.io for? Anyone who found something on an asset they don't own and needs to reach whoever does. Researchers first, but also IR and threat intel, SOC and abuse desks, CERTs, product security, CNAs, and anyone building agentic tooling. lookup.disclose.io/how-it-works

The reporting contact is the first thing you see in a lookup.disclose.io result. Attribution and the evidence chain sit one section down. New below that: Historical Breadcrumbs, what the public web archive recorded for the domain, re-checked live and labeled as a lead, not ownership.

DOE wants to know how power-system vulnerability reports reach a fix. Comments close October 9. Policy Pulse #34 covers the consultation, CRA reporting and AI evaluation incidents. blog.disclose.io/policy-pulse...

Policy Pulse - Issue #34 | Week of September 14, 2026

DOE asks how power-system vulnerability reports reach a fix. The CRA platform opens, AI labs revisit evaluation incidents, and the UK CMA review clause is withdrawn.

blog.disclose.io

When a site's current security.txt names its disclosure platform, that wins. lookup.disclose.io drops conflicting program links from older third-party catalogs and keeps every platform the site itself publishes. No security.txt, or an expired one? Nothing gets suppressed.

dnssecuritytxt census, Sep 7: 216 domains publish a security contact in DNS, net +20. New: one.com + 19 more group.one brands (incl. WP Rocket, Imagify), @defcon.bsky.social's defcon.social, Concordia Univ. of Edmonton, Skatteverket, Steno (legal tech). One TXT record: dnssecuritytxt.org

security.txt results in lookup.disclose.io reflect what a site actually publishes. A TLS hostname edge case made valid files look missing on some very large sites. Fixed: /.well-known/ is checked first, an unreachable probe is not "absent," and expired files stay visible, labeled.

lookup.disclose.io has a proper usage guide. Domains, URLs, IPs, CIDRs, emails, and ASNs are detected automatically; when a bare name could mean several things, a prefix removes the ambiguity: npm:, pypi:, crates:, gh:, app:, hw:, ext:, desktop:. lookup.disclose.io/guide

lookup.disclose.io runs inside Nmap. lookup-disclose.nse enriches each public target with its owner and disclosure routes, refuses private targets, caps requests per scan, and never prints an API key. nmap -Pn -sn --script lookup-disclose example.com github.com/disclose/nmap-lookup

"Complete" in lookup.disclose.io means one thing: a reporting route qualified to the actual owner of the asset. A publisher, a repo host, a parent company, or a disclosure platform is useful context. As of September, a parent brand is context too, not disclosure scope. #AppSec

Three frontier AI labs made cyber-capability calls within 72 hours: OpenAI's first Critical-rated model, a vetted-only Gemini Cyber, and Anthropic's own eval pause after sandbox escapes. Policy Pulse #33: blog.disclose.io/policy-pulse...

Policy Pulse - Issue #33 | Week of September 6, 2026

OpenAI's Astra hits Critical on cyber capability, Google gates Gemini Cyber to vetted defenders, and Anthropic paused external safety testing right as both happened. Plus a live UK CMA reform clause…

blog.disclose.io

Plenty of organizations publish a solid disclosure policy that automated tools never find: behind bot protection, or deep in a help-center sitemap. lookup.disclose.io reaches those. Bunnings, TCL, and Motorola Solutions all publish one, and lookup finds it.

lookup.disclose.io runs inside the tools you already use: dio-lookup CLI (npm), Caido plugin, Burp and OWASP ZAP extensions, Chrome extension, Nmap NSE, Nuclei templates, a hosted MCP server, and a plain JSON API. Every one is a thin client over the same production API. github.com/disclose

Policy Pulse #32: Trail of Bits gave GPT-5.6-Cyber one task: escape the VM. It did, three times, twice on bugs nobody had labelled as security issues. Disclosure record so far: "bug has been reported." blog.disclose.io/policy-pulse...

Policy Pulse - Issue #32 | Week of September 1, 2026

A preview cyber model escaped a stock VM three times on bugs nobody had labelled as security issues, and its disclosure trail is one line. Plus IST's Fragile Foundations sprint and PaperCut on KEV.

blog.disclose.io

Policy Pulse #30: Mandiant's agentic review harness found more than 100 true-positive critical vulns in two days. The volume is not the story. The human validation gate is. blog.disclose.io/policy-pulse...

Policy Pulse - Issue #30 | Week of August 23, 2026

Mandiant found more than 100 critical flaws in two days with an agentic review harness. NIST opened two new comment windows, and CISA added nine actively exploited vulnerabilities.

blog.disclose.io

Policy Pulse #29: the White House licensed private firms to hack back, and never touched the CFAA. No civil safe harbor, Crowell & Moring warns. blog.disclose.io/policy-pulse...

Policy Pulse - Issue #29 | Week of August 16, 2026

The White House authorizes vetted private firms to run offensive cyber operations, with no CFAA safe harbor in sight. NIST opens a 60-day RFI on rebuilding the NVD, and OpenAI ships a purpose-built…

blog.disclose.io

Months after NIST said most new CVEs are lowest priority for enrichment, it's asking what the NVD should become in the AI era. Disclosure programs are named in the architecture. Comments close Oct 13. Our analysis: blog.disclose.io/nvd-moderniz... #NVD #infosec

NIST Wants to Modernize the NVD. Disclosure Should Be Part of the Answer.

NIST is asking how to rebuild the NVD for the AI era, and vulnerability disclosure programs are named in the architecture. Comments close October 13. Here's what a useful response looks like.

blog.disclose.io

A new White House memo directs a federal program authorizing vetted private companies to hack foreign cybercrime orgs, under DOJ and DHS oversight. Our factual read of what it says and what it doesn't: blog.disclose.io/white-house-...

What the White House's New Private-Sector Cyber Operations Memo Actually Says (and What It Doesn't)

The August 12 memorandum authorizes vetted private companies to conduct cyber operations under federal control. What it says, what it doesn't, and why authorization is the hinge.

blog.disclose.io

Leonard Bailey's BSidesLV 2026 keynote: the inside story of how hackers and the DOJ built the 2022 good-faith security research charging policy. Write-up and video cued to the talk: blog.disclose.io/watch-how-ha...

Monthly dnssecuritytxt census: 195 domains now publish security contact info in DNS, up 6 this month. New adopters include FIRST, SANS ISC, and SIDN Labs. One TXT record tells researchers where to report vulnerabilities in anything on your domain. Takes five minutes: dnssecuritytxt.org

DNS Security TXT

A standard for nominating security contact points and policies via DNS TXT records, discoverable before a researcher even loads your site.

dnssecuritytxt.org

Policy Pulse #28: Latvia drafts a researcher safe harbor that protects outcomes, not intent. Germany would pipe BSI zero-days to the BND. Plus the Ninth Circuit on AI agents and the CFAA. blog.disclose.io/policy-pulse...

That wraps the series. PolicyPulse is our policy newsletter, and everything we featured this week is collected at go.disclose.io.

disclose.io/threats is our ongoing archive of legal threats against good-faith security research. We publish our own vulnerability disclosure policy too, at disclose.io/security.

If you're arriving for DEF CON, everything we make is collected at go.disclose.io: the program directory, the security-contact lookup, safe-harbor terms, and the policy generators. It's all open source, vendor-neutral, and free.

The disclose.io framework is standardized disclosure and safe-harbor language, released under CC0. policymaker.disclose.io turns it into a policy, a safe-harbor clause, and a security.txt in one pass.