Google’s Project Zero Overhauls Vulnerability Disclosure, Eliminating ‘Soak Time’ in Favor of Accelerated Timelines
Google’s elite security research unit, Project Zero, has officially scrapped its long-standing "90 + 30" vulnerability disclosure policy, signaling a seismic shift in how the cybersecurity industry approaches the lifecycle of software flaws. In a move that fundamentally changes the power dynamic between researchers, software vendors, and malicious actors, the team announced that it will transition to a rigid, accelerated disclosure schedule. Under the new "Full X" policy, Project Zero will publish technical details regarding discovered vulnerabilities exactly X days after reporting them to the relevant vendors, regardless of whether a functional fix or patch has been developed and deployed.
The policy change, detailed in a November 13 post by the research team, is a direct response to the rapidly evolving threat landscape, which has been profoundly altered by the integration of artificial intelligence into the vulnerability research lifecycle. By automating the discovery process, AI has fundamentally changed the speed at which bugs are identified, shifting the paradigm from a manual, painstaking search to a high-velocity automated pipeline. Project Zero noted that they are now discovering several vulnerabilities a week in target software ecosystems where they previously might have only identified a handful of issues over the course of an entire year.
The Death of the "Soak Time" and the Birth of "Full X"
For years, the industry standard—championed by Project Zero itself—was a 90-day disclosure window, often augmented by a 30-day "soak time" or grace period that allowed vendors additional breathing room to finish testing or deploying complex patches. That era has now come to an end. Under the new Full X mandate, the grace period, the "soak time," and the previous, more nuanced variant policies have been entirely removed.
The implementation of the new policy follows a deliberate, multi-year rollout schedule designed to pressure the industry into adapting to this faster cadence. The policy begins immediately as "Full 90." As of February 2, 2027, this will tighten to "Full 60," and by January 3, 2028, the deadline will reach its final, aggressive state of "Full 30."
Project Zero’s justification for this shift is rooted in the practical reality of modern exploitation. The research team argued that the traditional "soak time" is no longer a meaningful security buffer. In the current climate, sophisticated attackers are capable of reverse-engineering patches almost immediately upon release, rendering the extra time provided to vendors less of a protective measure for users and more of a window for exploitation to proliferate.
However, the policy does retain three specific, narrow exceptions. Technical details will remain withheld if the vulnerability is already being actively exploited in the wild, if the details have already entered the public domain through other channels, or if the vendor specifically requests that Project Zero publish the findings early. Outside of these scenarios, the clock will run continuously from the moment of disclosure.
Industry Tensions and the Patching Bottleneck
The move has not been without controversy. During the consultative phase of this transition, numerous vendors expressed deep concern to Project Zero, warning that an immediate and drastic change in disclosure timelines could have unintended, dangerous consequences. Vendors argued that the aggressive timeline might force them to prioritize "Project Zero" bugs over more critical, non-reported vulnerabilities, potentially leading to a chaotic triage environment. Some organizations even suggested that the pressure could cause some developers to become overwhelmed, potentially leading to burnout or a decline in the overall quality of software maintenance.
Despite these concerns, Project Zero has remained firm, maintaining that the objective is to compel vendors to fundamentally shorten the "patch gap"—the critical interval between a vendor releasing a fix and an organization successfully installing it. The research team further challenged the industry standard of tying disclosure timelines to a vulnerability’s severity rating. According to Project Zero, the severity of a bug is a reflection of its impact on the user, not a metric of how easily it can be discovered by an adversary. By treating all vulnerabilities with the same urgency, the team aims to strip away the excuses that often delay remediation efforts.
Defenders Forced to Re-evaluate Patch Management
The implications for enterprise security teams are profound. Ivan Milenkovic, Vice President of Risk Technology at Qualys, suggests that Project Zero has effectively "removed the snooze button" on the vulnerability response process. In an interview with Infosecurity, Milenkovic highlighted the disparity between the speed of research and the speed of enterprise IT.
"This describes an arrival rate that most patch programs were never built for," Milenkovic noted. For many organizations, the standard operational procedure is to operate on a monthly patching cadence. In the face of Project Zero’s new policy, this traditional approach is effectively obsolete. If a vulnerability is disclosed and potentially exploited within 30, 60, or even 90 days, a monthly cycle guarantees that the organization will remain exposed long after the technical details are available to the public—and, by extension, to attackers.
Milenkovic acknowledged that the pushback from vendors is a "fair response" to the challenges of secure software development, but he emphasized that the alternatives are increasingly bleak. If vendors are not forced to adhere to tighter deadlines, the initiative shifts entirely to the attackers, who are already operating at the speed of automation. Project Zero’s decision is an acknowledgment that the status quo was failing to keep pace with the democratization of sophisticated exploitation techniques.
A New Era of Transparency
The shift toward the "Full X" policy is not merely an administrative change; it represents a philosophical pivot. Project Zero will continue to track whether bugs are actually resolved, maintaining a record of vendor responsiveness and the efficacy of their remediation efforts. However, this fix status will no longer act as a gatekeeper for information.
By separating the publication of technical research from the status of a patch, Google is signaling that the public’s right to know about potential security risks outweighs the convenience of a slower, more controlled disclosure process. The team believes that transparency acts as a necessary forcing function, compelling vendors to invest in more robust, agile, and secure development lifecycles.
As the calendar approaches the 2028 deadline, the entire cybersecurity ecosystem—from software manufacturers to the security operations centers tasked with defending corporate networks—will be forced to reconcile their internal processes with this new reality. The era of the "90 + 30" window is over, and in its place is a future defined by accelerated disclosure and an urgent, uncompromising demand for faster, more reliable patching. For defenders, the message is clear: the gap between discovery and remediation is closing, and the time available to protect systems is rapidly shrinking.
| Source | : | Finance Poetry |
| Author | : | rifanmuazin |
| Editor | : | Finance Poetry Editorial Team |
