The Log4j zero day vulnerability has taken the world by storm and is the most critical and high profile vulnerability as of now. This vulnerability, also known as Log4Shell (which received the identifier CVE-2021-44228), enables exploitation of the Java-based logging component in the Apache Java library.
Due to the very widespread popularity of open source Log4j – used in applications from SAP to Jira to Cisco – attackers can now potentially access a very large number of companies’ applications and servers. They can spread malware, steal data and take control of applications. To make matters worse, exploitation is considered very easy.
The flaw was uncovered by the AliBaba cloud security team on November 24, and the first exploits were revealed to take place recently, on Dec. 9. CISA is working to address the issue, but until it does, IT vendors and CISOs are left on their own, attempting to create and release security patches before a widespread attack occurs.
Log4j Challenges for CISOs
But while IT vendors are releasing patches or sending updates about affected products, there is still more that is unknown than known about the risk most companies are dealing with. As a result, CISOs are facing two main challenges, under very stressful and time-sensitive conditions:
- Evaluating the Risk – CISOs are attempting to evaluate their networks and figure out if they are vulnerable or not. Potentially, they could be vulnerable if they use applications which make use of Log4j, or indirectly if they use a SaaS application that does.
- Waiting for Solutions – CISOs are waiting for all the security patches to come through so they can install them on time before an attack happens.
A Quick and Efficient Solution to Log4Shell: Zero Trust & Virtual Patching
Instead of waiting for vendors (or attackers), CISOs can take a proactive approach and virtually patch their critical applications with zero trust, immediately.
Cyolo, the agentless zero trust platform, enables CISOs and companies to protect their crown jewels, right now. Cyolo protects critical applications by denying access to them unless the user is authorized, regardless of previous authentications or accessibility. By using Cyolo, the applications are secured from unauthorized attempts to access them.
In other words, attackers who could exploit the Log4j vulnerability will not be able to know about the application’s existence, let alone connect and exploit them. This is true even if attackers have already exploited Log4j on other applications, not protected by Cyolo, and try to lateral move themselves into Cyolo-protected applications.
Critical Application Protection in Minutes
Installing Cyolo for virtual patching takes literally minutes, after which all applications are protected from the Log4j vulnerability.
It’s quick and simple:
- Identify your critical applications
- Reach out to ask for the Cyolo solution
- Install Cyolo in minutes
- Relax and plan your next steps strategically, knowing your data and customers are safe.
Log4Shell is today’s severe vulnerability, but what happens tomorrow? Or next year? Cyolo’s solution is ongoing – protecting applications and data and preventing attacker access, continuously and regardless of the most critical vulnerabilities out there.