<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><title>Automated Vulnerability Remediation</title><link>https://automatedvulnerabilityremediation.com/</link><description>Register of 14 platforms that clear a vulnerability backlog with agents: sourced facts under seven topics, and a backlog calculator. Read 10 Nov 2026.</description><lastBuildDate>Tue, 10 Nov 2026 00:00:00 GMT</lastBuildDate>
<item><title>How to measure a vulnerability backlog in hours, not findings</title><link>https://automatedvulnerabilityremediation.com/guides/how-to-measure-a-backlog/</link><guid>https://automatedvulnerabilityremediation.com/guides/how-to-measure-a-backlog/</guid><pubDate>Tue, 10 Nov 2026 00:00:00 GMT</pubDate><description>A backlog of 20,000 findings at 25 minutes of analysis each is 8,333 analyst hours, which is 463 working days for three analysts giving 30 hours a week. Me</description></item>
<item><title>Automated vulnerability remediation: what an agent can fix without a human</title><link>https://automatedvulnerabilityremediation.com/guides/what-an-agent-can-fix-without-a-human/</link><guid>https://automatedvulnerabilityremediation.com/guides/what-an-agent-can-fix-without-a-human/</guid><pubDate>Tue, 10 Nov 2026 00:00:00 GMT</pubDate><description>Vendors describe four outputs an agent can produce on its own: a pull request, a patch job, a network or web application firewall rule, and a ticket with t</description></item>
<item><title>How approval should work when an agent changes production</title><link>https://automatedvulnerabilityremediation.com/guides/how-approval-should-work/</link><guid>https://automatedvulnerabilityremediation.com/guides/how-approval-should-work/</guid><pubDate>Tue, 10 Nov 2026 00:00:00 GMT</pubDate><description>Approval works well when it is set per action: read-only steps run alone, reversible changes run in staged rings, and irreversible ones wait for a person. </description></item>
<item><title>Ownership mapping: finding who can fix a finding</title><link>https://automatedvulnerabilityremediation.com/guides/ownership-mapping/</link><guid>https://automatedvulnerabilityremediation.com/guides/ownership-mapping/</guid><pubDate>Tue, 10 Nov 2026 00:00:00 GMT</pubDate><description>Ownership mapping assigns each finding to a team that can change the asset. Onit claims about half of remediation tickets bounce because the owner is wrong</description></item>
<item><title>Reading a vendor's vulnerability remediation claim</title><link>https://automatedvulnerabilityremediation.com/guides/reading-a-vendors-remediation-claim/</link><guid>https://automatedvulnerabilityremediation.com/guides/reading-a-vendors-remediation-claim/</guid><pubDate>Tue, 10 Nov 2026 00:00:00 GMT</pubDate><description>Averlon states 110,000 critical and high issues became 260 pull requests and mean time to remediate fell from 45 days to 6, for an unnamed customer. Backli</description></item>
<item><title>The remediation SLA that holds</title><link>https://automatedvulnerabilityremediation.com/guides/the-remediation-sla-that-holds/</link><guid>https://automatedvulnerabilityremediation.com/guides/the-remediation-sla-that-holds/</guid><pubDate>Tue, 10 Nov 2026 00:00:00 GMT</pubDate><description>Rapid7's Q3 2026 report puts the average time from public disclosure to exploitation at three days, with 71% of tracked exploitation inside seven days. A 3</description></item>
<item><title>Mean time to remediate, measured honestly</title><link>https://automatedvulnerabilityremediation.com/guides/mean-time-to-remediate-measured-honestly/</link><guid>https://automatedvulnerabilityremediation.com/guides/mean-time-to-remediate-measured-honestly/</guid><pubDate>Tue, 10 Nov 2026 00:00:00 GMT</pubDate><description>Vendors cite mean time to remediate falling from 45 days to 6 (Averlon), from over two weeks to one hour (Backline) and from months to hours (Vicarius). Al</description></item>
<item><title>Vulnerability ownership at scale: grouping, routing and expiry</title><link>https://automatedvulnerabilityremediation.com/guides/vulnerability-ownership-at-scale/</link><guid>https://automatedvulnerabilityremediation.com/guides/vulnerability-ownership-at-scale/</guid><pubDate>Tue, 10 Nov 2026 00:00:00 GMT</pubDate><description>Zafran describes 700 findings collapsing into one OpenSSL upgrade ticket for the Platform team. Maze says one ticket can close 30 or more CVEs. Averlon rep</description></item>
<item><title>What to ask in a vulnerability remediation platform trial</title><link>https://automatedvulnerabilityremediation.com/guides/what-to-ask-in-a-remediation-platform-trial/</link><guid>https://automatedvulnerabilityremediation.com/guides/what-to-ask-in-a-remediation-platform-trial/</guid><pubDate>Tue, 10 Nov 2026 00:00:00 GMT</pubDate><description>A two-week trial of a vulnerability remediation platform should test seven things on your own data: exploitability evidence, the fix produced, the owner fo</description></item>
<item><title>Agentic vulnerability management, defined by what ships</title><link>https://automatedvulnerabilityremediation.com/guides/agentic-vulnerability-management-defined-by-what-ships/</link><guid>https://automatedvulnerabilityremediation.com/guides/agentic-vulnerability-management-defined-by-what-ships/</guid><pubDate>Tue, 10 Nov 2026 00:00:00 GMT</pubDate><description>Agentic vulnerability management means software agents carry a finding through steps a person used to do, and the test is what ships: a pull request, a pat</description></item>
<item><title>AI vulnerability management in the weekly remediation meeting</title><link>https://automatedvulnerabilityremediation.com/guides/ai-vulnerability-management-in-the-weekly-meeting/</link><guid>https://automatedvulnerabilityremediation.com/guides/ai-vulnerability-management-in-the-weekly-meeting/</guid><pubDate>Tue, 10 Nov 2026 00:00:00 GMT</pubDate><description>A weekly remediation meeting with agents in the loop covers five items: decisions the agents made and a person should check, items waiting for approval, ow</description></item>
</channel></rss>
