Automated vulnerability remediation: 14 platforms and what each fixes itself
What each platform fixes itself, who approves and what it reads
Show the platforms that fix by
Showing all 14 platforms, in alphabetical order.
Scroll the table sideways for more columns
| Platform | What it fixes itself | Who approves | Resolves the owner | Scanners it reads | Price |
|---|---|---|---|---|---|
| Astelia Security | Patch through a patch toolWAF or IPS mitigationPatch through a patch tool, WAF or IPS mitigation (firewall or IPS rule) | Human click in an approval queue | Yes: opens a ticket for the asset owner | Reads Tenable, Qualys, Rapid7 (named examples) | None found on 10 Nov 2026 |
Does well: Astelia derives reachability from network topology and firewall policy and proposes patches or firewall and IPS mitigations, with agent actions held in a human approval queue. Limited: Astelia's fixes are patches through patch tools and network mitigations; none found on 10 Nov 2026: tested code pull requests, named ticketing products, a published benchmark with a stated method, or pricing. | |||||
| Averlon | Pull requestConfiguration changePull request (application and infrastructure code), configuration change | Developer reviews each generated fix before merge | Yes: routes to the team that owns the code | Wiz, Tenable, Upwind, Qualys, Snyk | None found on 10 Nov 2026 |
Does well: Averlon pairs per-environment applicability, reachability and attack-chain analysis with a GitHub Actions remediation flow that opens ready-to-merge pull requests and assigns a ticket to the code owner, with a published customer result of 3,400 tickets reduced to 260 pull requests. Limited: Averlon's customer example leaves the customer unnamed and the method unstated; none found on 10 Nov 2026: a new-CVE time-to-answer, a customer agent builder, named ticketing integrations, or pricing. | |||||
| Backline Security | Tested pull requestTested pull request | Engineers stay in control of what gets merged | Yes: brings fixes to responsible people, assigns Jira tickets | Customer's existing production scanners (AWS Inspector on ECR named) | None found on 10 Nov 2026 |
Does well: Backline opens verified pull requests for SCA, container image and IaC findings and reports 86% to 95% autonomous fix rates in vendor case studies. Limited: Backline hands an issue to engineers with an explanation where no safe upgrade path exists; none found on 10 Nov 2026: customer-built agents, a dedicated zero-day lookup, pricing, or customer count. | |||||
| Cogent Security | None found on 10 Nov 2026vendor states it writes patches, acts via existing tools | Customer sets approval by action type, severity or asset | Yes: agents determine asset ownership (per SiliconANGLE) | Qualys, Rapid7, Tenable, Wiz, Snyk and others | None found on 10 Nov 2026 |
Does well: Cogent connects 200+ named security, IT and ticketing integrations to an ownership-aware agent workflow with configurable autonomy levels and approval gates, and publishes a method for its VR-1.1 repair benchmark result (57.9% of 190 LiveCVEBench tasks). Limited: Cogent's benchmark result comes from a vendor-run test with differing inference budgets across systems; none found on 10 Nov 2026: customer-built agents, pricing, headquarters, or headcount. | |||||
| Dux Security | Configuration changeConfiguration change (customer deploys the control) | None found on 10 Nov 2026 | None found on 10 Nov 2026 (auto-tags assets; routing not found) | None found on 10 Nov 2026 | None found on 10 Nov 2026 |
Does well: Dux positions around exploitability analysis and lightweight mitigations such as missing controls or config changes, with remediation limited to asset tagging and speeding up owners. Limited: Dux's remediation is limited to asset tagging and mitigations the customer deploys on its own; none found on 10 Nov 2026: generated pull requests, named integrations, named customers, pricing, or a method behind its exploitability conclusions. | |||||
| Maze | None found on 10 Nov 2026vendor states it validates fixes and suggests mitigations | Customer's team controls what gets merged | Yes: infers owner from commit history and code | Customer's existing scanners by API (none named) | None found on 10 Nov 2026 (vendor prices by cloud size) |
Does well: Maze defines exploitable as exploitable given the specific configuration, controls and context of the customer's environment, and routes validated fixes, with the investigation behind them, to the owning developer or coding agent for human review. Limited: Maze quotes pricing by cloud size without a public price list; none found on 10 Nov 2026: customer-built agents, owner follow-up or SLA tracking, a named integration list, or funding and headcount. | |||||
| Onit Security | None found on 10 Nov 2026vendor states plans and interim mitigations | Approval gate on every agent action | Yes: resolves owner from CMDB, ticketing and commit authorship | Scanners, cloud, EDR, CMDB already connected (none named) | None found on 10 Nov 2026 |
Does well: Onit documents seven named specialized agents (reachability, exploitability, context, ownership, prioritization, remediation, mitigation) feeding one approval-gated decision card, plus a Zero-Day Agent announced in October 2026. Limited: Onit's remediation text describes a plan rather than an opened pull request; none found on 10 Nov 2026: documented custom agents, a named integration list, named customer case studies, or pricing. | |||||
| Qualys | Own patch deploymentOwn patch deployment (also mitigate, uninstall, isolate hosts) | Customer sets policies and rings; ServiceNow change approval | None found on 10 Nov 2026 (CMDB and ITSM integrations only) | Own single agent; ETM consolidates other sources | None found on 10 Nov 2026 |
Does well: Qualys ships four named vendor-built agents inside Enterprise TruRisk Management, including a remediation agent that gates patch deployment on an AI reliability score and falls back to patchless mitigation and rollback. Limited: Qualys cites an unnamed customer remediation result without a published method; none found on 10 Nov 2026: customer-built agents, or per-finding owner resolution by code owner or team mapping. | |||||
| Rapid7 | None found on 10 Nov 2026vendor lists automated remediation workflows | None found on 10 Nov 2026 | None found on 10 Nov 2026 (remediation projects and SLAs, ticketing) | Own telemetry plus third-party data; 500+ integrations | None found on 10 Nov 2026 (usage-based by asset type) |
Does well: Rapid7 Exposure Command combines exploit likelihood, reachability, and business context in prioritization with automated remediation workflows and 500+ integrations, with authenticated checks published for emergent zero-days. Limited: Rapid7's remediation text does not say a tested pull request or virtual patch is produced; none found on 10 Nov 2026: agentic remediation features, per-finding owner resolution, or list prices. | |||||
| Rival Security | Tested pull requestConfiguration changeWAF or IPS mitigationTested pull request, WAF or IPS mitigation, configuration change | Team reviews the pull request | Yes: maps each finding to the team that can fix it | Wiz, Rapid7, Qualys; own SCA and Code scanners | None found on 10 Nov 2026 |
Does well: Rival ships ready-made, vendor-built and customer-built agents on one harness, and its published PHP2Shell write-up reports triaging customer repositories before scanners could detect the CVEs. Limited: Rival's own scanning shown on its site covers SCA and code only, and for everything else it works on the findings of the scanners a team already runs; none found on 10 Nov 2026: pricing, named customers, funding or headcount. | |||||
| Seemplicity | Configuration changeConfiguration change, compensating controls, ready-to-apply code fix | Each option marked deploy now or review first | Yes: assigns remediation to owners, syncs with CMDBs | Qualys, Rapid7, Tenable, Wiz, Orca, Prisma Cloud | None found on 10 Nov 2026 |
Does well: Seemplicity pairs AI Analysts that test exploitability with Response Options (compensating controls, config changes, patches) each carrying a readiness indicator, and routes work to owners via Jira, ServiceNow and similar tools. Limited: Seemplicity states its speed and savings figures without a method; none found on 10 Nov 2026: a time-to-answer measurement for a new CVE, customer-authored agents, or pricing. | |||||
| Tenable | Own patch deploymentOwn patch deployment (Patch Management); Hexa AI also creates tickets | Patch policies set autonomy; Hexa AI has human-in-the-loop approvals | None found on 10 Nov 2026 (ticketing integration only) | Connectors: Qualys, Rapid7, Wiz, CrowdStrike, Armis | None found on 10 Nov 2026 |
Does well: Tenable pairs a cross-domain exposure data model and attack path analysis with a Hexa AI agent fleet, an MCP server for customer-built agents, and a Patch Management module with guardrail policies. Limited: Tenable's pricing page lists capabilities without prices; none found on 10 Nov 2026: a feature mapping findings to an owning team, a measured new-CVE time-to-answer, or founded year and headcount. | |||||
| Vicarius | Own patch deploymentOwn patch deployment, plus in-memory exploit blocking (vShield) | AI scripts run only after a team member approves | None found on 10 Nov 2026 | Own detection; EDR, SIEM, CSPM, scanners feed in | None found on 10 Nov 2026 (annual subscription by asset count) |
Does well: Vicarius executes fixes itself (patching for 20,000+ apps, scripts, in-memory patchless protection) and holds AI-generated scripts as drafts until a person approves them. Limited: Vicarius states its false-positive and time-to-fix figures without a method; none found on 10 Nov 2026: automatic mapping of findings to owners, a named integration list, or list prices. | |||||
| Zafran | WAF or IPS mitigationTicket onlyWAF or IPS mitigation, ticket only for patches (Work Item) | None found on 10 Nov 2026 | Yes: routes fixes to the right team and owner | Tenable, Rapid7, Qualys, Wiz, Snyk, Palo Alto Networks | None found on 10 Nov 2026 |
Does well: Zafran reads live configuration of customers' EDR, WAF and firewall controls and can push a mitigation (for example a WAF rule) before a patch, with patch work routed as tickets. Limited: Zafran delivers patch remediation as a ticket work item rather than a pull request; none found on 10 Nov 2026: documented approval gates for each agent, or pricing, headquarters and customer count. | |||||
The category in 2026
Open the section
A vulnerability scanner finds flaws and writes them down. A remediation platform starts where the scanner stops: it decides which findings can be used against this environment, finds the person who owns the asset, prepares the change that closes the finding, and checks afterward that it closed. Agentic remediation means software agents do some of those steps without a person typing each one, inside limits the customer sets.
Platforms in the register differ in which steps they automate. Some open a pull request against the code repository. Some drive a patch tool, or push a firewall or web application firewall rule when no patch exists. Some stop at a ticket with the work already scoped. The register keeps these apart, because a team with a five-figure backlog and a team with a patch window every other Sunday need different things from the same word.
The register does not cover the scanner itself, the severity number attached to a finding, or the attack surface before it is scanned. It covers what happens after the scanner has produced its list, on 10 Nov 2026 and in the editions that follow. The Backlog Calculator turns your own finding count into analyst hours, so the size of the problem is stated before any platform is read.
Guides and glossary
- How to measure a vulnerability backlog in hours, not findings
- Automated vulnerability remediation: what an agent can fix without a human
- How approval should work when an agent changes production
- Ownership mapping: finding who can fix a finding
- Reading a vendor's vulnerability remediation claim
- The remediation SLA that holds
- Glossary, 32 terms
- 31 questions answered
Sources
27 sources, each with its read date
- Astelia Security: www.astelia.io/platform, read 10 Nov 2026
- Astelia Security: www.astelia.io/use-cases/identify-true-exposure, read 10 Nov 2026
- Averlon: www.averlon.ai/platform, read 10 Nov 2026
- Averlon: www.averlon.ai/, read 10 Nov 2026
- Backline Security: backline.ai/product/, read 10 Nov 2026
- Backline Security: backline.ai/case-studies/hands-off-fully-fixed/, read 10 Nov 2026
- Cogent Security: www.cogent.com/platform/assess, read 10 Nov 2026
- Cogent Security: www.cogent.com/blog/cogent-expands-its-ai-cyber-defense-factory-with-specular-ac, read 10 Nov 2026
- Dux Security: dux.io/, read 10 Nov 2026
- Maze: mazehq.com/platform/cloud, read 10 Nov 2026
- Maze: mazehq.com/, read 10 Nov 2026
- Onit Security: onit.security/platform/, read 10 Nov 2026
- Onit Security: onit.security/blog/reachable-vulnerabilities/, read 10 Nov 2026
- Qualys: www.qualys.com/apps/agentic-ai, read 10 Nov 2026
- Qualys: www.qualys.com/apps/trurisk-eliminate/, read 10 Nov 2026
- Rapid7: www.rapid7.com/products/command/exposure-management/, read 10 Nov 2026
- Rapid7: www.rapid7.com/products/command/pricing/, read 10 Nov 2026
- Rival Security: rival.security/, read 10 Nov 2026
- Rival Security: rival.security/use-cases, read 10 Nov 2026
- Seemplicity: seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/, read 10 Nov 2026
- Seemplicity: seemplicity.ai/news/live-edr-context-agentic-exposure-management/, read 10 Nov 2026
- Tenable: www.tenable.com/products/tenable-one, read 10 Nov 2026
- Tenable: www.tenable.com/products/tenable-one/capabilities/exposure-prioritization, read 10 Nov 2026
- Vicarius: www.vicarius.io/features/vrx-analysis, read 10 Nov 2026
- Vicarius: www.vicarius.io/, read 10 Nov 2026
- Zafran: www.zafran.io/, read 10 Nov 2026
- Zafran: www.zafran.io/solutions/use-cases/mitigate-risk, read 10 Nov 2026
Last reviewed 10 Nov 2026.