Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://mstdn.social/users/msw/statuses/111858551441620796">Matt "msw" Wilson (msw@mstdn.social)'s status on Friday, 02-Feb-2024 11:04:09 JST</a><a href="https://mstdn.social/@msw" title="msw@mstdn.social"><img src="https://gnusocial.jp/avatar/25406-48-20221113054622.webp" width="48" height="48" alt='Matt "msw" Wilson' style="position: absolute; left: 0; top: 0;">Matt "msw" Wilson</a></section><article><p>Unpopular opinion: "patch all the things" was a zero interest rate phenomenon.<br><a href="https://mstdn.social/tags/InfoSec" rel="tag">#InfoSec</a> <a href="https://mstdn.social/tags/CVE" rel="tag">#CVE</a> <a href="https://mstdn.social/tags/SBOM" rel="tag">#SBOM</a> <a href="https://mstdn.social/tags/Linux" rel="tag">#Linux</a> <a href="https://mstdn.social/tags/OpenSource" rel="tag">#OpenSource</a> <a href="https://mstdn.social/tags/OSS" rel="tag">#OSS</a> <a href="https://mstdn.social/tags/FOSS" rel="tag">#FOSS</a> <a href="https://mstdn.social/tags/Patching" rel="tag">#Patching</a> <br><a href="https://www.redhat.com/en/blog/patch-management-needs-a-revolution-part-4" rel="nofollow noreferrer">https://www.redhat.com/en/blog/patch-management-needs-a-revolution-part-4</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/2666201#notice-5284208">In conversation</a><time datetime="2024-02-02T11:04:09+09:00" title="Friday, 02-Feb-2024 11:04:09 JST">about 10 months ago</time> <span>from <span><a href="https://mstdn.social/@msw/111858551441620796" rel="external" title="Sent from mstdn.social via ActivityPub">mstdn.social</a></span></span><a href="https://mstdn.social/@msw/111858551441620796">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: www.redhat.com</div><h5><a href="https://www.redhat.com/en/blog/patch-management-needs-a-revolution-part-4">Patch management needs a revolution, part 4: Sane patching is safe patching is selective patching</a></h5><div></div></header><div>One of the biggest concerns with modern patch management is that we haven’t truly challenged our thinking around “patching everything” over the past 40 years. Today, we are still inundated with customer requests to patch everything, despite the available evidence showing that most vulnerabilities do not and will not ever see exploitation. So the larger question is, what is the purpose of the exercise?</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Matt "msw" Wilson (msw@mstdn.social)'s status on Friday, 02-Feb-2024 11:04:09 JST Matt "msw" Wilson
Unpopular opinion: "patch all the things" was a zero interest rate phenomenon.
#InfoSec #CVE #SBOM #Linux #OpenSource #OSS #FOSS #Patching
https://www.redhat.com/en/blog/patch-management-needs-a-revolution-part-4
In conversationabout 10 months ago from mstdn.socialpermalink
Attachments
1. Domain not in remote thumbnail source whitelist: www.redhat.com
  Patch management needs a revolution, part 4: Sane patching is safe patching is selective patching
  One of the biggest concerns with modern patch management is that we haven’t truly challenged our thinking around “patching everything” over the past 40 years. Today, we are still inundated with customer requests to patch everything, despite the available evidence showing that most vulnerabilities do not and will not ever see exploitation. So the larger question is, what is the purpose of the exercise?

Public

Embed Notice

HTML Code

Corresponding Notice