In this resource center, we will address the core facts regarding the recently disclosed security vulnerability in the Apache log4j project, which has been dubbed “Log4Shell”, why it’s important to address quickly, how to address it, and how to better prepare for future vulnerabilities.
.png?width=500&name=log4j%20(1).png)
If you work in an organization that uses open source to develop applications, by now you are probably aware of the recently disclosed vulnerability in log4j, commonly being referred to as the Log4Shell vulnerability.
Tidelift solutions architect lead Mark Galpin shares insights into theLog4Shell vulnerability and discusses how things have changed since Heartbleed, a similar zero day vulnerability from a decade ago. He shares how things have improved and discusses ways we can continue addressing the underlying issues even better. He shows how Tidelift can help with these challenges.
In this Upstream chat, Tracy Bannon from MITRE and Tidelift CEO and co-founder Donald Fischer discuss risk profile and ways organizations can force-rank priorities and how it applies to open source software specifically.
Donald and Tracy also discuss the recently disclosed security vulnerability in the Apache log4j project, which has been dubbed “Log4Shell”, why it’s important to address quickly, how to address it, and how to better prepare for future vulnerabilities. You won't want to miss this.
In this 20-minute briefing, Tidelift solutions architect lead Mark Galpin shares what you need to know about the recent Log4Shell vulnerability—and demos how Tidelift can help.
In this guide, you will learn:
50 Milk St, 16th Floor, Boston, MA 02109
.svg){kind=icon}