<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Java on Teddy Ferdinand</title><link>https://tferdinand.net/en/tags/java/</link><description>Recent content in Java on Teddy Ferdinand</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 20 Dec 2021 20:37:40 +0000</lastBuildDate><atom:link href="https://tferdinand.net/en/tags/java/index.xml" rel="self" type="application/rss+xml"/><item><title>Log4j from the eye of the storm</title><link>https://tferdinand.net/en/log4j-from-the-eye-of-the-storm/</link><pubDate>Mon, 20 Dec 2021 20:37:40 +0000</pubDate><guid>https://tferdinand.net/en/log4j-from-the-eye-of-the-storm/</guid><description>&lt;p&gt;Unless you live in a cave, you couldn’t miss the last few days the &lt;a href="https://logging.apache.org/log4j/2.x/security.html"&gt;flaws discovered on the Java log4j library&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;I’m not going to make another post talk about this flaw, but rather to talk about my experience in the field on the impact of this flaw at the operational level.&lt;/p&gt;
&lt;h2 id="the-importance-of-having-an-up-to-date-inventory"&gt;The importance of having an up-to-date inventory&lt;/h2&gt;
&lt;p&gt;I talked about this on Twitter (in French), but for me, this flaw highlights the fact that many companies lack an up-to-date inventory of their resources.&lt;/p&gt;</description></item></channel></rss>