This was a fav session from #S4x19. I think @stvemillertime made several GREAT points about why IT Security techniques are important when defending OT environments. 1/n
9:48-10:22: If you want to detect an ICS attack as far left of boom as possible, you should look for the IT attack first. (Looking for the OT attack is dangerously late-stage.) 2/n
8:30-9:26: In the Triton attack, 99 compromised machines were Windows servers or workstations. Only 1 was the safety controller... 99% of detection opportunities are conventional detection opportunities. 3/n
5:42-8:04 The vast majority of the Triton attack used conventional (IT) tools like NMAP, Powershell-invoked Mimikatz, & Meterpreter, webshells, VPN compromise, cryptcat, plink-tunneled RDP, scheduled tasks for persistence, AD Explorer & other sysinternals. 4/n
Are OT-specific tools and experience valuable? Absolutely. Shout out to @electricfork and the absolute brain trust that @RobertMLee has built at @DragosInc. 5/n
What I am saying is that OT networks are not so unique that IT tools are useless. Purdue model alone won’t save you. And I talk to a LOT of OT networks owners that are woefully ignoring or underusing classes of good tools because they have blind faith in their segmentation. 6/6
• • •
Missing some Tweet in this thread? You can try to
force a refresh
This DNS outage goes far beyond just Facebook. From my home internet, I'm getting dropped or inconsistent DNS responses for a variety of sites.
If your normal DNS resolvers are failing, here are some alternatives:
Google (8.8.8.8, 8.8.4.4)
Cloudflare (1.1.1.1)
Comodo (8.26.56.26)
OpenDNS (208.67.222.222)
Quad9 (9.9.9.9)
Verisign (64.6.65.6)
What I'm guessing: Facebook accidentally broke it's BGP routes, breaking their DNS. This caused big DNS resolvers (like Google) to backlog with failing queries. As these big DNS resolvers began to drop traffic, it broke a lot of other sites, too.