Then the first trojans started to hit us around the millenia, and patching became best practice.
However, still 15 years later it´s still very difficult to manage in a real world situation.
Enterprises need to verify that patches are not causing incompatibility and downtime, and how do you do that with thousands of internal applicatons? Sure, you can look at various soft patching techniques but ultimately you need to patch.
Various news sites are now reporting that a new Drupal security vulnerability is out. We should apparently assume that you have been hacked unless you patched within 7 hours. How is that working out for everyone?
I think we need to start realizing that we will not be able to patch, even if we do our very best.
We should obviously continue to patch, but do it more cleverely. That requires security intelligence and good configuration management so we can quickly see which systems are affected and what the risk is.
However, the real game changer is that we need to shift our budgets from protection to detection and response.
You can't hope to stop everything (especially not in 7 hours like in the Drupal example), but there is a good chance you can detect it, or at least deal with it.


