Insight #1
"The fact that log4j is used in ~64% of Java applications and only 50% of those have updated to a fully fixed version means attackers will continue to target it and in many cases be successful in exploiting this vulnerability. With the recent OMB-22-18 directive it is going to make it much more difficult for these organizations to hide their data about using vulnerable third-party components like log4j, but at least for now, attackers are going to continue to have a field day in finding paths to exploit through log4j."
Insight #2
"There are currently just over 68 CVEs released per day in 2022 (per
https://CVE.icu). Even the best security testing in the world cannot find all of these and notify you of them. What we have learned on the one-year anniversary of Log4j is that teams must rely on real-time protection for their applications to protect against zero days such as the issue with log4j. This is no different than some of the technologies released in the *nix systems years ago like DEP and ASLR. These runtime protections were designed to completely stomp out certain types of vulnerabilities and prevent attacks. The same technology exists for applications, and it is called RASP (runtime application self-protection). RASP provides zero-day protection immediately and should be one layer to the security onion in your toolbox."
Insight #3
"The top priority for all CIOs for 2023 should be cybersecurity, and more specifically securing your software ecosystem."