Google’s Project Zero Accelerates Vulnerability Disclosure Procedure
We independently review everything we recommend. When you buy through our links, we may earn a commission which is paid directly to our Australia-based writers, editors, and support staff. Thank you for your support!
Quick Overview
- Google’s Project Zero will now publicly disclose identified vulnerabilities within a week of notifying vendors.
- The goal is to shorten the “upstream patch gap” for quicker user protection.
- The current 90+30 days policy for bug remediation and patch application stays the same.
- Technical specifics will remain undisclosed until the bug-fixing timeline concludes.
- Experts advocate for enhanced government regulation alongside industry initiatives for enduring security improvements.
Insights on Project Zero’s New Policy
Google’s Project Zero, famous for its top-tier bug hunting team, has rolled out a fresh policy to bolster the rapidity and clarity of vulnerability disclosures. The team will now make vulnerabilities public within a week of notifying vendors, a strategy aimed at reducing the “upstream patch gap”—the lag between a vendor releasing a fix and its use in downstream products.
Effects on End Users
Tim Willis, Project Zero’s security engineering manager, stated that the new policy is aimed at reducing the time it takes for vulnerability fixes to reach users’ devices. He stressed that for users, a vulnerability is only truly fixed when they download and apply the update on their device, not merely when a patch is made available by a vendor.
Current Policies and Security Protocols
While Project Zero’s new policy hastens the initial disclosure timeframe, it upholds the existing structure established in 2020, which permits 90 days for vendors to rectify a bug and an extra 30 days for patch implementation. Crucially, Project Zero will refrain from sharing technical details or proof of concept code until after the deadline, preventing attackers from exploiting this knowledge.
Expert Perspectives and Government Involvement
Security expert Lee Barney commended the changes, observing the potential for heightened industry standards influenced by significant tech firms like Google. Nevertheless, Barney also underscored the need for stronger governmental regulation to ensure significant change. He referenced recent legislative initiatives such as Australia’s Cyber Security Act for IoT devices as vital steps forward.
Conclusion
Google’s Project Zero has set forth a new policy to disclose vulnerabilities more swiftly, increasing transparency and pushing vendors to hasten their patching processes. By publicly announcing vulnerabilities within a week, Project Zero seeks to lessen the risks related to the “upstream patch gap.” While the policy suggests improvements, experts emphasize the need for collaborative initiatives from both industry and government to secure long-term advancements in cybersecurity.
Q: What does the “upstream patch gap” mean?
A: It refers to the delay between when a vendor issues a fix and when it is implemented in downstream products.
Q: Will the new policy alter the current bug-fix timeline?
A: No, the 90+30 days policy for fixing bugs and adopting patches remains intact.
Q: How does Project Zero protect against exploitation of disclosed vulnerabilities?
A: Project Zero holds back technical details and proof of concept code until after the bug-fixing period concludes.
Q: What role do experts suggest for the government?
A: Experts advocate for stronger governmental regulation to support industry efforts and maintain cybersecurity improvements.
