SShortSingh.
Back to feed

Project Zero shifts to Full X policy, publishing bug details on a fixed schedule regardless of patch status

0
·2 views

Google's Project Zero has replaced its earlier '90 + 30' vulnerability disclosure policy with a staged 'Full X' model. Under the new approach, technical details are published a set number of days after a bug is reported to the vendor, whether or not a fix has shipped. That number is currently 90 days, dropping to 60 days in February 2027 and 30 days in January 2028. Project Zero says the shift responds to AI tools that speed up bug discovery and patch analysis, which make a post-fix rollout grace period less protective. The policy keeps only narrow exceptions, such as active exploitation in the wild, details already made public, or a vendor request. Defenders are therefore urged to shorten the gap between a fix becoming available and it being deployed.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingHacker News ·

IRS sign-in requires agreeing to ID.me terms, per consumer rights wiki

A post on Hacker News links to a consumer rights wiki page describing how accessing IRS online services requires users to accept ID.me's terms of service. The wiki entry examines what those terms involve for people signing in to federal tax accounts. The source material available is limited to the link and basic engagement metrics, with 27 points and 2 comments. Specific clauses and details of the terms are not reproduced in the provided text. Readers would need to consult the linked wiki page for the substance of the requirements.

0
ProgrammingDEV Community ·

Measuring one website change with the Google Search Console Performance report

The article explains how to use the Search Console Performance report to track clicks, impressions, CTR and average position before and after a single website update. It stresses defining the page, filters and comparison periods in advance, and recording the exact date the change went live. A before-and-after comparison shows only an association, since seasonality, shifting search demand and other events can affect the same metrics. Missing report rows are described as an evidence gap rather than proof a page never appeared in search. The author recommends keeping a change log of any other site modifications made in the same week so they can be considered as alternative explanations.

0
ProgrammingDEV Community ·

Sled Volt uses deterministic server replays to make its leaderboard tamper-proof

Sled Volt is a free 3D downhill sled game that runs in a browser tab and can be added to a phone's home screen. Its simulation runs on a fixed 60 Hz tick using only basic arithmetic, so identical inputs produce identical runs on any device. Instead of trusting submitted scores, the game uploads the player's inputs, and the server replays the run and ranks only the score it calculates itself. The same approach powers the Daily Run, where the course is generated from the date so players share a mountain and can race friends' ghost runs. The developers also capped run length to manage the server CPU cost of replaying long runs.

0
ProgrammingDEV Community ·

Tips for finding a remote internship and avoiding common pitfalls

The article offers guidance for students seeking remote internships, which are harder to find as competition for good roles has grown. It explains that postings labeled remote can differ, ranging from fully remote to region-restricted, hybrid, or remote only for part of the term, so applicants should verify the arrangement. Recommended search strategies include filtering job boards by remote location, checking employer career pages directly, and setting alerts to apply early. The piece also advises highlighting independent projects and remote collaboration experience in applications, preparing a reliable setup for video interviews, and watching for scam signs such as requests for payment. Finally, it suggests habits like weekly manager check-ins to help remote interns stay visible and build strong references.