Which is a dumb policy for security patches. When its fixed it should be released.
> If Google isn't willing to wait the two additional days such that the patch can be deployed within the regular update window, this means that Google effectively gives MS only 60 days to react and fix issues (because once they missed the second patch day, the vulnerability will be disclosed before the third).
Google doesn't dictate Microsoft's patch releasing policy. 90 days are 90 days. Microsoft doesn't have "only 60 days", they have 90 days like anyone else, and they chose to miss it by adhering to a policy of their own choosing that makes security patches less timely.
The whole purpose of a fixed 90-day window is to give reasonable time to fix a security vulnerability but also to create pressure to do so timely. Making exceptions for vendors to accommodate existing policies that make security fixes less timely would both increase the effort for Google (as a fixed time window is always easier to implement than one that varies with each vendors policies) and undermine the whole purpose of the 90-day timeline.
Applying the patch a few days later typically doesn't noticeably increase your risks but rolling them out unchecked can make some serious damage.
Before, many enterprises rarely patched because the testing involved was a huge pain and it fell outside what they typically planned for.
If you don't want to apply the patches as soon as they're released, then you'd be more than welcome to put them on hold for 4 weeks yourself when it's more convenient.
Your options become either to release an update the moment it's tested, immediately making vulnerable customers who have a change management policy (usually also the biggest and juiciest targets - fortune 500s including ironically the likes of Google), or delay any release until some coordinated date, giving everyone an equal and predictable opportunity to cope with the exposure, which is how Microsoft do it.
What are the chances that attackers or other agencies already know of these vulnerabilities and are exploiting them?
Microsoft's delays extend the time that the silent attackers have.
There are bad guys looking for 0-days out there. If they learn about the vulnerability from the patch, at least the world has the patch before the bad guys do. Now it's the opposite.
Edit: See _wmd's explanation about the technical details of all this in the same level of the answers.
You apply a dozen different fixes and test. Something breaks badly. You now have a dozen different root causes to check when, if you applied one at a time and tested (or applied one at a time and let your users test it, which is more commonplace than it should - automated testing tools exist for a reason) you'd know what broke.
I'd prefer to have fixes available for rollout as soon as possible and to decide whether I deploy them or not based on my tests. Automatic mandatory deployment could be on a fixed schedule, for those who can't test or don't care much about it.
Releasing the patch late (i.e., on patch day) makes that choice for everyone.
It's not that just the big companies are affected now: all users are.
Large enterprises already have centralized patch management, so they can decide how fast it gets pushed downstream to their users after MS releases the patch.
I haven't come across a source for that. Does one exist?
For all I know, Microsoft announced it in reaction to the publication, but I have no clue Google could have been made aware of it beforehand.
Edit: nevermind, I've found one.
You are new to IT aren't you?
Failure to blindly adhere to the common view isn't the same as being new.
Even so, this is a clash of two policies and Google needs to reevaluate its deadline (is 120 days better for everyone, including users?).
Perhaps responsible disclosure occasionally requires considering the unique circumstances of each security flaw?
This looks like a solution, but isn't. Perhaps Google's 90 day deadline is already a re-evaluation of a 60-day deadline that was made to accommodate holidays and companies with a once-a-month patch schedule. If Google's deadline was 120 and still hit two days before patch Tuesday, would you say the same thing but for 150?
(N.B. I'm not defending Google, just poking a hole in this particular idea.)
Microsoft do issue out of band updates but they are very rare and for very serious issues.
It isn't like Microsoft was stalling for time, they didn't ask for months, they asked for days to fir into their scheduled releases. It's also worth pointing out the enterprises time things on the patch Tuesday cycle. An earlier release causes all sorts of implementation problems, especially if only a day or two in advance. In all likelihood you wouldn't see many machines actually updated in that period, but cause significant extra grief.
Yes. Google designed Project Zero to "pressure firms into dealing with security problems more quickly." A firm policy with unambiguous enforcement has its advantages. Muddying the 90-day deadline with questions about when (and for whom) to make exceptions weakens it. For example, in the future, I expect Microsoft will not wait the extra two days in the event of a security disclosure from Google.
One may disagree with the 90-day policy to begin with. I, for one, think it should have had an exception process built in. But while these are Google policies, not laws, I respect them for adhering to published protocol. Even when it was difficult.
It's just like being late for work. "But I was only 5 minutes late." Late is late.
As far as I know, some other engineering areas have even the safety factor of 2 or 3. That means, you expect the stress x, but your process has to sustain even 3 x.
Edit: Zero tolerances are never a good idea.
http://civilrightsproject.ucla.edu/research/k-12-education/s...
Then again what does Google care, they don't use or support anything Microsoft, so it doesn't affect them.
As does Google Earth, Google Drive, the android development toolchain, and a handful of other desktop clients that I'm not going to bother to look up right now.
It seems to me Microsoft is like that student who has 3 months to do a project, but waits until the last 2 days, and then asks the professor to give him some more time. It was Microsoft's responsibility to patch the bug at the last Patch Tuesday.
If Google (or any other group that discovers security issues) has to take into account every policy of every software producer it becomes utterly impossible to have any disclosure policy.
If MS wants to handicap themselves, that's their problem. The rest of the world doesn't have to bend to their will, those days are over.
Yes, this is about being an ass. And it's Microsoft that's being an ass by claiming the rest of the world should take into account their peculiar policy.
Please don't sit on a fix until the time is more "convenient", give it to me now and let me be the judge on how important this security patch is to me.
MS is a huge company with an immense installed base and they have to be understandably careful with pushing updates. Working with them to disclose vulnerability on their regular patch day really wouldn't be such a bad thing for either Google nor the end users, even more so as we're talking about two days here and there even was a holiday week in the timespan.
This is about being an ass and I see no advantages for end users.
Even if Microsoft had not responded to Google at all, they could have waited for full three patch days (again, MS' patch deployment timeline is very much public knowledge by now) before publicly disclosing the issue.