The shutdown of operations of Colonial Pipeline captured the attention of the security community, government and consumers that suddenly couldn’t fill their gas tanks. (Colonial Pipeline)
Three weeks ago, the shutdown of operations of Colonial Pipeline captured the attention of the security community, government and consumers that suddenly couldn’t fill their gas tanks. Interestingly, interpretation of the incident – and the significance of the incident – varied.
Some saw this as a typical ransomware attack, albeit on a vulnerable target. Others saw this as reflective of weaknesses in the security posture of the nation’s critical infrastructure. And others felt the incident showcased inadequacies in the existing framework for public-private partnership.
So what was the long-term impact of this specific attack? Here we offer a rundown of some notable characteristics and outcomes of Colonial Pipeline, based upon interviews and our past reporting.
No, this was not an infection of the operational technology for Colonial Pipeline… but a shutdown resulted nonetheless.
When a critical infrastructure organization shuts down operations, as Colonial Pipeline did, the instinct for any security professional is to first question whether OT was compromised. We learned early on that it was not i ..
Support the originator by clicking the read the rest link below.
