The inevitable hacks are a way of life as cyberattacks rapidly proliferate. But you can limit the inevitable damage.
And when I say that cyberattacks rapidly proliferate, I do mean rapidly. Ask Route Fifty:
“The window between vulnerability discovery and exploitation has practically been reduced to zero.”
Which doesn’t help when you publicize an attack vector before the vendor plugs it. Marcus Hutchins recently vented:
“Just to be 100% clear, we came within a hair of having one of the worst mass-exploitation events in recent history, all because the Chainguard CEO unilaterally decided to break PHP’s embargo. Chainguard’s release resulted in someone being able to reproduce the exploit and release it publicly, 4 hours ahead of the patch being released.”
Combine all of it, and in the current environment assume that the hackers WILL get you. So what do you do?
That’s why Route Fifty talked about resilience:
“Since attackers move faster than agencies can remediate vulnerabilities, resilience must depend on what happens after an attacker gets in. The ability to contain an intrusion before it spreads to critical systems and disrupts public services is critical.”
Critical systems? I’ve talked about those: water, energy, transportation. If a hacker gets into these or other critical infrastructure systems, the hacker can massively disrupt operations…unless you insulate your system from disruption.
To protect our critical infrastructure from the inevitable hacks, these systems (and non-critical systems also) need to contain movement by the attackers, segment the subsystems, and support “the ability to isolate a compromised system while keeping unaffected systems running,”



