With the news of the log4Shell bug making the rounds on industry and mainstream media, security experts are scrambling to address the implications of widespread bug patches and shared open-source utilities.
Here, we wanted to address some terminologies around the bug, specifically references to this bug representing a zero-day exploit. We’ll define zero-day exploits, why they are so dangerous and how security firms address them.
December 7, 2021–the Google Threat Analysis Group (TAG) announced that it has identified and temporarily disrupted the Glupteba botnet responsible for infecting an estimated 1 million computers and IoT devices.
This temporary disruption seems to have slightly impacted the botnet’s operation, but currently, the network is still operational.
Many of us may hear about botnets in the news or our compliance meetings… but what is a botnet? Here, we will cover the topic briefly and discuss the implications of Google’s move against this particular threat actor.
Malware is a significant, and continuing, problem. A 2019 Verizon study shows that 28% of all data breaches involve malware, and new forms of malware and ransomware are emerging into the wild almost daily.
The challenge of fighting malware is that hackers are finding new ways to inject programs into systems. Even with advanced compliance and security guidelines in private and public markets, these hackers are working every technical and social angle possible to attack industrial, commercial and defense systems. And, unfortunately, it only takes one malicious program to completely bring a system to its knees. We’ve seen this most recently and publicly with the Colonial Pipeline ransomware attack, which cost the company $2.3M.
In the past 5 years, new forms of malware have emerged. Two of these, encrypted and fileless malware, have become more sophisticated and, thus, more dangerous. These attacks are harder to detect, using our existing security measures and assumptions about malware against us.