I’m scheduled to join @jimsciutto on @CNN at 10am Eastern to talk about ransomware and intrusions into our industrial infrastructure in context of the Colonial Pipeline incident. Join me if you can and thanks for tuning in.
In my opinion there’s some bad takes out there but overall it’s completely reasonable that folks are paying attention. This is the most disruptive incident we’ve seen on US energy infrastructure from cyber intrusions. Colonial Pipeline is the victim and has done a lot right.
They contacted a top tier incident response firm (FireEye/Mandiant) for the enterprise compromise (only IT impacted it seems) to lead the response. They informed the USG who had great folks from CISA/FBI/DOE supporting. They focused on safety and took operations down proactively.
Congress and others will reasonably ask: “if a criminal can do this, what more could a state adversary could do?” While we should avoid hype this is a very reasonable question. The reality is our infrastructure is undergoing a rapid digital transformation.
While the ransomware was confined to IT this could have been much worse if it had hit OT and at Dragos we have handled such cases and they candidly suck. As our industries change the historical mindset of “segment and disconnect OT” just isn’t practical in most cases.
75%+ of many of the standards/regulations/frameworks/etc. push for preventive controls (segmentation, authentication, anti malware, patching, etc.) all good controls but that leaves an under investment in detection and response. As our infrastructure changes so will our threats.
What we see most commonly is without visibility and monitoring in OT networks the preventive controls are not applied everywhere and atrophy over time unknowningly to the defenders.
Many realize this though. The current White House administration has rightfully pushed for a 100 day action plan to encourage visibility, detection, and response enhancements in OT in the electric sector and likely following suit in water and natural gas to raise awareness
To the practitioners out there thinking about their OT networks I would encourage engaging firms with OT/ICS incident response experience. Conduct a TTX to rehearse. Use burn down to do an Architecture Review of what you have today and it’s state. Then move into monitoring in OT
For the executives out there realize your IT and Security staff are usually already under invested in. Picking up a whole new mission set with focus (OT) requires additional resources. Elevate the conversation in your org and invest in your people to enable your business.
To the policy folks out there - realize our infrastructure owners largely know what to do. They don’t need silver bullets and it’s not a need to invent new technologies. It’s about communicating clearly on what investments are needed and enabling them to make those investments
The governments best role isn’t fly away teams and technology deployments. It’s amplification of what works, relevant and actionable information sharing, consistent messaging, setting the rules, holding foreign actors accountable, and investing in the ecosystem. That scales.
All in all this incident isn’t anything to be fearful over. But it is a public example of what many are concerned about and it could have been much worse. Colonial Pipeline is doing a great job so far as we can tell. Others may not. If we approach this thoughtfully we can win.
Here's a link to the interview. Thanks for having me on Jim and CNN crew!
To the security professionals facing difficulties getting an entry level job, being properly resourced, facing internal policy issues, being beaten down by competing frameworks/guidance/advice even from USG...the “if NSA could monitor your networks we’d fix it” is insulting.
I really do like the NSA; having served there I know the amazing work they do. I’m also a privacy advocate as many there are. There’s real roles and responsibilities for government to help private sector. More surveillance isn’t the answer. Actually there is no one answer.
When you’re in USG (NSA/DHS/DOD/etc.) you hear that people need help. You have insights and training. You want to help. It’s awesome. But the problems aren’t that simple. You also see rising threats but don’t see the closure that happens inside those companies. It creates angst
There’s a new @nytimes article out on a @RecordedFuture report coming out tomorrow ok potential Chinese activity targeting Indian electric sites. I’ll hold broad thoughts for the report to drop where I can dig in but a few initial thoughts: nytimes.com/2021/02/28/us/…
First, it’d be no surprise to find that between two states that have conflict (and with some skirmishes bordering on going larger) that there would be targeting of critical national infrastructure such as the electric system (power grid). So the claim seems very reasonable
Interestingly, the NYT writes: “Now, a new study lends weight to the idea that those two events may well have been connected” referring to a power outage last year in India. But what’s interesting is the RF analysts don’t seem to say that noting instead a link is unsubstantiated
A quick thread on intelligence analysis in the context of cyber threat intelligence. I see a number of CTI analysts get into near analysis paralysis phases for over thinking their assessments or over obsessing about if they might be wrong. (1/x)
Consider this scenario. A CTI analyst identifies new intrusions and based on the collection available and their expertise note that the victims are all banks. Their consumer wants to know when threats specifically target banks (not just that banks are victims).
The CTI analyst has, from their collection, at this time, and based on their expertise enough to make an activity group (leveraging the Diamond Model in this example) that meet's the requirement of their consumer. So what's the problem?
Yesterday in the Congressional hearing on homeland cybersecurity @C_C_Krebs and @DAlperovitch very kindly called out @DragosInc as a good example/company to work with in ICS/OT. Not “buy Dragos stuff” but “here’s a good example of an approach” and I just want to say thanks
We’ve been afforded a really cool place in the community to be allowed to focus on ICS/OT and have a ton of support from around the community.
What mostly stood out to me on this topic is that both recognized the unique approach required for ICS (Dragos or not)
Enterprise security is very important. And there’s lots to learn from them for ICS. But ICS security is different especially when dealing with physical systems. Understanding the unique risks, systems, etc all matter but most important is understanding the mission and priorities
The fact that so many are focusing on the water plant using Windows 7, which had nothing to do with how the attack was done, is interesting. Folks have an obsession with vulnerabilities and while they can matter a lot it is a fundamentally different value prop in ICS.
The attack took advantage of TeamViewer. In this instance the OS didn’t matter. The TeamViewer application was Internet facing and available. The attack took advantage of the HMI, that’s not a software vuln issue, they just did what operators could do on the system natively
There’s a lot of “insecure by design” systems in ICS. Meaning most of the things you want to do you don’t need a vulnerability or exploit to do.
Also a lot of IT security is system or data security, protect the system don’t let folks get root, encrypt the data, etc. ICS is not
In my career I have found the loudest naysayer voices find themselves in echo chambers to make themselves feel like thought leaders but are often well in the minority and simply not part of where the real work happens, ostracized by the do’ers for being heroes in their own mind.
My advice to the folks who find themselves trapped in those echo chambers is to step out of the social media bubble when necessary and look into the much larger community and partake in it and move the needle forward. In all corners of this infosec industry you’ll find the do’ers
It’s appropriate to have informed discussion about what the best paths forward are. But if you find yourself critiquing more than working - ask yourself what path you’re on. Everyone’s biases, that’s ok, but make sure you’re building up more than tearing down or you’ll be alone