# Guides for clearing a vulnerability backlog

Guides, read 10 Nov 2026

**The short answer.** Eleven guides cover how to measure a backlog, what an agent can fix without a person, how approval works, ownership, reading a vendor claim, the remediation SLA, mean time to remediate, and trial questions. Each cites public sources such as CISA BOD 22-01 and NIST SP 800-40 Rev. 4, dated 10 Nov 2026.

- [How to measure a vulnerability backlog in hours, not findings](/guides/how-to-measure-a-backlog/): Measuring. 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.
- [Automated vulnerability remediation: what an agent can fix without a human](/guides/what-an-agent-can-fix-without-a-human/): Automation. 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 the work scoped.
- [How approval should work when an agent changes production](/guides/how-approval-should-work/): Control. 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.
- [Ownership mapping: finding who can fix a finding](/guides/ownership-mapping/): Ownership. Ownership mapping assigns each finding to a team that can change the asset.
- [Reading a vendor's vulnerability remediation claim](/guides/reading-a-vendors-remediation-claim/): Evidence. 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.
- [The remediation SLA that holds](/guides/the-remediation-sla-that-holds/): SLA. 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.
- [Mean time to remediate, measured honestly](/guides/mean-time-to-remediate-measured-honestly/): Metrics. 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).
- [Vulnerability ownership at scale: grouping, routing and expiry](/guides/vulnerability-ownership-at-scale/): Ownership. Zafran describes 700 findings collapsing into one OpenSSL upgrade ticket for the Platform team.
- [What to ask in a vulnerability remediation platform trial](/guides/what-to-ask-in-a-remediation-platform-trial/): Trial. A two-week trial of a vulnerability remediation platform should test seven things on your own data: exploitability evidence, the fix produced, the owner found, the speed on a new disclosure, agent limits, stack fit and the proof kept.
- [Agentic vulnerability management, defined by what ships](/guides/agentic-vulnerability-management-defined-by-what-ships/): Definition. 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 patch job, a rule, or a scoped ticket.
- [AI vulnerability management in the weekly remediation meeting](/guides/ai-vulnerability-management-in-the-weekly-meeting/): Practice. 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, owner-less findings, mitigations nearing expiry, and anything newly exploited.

## Related pages

- [How to measure a vulnerability backlog in hours, not findings](/guides/how-to-measure-a-backlog/)
- [Automated vulnerability remediation: what an agent can fix without a human](/guides/what-an-agent-can-fix-without-a-human/)
- [How approval should work when an agent changes production](/guides/how-approval-should-work/)
- [How the register works, and what it leaves out](/method/)
- [Automated vulnerability remediation: 14 platforms and what each fixes itself](/)

## Sources

- Astelia Security: www.astelia.io/platform: https://www.astelia.io/platform (read 10 Nov 2026)
- Averlon: www.averlon.ai/platform: https://www.averlon.ai/platform (read 10 Nov 2026)
- Backline Security: backline.ai/product/: https://backline.ai/product/ (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/guides/
