Watch the video, transcript and sources
https://www.youtube.com/watch?v=eHkbrt81r0Q
+ Fixed report-date publication
- Default post-patch soak timer
+ Shorter clocks planned in stagesGoogle wants faster fixes. Its first policy change can keep some early-patched bug details private longer.
Natalie Silvanovich's November 13 announcement replaces Project Zero's ordinary post-patch waiting rule with a fixed disclosure clock. The current policy is Full 90: technical details ordinarily become public ninety days after the team reports the vulnerability to its vendor. An early patch leaves that endpoint in place.
Follow the report clock
Project Zero is Google's security research team. It sends technical reports to responsible vendors or open-source projects, then publishes their technical details under its disclosure policy. This is the team's publication policy. It concerns those reports and includes defined exceptions.
The historical 2021 rule held details for thirty days after an ordinary bug was fixed within its deadline. That waiting period was intended to let users install patches. The new ordinary clock attaches publication to the original report date. Default grace-period and special variant handling are removed.
The distinction matters because a released patch, an installed update and a public technical explanation are different milestones. The restart reminder on your laptop has a very good understanding of this distinction.
The patch gap remains
Google calls the release-to-installation interval the patch gap. Silvanovich argues that AI has made patch analysis fast enough that near-zero patch-to-exploitation is a reasonable, imperfect planning model. The qualifier matters. This is Google's stated reasoning, with no independent exploitation benchmark in this episode.
The team wants faster rollout or other protections while remediation proceeds. It also describes a workload problem: some targets now produce several vulnerabilities a week, where it previously found a few a year. Negotiating whether each report counts as fixed becomes difficult to automate. The meeting produces another meeting.
The shorter policies are future plans
Google plans Full 60 for February 2, 2027. That would put ordinary publication sixty days after reporting. It plans Full 30 for January 3, 2028. Current Full 90 remains the ordinary policy until the change.
The official FAQ says reports retain the policy that applied when they were submitted. Vendors raised concerns about exposing unfixed bugs, distorted repair priorities and impossible targets. The transition is intended to give them time to improve their processes.
Defined exceptions remain for active exploitation against real users, already-public technical details and earlier disclosure requested by the affected vendor. Rare harm-prevention exceptions also remain. Project Zero continues tracking fixes and communicating unfixed status; that status ceases deciding the ordinary disclosure endpoint.
The worked example explains the tradeoff
The current policy's example patches a bug on day 47 and publishes details on day 90. Applying the historical ordinary fix-plus-30 rule calculates to day 77. That is thirteen days later for technical details under the current example, with the patch available on the same day.
These are an official policy illustration and our arithmetic. User installation time is unknown. For a deadline-day fix, the old extra month before publication disappears. The new clock can change the wait in either direction depending on fix timing.
Verdict: NEEDS REVIEW
I'd judge this policy by how quickly users actually get protected, while watching the early-fix disclosure tradeoff. A clearer publication schedule is useful; patch deployment still needs to reach the systems people depend on.
And that's the diff for today. I'm Niko from Axrisi. Merge responsibly.
Sources
Visual credits
Whole portrait-based ABC/cover artworks adapt World Economic Forum's Pichai portrait, source, CC BY 3.0, original linked video. Background removed, resized and placed with new typography. Pichai identifies Google; Natalie authored the policy. No endorsement or current personal reaction is implied.
The full episode includes an original Daily Diff process drawing and a brief silent fictional calendar reaction from Mr Bean's Holiday featuring Rowan Atkinson, GIPHY source. Film/source owners retain copyright; public hosting is no licence, legal clearance or blanket reuse grant. Google/source articles retain copyright. The recording shows public policy prose; no operational security test was performed.

