When the Log4j security flaw (opens in a new tab) reared its ugly head — allowing cybercriminals to penetrate vulnerable computer networks with a single line of code — it seemed to be a once-in-a-blue-moon cybersecurity threat, a nuclear zero-day vulnerability that needed to be patched immediately.
But then, before you could say déjà vu, the Spring4Shell (opens in a new tab) zero-day came along, capturing more headlines, panicking senior executives, and sending security teams into 24/7 overdrive.
Times have certainly changed. It used to be that criminal hackers would reliably exploit such zero-days (code flaws that a software creator or vendor does not know exist until they are found or exploited) every few years or so.
Now, as companies and governments increasingly rely on third-party software to run networks and organizational apps, these zero-days are becoming more frequent and severe.
Stay in the hunt!
But IT security professionals—and the executive leaders and boards they answer to—are asking: Are zero-days really increasing and getting worse? Or are security researchers and the bug bounty hunters who ferret out these flaws just getting better at their job?
“Every zero-day is not a critical all-hands scenario.”Melissa Bischoping, director of endpoint security research, Tanium
Melissa Bischoping, a director of endpoint security research at Tanium, believes it’s the latter. “More zero-days are showing up, in part because so many people are looking for them now,” says Bischoping, who also runs threat-hunting workshops. “Every zero-day is not a critical all-hands scenario. The looming threat of the ‘big ones’ keeps you up at night, but those are only a fraction of the zero-days we see. I advise people to evaluate and react accordingly based on severity, not solely on the fact that it’s a zero-day.”
That said, she warns that it’s crucial for security professionals to stay in the hunt. Given the way criminal hackers can weaponize a single vulnerability to create widespread havoc (see the SolarWinds hack and its impact on companies and governments), staying on top of zero-days is key to network security.
Zero-day exploits are becoming more severe
Steve Wilson, chief product officer at Contrast Security, which provides a unified platform to help developers code more securely, sees an increase in the number and severity of zero-day exploits on the application layer, where Contrast focuses its work. A key reason, he says, is that much of the software code that enterprises use today was actually written many years or even decades ago. Apache Log4j, a Java library, has a 20-year-old history and is largely maintained by volunteers (opens in a new tab), Wilson notes.
“Many of the fundamental assumptions in these libraries were made in a time when developers knew less about how to build secure code,” says Wilson. “Hackers are now clearly looking at these older, highly deployed ecosystems, where chinks in the armor can have massive repercussions.”
A growing attack surface
Tony Lauro, director of security technology and strategy at Akamai Technologies, agrees zero-day threats will persist for the foreseeable future, in large part because so many companies are digitizing, moving to the cloud (opens in a new tab), and letting employees work remotely (opens in a new tab) from a variety of endpoint devices.
“Unfortunately, we’re going to see this problem get worse before it gets better because there will be more available attack surfaces for attackers to target,” says Lauro. “And certainly, with all the new generations that are coming online, there’s bound to be more pools of victims as well.”
[Read also: What you don’t know about the remote-work revolution may hurt you] (opens in a new tab)
What’s more, zero-day exploits could increase because they are becoming moneymakers for the cyber underworld. NSA Director of Cybersecurity Rob Joyce told one panel at this year’s RSA Conference that ransomware gangs are using their profits to buy zero-day exploits, and that his agency is concerned with how quickly criminals can take advantage of newly disclosed software vulnerabilities.
The sky is not falling — until it is
Though some zero-day exploits may seem more menacing than they really are, IT security departments must take them all seriously and do their utmost to defend against them.
“They’re getting 150,000 different warnings about various vulnerabilities, and that can be almost numbing.”Frank Dickson, group vice president, IDC
Some security teams will balk at this approach. They’ve spent years hearing vendors, researchers, and software developers flagging new zero-days that end up as big nothing burgers. Besides, most security teams are overworked, understaffed, and underfunded. As such, they tend to ignore non-urgent alarms.
“It’s ‘alert fatigue (opens in a new tab),’” says Frank Dickson, group vice president at IDC. “They’re getting 150,000 different warnings about various vulnerabilities, and that can be almost numbing.”
Dickson says companies must first address such frustrations. They must also address the threat zero-days pose by making a few obvious and less obvious changes in their cyber hygiene (opens in a new tab), such as:
Incidentally, there are many worthy enterprise-class asset management tools that can help with this, but equally as important is to address the culture around deprioritizing cybersecurity and hygiene for the sake of speed.
“We’re all going to have to continue fighting zero-days. The only easy day was yesterday.”Tony Lauro, director of security technology and strategy, Akamai Technologies
Dickson says that has to change. Organizations must incentivize software developers to meet hard security goals. “Developers today are compensated for their ability to deliver products by a deadline and drive revenue, but we don’t necessarily compensate them for secure coding,” he says. “We should. Driving a security paradigm from the top down in organizations is extremely important.”
Bischoping adds that it’s also crucial to avoid hitting developers with a stick when occasional vulnerabilities appear and become zero-days. “We need to stop this culture of assigning blame when there is a breach,” she says. “Yes, you want to be able to go back and determine if the code was written poorly and look to see if processes were followed. But taking a punitive approach is counterproductive and doesn’t really solve anything. You need to focus instead on understanding the gaps that introduced the vulnerability and how to continually improve with each root cause analysis.”
This is primarily because of the unforeseen nature of zero-days, which can often graduate from vulnerabilities into exploits and attacks in a matter of days. In addition, because vendors are typically learning about vulnerabilities long after their creation, they don’t always have an effective patch ready. Many times, the best they can do is offer temporary configuration-tweak suggestions, pending
an update.
Bischoping recommends creating and constantly updating a playbook to cover such matters as:
“If you put in all the work now, when the five-alarm fire bells go off, you’ll have the confidence to know that most of what you’ll need to do is right there in your playbook,” says Bischoping.
Zero-day attacks are not a foregone conclusion. They might not affect most organizations, but they’re not going away.
“The battle is not done. We’re all going to have to continue fighting zero-days,” says Akamai’s Lauro. “The only easy day was yesterday, essentially.”



