News for hackers. Stuff that matters.
Re:The Colonial Pipeline Was Fine, Shutdown to Make Sure Its... by MattGaiser on Tuesday May 18, 2021 @03:41AM (#27192137)
> 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?

Re:The Colonial Pipeline Was Fine, Shutdown to Make Sure Its... by Dylan16807 on Tuesday May 18, 2021 @03:46AM (#27192168)
Please 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.

Re:The Colonial Pipeline Was Fine, Shutdown to Make Sure Its... by mschuster91 on Tuesday May 18, 2021 @04:25AM (#27192355)
> 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.