Forum Discussion
Apache Log4j Detection for Windows - Manifest / Properties...
Apache Log4j Detection for Windows - Manifest / Properties Detection Update Summary: In the light of resource requirements to scan entire file systems along with inspecting each Java archive file ...
Great, happy to see that resource utilization for plugin 156001 is improved. Seeing memory on our production VM's running 8Gb RAM maxed out for an extended period of time was not entertaining.
However, 50% of our environment is Windows Server 2012 R2 that does not - nor will ever be running - newly-mandatory PowerShell 5.x or better (or either of its .NET and WMF prerequisites). This is resulting in False Negatives Positives in a production environment, and affecting our ability to get a remediation plan to the customer.
Is there any hope for production sites that need both plugin 156001 to identify Log4j JAR files and to maintain Windows Server 2012 R2 until it is retired?
