Log4j has been the talk of the town for several weeks now. We have also already commented on this in a detailed post blog about Log4j and Log4Shell.
There are many descriptions of the vulnerability and its criticality on the Internet (CVE-2021-44228 in Apache Log4j 2). Nevertheless, many IT departments are already challenged by the simple question: "Am I affected at all, and if so, on which systems and in which application?"
There is a compilation of the affected applications on Github, for example. But do companies actually use them?
Even if the IT department has appropriate asset management, so-called shadow IT is left out of the picture here.
This can be remedied by comprehensive vulnerability scanning, offered by DriveLock for end devices. (Watch the webcast about it on the right). This allows you to scan all systems with little effort and provides you with clarity as to which application may require any action.
For the users of our DriveLock Vulnerability Management, we have built a simple and clear dashboard that bundles the relevant information around Log4j.
DriveLock Vulnerability Management Dashboard
1. In the DriveLock Operations Center, select "Add new dashboard tab".
2. In the pop-up window for creating a dashboard, select "New dashboard from string". Then copy the string below into the input field.
This gives you a dashboard that shows the relevant vulnerabilities in the upper section and the affected machines in the lower section.
We will be happy to answer any questions you may have about DriveLock Vulnerability Management!