RE: https://ohai.social/@senficon/115417214885782255

#Log4j is popular.
#OpenSource funding is necessary.
Thanks to the @sovtechfund, which did so much for us after Log4shell!

RE: https://ohai.social/@senficon/115417214885782255

#Log4j is popular.
#OpenSource funding is necessary.
Thanks to the @sovtechfund, which did so much for us after Log4shell!

I never imagined GitHub would ask me to speak about Log4Shell.
But it happened.

GitHub asked me to share the story as I lived it, for the benefit of all maintainers and users of open source. How could I say no?

I hope it helps build a more secure future.

No more Log4Shell.

https://github.blog/open-source/inside-the-breach-that-broke-the-internet-the-untold-story-of-log4shell/

#opensource #log4j #Log4Shell #programming #security #hacking #Github

I never imagined GitHub would ask me to speak about Log4Shell.
But it happened.

GitHub asked me to share the story as I lived it, for the benefit of all maintainers and users of open source. How could I say no?

I hope it helps build a more secure future.

No more Log4Shell.

https://github.blog/open-source/inside-the-breach-that-broke-the-internet-the-untold-story-of-log4shell/

#opensource #log4j #Log4Shell #programming #security #hacking #Github

Is it possible that #Log4j will be the most expensive global #InfoSec incident ever, not because of meaningful losses stemming from successful exploitation, but because it continues to be part of the continuous “ #SBOM and patch all the things will fix this!!” drumbeat?

Thinking about #InfoSec organizational behaviors derived from cognitive bias. In particular, availability bias from things that are memorable.

#Log4j#Heartbleed #SolarWinds#ShellShock#Spectre#Meltdown#SQLSlammer