Re:Disclosing vulnerabilities to protect users
by acdha on Monday October 31, 2016 @10:56PM
(#12843016)
Never underestimate the degree to which enterprise IT departments view change as something to be feared. I once heard someone say that they wanted to delay Chrome updates until their security team could review them — said review process basically being waiting in a backlog for weeks and then someone searches for CVEs posted on that version.
[ Parent
| on HN ]
Re:Disclosing vulnerabilities to protect users
by technion on Tuesday November 01, 2016 @05:49AM
(#12844418)
I worked with a Government group that firmly rejected the concept of Windows security updates.
The general premise was, if you apply an update and something breaks (note that "changed behaviour" means "broken"), someone's head will roll. If you do nothing and get compromised, it's those damned <country> hackers again.
Re:Disclosing vulnerabilities to protect users
by nailer on Tuesday November 01, 2016 @05:07AM
(#12844272)
> Never underestimate the degree to which enterprise IT departments view change as something to be feared.
This. These supposedly risk-averse organisations also have no concept of the risk of stasis, only the risk of change.
Re:Disclosing vulnerabilities to protect users
by protomyth on Tuesday November 01, 2016 @11:00AM
(#12846150)
> Never underestimate the degree to which enterprise IT departments view change as something to be feared.
Never underestimate the management's ability to fire a Enterprise IT workers for applying an update that the developer's swear changes no behavior in the companies enterprise software, but actually does.
// been on both sides, we suck at testing and risk assessment in this profession