Colonial Pipeline, the artery carrying 45% of the East Coast’s fuel, shut down for six days this fortnight after a ransomware hit, and the detail the file exists to preserve: the attack (DarkSide, a ransomware-as-a-service franchise complete with affiliate programs and a press policy, cybercrime has unit economics and brand guidelines now) encrypted the business systems, not the pipeline controls; Colonial shut the pipeline preemptively, substantially because the billing system was down, they couldn’t meter what they moved (per reporting). Civilization’s load-bearing infrastructure was down for six days at the join between OT and IT, at the invoice layer (the read-architectures-for-their-billing doctrine achieving its dark apotheosis). The cascade was pure old-familiar-genre: panic-buying emptied stations across the Southeast (people filming themselves pumping gas into plastic bags, the thundering herd, drink, now flammable), the ransom got paid ($4.4M; the FBI would claw back a chunk within weeks via the attackers’ own wallet hygiene), and the executive-order/regulatory response (mandatory incident reporting for pipelines) shipped faster than any post-incident action item this archive has filed from the private sector. Beirut’s clause with a rare epilogue: sometimes the warnings get re-routed to someone with authority.
The crypto ledger performed its scheduled comedy and correction in one arc: Elon hosted SNL (May 8) and Dogecoin, hyped to ~$0.73 into the show, crashed during the live broadcast the moment he called it “a hustle” in a sketch (the meme-consensus engine discovering it had priced in its own punchline); then Tesla suspended Bitcoin payments over energy concerns (reversing years-old enthusiasm), China reiterated bans, and the whole complex shed ~40% in days. The eschatology executes on schedule, date unknowable as always, proximate cause: a comedy show. The archive rests.
TIL: OT/IT segmentation in practice. The pipeline SCADA systems were reportedly isolatable, but the business dependency (billing, scheduling, safety-compliance paperwork) made “keep operating blind” untenable. Availability isn’t just “can the system run,” it’s “can the organization responsibly let it” (the certification file; the paperwork is load-bearing, always).