Takeaways from a global malware disaster

Posted May 23, 2017 3:19 UTC (Tue) by ringerc (subscriber, #3071)
In reply to: Takeaways from a global malware disaster by jschrod
Parent article: Vulnerability hoarding and Wcry

Often we just can't get them to schedule downtime, or provide the time and resources for a low- or zero-downtime upgrade/update.

Takeaways from a global malware disaster

Posted May 23, 2017 3:47 UTC (Tue) by raven667 (subscriber, #5198) [Link] (2 responses)

This attitude always betrays an organization that is exposed to a lot of risk to continuity of operations, if they can't take the downtime for patching, they are really going to be unhappy when their system is totally dead due to preventable predictable failures.

Takeaways from a global malware disaster

Posted May 27, 2017 3:49 UTC (Sat) by ghane (guest, #1805) [Link] (1 responses)

> This attitude always betrays an organization that is exposed to a lot of risk to continuity of operations, if they can't take the downtime for patching, they are really going to be unhappy when their system is totally dead due to preventable predictable failures.

Yes, but if I _have_ to be unhappy, why not be unhappy at some point in the future? Why be unhappy now?

(And all reboots are dangerous, you never know what unsaved configs you are running)

It is not only CEO who have short-term objectives, it is Sys Adms too.

--
Sanjeev, who is a smoker. Not died even once yet. So there!

Takeaways from a global malware disaster

Posted May 29, 2017 4:40 UTC (Mon) by raven667 (subscriber, #5198) [Link]

Not only can you put off being unhappy into the future, where it might be someone elses problem, but depending on the failure you have an opportunity to come in on your white horse and save the day, proving your worthiness to an organization that doesn't understand the failure was preventable. Those are powerful motivations for professional malpractice.