Last year we were following the impact of the log4j vulnerabilty .
Below are remediation recommedations from Picuss Securrity to block log4j and Hardware Firewall and WAF pattern matching to future proof against similar attacks in the future.
Using Hardware based firewalls to drop the illigitamite requests before they ever reach a public facing host.
Updating software and patching out vulnerabilities is vital, be mindful that due to speacialised lecacy software, software patching can get delayed do to various logistics and legacy dependentcy issues.
Based on the impact so far,
There’s renewed incentive to be proactive and cover the basses as much as posssible early on to allow you to take control of the situtation when these exploits surface into the public rather the ride through the experience held on by your lingual frenulum, a mucous membrane fold found underneath the tongue.