Google Project Zero’s 90-Day Disclosure Clock Explained

Zusammenfassung

Pixel’s announcement explains Project Zero’s current Full 90 policy, which sets technical disclosure 90 days after a vulnerability is reported, regardless of when a patch ships. It compares the rule with the historical policy, where an early fix could lead to publication 30 days after patching, and notes that disclosure timelines affect vendors and users alike.

DEV Community

Google security disclosure: Project Zero's fixed clock explained

Google security disclosure is getting a different clock. Project Zero's new ordinary policy starts the publication timer when its researchers report a vulnerability to the responsible vendor. An early patch leaves that timer running toward the same endpoint. For some early fixes, technical details can remain private longer than under the previous ordinary rule, even as Google prepares shorter disclosure windows for the future. TL;DR Current Full 90 ordinarily publishes technical details ninety days after reporting. Defined exceptions remain. The historical 2021 ordinary rule published details thirty days after a fix shipped within its deadline. Google's current policy example patches on day 47 and publishes on day 90. The historical ordinary rule calculates to day 77 for that example. A deadline-day fix loses the old extra month before technical disclosure. Fix timing therefore changes the direction of the comparison. Google plans shorter clocks in stages, while existing reports keep the policy that applied when they were submitted. How Google security disclosure now uses the report date Project Zero is Google's security research team. It sends a detailed technical report to the vendor or open-source project responsible for fixing a vulnerability. Its disclosure policy determines when those technical details become public in the team's tracker. The official FAQ describes the reporting and publication process. The November 13 announcement by Natalie Silvanovich introduces Full X. The current value of X is ninety. The dedicated policy page says the vendor has that interval to make a patch available to users, and the ordinary technical disclosure endpoint stays fixed regardless of when the vulnerability is fixed. That produces a simpler scheduling question for vendors: when did the report arrive? The answer establishes the ordinary publication date. Shipping a patch earlier still protects people who install it, but it no longer starts a separate ordinary disclosure timer. This governs Project Zero's own reports. Other research teams and vendors can have their own workflows. Reading this policy as a universal obligation for every vulnerability report would lose the scope the team describes, including its expectations about report quality and demonstrated security impact. What the historical post-patch rule did Tim Willis's official 2021 policy table supplies the historical comparison. For an ordinary issue fixed within ninety days, technical details were published thirty days after the fix. The team called that period patch adoption time. The practical intention was to leave time for an available update to reach users before researchers released a public technical explanation. That explanation can help defenders assess risk, understand a fix and investigate related weaknesses. The historical article also acknowledged the defensive costs of waiting for details, including prioritizing deployment and testing patch efficacy. The shorthand "90 plus 30" can obscure the early-fix case. A vendor fixing a bug well before its deadline started the post-patch interval at that early fix. Earlier patches could bring disclosure forward within that combined window. Historical grace periods and actively exploited cases had additional rules, so this article keeps the comparison to the ordinary fixed-within-deadline case. This also explains why removing a post-patch interval does not necessarily move every publication earlier. The event that starts the clock changes. That is the important part of the diff, and it is easy to miss when a headline only lists the length of the window. A patch release and a protected user are different milestones Silvanovich defines the patch gap as the time between a security fix being released and the user installing the relevant update. An available patch can sit between a vendor's release process and the systems that need it. Publication timing cannot tell you that every installation has reached the fixed version...
Google Project Zero’s 90-Day Disclosure Clock Explained
Powered by Readybot.io

Das Neueste von Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …