Menu

Post image 1
Post image 2
1 / 2
0

Lessons from Log4Shell: Building a CRA-Ready Log4j

DEV Community·Whitney·26 days ago
#Okb984DX
Reading 0:00
15s threshold

By: Piotr P. Karwasz, VP Logging, Apache Software Foundation The disclosure of Log4Shell (CVE-2021-44228) on December 9, 2021 did not just expose a vulnerability: it exposed a way of building software that was no longer fit for purpose, and it helped bring the European Cyber Resilience Act into being. I recently hosted a session for the Open Regulatory Compliance community’s CRA Monday series to tell the story from the inside: what the Apache Logging team actually did in the years after Log4Shell to rebuild the project as something CRA-ready. This blog recaps and expands upon that session; you can also watch the recording or view the slides . A Wake-Up Call for the Software Ecosystem Log4Shell’s impact was unprecedented in scale. Apache Log4j is embedded so deeply across the software ecosystem that the vulnerability propagated almost everywhere at once and most organizations had no idea where they were exposed.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More