/* ---- Google Analytics Code Below */

Monday, February 07, 2022

Addressing Log4J

  This pervasive vulnerability will require continued care and attention to fully remediate and detect permutations. Here are some ways to get started.

Jeremy Colvin  in Darkreading

Technical Product Marketer, Uptycs

"Well done" to the security engineers and managers who labored in the trenches in recent weeks. But if you thought the Log4j vulnerability was last year's problem, think again. In 2022, this vulnerability will require care and attention to fully remediate and detect permutations.

Log4j fears centered on the pervasive use of the Java logging library and how easily an unauthenticated attacker could leverage the exploit for remote code execution (RCE). We have implemented updated configurations, and feel prepared to mitigate the suite of Log4j exploits — for now. However, permutations of this exploit are already emerging and long-term solutions involving full upgrades to core infrastructure are likely pending at your organization.

Because of subsequent emerging common vulnerabilities and exposures (CVEs) and how hastily many teams made config changes and scanned assets for vulnerable software, it will be months before Log4j is truly behind us and under control. Many organizations are stuck in either the discovery phase trying to fully map where their systems use Java or Log4j or in remediation as operational or system limitations restrict their ability to roll out full patches.

Be prepared to execute a full remediation process because initial configuration changes become inadequate and the vulnerability permutates. The following best practices/focus points will help ready your security team and colleagues.  .... ' 

No comments: