Log4Shell Log4j 2 – not affecting our service!


We have not been affected by the Log4Shell (log4j) exploit. We’ve scanned all servers, confirmed that whilst lots of attempts to use the exploit, none had been successful. We’ve removed the vulnerable class from the log4j package, updated some configuration, and rebuilt our services. To find out more see here.