Your organization’s IT environment could be at risk.
First reported on December 9, 2021, the Apache Log4j vulnerability is one of the most serious vulnerabilities on the internet in recent years, putting millions of devices at risk. Here’s what you need to know.
It could be on any device
Log4j is widely used on Windows, Linux, Mac, IoT, home devices, etc.
It could be anywhere on disk
Log4j is commonly renamed and repackaged, meaning the vulnerability can be present anywhere.
It is exploited in real time
Log4j has been targeted in 800,000+ attacks within 72 hours of the vulnerability publication.
It could cost you
The Federal Trade Commission plans to pursue companies who don't remedy the Log4j vulnerability.
0
CVSS score
0
Cyberattack attempts within first 72 hours of vulnerability publication
0
Exploits per second, according to Cloudflare
Good enough isn't good enough when it comes to Log4j
Tanium can help you scan, search and hunt down Log4j exposure you didn't even know existed. These modules give you a starting point, narrow down the search and pinpoint exact locations of Log4j.
Read our full guidanceInteract
Included with Tanium Core
What is it?
List of applications installed in plain sight on your endpoints
What does it do?
Great for understanding the IT estate, counting software licenses and serving as a starting point for your Log4j hunt
Why does it matter?
Immediately gain visibility into your IT environment
Index
Included with Threat Response
What is it?
List of unique filenames and folders on your endpoints
What does it do?
Great for searching known file names and hashes and locating the paths of those files
Why does it matter?
Search deeper and quickly find Log4j by name in known file folders
Reveal
What is it?
Indexed search of every folder, file and its contents
What does it do?
Great for uncovering hidden instances of Log4j. Reveal can spot traces of Log4j inside nested or renamed files and archived folders (e.g., .jar, .zip, etc.) as well as references to Log4j inside file content
Why does it matter?
Log4j has nowhere to hide even when a file name has been changed — maliciously or by design