4 ms·
> didn’t actually shut down the pipeline. It impacted the billing system at the Colonial Pipeline Co., which shut it down because they were worried about how t
by MattGaiser 5y ago
> didn’t actually shut down the pipeline. It impacted the billing system at the Colonial Pipeline Co., which shut it down because they were worried about how they’d collect payments.
What? Did the author think that the ransomeware literally locked valves?
- Dylan16807 5y agoPlease try reading the article again. "the operational network that controls its pipelines and distributes fuel is separate from the corporate network and wasn’t infected" The article thinks it matters whether the ransomware gets on the operational network, not your strawman.
- mschuster91 5y ago> Did the author think that the ransomeware literally locked valves? In the early times of the pipeline shutdown this was exactly what was feared. Malware attacking, damaging, destroying or abusing industrial embedded devices to persist in to survive cleanups is nothing new. Stuxnet was just the tip of the iceberg.