Insight #1
Spring4Shell, the latest vulnerability in a Java ubiquitous library is the second major vulnerability in the last 4 months. It’s time we get focused on how we secure our open source by employing easier upgrade paths and utilizing instrumentation-based protections from attacks against 0-days.
Insight #2
Security should be designed as “secure by default,” especially when it comes to third-party libraries and frameworks. Requiring a developer to read the documentation to strengthen the security configurations or even to turn on security, who on average import 126+ different third-party libraries, is a bad approach. Security should be strong out of the box, adding documentation about how to tweak the configuration if needed, with detailed implications of doing so.
Insight #3
Security ops teams in organizations that make heavy use of SaaS-based services should be ingesting and monitoring any logs they can to detect malicious actions. Most SaaS services have a logging facility you can offload into your SIEM. Start with your highest risk systems today.