<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Risk on S3H.com</title>
    <link>https://s3h.com/tags/risk/</link>
    <description>Recent content in Risk on S3H.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 25 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://s3h.com/tags/risk/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Vulnerability Management Backlog Every Organization Has and Nobody Talks About</title>
      <link>https://s3h.com/2026/03/25/the-vulnerability-management-backlog-every-organization-has-and-nobody-talks-about/</link>
      <pubDate>Wed, 25 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://s3h.com/2026/03/25/the-vulnerability-management-backlog-every-organization-has-and-nobody-talks-about/</guid>
      <description>&lt;p&gt;Vulnerability management programs have a dirty secret that annual security assessments and compliance audits politely decline to examine: the remediation backlog. Organizations that have deployed vulnerability scanners — Tenable, Qualys, Rapid7 — know their vulnerability count precisely. Most of them have more open vulnerabilities than they will remediate in the coming year. Many have more open vulnerabilities than they will remediate in the next three years at their current remediation pace.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
