Blogs
Still Running Vulnerable Log4j Instances?
The Log4j exploit was discovered in December 2021, and by now, it should have been resolved. However, it persists.
Tag
9 articles

Blogs
Modern applications rely on open source components for up to 90% of their code, creating a vast attack surface dominated by inhemalicious supply chain injections. High-profile incidents like Log4j and the sabotage of colors.js hig…
Showing 1–9 of 9
Blogs
The Log4j exploit was discovered in December 2021, and by now, it should have been resolved. However, it persists.
Business of DevOps
The open web application security project (OWASP) recently updated its top 10 list of the most critical security risks to web applications after four years. It represents the most…
Business of DevOps
The recent Log4j/Log4Shell vulnerability was a wake-up call that threats aren’t going to wait until the industry gets up to speed on software supply chain security. While the Log4j…
Blogs
As new vulnerabilities are discovered on a daily basis, DevOps teams must integrate security into the early stages of the development lifecycle and be vigilant about what elements…
Application Performance Management/Monitoring
The recent discovery of the Apache Log4j vulnerability has wide-ranging implications for anyone who develops software, especially for those in the DevOps realm. What’s most troubli…
Continuous Delivery
In 2021, the security story in DevOps and DevSecOps has been the supply chain. So, it’s only fitting that we are currently experiencing the mother of all supply chain issues with t…
Best of 2021
In this week’s The Long View: Improving U.S. government CX, how much money Mozilla makes, and the latest on the Log4j/Log4Shell débâcle.