By Gregory Hale
With tensions mounting on a daily basis between Russia and the Ukraine along with various allies across the world, it is becoming clearer critical infrastructure could end up caught in the crosshairs of any kind of aggression.
It only makes sense, said Eric Byres, chief technology officer at software bill of materials provider, aDolus.
“An attack on the critical infrastructure is below the threshold of when bombs and bullets start flying,” Byres said. “If they drop a bomb on the United States, it is war. But if it is a cyberattack on the United States, they can deny it, then it will take two months for us to figure out who did it, and it is a soft attack where no one will probably die. So, there is lots of deniability, and lots of high public perception issues.”
A Department of Homeland Security (DHS) warning Sunday said Russia may pursue a cyberattack against the United States as tensions increase over Moscow’s buildup of forces near the border with Ukraine comes on the heels of a similar Cybersecurity and Infrastructure Security Agency (CISA) alert issued last week.
The latest DHS bulletin outlined Russia could launch such an attack if it perceived any U.S. or NATO response to be a threat to its own national security.
Cyber Weapons
While a political conflict often ends up solved through diplomacy or negotiation, in this age of cyber acuity, instead of guns and bombs, the potential for breaking out cyber weapons that can cause damage just increases.
One such scenario is the Log4j vulnerability. Apache Log4j software library versions 2.0-beta9 to 2.14.1 Zero Day is a critical vulnerability affecting a wide range of systems and users. While there are fixes available, not everyone knows or understands if they are using it.
The Log4j vulnerability (called Log4Shell which is CVE-2021-44228) is a result of overly provisioned features that were enabled by default, an insecure default configuration, and the implicit trust of messages. Log4j utility had message lookup substitution enabled by default. As a result, attackers can craft a special request that could make the utility remotely download and execute a payload.
Dragonfly was an attack where Russian operators created their own Zero Day. The same can be said for the NotPetya attack, Byres said.
“Log 4j should be in its own category,” said. “In most Russia attacks, it’s them finding a weak point in a supply chain and then exploiting it. Log4j is a Christmas present where they don’t have to do half the work.”
All About Scale
When it comes to attacks, the Russians are interested in scale.
“Take SolarWinds, they are thinking let’s attack one company and get into 18,000.,” Byres said. “That seems to be the modus operandi. The thing about Log4j is it is a way to get in fast. It tends to be used by a developer, working for a developer, working for a developer, it is deep down there. Nobody buys Log4j. Nobody says I am going to use Log4j in my refinery today. I am using GE software, which happens to use Log4j. Log4J is a gift to the Russians and other foreign attackers who are not going to use it today. They are going to use it to get into a critical server on the plant floor and sit there and they are going to close down that opportunity, or they may even fix the issue, then once they are in, they are going to leave an alternative back door.”
There is a difference between political tensions and an attack on the critical infrastructure, but the Russians will focus on anything that will give them political impact.
“The Russians know an attack on the critical infrastructure will get press and could potentially turn the American public against defending Ukraine,” Byres said. “There are three intelligence services in Russia, the GRU, who you can thank for Dragonfly, the attacks in the Ukraine in the past and NotPetya. They tend to be cowboys. They don’t care about collateral damage. They don’t try to be subtle.
“Then you have the SVR, the foreign intelligence service, they are the folks operating SolarWinds, their goal was to be subtle and fly under the radar, so you don’t discover us. Then there is the Federal Security Service or the FSR, the old KGB, which deals with more domestic work,” Byres said.
The question now is if companies are prepared and what can they do to stay on alert?
All-Inclusive Security Mindset
It used to be companies would ask their IT departments if they are ready, and they would say “yes we are” without even thinking about OT.
“I think one of the improvements we are now seeing companies are prepared and that is with OT and IT where before it was just IT,” Byres said.
Byres also added the Canadian government issued a warning about potential attacks and one of the interesting points that came out of the advisory was a directive saying you should test and prepare for isolation of the OT system from the IT system. It asked if a company would be able to run the OT system if the IT system is turned off.
In the case of the Colonial Pipeline attack this past May, the answer was no. Colonial Pipeline suffered a ransomware attack on its IT system and it forced the company to shut down its entire operation cause panic along the eastern seaboard in the United States.
How can companies defend themselves?
“How do you find out if you have Log4J? If you don’t have any Log4j, you don’t have any problems,” Byres said. “The challenge right now is finding out if the software you are running has Log4j buried in there. I was talking to a U.S. defense contractor last week and he was saying it has taken him two weeks to contact all the vendors he uses to ask them if they are running Log4j in the software they supply. Two weeks? That is a lifetime for an attacker.”
Other Attacks
While the Russian-Ukraine issue may or may not go away, but Byres sees potential other attacks brewing.
“I believe the activity of the malware community that is based in the former Soviet-bloc countries where we could see a bunch of really nasty activity by Russian criminal gangs,” Byres said.
To reduce the likelihood of a damaging cyber intrusion, CISA suggests organizations to:
- Validate all remote access to the organization’s network and privileged or administrative access requires multi-factor authentication.
- Ensure software is up to date, prioritizing updates that address known exploited vulnerabilities identified by CISA.
- Confirm the organization’s IT personnel have disabled all ports and protocols not essential for business purposes.
- If the organization is using cloud services, ensure IT personnel have reviewed and implemented strong controls outlined in CISA’s guidance.
It is not all doom and gloom as the industry is seeing real progress.
“We have gone from the days of asking if this critical infrastructure safe, ‘oh yeah, we have the IT department nailed down; oh, what is the OT department?’ We have moved on to the point where is everyone is aware.”

