# Automated Vulnerability Remediation: every page as markdown
A reference that lists and does not rank. Register of 14 platforms that clear a vulnerability backlog with agents: sourced facts under seven topics, and a backlog calculator. Read 10 Nov 2026.
---
# Automated vulnerability remediation: 14 platforms and what each fixes itself
REGISTER, read 10 Nov 2026
**The short answer.** Automated vulnerability remediation is software that closes a finding itself: a tested pull request, a patch sent through a patch tool, a configuration or WAF change, or a ticket scoped for the owner. This register lists 14 platforms alphabetically with what each fixes, who approves and how it is priced, each fact sourced and read on 10 Nov 2026.
Backlog Calculator defaults: 20000 findings, 25 minutes each, 3 analysts, 30 hours a week each, 0 percent removed before analysis. Result: 20000 findings left, 8333 analyst hours, 463 working days. The [calculator page](/calculator/) states every assumption.
## What each platform fixes itself, who approves and what it reads
The register can be filtered by what each platform fixes itself: tested pull request, pull request, patch through a patch tool, own patch deployment, configuration change, waf or ips mitigation, ticket only, none found.
| Platform | What it fixes itself | Who approves | Resolves the owner | Scanners it reads | Price |
| --- | --- | --- | --- | --- | --- |
| [Astelia Security](/platforms/astelia/) | Patch 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 |
| [Averlon](/platforms/averlon/) | Pull 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 |
| [Backline Security](/platforms/backline/) | Tested 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 |
| [Cogent Security](/platforms/cogent/) | None found on 10 Nov 2026: vendor 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 |
| [Dux Security](/platforms/dux/) | Configuration 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 |
| [Maze](/platforms/maze/) | None found on 10 Nov 2026: vendor 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) |
| [Onit Security](/platforms/onit/) | None found on 10 Nov 2026: vendor 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 |
| [Qualys](/platforms/qualys/) | Own 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 |
| [Rapid7](/platforms/rapid7/) | None found on 10 Nov 2026: vendor 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) |
| [Rival Security](/platforms/rival/) | Tested 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 |
| [Seemplicity](/platforms/seemplicity/) | Configuration 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 |
| [Tenable](/platforms/tenable/) | Own 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 |
| [Vicarius](/platforms/vicarius/) | Own 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) |
| [Zafran](/platforms/zafran/) | WAF 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 |
Platforms in alphabetical order. Each cell comes from the sourced facts on the platform's profile, read on or before 10 Nov 2026; none found means the platform's pages were checked on that date and said nothing on the point.
## What each does well, and where it is limited
- **Astelia Security:** **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:** **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:** **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:** **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:** **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:** **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:** **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:** **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:** **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:** **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:** **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:** **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:** **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:** **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
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](/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/)
- [Ownership mapping: finding who can fix a finding](/guides/ownership-mapping/)
- [Reading a vendor's vulnerability remediation claim](/guides/reading-a-vendors-remediation-claim/)
- [The remediation SLA that holds](/guides/the-remediation-sla-that-holds/)
- [Glossary, 32 terms](/glossary/)
- [31 questions answered](/faq/)
## Sources
- Astelia Security: www.astelia.io/platform: https://www.astelia.io/platform (read 10 Nov 2026)
- Astelia Security: www.astelia.io/use-cases/identify-true-exposure: https://www.astelia.io/use-cases/identify-true-exposure (read 10 Nov 2026)
- Averlon: www.averlon.ai/platform: https://www.averlon.ai/platform (read 10 Nov 2026)
- Averlon: www.averlon.ai/: https://www.averlon.ai/ (read 10 Nov 2026)
- Backline Security: backline.ai/product/: https://backline.ai/product/ (read 10 Nov 2026)
- Backline Security: backline.ai/case-studies/hands-off-fully-fixed/: https://backline.ai/case-studies/hands-off-fully-fixed/ (read 10 Nov 2026)
- Cogent Security: www.cogent.com/platform/assess: https://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: https://www.cogent.com/blog/cogent-expands-its-ai-cyber-defense-factory-with-specular-acquisition (read 10 Nov 2026)
- Dux Security: dux.io/: https://dux.io/ (read 10 Nov 2026)
- Maze: mazehq.com/platform/cloud: https://mazehq.com/platform/cloud (read 10 Nov 2026)
- Maze: mazehq.com/: https://mazehq.com/ (read 10 Nov 2026)
- Onit Security: onit.security/platform/: https://onit.security/platform/ (read 10 Nov 2026)
- Onit Security: onit.security/blog/reachable-vulnerabilities/: https://onit.security/blog/reachable-vulnerabilities/ (read 10 Nov 2026)
- Qualys: www.qualys.com/apps/agentic-ai: https://www.qualys.com/apps/agentic-ai (read 10 Nov 2026)
- Qualys: www.qualys.com/apps/trurisk-eliminate/: https://www.qualys.com/apps/trurisk-eliminate/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/products/command/exposure-management/: https://www.rapid7.com/products/command/exposure-management/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/products/command/pricing/: https://www.rapid7.com/products/command/pricing/ (read 10 Nov 2026)
- Rival Security: rival.security/: https://rival.security/ (read 10 Nov 2026)
- Rival Security: rival.security/use-cases: https://rival.security/use-cases (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/: https://seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/news/live-edr-context-agentic-exposure-management/: https://seemplicity.ai/news/live-edr-context-agentic-exposure-management/ (read 10 Nov 2026)
- Tenable: www.tenable.com/products/tenable-one: https://www.tenable.com/products/tenable-one (read 10 Nov 2026)
- Tenable: www.tenable.com/products/tenable-one/capabilities/exposure-prioritization: https://www.tenable.com/products/tenable-one/capabilities/exposure-prioritization (read 10 Nov 2026)
- Vicarius: www.vicarius.io/features/vrx-analysis: https://www.vicarius.io/features/vrx-analysis (read 10 Nov 2026)
- Vicarius: www.vicarius.io/: https://www.vicarius.io/ (read 10 Nov 2026)
- Zafran: www.zafran.io/: https://www.zafran.io/ (read 10 Nov 2026)
- Zafran: www.zafran.io/solutions/use-cases/mitigate-risk: https://www.zafran.io/solutions/use-cases/mitigate-risk (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/
---
# How the register works, and what it leaves out
Method, read 10 Nov 2026
**The short answer.** The Remediation Register lists 14 platforms in alphabetical order and does not weight them or order them by merit. Each fact sits under one of seven topics, carries a source URL and a read date of 10 Nov 2026, and is labelled the vendor's claim, a third-party source, or none found on that date.
The site lists platforms and does not order them by merit. No number rates a platform anywhere in it, and no page names a pick. Vendors appear in alphabetical order on every page that names more than one. Every platform has the same fields in the same order: what it proves about exploitability, how it ships a fix, how it finds an owner, how fast it answers a new disclosure, what agents you can shape, what stack it works on, and what proof it publishes.
A fact enters the register only from a page the editor opened. The entry records the page URL, the date it was read, and a short quotation. A statement on the vendor's own site is labelled the vendor's claim. A statement from press or another outside party is labelled third-party source. Where a page was read and the thing was not there, the entry says none found on that date, with the date. That is a statement about the pages read, not about the product.
## This site lists and does not rank
Automated Vulnerability Remediation lists and does not rank. The register gives each of the 14 platforms the same five buyer columns and the same seven topics, sorted by name, and no column adds up to a total or a pick.
## How facts are sourced and labelled
A platform's line in the register holds what it claims, who said it, where it was read and when. Vendor's claim marks a platform describing itself, for example a pull request rate on its own blog. Third-party source marks an analyst, a news outlet or a customer case not hosted by the vendor. None found on a date marks a page searched on that day where the point was absent.
- The read date sits beside every source link on the profile and again in the Sources list under it.
- First edition pages were read by 10 Nov 2026; the news added on 19 Nov 2026 carries its own read date.
- A wrong line is fixed on the profile and logged with its date on the [corrections page](/corrections/).
## Facts read per platform
The counts below are the fact lines recorded for each platform, split by label. They show how much was published and read, not how good a platform is.
| Platform | What it is | Facts read | Third-party facts | Vendor claims | None-found lines |
| --- | --- | --- | --- | --- | --- |
| [Astelia Security](/platforms/astelia/) | AI-native exposure management with reachability analysis and agentic remediation | 41 | 1 | 35 | 5 |
| [Averlon](/platforms/averlon/) | Agentic remediation (exposure/attack-chain analysis with fixes delivered into developer workflows) | 40 | 0 | 36 | 4 |
| [Backline Security](/platforms/backline/) | Agentic remediation (Autonomous Exposure Remediation) | 44 | 3 | 38 | 3 |
| [Cogent Security](/platforms/cogent/) | Agentic vulnerability management and remediation (AI agents across the full vulnerability lifecycle) | 40 | 10 | 28 | 2 |
| [Dux Security](/platforms/dux/) | Agentic exposure management (exploitability analysis, mitigation, remediation acceleration) | 28 | 0 | 20 | 8 |
| [Maze](/platforms/maze/) | Agentic vulnerability investigation and remediation (code and cloud) | 37 | 0 | 33 | 4 |
| [Onit Security](/platforms/onit/) | Agentic exposure management / remediation (decision-based) | 37 | 1 | 32 | 4 |
| [Qualys](/platforms/qualys/) | Exposure/RBVM platform with remediation and agentic AI | 37 | 0 | 36 | 1 |
| [Rapid7](/platforms/rapid7/) | Exposure/RBVM platform with remediation workflows | 31 | 0 | 28 | 3 |
| [Rival Security](/platforms/rival/) | Agentic security platform / agent harness for vulnerability management, code and cloud security | 40 | 0 | 35 | 5 |
| [Seemplicity](/platforms/seemplicity/) | Agentic exposure management and response (RBVM/CTEM workflow with AI analysts) | 41 | 0 | 38 | 3 |
| [Tenable](/platforms/tenable/) | Exposure management platform with remediation and agentic orchestration | 39 | 1 | 35 | 3 |
| [Vicarius](/platforms/vicarius/) | Remediation-first exposure platform (patching, scripting, patchless protection) | 38 | 0 | 36 | 2 |
| [Zafran](/platforms/zafran/) | Exposure management platform with mitigation via existing controls (agentic features) | 38 | 0 | 36 | 2 |
Platforms in alphabetical order. Counts are the fact lines read for each platform up to 10 Nov 2026; the labels are explained on the Method page.
## Order rules
- Vendors are listed alphabetically by display name, ignoring case. No vendor is placed first by design, and no page orders vendors by merit.
- Every vendor has the same fields in the same order: what it is, what it does well, where it is limited, then the facts under the seven topics, then profile facts.
- The two vendors of a side-by-side page are ordered alphabetically too, in the address and in the title, and the list of pairs is alphabetical.
- News items are listed by date, newest first.
- Glossary terms are listed alphabetically.
## The seven topics
Facts are grouped under seven topics. They are headings for reading, not measures, and no topic carries a weight.
- Proves exploitability in your environment: whether the product shows that a finding is reachable and exploitable in the customer's own cloud, code and controls, with the evidence.
- Ships the fix: whether the product produces the fix itself (a tested pull request, a configuration change, a mitigation) with a human approving, or stops at a ticket.
- Finds the owner: whether it resolves each finding to the team that can fix it, and follows up.
- Speed on a new disclosure: how fast it answers where a new CVE hits the customer after a public disclosure, as documented.
- Agents you can shape: ready-made agents, agents the vendor builds for the customer and agents the customer builds, with the controls on each.
- Works on the stack you have: which scanners, cloud, code hosts and ticketing systems it reads.
- Proof: published results with a method, named customers and research.
Facts are dated. A fact read on 10 Nov 2026 describes the page on that day. Vendors change their sites, so every entry shows when it was read, and the register is reissued as pages are read again.
Corrections are made on the page and listed with their date on the corrections page. A vendor or a reader who finds a fact that no longer matches its source can write to editor@automatedvulnerabilityremediation.com with the URL and the line.
Customer results, benchmark figures and speed claims are reproduced as the vendor states them, with their method where the vendor gives one. A figure published without a method is marked as such. The register does not add its own measurement to a vendor's number.
The seven topics are fixed: proves exploitability in your environment, ships the fix, finds the owner, speed on a new disclosure, agents you can shape, works on the stack you have, proof. The two guides on reading a claim and on the trial questions show how to test each topic yourself.
## Read dates and refresh
Platform pages change faster than the register: pricing pages appear, agents are renamed. Each profile is re-read at least every 90 days, and the register edition on the datasets page moves with it.
## Related pages
- [The Backlog Calculator](/calculator/)
- [Guides](/guides/)
- [Glossary](/glossary/)
- [31 questions answered](/faq/)
## 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)
- Cogent Security: www.cogent.com/platform/assess: https://www.cogent.com/platform/assess (read 10 Nov 2026)
- Dux Security: dux.io/: https://dux.io/ (read 10 Nov 2026)
- Maze: mazehq.com/platform/cloud: https://mazehq.com/platform/cloud (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/method/
---
# The 14 platforms, listed alphabetically
Platforms, read 10 Nov 2026
**The short answer.** The register lists 14 platforms in alphabetical order, from Astelia to Zafran. Each profile uses the same seven topics in the same order, with every fact tied to a source URL and a read date of 10 Nov 2026. Entries are labelled the vendor's claim, a third-party source, or none found.
| Platform | What it is | Facts read |
| --- | --- | --- |
| [Astelia Security](/platforms/astelia/) | AI-native exposure management with reachability analysis and agentic remediation | 41 |
| [Averlon](/platforms/averlon/) | Agentic remediation (exposure/attack-chain analysis with fixes delivered into developer workflows) | 40 |
| [Backline Security](/platforms/backline/) | Agentic remediation (Autonomous Exposure Remediation) | 44 |
| [Cogent Security](/platforms/cogent/) | Agentic vulnerability management and remediation (AI agents across the full vulnerability lifecycle) | 40 |
| [Dux Security](/platforms/dux/) | Agentic exposure management (exploitability analysis, mitigation, remediation acceleration) | 28 |
| [Maze](/platforms/maze/) | Agentic vulnerability investigation and remediation (code and cloud) | 37 |
| [Onit Security](/platforms/onit/) | Agentic exposure management / remediation (decision-based) | 37 |
| [Qualys](/platforms/qualys/) | Exposure/RBVM platform with remediation and agentic AI | 37 |
| [Rapid7](/platforms/rapid7/) | Exposure/RBVM platform with remediation workflows | 31 |
| [Rival Security](/platforms/rival/) | Agentic security platform / agent harness for vulnerability management, code and cloud security | 40 |
| [Seemplicity](/platforms/seemplicity/) | Agentic exposure management and response (RBVM/CTEM workflow with AI analysts) | 41 |
| [Tenable](/platforms/tenable/) | Exposure management platform with remediation and agentic orchestration | 39 |
| [Vicarius](/platforms/vicarius/) | Remediation-first exposure platform (patching, scripting, patchless protection) | 38 |
| [Zafran](/platforms/zafran/) | Exposure management platform with mitigation via existing controls (agentic features) | 38 |
Alphabetical by name. The count is every fact line read for the platform, with any label.
## Related pages
- [Astelia Security: what it is, what it does well and where it is limited](/platforms/astelia/)
- [Averlon: what it is, what it does well and where it is limited](/platforms/averlon/)
- [Backline Security: what it is, what it does well and where it is limited](/platforms/backline/)
- [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)
- Cogent Security: www.cogent.com/platform/assess: https://www.cogent.com/platform/assess (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/platforms/
---
# Astelia Security: what it is, what it does well and where it is limited
Platform profile, read 10 Nov 2026
**The short answer.** Astelia Security sells AI-native exposure management with reachability analysis and agentic remediation, as its pages read on 10 Nov 2026 describe it. 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. Every line below carries its source and the date it was read.
## What it is
AI-native exposure management with reachability analysis and agentic remediation.
## What it 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.
## Where it is 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.
## Facts read, by topic
Each line below carries a label, the page it was read on and the date. A vendor's claim is the vendor's own statement about itself; a third-party source is one that is not the vendor; a line that starts with none found says nothing was published on that date. Astelia Security has 41 lines on file, read up to 10 Nov 2026; the Astelia Security pages behind them are listed under Sources.
### Proves exploitability in your environment
- Vendor's claim: Platform maps network topology and uses agentic AI to analyze exploit requirements per vulnerability. ([source](https://www.astelia.io/platform), read 10 Nov 2026)
- Vendor's claim: Reachability classification correlates topology, asset context and runtime data. ([source](https://www.astelia.io/platform), read 10 Nov 2026)
- Vendor's claim: Every finding, including deprioritized ones, carries evidence of exposure or its absence. ([source](https://www.astelia.io/use-cases/identify-true-exposure), read 10 Nov 2026)
- Vendor's claim: Vendor claim from funding release: in some deployments about 30 of nearly 3 million vulnerabilities were genuinely exploitable. ([source](https://www.astelia.io/newsroom/astelia-raises-35m-to-turn-exposure-management-from-guesswork-into-ai-powered-precision), read 10 Nov 2026)
- Vendor's claim: Attack path visualization to critical assets through network controls and open ports. ([source](https://www.astelia.io/platform), read 10 Nov 2026)
### Ships the fix
- Vendor's claim: Remediation includes non-patch routes when patching is not an option. ([source](https://www.astelia.io/use-cases/streamline-remediation), read 10 Nov 2026)
- Vendor's claim: Agents pick the fastest fix (patch, firewall or IPS rule) and implement it via the existing stack with a human in the loop. ([source](https://www.astelia.io/use-cases/deploy-astelia-agents), read 10 Nov 2026)
- Vendor's claim: Example workflow: drafted ticket and firewall rule wait in an approval queue for a human click. ([source](https://www.astelia.io/post/closing-the-exposure-loop), read 10 Nov 2026)
- Vendor's claim: Where a patch exists the workflow drives it through the patch management tool. ([source](https://www.astelia.io/post/closing-the-exposure-loop), read 10 Nov 2026)
- Vendor's claim: Verified remediation: confirms when attack paths are blocked. ([source](https://www.astelia.io/use-cases/streamline-remediation), read 10 Nov 2026)
- None found on 10 Nov 2026: Tested code pull requests for application vulnerabilities; fixes described are patches via patch tools and network mitigations. ([source](https://www.astelia.io/use-cases/streamline-remediation), read 10 Nov 2026)
### Finds the owner
- Vendor's claim: Example workflow opens a ticket for the asset owner and proposes an interim network mitigation. ([source](https://www.astelia.io/post/closing-the-exposure-loop), read 10 Nov 2026)
- Vendor's claim: Agents cover routing ownership and driving remediation. ([source](https://www.astelia.io/ai-info-page), read 10 Nov 2026)
- Vendor's claim: Investigator agent coordinates next steps across the tech stack. ([source](https://www.astelia.io/use-cases/deploy-astelia-agents), read 10 Nov 2026)
### Speed on a new disclosure
- Vendor's claim: Hunter agent checks new and zero-day vulnerabilities against the SBOM before scanners detect them. ([source](https://www.astelia.io/use-cases/deploy-astelia-agents), read 10 Nov 2026)
- Vendor's claim: Zero-day and new-CVE detection matches against software inventory before the next scanner cycle. ([source](https://www.astelia.io/ai-info-page), read 10 Nov 2026)
- Vendor's claim: Workflows trigger automatically on each new advisory. ([source](https://www.astelia.io/post/closing-the-exposure-loop), read 10 Nov 2026)
- None found on 10 Nov 2026: A numeric time-to-answer claim or a published response write-up for a named CVE. ([source](https://www.astelia.io/use-cases/deploy-astelia-agents), read 10 Nov 2026)
### Agents you can shape
- Vendor's claim: Three named vendor-built agents: Hunter (zero-day detection), Investigator (triage), Fixer (remediation). ([source](https://www.astelia.io/use-cases/deploy-astelia-agents), read 10 Nov 2026)
- Vendor's claim: Customers write a workflow spec in natural language and a Planner agent builds it. ([source](https://www.astelia.io/post/closing-the-exposure-loop), read 10 Nov 2026)
- Vendor's claim: Marketplace of ready-made agents and skills. ([source](https://www.astelia.io/post/closing-the-exposure-loop), read 10 Nov 2026)
- Vendor's claim: Controls: approval queues, role-based access control, audit and execution logs. ([source](https://www.astelia.io/ai-info-page), read 10 Nov 2026)
- Vendor's claim: Fine-grained tool scopes and human-in-the-loop checkpoints are stated design principles. ([source](https://www.astelia.io/post/closing-the-exposure-loop), read 10 Nov 2026)
- Vendor's claim: Astelia MCP exposes reachability data to customers' own AI assistants. ([source](https://www.astelia.io/post/closing-the-exposure-loop), read 10 Nov 2026)
### Works on the stack you have
- Vendor's claim: Named firewalls and scanners read through read-only integrations. ([source](https://www.astelia.io/ai-info-page), read 10 Nov 2026)
- Vendor's claim: Threat intel sources: CISA KEV, NVD, advisories, public PoCs and EPSS. ([source](https://www.astelia.io/ai-info-page), read 10 Nov 2026)
- Vendor's claim: Agents connect through 100+ MCP integrations to ticketing, CMDB, patch management and communication tools. ([source](https://www.astelia.io/ai-info-page), read 10 Nov 2026)
- Vendor's claim: Sits above scanners the customer already runs. ([source](https://www.astelia.io/ai-info-page), read 10 Nov 2026)
- None found on 10 Nov 2026: Named ticketing products (Jira, ServiceNow) or named public cloud providers on the platform, use-case or ai-info pages. ([source](https://www.astelia.io/platform), read 10 Nov 2026)
### Proof
- Vendor's claim: Named customer quote: Justin Dellaportas, CISO at Syniverse. ([source](https://www.astelia.io/platform), read 10 Nov 2026)
- Vendor's claim: Named customer quotes also from AlphaSense and Bilfinger CISOs. ([source](https://www.astelia.io/platform), read 10 Nov 2026)
- Vendor's claim: Funding release states dozens of customers including Fortune 500 companies. ([source](https://www.astelia.io/newsroom/astelia-raises-35m-to-turn-exposure-management-from-guesswork-into-ai-powered-precision), read 10 Nov 2026)
- Vendor's claim: Newsroom lists Fortune Cyber 60 (2026-2027) and Fast Company Next Big Things in Tech recognition. ([source](https://www.astelia.io/newsroom), read 10 Nov 2026)
- None found on 10 Nov 2026: Published benchmark or results with a stated method. ([source](https://www.astelia.io/newsroom), read 10 Nov 2026)
## Profile facts
- Vendor's claim: Funding: $35M combined seed and Series A led by Index Ventures and Team8, Feb 24, 2026. ([source](https://www.astelia.io/newsroom/astelia-raises-35m-to-turn-exposure-management-from-guesswork-into-ai-powered-precision), read 10 Nov 2026)
- Third-party source: SecurityWeek confirms $35 million seed and Series A led by Index Ventures and Team8 (Feb 25, 2026). ([source](https://www.securityweek.com/astelia-raises-35-million-for-exposure-management/), read 10 Nov 2026)
- Vendor's claim: Founded 2024 by former Israeli National Red Team members (SecurityWeek text says 2014, likely a typo). ([source](https://www.astelia.io/ai-info-page), read 10 Nov 2026)
- Vendor's claim: HQ: New York, NY. ([source](https://www.astelia.io/about), read 10 Nov 2026)
- Vendor's claim: Founders: Alon Noy (CEO), Nadav Ostrovsky (CTO), Roy Rajwan (CPO). ([source](https://www.astelia.io/about), read 10 Nov 2026)
- Vendor's claim: Category: AI-native exposure management for large enterprises with on-prem, hybrid and cloud networks. ([source](https://www.astelia.io/ai-info-page), read 10 Nov 2026)
- None found on 10 Nov 2026: Pricing, headcount, module count (careers page lists no roles). ([source](https://www.astelia.io/careers), read 10 Nov 2026)
## Links
- [Side by side](/compare/): Pairs of platforms, with the sourced facts in the same rows.
- [Astelia Security on its own site](https://www.astelia.io/)
## Related pages
- [The 14 platforms, listed alphabetically](/platforms/)
- [Averlon: what it is, what it does well and where it is limited](/platforms/averlon/)
- [Zafran: what it is, what it does well and where it is limited](/platforms/zafran/)
- [Backline Security: what it is, what it does well and where it is limited](/platforms/backline/)
## Sources
- Astelia Security: www.astelia.io/platform: https://www.astelia.io/platform (read 10 Nov 2026)
- Astelia Security: www.astelia.io/use-cases/identify-true-exposure: https://www.astelia.io/use-cases/identify-true-exposure (read 10 Nov 2026)
- Astelia Security: www.astelia.io/newsroom/astelia-raises-35m-to-turn-exposure-management-from-gues: https://www.astelia.io/newsroom/astelia-raises-35m-to-turn-exposure-management-from-guesswork-into-ai-powered-precision (read 10 Nov 2026)
- Astelia Security: www.astelia.io/use-cases/streamline-remediation: https://www.astelia.io/use-cases/streamline-remediation (read 10 Nov 2026)
- Astelia Security: www.astelia.io/use-cases/deploy-astelia-agents: https://www.astelia.io/use-cases/deploy-astelia-agents (read 10 Nov 2026)
- Astelia Security: www.astelia.io/post/closing-the-exposure-loop: https://www.astelia.io/post/closing-the-exposure-loop (read 10 Nov 2026)
- Astelia Security: www.astelia.io/ai-info-page: https://www.astelia.io/ai-info-page (read 10 Nov 2026)
- Astelia Security: www.astelia.io/newsroom: https://www.astelia.io/newsroom (read 10 Nov 2026)
- securityweek.com: /astelia-raises-35-million-for-exposure-management/: https://www.securityweek.com/astelia-raises-35-million-for-exposure-management/ (read 10 Nov 2026)
- Astelia Security: www.astelia.io/about: https://www.astelia.io/about (read 10 Nov 2026)
- Astelia Security: www.astelia.io/careers: https://www.astelia.io/careers (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/platforms/astelia/
---
# Averlon: what it is, what it does well and where it is limited
Platform profile, read 10 Nov 2026
**The short answer.** Averlon sells agentic remediation (exposure/attack-chain analysis with fixes delivered into developer workflows), as its pages read on 10 Nov 2026 describe it. 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.
## What it is
Agentic remediation (exposure/attack-chain analysis with fixes delivered into developer workflows).
## What it 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.
## Where it is 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.
## Facts read, by topic
Each line below carries a label, the page it was read on and the date. A vendor's claim is the vendor's own statement about itself; a third-party source is one that is not the vendor; a line that starts with none found says nothing was published on that date. Averlon has 40 lines on file, read up to 10 Nov 2026; the Averlon pages behind them are listed under Sources.
### Proves exploitability in your environment
- Vendor's claim: Averlon says it checks applicability against the customer's own environment and tests reachability across network configuration, IAM policies and Kubernetes RBAC. ([source](https://www.averlon.ai/platform), read 10 Nov 2026)
- Vendor's claim: Attack chains are mapped to MITRE ATT&CK, with blast radius, and fixes that break the most chains are placed first. ([source](https://www.averlon.ai/platform), read 10 Nov 2026)
- Vendor's claim: The homepage demo shows per-finding evidence fields (network exploitability, external exposure, known exploits, access to critical data, attack-chain membership) behind each triage decision. ([source](https://www.averlon.ai/), read 10 Nov 2026)
- Vendor's claim: Averlon lists compensating-control assessment as a capability, to find controls already limiting risk. ([source](https://www.averlon.ai/why-averlon), read 10 Nov 2026)
### Ships the fix
- Vendor's claim: Averlon says it delivers context-aware fixes inside IDEs, source control and CLI, and applies the same reasoning before merge. ([source](https://www.averlon.ai/), read 10 Nov 2026)
- Vendor's claim: Its GitHub Actions generate ready-to-merge pull requests for application and infrastructure issues. ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
- Vendor's claim: Fix actions cover container images, Terraform and Pulumi IaC, and Kubernetes Helm charts. ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
- Vendor's claim: The vendor's example flow expects a human developer to review each generated fix (about 15 minutes per fix in its example). ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
- Vendor's claim: Where patching is not the route, Averlon lists risk mitigation by adjusting compensating controls or applying tailored remediation. ([source](https://www.averlon.ai/why-averlon), read 10 Nov 2026)
- Vendor's claim: Precog evaluates proposed changes in CI (for example GitHub) and delivers the fix to the developer alongside the alert. ([source](https://www.averlon.ai/platform), read 10 Nov 2026)
### Finds the owner
- Vendor's claim: Averlon traces a base-image vulnerability to the Dockerfile and routes it to the team that owns it. ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
- Vendor's claim: For each fix group it creates a pull request plus a ticket for that PR assigned to the developer who owns the code. ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
- Vendor's claim: In the vendor's customer example, issues were mapped to their source (base image or dependency) and grouped, instead of being assigned individually. ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
### Speed on a new disclosure
- Vendor's claim: A customer quote on the vendor site credits Averlon with saving time in 0-day incident response for the libWebp vulnerability. ([source](https://www.averlon.ai/), read 10 Nov 2026)
- Vendor's claim: Averlon published a response write-up dated Nov 2, 2026 on CVE-2026-98432, about 18 days after the CVE was published on October 15, 2026, covering which network paths expose a host. ([source](https://www.averlon.ai/blog/cve-2026-98432-linux-kernel-tcp-use-after-free), read 10 Nov 2026)
- Vendor's claim: It also published an explainer for React2Shell (CVE-2025-55182) on Dec 4, 2025, updated as new CVEs followed. ([source](https://www.averlon.ai/blog/react2shell-cve-2025-55182-explained), read 10 Nov 2026)
- Vendor's claim: Averlon runs a vulnerability intelligence site (research.averlon.ai); its page content was not readable in a plain fetch beyond the title. ([source](https://research.averlon.ai/vulnerability-intelligence), read 10 Nov 2026)
- None found on 10 Nov 2026: A stated time-to-answer for a new CVE (minutes or hours figure) on home, platform or why-averlon pages ([source](https://www.averlon.ai/), read 10 Nov 2026)
### Agents you can shape
- Vendor's claim: The platform lists Mitigation Agents and Remediation Agents as ready-made components. ([source](https://www.averlon.ai/platform), read 10 Nov 2026)
- Vendor's claim: The homepage demo shows a 'Remediation Agent' proposing a pull request that waits for merge, and 'Autonomous AI Triage' on each finding. ([source](https://www.averlon.ai/), read 10 Nov 2026)
- Vendor's claim: Guardrail described: fixes arrive as pull requests that pass checks and are reviewed by developers before merge. ([source](https://www.averlon.ai/), read 10 Nov 2026)
- Vendor's claim: Averlon also runs Cynos, a separate inference platform giving API access to models from several providers (not described as a customer agent builder). ([source](https://www.averlon.ai/), read 10 Nov 2026)
- None found on 10 Nov 2026: An agent builder or customer-built agent feature on averlon.ai platform pages ([source](https://www.averlon.ai/platform), read 10 Nov 2026)
### Works on the stack you have
- Vendor's claim: Averlon integrates with scanners including Wiz, Tenable, Upwind, Qualys and Snyk. ([source](https://www.averlon.ai/platform), read 10 Nov 2026)
- Vendor's claim: It ingests findings from posture, identity, runtime, vulnerability scanners and code. ([source](https://www.averlon.ai/platform), read 10 Nov 2026)
- Vendor's claim: A Wiz integration post describes Wiz supplying risk context while Averlon does triage and remediation. ([source](https://www.averlon.ai/blog/averlon-and-wiz-accelerate-remediation-and-reduce-exposure), read 10 Nov 2026)
- Vendor's claim: Remediation actions are published on the GitHub Marketplace; Terraform, Pulumi and Helm are read. ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
- None found on 10 Nov 2026: Named ticketing integrations (Jira, ServiceNow); the blog says tickets are auto-assigned but does not name the system ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
### Proof
- Vendor's claim: A vendor-published customer example: 110,000 critical and high issues, 3,400 tickets, became 260 pull requests; MTTR fell from 45 days to 6 days (customer unnamed). ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
- Vendor's claim: The same example reports mean time to remediate down from 45 days to 6 days. ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
- Vendor's claim: The Why Averlon page shows a noise-reduction example (140K issues on 28K assets reduced to 6,924 critical issues on 310 assets); customer unnamed, method not stated on the page. ([source](https://www.averlon.ai/why-averlon), read 10 Nov 2026)
- Vendor's claim: Homepage headline metrics (90% faster remediation, 95% fewer false positives) are stated without a method on the page. ([source](https://www.averlon.ai/), read 10 Nov 2026)
- Vendor's claim: Named CISO testimonials appear (for example Scott Roberts, CISO) but company names are mostly withheld. ([source](https://www.averlon.ai/), read 10 Nov 2026)
- Vendor's claim: Published research content includes a whitepaper on development-environment attacks (Oct 2025 to Apr 2026). ([source](https://www.averlon.ai/), read 10 Nov 2026)
## Profile facts
- Vendor's claim: Averlon came out of stealth May 23, 2024 with $8M led by Voyager Capital (Salesforce Ventures, Outpost Ventures), for $10.5M total funding. ([source](https://www.averlon.ai/blog/averlon-comes-out-of-stealth-mode-with-10m-in-funding-to-advance-ai-powered-cloud-security), read 10 Nov 2026)
- Vendor's claim: The investment was led by Voyager Capital with Salesforce Ventures and Outpost Ventures. ([source](https://www.averlon.ai/blog/averlon-comes-out-of-stealth-mode-with-10m-in-funding-to-advance-ai-powered-cloud-security), read 10 Nov 2026)
- Vendor's claim: Founded in 2022 by Sunil Gottumukkala (CEO) and Vishal Agarwal (CTO). ([source](https://www.averlon.ai/blog/averlon-comes-out-of-stealth-mode-with-10m-in-funding-to-advance-ai-powered-cloud-security), read 10 Nov 2026)
- Vendor's claim: Product names: Averlon Agentic Remediation Operations platform, Precog (pre-merge), Cynos (inference platform). ([source](https://www.averlon.ai/), read 10 Nov 2026)
- Vendor's claim: Platform spans VM, CSPM, KSPM, CIEM, CWPP, ASPM and DSPM capability labels. ([source](https://www.averlon.ai/platform), read 10 Nov 2026)
- None found on 10 Nov 2026: Pricing, headcount, HQ and customer count on home, about, platform, why-averlon ([source](https://www.averlon.ai/about), read 10 Nov 2026)
## Links
- [Side by side](/compare/): Pairs of platforms, with the sourced facts in the same rows.
- [Averlon on its own site](https://www.averlon.ai/)
## Related pages
- [The 14 platforms, listed alphabetically](/platforms/)
- [Backline Security: what it is, what it does well and where it is limited](/platforms/backline/)
- [Astelia Security: what it is, what it does well and where it is limited](/platforms/astelia/)
- [Cogent Security: what it is, what it does well and where it is limited](/platforms/cogent/)
## Sources
- Averlon: www.averlon.ai/platform: https://www.averlon.ai/platform (read 10 Nov 2026)
- Averlon: www.averlon.ai/: https://www.averlon.ai/ (read 10 Nov 2026)
- Averlon: www.averlon.ai/why-averlon: https://www.averlon.ai/why-averlon (read 10 Nov 2026)
- Averlon: www.averlon.ai/blog/automating-remediation-application-infrastructure-security-i: https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues (read 10 Nov 2026)
- Averlon: www.averlon.ai/blog/cve-2026-98432-linux-kernel-tcp-use-after-free: https://www.averlon.ai/blog/cve-2026-98432-linux-kernel-tcp-use-after-free (read 10 Nov 2026)
- Averlon: www.averlon.ai/blog/react2shell-cve-2025-55182-explained: https://www.averlon.ai/blog/react2shell-cve-2025-55182-explained (read 10 Nov 2026)
- Averlon: research.averlon.ai/vulnerability-intelligence: https://research.averlon.ai/vulnerability-intelligence (read 10 Nov 2026)
- Averlon: www.averlon.ai/blog/averlon-and-wiz-accelerate-remediation-and-reduce-exposure: https://www.averlon.ai/blog/averlon-and-wiz-accelerate-remediation-and-reduce-exposure (read 10 Nov 2026)
- Averlon: www.averlon.ai/blog/averlon-comes-out-of-stealth-mode-with-10m-in-funding-to-adv: https://www.averlon.ai/blog/averlon-comes-out-of-stealth-mode-with-10m-in-funding-to-advance-ai-powered-cloud-security (read 10 Nov 2026)
- Averlon: www.averlon.ai/about: https://www.averlon.ai/about (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/platforms/averlon/
---
# Backline Security: what it is, what it does well and where it is limited
Platform profile, read 10 Nov 2026
**The short answer.** Backline Security sells agentic remediation (Autonomous Exposure Remediation), as its pages read on 10 Nov 2026 describe it. Backline opens verified pull requests for SCA, container image and IaC findings and reports 86% to 95% autonomous fix rates in vendor case studies. Every line below carries its source and the date it was read.
## What it is
Agentic remediation (Autonomous Exposure Remediation).
## What it 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.
## Where it is 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.
## Facts read, by topic
Each line below carries a label, the page it was read on and the date. A vendor's claim is the vendor's own statement about itself; a third-party source is one that is not the vendor; a line that starts with none found says nothing was published on that date. Backline Security has 44 lines on file, read up to 10 Nov 2026; the Backline Security pages behind them are listed under Sources.
### Proves exploitability in your environment
- Vendor's claim: Product FAQ says agents analyze actual exploitability in the customer runtime environment. ([source](https://backline.ai/product/), read 10 Nov 2026)
- Vendor's claim: Agents check code reachability and cloud configuration to separate active threats from dormant packages. ([source](https://backline.ai/product/), read 10 Nov 2026)
- Vendor's claim: Telecom case study: exploitability and reachability analysis per vulnerability in under two minutes. ([source](https://backline.ai/case-studies/hands-off-fully-fixed/), read 10 Nov 2026)
- Vendor's claim: Data-analytics case study: reachability, exploitability and fixability analysis layered over existing tools. ([source](https://backline.ai/case-studies/five-weeks-to-under-a-day/), read 10 Nov 2026)
- Vendor's claim: HTTP2Shell write-up: reachability traced per service, unreachable findings dismissed under the customer remediation policy. ([source](https://backline.ai/blog/http2shell-three-images-one-cve/), read 10 Nov 2026)
### Ships the fix
- Vendor's claim: Backline generates, tests and delivers production-ready fixes rather than tickets. ([source](https://backline.ai/), read 10 Nov 2026)
- Vendor's claim: Each remediation includes a plan and a ready-to-review PR linked to the originating findings. ([source](https://backline.ai/product/), read 10 Nov 2026)
- Vendor's claim: Fix types covered: SCA dependency, container image CVEs and IaC misconfigurations. ([source](https://backline.ai/product/), read 10 Nov 2026)
- Vendor's claim: Validation before delivery: existing unit tests and dependency checks are run before a fix is proposed. ([source](https://backline.ai/product/), read 10 Nov 2026)
- Vendor's claim: Human control: fixes ship as standard pull requests, so rollback uses existing Git workflows; engineers stay in control of merges. ([source](https://backline.ai/product/), read 10 Nov 2026)
- Vendor's claim: Where no safe upgrade path exists, the platform flags the issue and hands it to engineers with an explanation. ([source](https://backline.ai/product/), read 10 Nov 2026)
- Vendor's claim: Fixaition page shows a cloud config fix example (security group rule) in addition to package and base image fixes. ([source](https://backline.ai/fixaition/), read 10 Nov 2026)
### Finds the owner
- Vendor's claim: Owner post: Backline brings each remediation to the responsible people in Slack, Microsoft Teams and Jira and stays in the conversation until the finding is gone. ([source](https://backline.ai/blog/finding-and-chasing-the-owner-of-a-fix-in-jira-teams-or-slack/), read 10 Nov 2026)
- Vendor's claim: It follows up and escalates when nothing moves. ([source](https://backline.ai/blog/finding-and-chasing-the-owner-of-a-fix-in-jira-teams-or-slack/), read 10 Nov 2026)
- Vendor's claim: In Jira it opens and maintains a ticket in the team's own project. ([source](https://backline.ai/blog/finding-and-chasing-the-owner-of-a-fix-in-jira-teams-or-slack/), read 10 Nov 2026)
- Vendor's claim: Routing runs inside policies the customer sets. ([source](https://backline.ai/blog/finding-and-chasing-the-owner-of-a-fix-in-jira-teams-or-slack/), read 10 Nov 2026)
### Speed on a new disclosure
- Vendor's claim: Published response write-up on HTTP2Shell (Node.js Brotli CVE): it reached Backline customers via container image scans, so detection depends on the connected scanner. ([source](https://backline.ai/blog/http2shell-three-images-one-cve/), read 10 Nov 2026)
- Vendor's claim: Remediation-speed claim: MTTR down to one hour from more than two weeks per vulnerability at a Fortune 500 manufacturer (unnamed). ([source](https://backline.ai/case-studies/case-study-closing-the-exposure-window/), read 10 Nov 2026)
- Vendor's claim: Remediation-speed claim: average time to fix went from 5 weeks to 2 hours at a data-analytics company (unnamed). ([source](https://backline.ai/case-studies/five-weeks-to-under-a-day/), read 10 Nov 2026)
- None found on 10 Nov 2026: A dedicated zero-day or new-CVE exposure lookup feature, or a time-to-answer claim for new disclosures, on the home or product pages. ([source](https://backline.ai/product/), read 10 Nov 2026)
### Agents you can shape
- Vendor's claim: Four named vendor-built agents: Analyst (Andy), Planner (Polly), Coder (Codie), Verifier (Vera). ([source](https://backline.ai/), read 10 Nov 2026)
- Vendor's claim: Verifier agent validates every fix through testing. ([source](https://backline.ai/), read 10 Nov 2026)
- Vendor's claim: Autonomy split: 80% auto fix handled end to end, 20% hybrid with human-in-the-loop input. ([source](https://backline.ai/), read 10 Nov 2026)
- Vendor's claim: Vendor-built custom behavior: agent behavior tuned to the customer SDLC (build conventions, release rules). ([source](https://backline.ai/case-studies/hands-off-fully-fixed/), read 10 Nov 2026)
- Vendor's claim: Access control: zero-trust, identity-based access to the SaaS and connected systems. ([source](https://backline.ai/), read 10 Nov 2026)
- None found on 10 Nov 2026: Customer-built agents or an agent-builder on the home, product, fixaition, company pages. ([source](https://backline.ai/product/), read 10 Nov 2026)
### Works on the stack you have
- Third-party source: TechCrunch (Jan 2025): takes notifications from other security tools and remediates. ([source](https://techcrunch.com/2025/01/30/backline-automatically-remediates-security-vulnerabilities/), read 10 Nov 2026)
- Vendor's claim: Ingests findings from the customer's existing production scanners. ([source](https://backline.ai/product/), read 10 Nov 2026)
- Vendor's claim: Integrates with security stack, communication platforms and code repositories (no named list in page text). ([source](https://backline.ai/), read 10 Nov 2026)
- Vendor's claim: Named ticketing and chat: Slack, Microsoft Teams, Jira. ([source](https://backline.ai/blog/finding-and-chasing-the-owner-of-a-fix-in-jira-teams-or-slack/), read 10 Nov 2026)
- Vendor's claim: Named scanner in customer environments: AWS Inspector on ECR. ([source](https://backline.ai/blog/http2shell-three-images-one-cve/), read 10 Nov 2026)
### Proof
- Vendor's claim: Named customer quote: Arkose Labs senior security architect. ([source](https://backline.ai/), read 10 Nov 2026)
- Vendor's claim: Named customer quotes also from Cockroach Labs, Celanese and Thetaray on the home page. ([source](https://backline.ai/), read 10 Nov 2026)
- Vendor's claim: Case study: Fortune 500 manufacturer, 20x remediation capacity and 100% auto-merged fixes (customer unnamed). ([source](https://backline.ai/case-studies/case-study-closing-the-exposure-window/), read 10 Nov 2026)
- Vendor's claim: Case study: telecom provider, 95% of fixes with zero manual code changes (customer unnamed). ([source](https://backline.ai/case-studies/hands-off-fully-fixed/), read 10 Nov 2026)
- Vendor's claim: Case study: data-analytics company, hundreds of thousands of open vulnerabilities, few dozen fixes (customer unnamed). ([source](https://backline.ai/case-studies/five-weeks-to-under-a-day/), read 10 Nov 2026)
- Vendor's claim: Product page typical-results claims: 95% reduced risk, 60% faster MTTR, 100% consistent SLA (no method given). ([source](https://backline.ai/product/), read 10 Nov 2026)
## Profile facts
- Third-party source: Funding: $9 million seed round led by StageOne Ventures, announced Jan 30, 2025. ([source](https://techcrunch.com/2025/01/30/backline-automatically-remediates-security-vulnerabilities/), read 10 Nov 2026)
- Vendor's claim: Founders and leadership listed on company page. ([source](https://backline.ai/company/), read 10 Nov 2026)
- Third-party source: CEO previously co-founded Whitebox Security (sold to SailPoint) and Apolicy (acquired by Sysdig). ([source](https://techcrunch.com/2025/01/30/backline-automatically-remediates-security-vulnerabilities/), read 10 Nov 2026)
- Vendor's claim: Category: Autonomous Exposure Remediation, which it says Gartner named in June 2026. ([source](https://backline.ai/product/), read 10 Nov 2026)
- Vendor's claim: Company name in footer: Backline AI, Inc. ([source](https://backline.ai/), read 10 Nov 2026)
- Vendor's claim: News page lists a CrowdStrike and AWS accelerator selection (2025). ([source](https://backline.ai/news/), read 10 Nov 2026)
- None found on 10 Nov 2026: Pricing, headcount, HQ address, customer count on home, product, company pages. ([source](https://backline.ai/company/), read 10 Nov 2026)
## Links
- [Side by side](/compare/): Pairs of platforms, with the sourced facts in the same rows.
- [Backline Security on its own site](https://backline.ai/)
## Related pages
- [The 14 platforms, listed alphabetically](/platforms/)
- [Cogent Security: what it is, what it does well and where it is limited](/platforms/cogent/)
- [Averlon: what it is, what it does well and where it is limited](/platforms/averlon/)
- [Dux Security: what it is, what it does well and where it is limited](/platforms/dux/)
## Sources
- Backline Security: backline.ai/product/: https://backline.ai/product/ (read 10 Nov 2026)
- Backline Security: backline.ai/case-studies/hands-off-fully-fixed/: https://backline.ai/case-studies/hands-off-fully-fixed/ (read 10 Nov 2026)
- Backline Security: backline.ai/case-studies/five-weeks-to-under-a-day/: https://backline.ai/case-studies/five-weeks-to-under-a-day/ (read 10 Nov 2026)
- Backline Security: backline.ai/blog/http2shell-three-images-one-cve/: https://backline.ai/blog/http2shell-three-images-one-cve/ (read 10 Nov 2026)
- Backline Security: backline.ai/: https://backline.ai/ (read 10 Nov 2026)
- Backline Security: backline.ai/fixaition/: https://backline.ai/fixaition/ (read 10 Nov 2026)
- Backline Security: backline.ai/blog/finding-and-chasing-the-owner-of-a-fix-in-jira-teams-or-slack/: https://backline.ai/blog/finding-and-chasing-the-owner-of-a-fix-in-jira-teams-or-slack/ (read 10 Nov 2026)
- Backline Security: backline.ai/case-studies/case-study-closing-the-exposure-window/: https://backline.ai/case-studies/case-study-closing-the-exposure-window/ (read 10 Nov 2026)
- techcrunch.com: /2025/01/30/backline-automatically-remediates-security-vulnerabilities: https://techcrunch.com/2025/01/30/backline-automatically-remediates-security-vulnerabilities/ (read 10 Nov 2026)
- Backline Security: backline.ai/company/: https://backline.ai/company/ (read 10 Nov 2026)
- Backline Security: backline.ai/news/: https://backline.ai/news/ (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/platforms/backline/
---
# Cogent Security: what it is, what it does well and where it is limited
Platform profile, read 10 Nov 2026
**The short answer.** Cogent Security sells agentic vulnerability management and remediation (AI agents across the full vulnerability lifecycle), as its pages read on 10 Nov 2026 describe it. 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.
## What it is
Agentic vulnerability management and remediation (AI agents across the full vulnerability lifecycle).
## What it 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).
## Where it is 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.
## Facts read, by topic
Each line below carries a label, the page it was read on and the date. A vendor's claim is the vendor's own statement about itself; a third-party source is one that is not the vendor; a line that starts with none found says nothing was published on that date. Cogent Security has 40 lines on file, read up to 10 Nov 2026; the Cogent Security pages behind them are listed under Sources.
### Proves exploitability in your environment
- Vendor's claim: Cogent says it prioritizes by real exploitability and business impact, not only CVSS. ([source](https://www.cogent.com/platform/assess), read 10 Nov 2026)
- Vendor's claim: On PHP2Shell, Cogent says it narrowed 2,266 affected assets (Fortune 500 average) to 16 using runtime exposure, internet reachability and business criticality. ([source](https://www.cogent.com/blog/cogent-expands-its-ai-cyber-defense-factory-with-specular-acquisition), read 10 Nov 2026)
- Vendor's claim: A knowledge graph links assets to owners, business functions, network exposure and compensating controls. ([source](https://www.cogent.com/ai/cogent-ai-engine), read 10 Nov 2026)
- Vendor's claim: Every output shows its chain of logic: data sources, agents involved and why that path was chosen. ([source](https://www.cogent.com/ai/cogent-ai-engine), read 10 Nov 2026)
- Vendor's claim: Cogent Research reports 34 new attack paths viable for AI agent swarms in the average enterprise per month, based on 43M assets. ([source](https://www.cogent.com/platform/cyber-defense-factory), read 10 Nov 2026)
### Ships the fix
- Third-party source: Its VR-1.1 model writes fixes for newly disclosed vulnerabilities; each patch goes to a separate review that tries to bypass it. ([source](https://siliconangle.com/2026/11/03/exclusive-cogent-securitys-vr-1-1-model-outscores-claude-code-and-codex-on-vulnerability-repair/), read 10 Nov 2026)
- Third-party source: VR-1.1 also writes regression tests intended to fail if a later change reopens the flaw. ([source](https://siliconangle.com/2026/11/03/exclusive-cogent-securitys-vr-1-1-model-outscores-claude-code-and-codex-on-vulnerability-repair/), read 10 Nov 2026)
- Vendor's claim: Cogent finds the fix, assesses impact and executes through existing tools, from assisted to fully autonomous. ([source](https://www.cogent.com/), read 10 Nov 2026)
- Vendor's claim: High-impact changes require human approval and an audit trail. ([source](https://www.cogent.com/ai/autonomy-levels), read 10 Nov 2026)
- Vendor's claim: Granular approval workflows let customers choose where agents act alone and where they pause for sign-off. ([source](https://www.cogent.com/ai/cogent-ai-engine), read 10 Nov 2026)
### Finds the owner
- Third-party source: Per SiliconANGLE, agents determine asset ownership and map vulnerabilities to affected services. ([source](https://siliconangle.com/2026/02/18/cogent-security-raises-42m-scale-ai-agents-enterprise-vulnerability-remediation/), read 10 Nov 2026)
- Third-party source: Per SiliconANGLE, agents track remediation status and verify completion after patches or config changes. ([source](https://siliconangle.com/2026/02/18/cogent-security-raises-42m-scale-ai-agents-enterprise-vulnerability-remediation/), read 10 Nov 2026)
- Vendor's claim: The Discover page demo shows agents resolving an asset owner from ServiceNow CMDB and checking Jira ticket history. ([source](https://www.cogent.com/platform/discover), read 10 Nov 2026)
- Vendor's claim: The CSC Generation case study says the team previously mapped owners, routed tickets and tracked SLAs manually. ([source](https://www.cogent.com/customers/csc-generation), read 10 Nov 2026)
### Speed on a new disclosure
- Vendor's claim: Cogent says it identifies vulnerable software within minutes of disclosure. ([source](https://www.cogent.com/platform/discover), read 10 Nov 2026)
- Vendor's claim: Homepage claim: identify vulnerable software within minutes of a new disclosure, before scanners can. ([source](https://www.cogent.com/), read 10 Nov 2026)
- Vendor's claim: Cogent's Nov 10 post cites its PHP2Shell analysis, listed on the homepage as dated Oct 21, 2026, the same day as the disclosure. ([source](https://www.cogent.com/blog/cogent-expands-its-ai-cyber-defense-factory-with-specular-acquisition), read 10 Nov 2026)
### Agents you can shape
- Third-party source: Cogent's VR-1 and VR-1.1 are vendor-built reasoning models for vulnerability repair. ([source](https://siliconangle.com/2026/11/03/exclusive-cogent-securitys-vr-1-1-model-outscores-claude-code-and-codex-on-vulnerability-repair/), read 10 Nov 2026)
- Vendor's claim: Ready-made specialized agents handle normalization, enrichment, risk assessment and remediation planning. ([source](https://www.cogent.com/ai/cogent-ai-engine), read 10 Nov 2026)
- Vendor's claim: Agents check customer-defined guardrails before every action. ([source](https://www.cogent.com/ai/cogent-ai-engine), read 10 Nov 2026)
- Vendor's claim: Autonomy is staged: start with recommendations and review, then expand. ([source](https://www.cogent.com/ai/autonomy-levels), read 10 Nov 2026)
- None found on 10 Nov 2026: Customer-built agents: none found on 2026-11-10: an agent builder or customer-defined agent feature on cogent.com platform and AI pages ([source](https://www.cogent.com/ai/cogent-ai-engine), read 10 Nov 2026)
### Works on the stack you have
- Vendor's claim: Scanner integrations include Qualys, Rapid7 and Tenable. ([source](https://www.cogent.com/platform/integrations), read 10 Nov 2026)
- Vendor's claim: Cloud security ingestion: AWS, Lacework, Orca, Upwind, Wiz. ([source](https://www.cogent.com/platform/integrations), read 10 Nov 2026)
- Vendor's claim: Ticketing integrations: Jira and ServiceNow ITSM (push and track tickets). ([source](https://www.cogent.com/platform/integrations), read 10 Nov 2026)
- Vendor's claim: Endpoint integrations: CrowdStrike, Microsoft Defender for Endpoint, SentinelOne. ([source](https://www.cogent.com/platform/integrations), read 10 Nov 2026)
- Vendor's claim: AppSec integrations: Black Duck, GitHub, Snyk, SonarQube, Veracode. ([source](https://www.cogent.com/platform/integrations), read 10 Nov 2026)
- Vendor's claim: Asset sources include Microsoft Intune, ServiceNow CMDB and VMware vSphere; network: FortiManager; EASM: IONIX. ([source](https://www.cogent.com/platform/integrations), read 10 Nov 2026)
### Proof
- Third-party source: VR-1.1 passed 57.9% of 190 LiveCVEBench tasks; Claude Code and Codex scored 45.3% (vendor-run test, reported by SiliconANGLE). ([source](https://siliconangle.com/2026/11/03/exclusive-cogent-securitys-vr-1-1-model-outscores-claude-code-and-codex-on-vulnerability-repair/), read 10 Nov 2026)
- Third-party source: Method notes: outbound network blocked during repairs and grading tests hidden; inference budgets differed across systems. ([source](https://siliconangle.com/2026/11/03/exclusive-cogent-securitys-vr-1-1-model-outscores-claude-code-and-codex-on-vulnerability-repair/), read 10 Nov 2026)
- Third-party source: SiliconANGLE names Upwind, Alteryx and CSC Generation as customers and says Cogent works with dozens of Fortune 1000 companies. ([source](https://siliconangle.com/2026/02/18/cogent-security-raises-42m-scale-ai-agents-enterprise-vulnerability-remediation/), read 10 Nov 2026)
- Vendor's claim: CSC Generation case study: 3 hours to full assessment, 100% of vulnerabilities managed autonomously (vendor-published). ([source](https://www.cogent.com/customers/csc-generation), read 10 Nov 2026)
- Vendor's claim: Homepage case-study stats: 3x team output, 97% reduction in exposure window for critical vulns. ([source](https://www.cogent.com/), read 10 Nov 2026)
- Vendor's claim: Q4 2026 threat report from Cogent Research is based on 43M assets, 1.2B findings and 50+ Fortune 1000 organizations. ([source](https://www.cogent.com/platform/cyber-defense-factory), read 10 Nov 2026)
## Profile facts
- Third-party source: Series A of $42M led by Bain Capital with Greylock Partners and Definition Capital, announced Feb 18, 2026. ([source](https://siliconangle.com/2026/02/18/cogent-security-raises-42m-scale-ai-agents-enterprise-vulnerability-remediation/), read 10 Nov 2026)
- Third-party source: Founded in 2025, formally launched July 2025; works with dozens of Fortune 1000 companies (per SiliconANGLE). ([source](https://siliconangle.com/2026/02/18/cogent-security-raises-42m-scale-ai-agents-enterprise-vulnerability-remediation/), read 10 Nov 2026)
- Vendor's claim: Acquired Specular (Google-backed AI security platform) on 10 Nov 2026. ([source](https://www.cogent.com/blog/cogent-expands-its-ai-cyber-defense-factory-with-specular-acquisition), read 10 Nov 2026)
- Vendor's claim: Co-founders: Vineet Edupuganti (CEO), Thanos Baskous (VP Engineering), Geng Sng (CTO). ([source](https://www.cogent.com/company/about), read 10 Nov 2026)
- Vendor's claim: Product areas: Discover, Assess, Remediate, Report; Cyber Defense Factory; Cogent AI Engine; Cogent Research. ([source](https://www.cogent.com/), read 10 Nov 2026)
- None found on 10 Nov 2026: Pricing, HQ and headcount: none found on 2026-11-10: pricing, HQ and headcount on home, company/about, newsroom ([source](https://www.cogent.com/company/about), read 10 Nov 2026)
## Links
- [Side by side](/compare/): Pairs of platforms, with the sourced facts in the same rows.
- [Cogent Security on its own site](https://www.cogent.com/)
## Related pages
- [The 14 platforms, listed alphabetically](/platforms/)
- [Dux Security: what it is, what it does well and where it is limited](/platforms/dux/)
- [Backline Security: what it is, what it does well and where it is limited](/platforms/backline/)
- [Maze: what it is, what it does well and where it is limited](/platforms/maze/)
## Sources
- Cogent Security: www.cogent.com/platform/assess: https://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: https://www.cogent.com/blog/cogent-expands-its-ai-cyber-defense-factory-with-specular-acquisition (read 10 Nov 2026)
- Cogent Security: www.cogent.com/ai/cogent-ai-engine: https://www.cogent.com/ai/cogent-ai-engine (read 10 Nov 2026)
- Cogent Security: www.cogent.com/platform/cyber-defense-factory: https://www.cogent.com/platform/cyber-defense-factory (read 10 Nov 2026)
- Cogent Security: www.cogent.com/: https://www.cogent.com/ (read 10 Nov 2026)
- siliconangle.com: /2026/11/03/exclusive-cogent-securitys-vr-1-1-model-outscores-claude-c: https://siliconangle.com/2026/11/03/exclusive-cogent-securitys-vr-1-1-model-outscores-claude-code-and-codex-on-vulnerability-repair/ (read 10 Nov 2026)
- Cogent Security: www.cogent.com/ai/autonomy-levels: https://www.cogent.com/ai/autonomy-levels (read 10 Nov 2026)
- siliconangle.com: /2026/02/18/cogent-security-raises-42m-scale-ai-agents-enterprise-vuln: https://siliconangle.com/2026/02/18/cogent-security-raises-42m-scale-ai-agents-enterprise-vulnerability-remediation/ (read 10 Nov 2026)
- Cogent Security: www.cogent.com/platform/discover: https://www.cogent.com/platform/discover (read 10 Nov 2026)
- Cogent Security: www.cogent.com/customers/csc-generation: https://www.cogent.com/customers/csc-generation (read 10 Nov 2026)
- Cogent Security: www.cogent.com/platform/integrations: https://www.cogent.com/platform/integrations (read 10 Nov 2026)
- Cogent Security: www.cogent.com/company/about: https://www.cogent.com/company/about (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/platforms/cogent/
---
# Dux Security: what it is, what it does well and where it is limited
Platform profile, read 10 Nov 2026
**The short answer.** Dux Security sells agentic exposure management (exploitability analysis, mitigation, remediation acceleration), as its pages read on 10 Nov 2026 describe it. 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. Every line below carries its source and the date it was read.
## What it is
Agentic exposure management (exploitability analysis, mitigation, remediation acceleration).
## What it 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.
## Where it is 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.
## Facts read, by topic
Each line below carries a label, the page it was read on and the date. A vendor's claim is the vendor's own statement about itself; a third-party source is one that is not the vendor; a line that starts with none found says nothing was published on that date. Dux Security has 28 lines on file, read up to 10 Nov 2026; the Dux Security pages behind them are listed under Sources.
### Proves exploitability in your environment
- Vendor's claim: Dux maps how vulnerabilities, assets and controls connect to judge exploitability. ([source](https://dux.io/), read 10 Nov 2026)
- Vendor's claim: Stated aim: separate reachable from truly exploitable risk. ([source](https://dux.io/), read 10 Nov 2026)
- Vendor's claim: Home page lead: AI agents for instant exploitability analysis. ([source](https://dux.io/), read 10 Nov 2026)
- Vendor's claim: Exploitability stage answers where the customer is already protected. ([source](https://dux.io/), read 10 Nov 2026)
- None found on 10 Nov 2026: Evidence examples, sample outputs or a method for exploitability conclusions. ([source](https://dux.io/), read 10 Nov 2026)
### Ships the fix
- Vendor's claim: Dux favors lightweight mitigations such as a missing control or config change instead of a patch. ([source](https://dux.io/), read 10 Nov 2026)
- Vendor's claim: Mitigations are ones the customer deploys on its own. ([source](https://dux.io/), read 10 Nov 2026)
- Vendor's claim: Remediation stage speeds up the fix process by tagging assets and tying data sources together. ([source](https://dux.io/), read 10 Nov 2026)
- None found on 10 Nov 2026: Generated pull requests, tested code fixes or approval-gated automated changes. ([source](https://dux.io/), read 10 Nov 2026)
### Finds the owner
- Vendor's claim: Remediation stage poses the question of who should remediate. ([source](https://dux.io/), read 10 Nov 2026)
- Vendor's claim: Auto-tagging of every asset is the ownership mechanism described. ([source](https://dux.io/), read 10 Nov 2026)
- None found on 10 Nov 2026: Ticket routing, follow-up or escalation features. ([source](https://dux.io/), read 10 Nov 2026)
### Speed on a new disclosure
- Vendor's claim: Positioning is speed against attackers. ([source](https://dux.io/), read 10 Nov 2026)
- Vendor's claim: Home page frames time-to-exploit collapsing from weeks to minutes. ([source](https://dux.io/), read 10 Nov 2026)
- None found on 10 Nov 2026: Zero-day response feature, time-to-answer number or published response write-up. ([source](https://dux.io/), read 10 Nov 2026)
### Agents you can shape
- Vendor's claim: Dux uses AI agents across analysis, mitigation and remediation acceleration. ([source](https://dux.io/), read 10 Nov 2026)
- None found on 10 Nov 2026: Named ready-made agents, customer-built agents, or controls and guardrails. ([source](https://dux.io/), read 10 Nov 2026)
### Works on the stack you have
- Vendor's claim: Mitigation stage works from the customer's existing stack. ([source](https://dux.io/), read 10 Nov 2026)
- Vendor's claim: Dux reviews the whole security posture to find mitigations. ([source](https://dux.io/), read 10 Nov 2026)
- None found on 10 Nov 2026: Named scanner, cloud, code host or ticketing integrations. ([source](https://dux.io/), read 10 Nov 2026)
### Proof
- Vendor's claim: Quote from Mille Gandelsman (CPO at Opti, ex-VP at Tenable) on the home page. ([source](https://dux.io/), read 10 Nov 2026)
- Vendor's claim: Quote from Andrew Wilder (CSO at Vetcor, ex-Nestle) on the home page. ([source](https://dux.io/), read 10 Nov 2026)
- Vendor's claim: Quote from Rinki Sethi (CSO at Upwind, ex-BILL). ([source](https://dux.io/), read 10 Nov 2026)
- None found on 10 Nov 2026: Named customers, case studies, published results or research publications (quotes above are from named security executives, not stated customers). ([source](https://dux.io/), read 10 Nov 2026)
## Profile facts
- Vendor's claim: Product category on page title and heading: Agentic Exposure Management. ([source](https://dux.io/), read 10 Nov 2026)
- Vendor's claim: Company legal name in footer: Dux, Inc. ([source](https://dux.io/), read 10 Nov 2026)
- Vendor's claim: Company description: built by security veterans. ([source](https://dux.io/), read 10 Nov 2026)
- None found on 10 Nov 2026: Pricing, funding, investors (a Backed by section shows logos only, no text), founders, HQ, headcount, careers (dux.io/about and /careers return 404). ([source](https://dux.io/), read 10 Nov 2026)
## Links
- [Side by side](/compare/): Pairs of platforms, with the sourced facts in the same rows.
- [Dux Security on its own site](https://dux.io/)
## Related pages
- [The 14 platforms, listed alphabetically](/platforms/)
- [Maze: what it is, what it does well and where it is limited](/platforms/maze/)
- [Cogent Security: what it is, what it does well and where it is limited](/platforms/cogent/)
- [Onit Security: what it is, what it does well and where it is limited](/platforms/onit/)
## Sources
- Dux Security: dux.io/: https://dux.io/ (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/platforms/dux/
---
# Maze: what it is, what it does well and where it is limited
Platform profile, read 10 Nov 2026
**The short answer.** Maze sells agentic vulnerability investigation and remediation (code and cloud), as its pages read on 10 Nov 2026 describe it. 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.
## What it is
Agentic vulnerability investigation and remediation (code and cloud).
## What it 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.
## Where it is 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.
## Facts read, by topic
Each line below carries a label, the page it was read on and the date. A vendor's claim is the vendor's own statement about itself; a third-party source is one that is not the vendor; a line that starts with none found says nothing was published on that date. Maze has 37 lines on file, read up to 10 Nov 2026; the Maze pages behind them are listed under Sources.
### Proves exploitability in your environment
- Vendor's claim: Maze defines exploitable relative to the customer's own configuration, controls and context, not CVSS or exploit-in-the-wild status. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
- Vendor's claim: Every recommendation is said to carry the evidence and reasoning behind it. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
- Vendor's claim: Maze says 90% of vulnerabilities it analyzes are not exploitable when investigated. ([source](https://mazehq.com/), read 10 Nov 2026)
- Vendor's claim: Runtime context is gathered without installing sensors. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
- Vendor's claim: Maze Code decides exploitability in the customer's environment, not only reachability. ([source](https://mazehq.com/platform/code), read 10 Nov 2026)
- Vendor's claim: In the Cohere Health story, 51% of findings were judged not exploitable and each decision, including closed ones, came with evidence. ([source](https://mazehq.com/customer-story/how-cohere-health-cleared-92-of-its-critical-and-high-findings), read 10 Nov 2026)
### Ships the fix
- Vendor's claim: Agents verify that a fix resolves the vulnerability without introducing new ones. ([source](https://mazehq.com/solutions/remediation), read 10 Nov 2026)
- Vendor's claim: Maze generates and validates fixes but the customer's team controls what gets merged. ([source](https://mazehq.com/solutions/remediation), read 10 Nov 2026)
- Vendor's claim: Where patching is not possible, Maze suggests mitigations that break the exploitability chain. ([source](https://mazehq.com/solutions/remediation), read 10 Nov 2026)
- Vendor's claim: Agents bundle proven-exploitable CVEs into single fixes, so one ticket can close 30 or more. ([source](https://mazehq.com/solutions/remediation), read 10 Nov 2026)
- Vendor's claim: Agents offer several fix options rather than one textbook fix. ([source](https://mazehq.com/solutions/remediation), read 10 Nov 2026)
### Finds the owner
- Vendor's claim: Agents infer the owner from commit history and code, then route the fix to the developer or coding agent. ([source](https://mazehq.com/solutions/remediation), read 10 Nov 2026)
- Vendor's claim: Fixes are delivered into ticketing platforms or coding agents (Slack or Teams optional). ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
- None found on 10 Nov 2026: Follow-up after routing (reminders, SLA tracking, escalation): none found on 2026-11-10: owner follow-up or SLA tracking on remediation, platform/cloud and platform/code pages ([source](https://mazehq.com/solutions/remediation), read 10 Nov 2026)
### Speed on a new disclosure
- Vendor's claim: Maze says agents sweep every instance for a new zero-day in hours, before scanners have a signature. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
- Vendor's claim: Maze claims agents recognize zero-day vulnerabilities and triage them before scanners see them. ([source](https://mazehq.com/), read 10 Nov 2026)
- Vendor's claim: Maze published a response write-up on PHP2Shell dated Oct 22, 2026, one day after the Oct 21 patch release. ([source](https://mazehq.com/blog/php2shell), read 10 Nov 2026)
### Agents you can shape
- Vendor's claim: Maze Cloud and Maze Code are agent-driven products; AI-SCA and AI-SAST are named agent modules. ([source](https://mazehq.com/), read 10 Nov 2026)
- Vendor's claim: Vendor-built agents run on custom infrastructure, trained on domain tasks and checked by multiple validation layers. ([source](https://mazehq.com/platform), read 10 Nov 2026)
- Vendor's claim: Maze integrates with coding agents such as Claude and Cursor. ([source](https://mazehq.com/platform), read 10 Nov 2026)
- Vendor's claim: Data control: Maze does not train or fine-tune the underlying models on customer code or findings; single-tenant hosting is offered. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
- None found on 10 Nov 2026: Customer-built agents: none found on 2026-11-10: an agent builder or custom-agent feature on mazehq.com platform pages ([source](https://mazehq.com/platform), read 10 Nov 2026)
### Works on the stack you have
- Vendor's claim: Maze needs a read-only cloud role and an API connection to vulnerability scanners. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
- Vendor's claim: It pulls and deduplicates findings from existing scanners. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
- Vendor's claim: The Cohere Health story lists AWS and containers as the environment. ([source](https://mazehq.com/customer-story/how-cohere-health-cleared-92-of-its-critical-and-high-findings), read 10 Nov 2026)
- None found on 10 Nov 2026: Specific scanner, code host and ticketing product names: none found on 2026-11-10: a named integration list on mazehq.com (the FAQ says only that it connects to the scanners customers already have) ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
### Proof
- Vendor's claim: Cohere Health story: 92% of critical and high findings not exploitable, downgraded or remediated. ([source](https://mazehq.com/customer-story/how-cohere-health-cleared-92-of-its-critical-and-high-findings), read 10 Nov 2026)
- Vendor's claim: Same story: 87% of critical and high findings were not exploitable or safe to deprioritize. ([source](https://mazehq.com/customer-story/how-cohere-health-cleared-92-of-its-critical-and-high-findings), read 10 Nov 2026)
- Vendor's claim: Named customer quotes: Alloy, Cohere Health, Forge, PartsSource. ([source](https://mazehq.com/), read 10 Nov 2026)
- Vendor's claim: Maze claims deployment by multiple Fortune 100 organizations. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
- Vendor's claim: Maze publishes vulnerability research posts, for example a Langfuse SSO bug found by Maze Code. ([source](https://mazehq.com/blog/php2shell), read 10 Nov 2026)
## Profile facts
- Vendor's claim: Maze was started in 2024. ([source](https://mazehq.com/our-story), read 10 Nov 2026)
- Vendor's claim: Pricing is based on the size of the customer's cloud infrastructure; no public price list. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
- Vendor's claim: Certifications: ISO 27001 and SOC 2 Type II. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
- Vendor's claim: Hosted in AWS with multi-tenant or single-tenant options. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
- Vendor's claim: Maze says it fits no existing category (CTEM, RBVM, UVM, RemOps, ASPM). ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
- None found on 10 Nov 2026: Funding, HQ, headcount and founders' names: none found on 2026-11-10: funding, HQ, headcount, founder names on home, our-story, platform pages ([source](https://mazehq.com/our-story), read 10 Nov 2026)
## Links
- [Side by side](/compare/): Pairs of platforms, with the sourced facts in the same rows.
- [Maze on its own site](https://mazehq.com/)
## Related pages
- [The 14 platforms, listed alphabetically](/platforms/)
- [Onit Security: what it is, what it does well and where it is limited](/platforms/onit/)
- [Dux Security: what it is, what it does well and where it is limited](/platforms/dux/)
- [Qualys: what it is, what it does well and where it is limited](/platforms/qualys/)
## Sources
- Maze: mazehq.com/platform/cloud: https://mazehq.com/platform/cloud (read 10 Nov 2026)
- Maze: mazehq.com/: https://mazehq.com/ (read 10 Nov 2026)
- Maze: mazehq.com/platform/code: https://mazehq.com/platform/code (read 10 Nov 2026)
- Maze: mazehq.com/customer-story/how-cohere-health-cleared-92-of-its-critical-and-high-: https://mazehq.com/customer-story/how-cohere-health-cleared-92-of-its-critical-and-high-findings (read 10 Nov 2026)
- Maze: mazehq.com/solutions/remediation: https://mazehq.com/solutions/remediation (read 10 Nov 2026)
- Maze: mazehq.com/blog/php2shell: https://mazehq.com/blog/php2shell (read 10 Nov 2026)
- Maze: mazehq.com/platform: https://mazehq.com/platform (read 10 Nov 2026)
- Maze: mazehq.com/our-story: https://mazehq.com/our-story (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/platforms/maze/
---
# Onit Security: what it is, what it does well and where it is limited
Platform profile, read 10 Nov 2026
**The short answer.** Onit Security sells agentic exposure management / remediation (decision-based), as its pages read on 10 Nov 2026 describe it. 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. Every line below carries its source and the date it was read.
## What it is
Agentic exposure management / remediation (decision-based).
## What it 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.
## Where it is 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.
## Facts read, by topic
Each line below carries a label, the page it was read on and the date. A vendor's claim is the vendor's own statement about itself; a third-party source is one that is not the vendor; a line that starts with none found says nothing was published on that date. Onit Security has 37 lines on file, read up to 10 Nov 2026; the Onit Security pages behind them are listed under Sources.
### Proves exploitability in your environment
- Vendor's claim: Platform layer that validates whether each exposure is reachable and exploitable in the customer environment, so only real risk continues. ([source](https://onit.security/platform/), read 10 Nov 2026)
- Vendor's claim: Exploitability signals named: network reachability, runtime and loaded status, and live exploit intelligence such as KEV and weaponization. ([source](https://onit.security/platform/), read 10 Nov 2026)
- Vendor's claim: A Reachability Agent returns a per-asset finding (reachable, restricted, internal, not reachable, unknown) with the path or the blocker as evidence, read-only. ([source](https://onit.security/blog/reachable-vulnerabilities/), read 10 Nov 2026)
- Vendor's claim: An Exploitability Agent checks host conditions (component present, loaded, configured in the exploitable way); failed findings are kept with the reason. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
- Vendor's claim: When evidence is missing an agent says unknown with the reason instead of guessing. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
### Ships the fix
- Vendor's claim: A Remediation Agent builds a step-by-step remediation plan (patch/version, deployment path, restart and validation steps, rollback) per asset; the published text describes a plan, not an automatically opened pull request. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
- Vendor's claim: A Mitigation Agent proposes interim mitigations (disable a feature, tighten a firewall rule, compensating control), tagged by time, complexity and operational impact. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
- Vendor's claim: Human approval gate on every agent action, with audit trail and one-step reversal, for both remediations and mitigations. ([source](https://onit.security/platform/), read 10 Nov 2026)
- Vendor's claim: Vendor states nothing executes without approval. ([source](https://onit.security/platform/), read 10 Nov 2026)
### Finds the owner
- Vendor's claim: Resolves the owner from CMDB, ticketing and communication tools rather than leaving owner guessing to the customer. ([source](https://onit.security/), read 10 Nov 2026)
- Vendor's claim: Ownership inferred from commit authorship, historical patterns and service maps, and re-resolved after reorganizations. ([source](https://onit.security/platform/), read 10 Nov 2026)
- Vendor's claim: After assigning, it nudges, escalates and tracks the work to closure. ([source](https://onit.security/platform/), read 10 Nov 2026)
- Vendor's claim: Vendor reports roughly half of remediation tickets bounce because the owner is wrong on arrival (its own field observation, no published method). ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
### Speed on a new disclosure
- Vendor's claim: A Zero-Day Agent is described as catching a zero-day as it breaks, finding every exposed asset and proving which are exploitable, in minutes (blog dated Oct 23, 2026). ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
- Vendor's claim: The Zero-Day Agent was announced ahead of general availability as of the blog date. ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
- Vendor's claim: Published write-up of the PHP2Shell zero-day (leak Oct 20, 2026) walks through the four questions the agent answers. ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
- Vendor's claim: Zero-Day Agent limits: no live exploits against production, no new endpoint agent, no disruptive action without approval. ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
- Vendor's claim: Headline time-to-resolve claim on the platform page (no method shown). ([source](https://onit.security/platform/), read 10 Nov 2026)
### Agents you can shape
- Vendor's claim: Ready-made specialized agents (discovery, ownership, exploitability, threat intel, prioritization, resolution, remediation, mitigation) run in parallel on one shared context. ([source](https://onit.security/platform/), read 10 Nov 2026)
- Vendor's claim: Named agents in the Decision Center: Reachability, Exploitability, Context, Ownership, Prioritization, Remediation, Mitigation. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
- Vendor's claim: Guardrail model: a person reviews each decision once; approved decisions become standing rules covering matching exposures, logged and reversible. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
- Vendor's claim: Agent controls: customer can adjust one agent without touching the others. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
- None found on 10 Nov 2026: Documentation of customer-built or custom agents on onit.security ([source](https://onit.security/platform/), read 10 Nov 2026)
### Works on the stack you have
- Vendor's claim: Sources are described by category: security tools, cloud, CMDBs, ticketing and collaboration systems (scanners, CSPM, EDR/XDR). ([source](https://onit.security/platform/), read 10 Nov 2026)
- Vendor's claim: Knowledge sources include asset inventories, ticketing and change history, wikis, Slack and Teams threads, email, cloud tags, directories and code repositories. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
- Vendor's claim: Zero-Day Agent reads scanners, cloud accounts, EDR and CMDB already connected, and checks exploitability read-only through the EDR. ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
- None found on 10 Nov 2026: A list of named scanner, cloud, code host or ticketing product integrations on onit.security ([source](https://onit.security/), read 10 Nov 2026)
### Proof
- Vendor's claim: Named-person testimonials appear on the home page (titles only, employers not named in the quote block). ([source](https://onit.security/), read 10 Nov 2026)
- Vendor's claim: Anecdote of an unnamed Fortune 500 customer where three tools showed no findings and Onit found two devices on a KEV-listed product. ([source](https://onit.security/blog/reachable-vulnerabilities/), read 10 Nov 2026)
- Vendor's claim: Research and thought-leadership blog cadence (posts Jul to Nov 2026) citing Mandiant M-Trends and Verizon DBIR; no original measured study seen. ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
- None found on 10 Nov 2026: Named customer case studies or a published measurement method for the 55 days to 2.7 hours claim ([source](https://onit.security/), read 10 Nov 2026)
## Profile facts
- Vendor's claim: Founders: Elad Ben Meir (CEO), Ofer Amitai (CPO), Tom Winter (CTO). ([source](https://onit.security/company/), read 10 Nov 2026)
- Vendor's claim: CEO background: previously CEO of SCADAfence (acquired by Honeywell). ([source](https://onit.security/company/), read 10 Nov 2026)
- Vendor's claim: Funding: seed round closed in 2025; amount not stated on the page. ([source](https://onit.security/company/), read 10 Nov 2026)
- None found on 10 Nov 2026: Headquarters address, headcount, seed amount, pricing and customer count on onit.security ([source](https://onit.security/company/), read 10 Nov 2026)
- Vendor's claim: Product category and names: Decision-Based Exposure Management, Decision Center; site title calls it an agentic exposure management and SecOps platform. ([source](https://onit.security/), read 10 Nov 2026)
- Third-party source: Name caution: onit.com is an unrelated legal operations software company, not Onit Security. ([source](https://www.onit.com/), read 10 Nov 2026)
## Links
- [Side by side](/compare/): Pairs of platforms, with the sourced facts in the same rows.
- [Onit Security on its own site](https://onit.security/)
## Related pages
- [The 14 platforms, listed alphabetically](/platforms/)
- [Qualys: what it is, what it does well and where it is limited](/platforms/qualys/)
- [Maze: what it is, what it does well and where it is limited](/platforms/maze/)
- [Rapid7: what it is, what it does well and where it is limited](/platforms/rapid7/)
## Sources
- Onit Security: onit.security/platform/: https://onit.security/platform/ (read 10 Nov 2026)
- Onit Security: onit.security/blog/reachable-vulnerabilities/: https://onit.security/blog/reachable-vulnerabilities/ (read 10 Nov 2026)
- Onit Security: onit.security/blog/ai-agents-vulnerability-management/: https://onit.security/blog/ai-agents-vulnerability-management/ (read 10 Nov 2026)
- Onit Security: onit.security/: https://onit.security/ (read 10 Nov 2026)
- Onit Security: onit.security/blog/zero-day-response/: https://onit.security/blog/zero-day-response/ (read 10 Nov 2026)
- Onit Security: onit.security/company/: https://onit.security/company/ (read 10 Nov 2026)
- onit.com: /: https://www.onit.com/ (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/platforms/onit/
---
# Qualys: what it is, what it does well and where it is limited
Platform profile, read 10 Nov 2026
**The short answer.** Qualys sells exposure/RBVM platform with remediation and agentic AI, as its pages read on 10 Nov 2026 describe it. 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.
## What it is
Exposure/RBVM platform with remediation and agentic AI.
## What it 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.
## Where it is 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.
## Facts read, by topic
Each line below carries a label, the page it was read on and the date. A vendor's claim is the vendor's own statement about itself; a third-party source is one that is not the vendor; a line that starts with none found says nothing was published on that date. Qualys has 37 lines on file, read up to 10 Nov 2026; the Qualys pages behind them are listed under Sources.
### Proves exploitability in your environment
- Vendor's claim: Agent Val uses TruConfirm to test whether an exposure is reachable and weaponizable by an attacker in the customer's environment. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
- Vendor's claim: After mitigation, the agent re-checks exploit validation and keeps an audit trail. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
- Vendor's claim: Qualys says validated exploitability narrows a large backlog to the 1% to fix now. ([source](https://www.qualys.com/apps/trurisk-eliminate/), read 10 Nov 2026)
- Vendor's claim: Agent Nyra maps weaponized CVEs to impacted assets and re-orders the risk backlog by active exploitation. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
- Vendor's claim: Qualys describes an agent-based extension of exploit validation to internal assets for attack-path coverage. ([source](https://www.qualys.com/post-mythos-autonomous-remediation), read 10 Nov 2026)
### Ships the fix
- Vendor's claim: TruRisk Eliminate 2.0 Agent Sara coordinates remediation across Qualys and third-party ecosystems to patch, mitigate, uninstall, or isolate hosts. ([source](https://www.qualys.com/apps/trurisk-eliminate/), read 10 Nov 2026)
- Vendor's claim: AI patch reliability scoring decides deployment approach: zero-touch for high confidence, ring-staged for medium, manual CAB for low. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
- Vendor's claim: When no patch exists, it runs patchless strategies such as mitigate, uninstall, custom script, fix, and isolate. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
- Vendor's claim: Automatic rollback if a deployment causes issues, and verification that the vulnerability is fixed rather than only the ticket closed. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
- Vendor's claim: Customers set policies, maintenance windows, and ring conditions; ServiceNow change integration keeps changes under existing approval. ([source](https://www.qualys.com/apps/trurisk-eliminate/), read 10 Nov 2026)
- Vendor's claim: TruRisk Eliminate 2.0 capabilities including patch reliability scoring and Remediation Waves were generally available as of October 1, 2026. ([source](https://blog.qualys.com/product-tech/2026/08/03/zero-day-remediation-operational-resiliency-trurisk-eliminate), read 10 Nov 2026)
### Finds the owner
- Vendor's claim: Qualys Patch Management lists bidirectional integrations with CMDB and ITSM tools. ([source](https://www.qualys.com/apps/patch-management/), read 10 Nov 2026)
- Vendor's claim: ETM positions remediation workflows with automated patching, IT tickets, and real-time alerts; no per-finding owner resolution (code owner or team mapping) was found. ([source](https://www.qualys.com/apps/enterprise-trurisk-management), read 10 Nov 2026)
- Vendor's claim: Cloud Workflow Automation is described as automating remediation workflows using asset criticality and blast radius. ([source](https://www.qualys.com/apps/enterprise-trurisk-management), read 10 Nov 2026)
### Speed on a new disclosure
- Vendor's claim: Agent Insta (scanless detection) claims real exposure within minutes of disclosure by correlating existing telemetry. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
- Vendor's claim: Qualys cites time-to-exploit collapsing from weeks to hours and positions its Risk Operations Center around that. ([source](https://www.qualys.com/post-mythos-autonomous-remediation), read 10 Nov 2026)
- Vendor's claim: Qualys published a blog on zero-day remediation and operational resiliency with TruRisk Eliminate (dated 2026-08-03 in URL). ([source](https://blog.qualys.com/product-tech/2026/08/03/zero-day-remediation-operational-resiliency-trurisk-eliminate), read 10 Nov 2026)
- Vendor's claim: Qualys cites Cintas patching the most severe threats automatically in under 24 hours. ([source](https://www.qualys.com/customers/success-stories/cintas-replaces-manual-patching-tasks-with-risk-based-from-qualys-enterprise-trurisk-platform), read 10 Nov 2026)
### Agents you can shape
- Vendor's claim: Qualys ships ready-made AI agents inside ETM: Agent Insta (detection), Agent Val (validation), Agent Sara (remediation), Agent Nyra (threat prioritization). ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
- Vendor's claim: ROCky is a conversational AI interface in the Risk Operations Center that queries exposure data and navigates remediation workflows. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
- Vendor's claim: Guardrails: confidence-gated waves, staged rollout, CAB for low-reliability patches, and automatic rollback. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
- Vendor's claim: Operational Resiliency watches system health through Qualys checks or partner integrations such as Dynatrace, pausing and rolling back if something looks wrong. ([source](https://www.qualys.com/apps/trurisk-eliminate/), read 10 Nov 2026)
- None found on 10 Nov 2026: Customer-built agents: none found on 2026-11-10 on the Qualys agentic AI page read (agents described are vendor-built). ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
### Works on the stack you have
- Vendor's claim: Qualys ETM consolidates data from on-premises, cloud, containers, identities, and applications. ([source](https://www.qualys.com/apps/enterprise-trurisk-management), read 10 Nov 2026)
- Vendor's claim: Qualys platform covers VMDR, CSAM, EASM, CSPM, KCS, CWP, IaC security, CIEM, SSPM, DSPM, and software supply chain risk. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
- Vendor's claim: Named integrations seen: ServiceNow (change) and Dynatrace (health checks). ([source](https://www.qualys.com/apps/trurisk-eliminate/), read 10 Nov 2026)
- Vendor's claim: Single-agent architecture covering on-premises, cloud and web applications. ([source](https://www.qualys.com/about-qualys), read 10 Nov 2026)
### Proof
- Vendor's claim: Cintas case study: replaced manual patching with Qualys VMDR, Patch Management, TruRisk and CSAM. ([source](https://www.qualys.com/customers/success-stories/cintas-replaces-manual-patching-tasks-with-risk-based-from-qualys-enterprise-trurisk-platform), read 10 Nov 2026)
- Vendor's claim: Qualys states 10,000+ subscription customers in 130+ countries. ([source](https://www.qualys.com/about-qualys), read 10 Nov 2026)
- Vendor's claim: Qualys states it participates in Project Glasswing with Anthropic's Claude Mythos Preview. ([source](https://www.qualys.com/about-qualys), read 10 Nov 2026)
- Vendor's claim: Qualys cites a customer cutting remediation times from weeks to minutes (unnamed, no method published on the page). ([source](https://www.qualys.com/apps/trurisk-eliminate/), read 10 Nov 2026)
- Vendor's claim: Qualys pages cite Verizon 2026 DBIR statistics; no published method for Qualys's own remediation time claims was found on the pages read. ([source](https://www.qualys.com/post-mythos-autonomous-remediation), read 10 Nov 2026)
## Profile facts
- Vendor's claim: Qualys, Inc. is publicly traded on NASDAQ as QLYS and still operates under the Qualys name. ([source](https://www.qualys.com/about-qualys), read 10 Nov 2026)
- Vendor's claim: Qualys says it is one of the first SaaS security vendors, since 1999. ([source](https://www.qualys.com/about-qualys), read 10 Nov 2026)
- Vendor's claim: Qualys describes itself as a unified platform to power a risk operations center, with a majority of the Forbes Global 100 and Fortune 100 as customers. ([source](https://www.qualys.com/about-qualys), read 10 Nov 2026)
- Vendor's claim: Products: Enterprise TruRisk Management (ETM), TruRisk Eliminate 2.0, Patch Management, TruConfidence engine, ROCky, Agent Insta/Val/Sara/Nyra. ([source](https://www.qualys.com/apps/trurisk-eliminate/), read 10 Nov 2026)
- Vendor's claim: Pricing: none found on the Qualys product pages read (free trial offered for TruRisk Eliminate); funding and headcount none found. ([source](https://blog.qualys.com/product-tech/2026/08/03/zero-day-remediation-operational-resiliency-trurisk-eliminate), read 10 Nov 2026)
## Links
- [Side by side](/compare/): Pairs of platforms, with the sourced facts in the same rows.
- [Qualys on its own site](https://www.qualys.com/)
## Related pages
- [The 14 platforms, listed alphabetically](/platforms/)
- [Rapid7: what it is, what it does well and where it is limited](/platforms/rapid7/)
- [Onit Security: what it is, what it does well and where it is limited](/platforms/onit/)
- [Rival Security: what it is, what it does well and where it is limited](/platforms/rival/)
## Sources
- Qualys: www.qualys.com/apps/agentic-ai: https://www.qualys.com/apps/agentic-ai (read 10 Nov 2026)
- Qualys: www.qualys.com/apps/trurisk-eliminate/: https://www.qualys.com/apps/trurisk-eliminate/ (read 10 Nov 2026)
- Qualys: www.qualys.com/post-mythos-autonomous-remediation: https://www.qualys.com/post-mythos-autonomous-remediation (read 10 Nov 2026)
- Qualys: blog.qualys.com/product-tech/2026/08/03/zero-day-remediation-operational-resilie: https://blog.qualys.com/product-tech/2026/08/03/zero-day-remediation-operational-resiliency-trurisk-eliminate (read 10 Nov 2026)
- Qualys: www.qualys.com/apps/patch-management/: https://www.qualys.com/apps/patch-management/ (read 10 Nov 2026)
- Qualys: www.qualys.com/apps/enterprise-trurisk-management: https://www.qualys.com/apps/enterprise-trurisk-management (read 10 Nov 2026)
- Qualys: www.qualys.com/customers/success-stories/cintas-replaces-manual-patching-tasks-w: https://www.qualys.com/customers/success-stories/cintas-replaces-manual-patching-tasks-with-risk-based-from-qualys-enterprise-trurisk-platform (read 10 Nov 2026)
- Qualys: www.qualys.com/about-qualys: https://www.qualys.com/about-qualys (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/platforms/qualys/
---
# Rapid7: what it is, what it does well and where it is limited
Platform profile, read 10 Nov 2026
**The short answer.** Rapid7 sells exposure/RBVM platform with remediation workflows, as its pages read on 10 Nov 2026 describe it. 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. Every line below carries its source and the date it was read.
## What it is
Exposure/RBVM platform with remediation workflows.
## What it 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.
## Where it is 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.
## Facts read, by topic
Each line below carries a label, the page it was read on and the date. A vendor's claim is the vendor's own statement about itself; a third-party source is one that is not the vendor; a line that starts with none found says nothing was published on that date. Rapid7 has 31 lines on file, read up to 10 Nov 2026; the Rapid7 pages behind them are listed under Sources.
### Proves exploitability in your environment
- Vendor's claim: Exposure Command prioritizes using exploit likelihood, reachability, severity, and business context. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
- Vendor's claim: Exposure Command tier adds attack path analysis and contextual risk prioritization. ([source](https://www.rapid7.com/products/command/pricing/), read 10 Nov 2026)
- Vendor's claim: Exposure Command provides a risk score based on toxic combinations plus internal and external views. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
- Vendor's claim: Rapid7 describes a threat-aware active risk score in the Essentials tier. ([source](https://www.rapid7.com/products/command/pricing/), read 10 Nov 2026)
- Vendor's claim: Rapid7's Gartner-report blog says its VM brings attack-surface visibility, threat intelligence, business context, and attack-path analysis together. ([source](https://www.rapid7.com/blog/post/ai-gartner-report-attack-paths-closing-faster-than-patchable/), read 10 Nov 2026)
### Ships the fix
- Vendor's claim: Exposure Command offers no-code native automation for automated remediation. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
- Vendor's claim: Exposure Command lists automated remediation workflows and automated cloud remediation as tier features. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
- Vendor's claim: Rapid7 says built-in remediation workflows give AI-powered remediation guidance, automation, and team workflows; the page does not say a tested PR or virtual patch is produced. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
- Vendor's claim: Rapid7's own analysis says reducing exposure still requires teams to choose the remediation or compensating control and verify the result. ([source](https://www.rapid7.com/blog/post/ai-gartner-report-attack-paths-closing-faster-than-patchable/), read 10 Nov 2026)
### Finds the owner
- Vendor's claim: Essentials tier includes remediation projects and SLAs. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
- Vendor's claim: Automated notification and ticketing gives developers real-time feedback. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
- None found on 10 Nov 2026: Per-finding resolution to an owning team (for example from code owners or cloud tags): none found on 2026-11-10 on the Exposure Command page read. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
### Speed on a new disclosure
- Vendor's claim: For Ivanti Connect Secure zero-days, Rapid7 stated authenticated vulnerability checks were available since the 2026-10-30 content release (the day CISA added them to KEV). ([source](https://www.rapid7.com/blog/post/etr-additional-ivanti-connect-secure-zero-days-exploited-in-the-wild-cve-2026-111357-cve-2026-118527/), read 10 Nov 2026)
- Vendor's claim: Rapid7 runs an Emergent Threat Response blog stream for high-priority threats. ([source](https://www.rapid7.com/blog/tag/emergent-threat-response/), read 10 Nov 2026)
- Vendor's claim: Rapid7 Q3 2026 threat update says three days is the average time from high-severity vulnerability disclosure to exploitation. ([source](https://www.rapid7.com/blog/post/tr-q3-2026-threat-update-attackers-exploiting-vulnerabilities-within-3-days/), read 10 Nov 2026)
### Agents you can shape
- Vendor's claim: Rapid7 references AI-powered remediation guidance in Exposure Command and human-centric AI in its SOC offering; no controls model for agents was documented. ([source](https://www.rapid7.com/solutions/ai-powered-security-operations-soc/), read 10 Nov 2026)
- Vendor's claim: Rapid7 reports internal practitioner exploration of Claude Mythos Preview through Project Glasswing. ([source](https://www.rapid7.com/blog/post/ai-gartner-report-attack-paths-closing-faster-than-patchable/), read 10 Nov 2026)
- None found on 10 Nov 2026: Agentic remediation features, Remediation Hub, or ready-made or customer-built AI agents for exposure management: none found on 2026-11-10 on the Exposure Command, InsightVM, pricing, or AI-SOC pages read (the word agentic did not appear). ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
### Works on the stack you have
- Vendor's claim: Exposure Command lists 500+ integrations across cloud, identity, ITSM, ticketing, EDR, and CI/CD. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
- Vendor's claim: Cloud coverage includes AWS, Azure, GCP, and Kubernetes, plus Oracle Cloud and Alibaba Cloud in the extended tier. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
- Vendor's claim: Exposure Command adds infrastructure-as-code scanning and DAST. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
- Vendor's claim: Exposure Command correlates third-party findings with Rapid7 vulnerability telemetry. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
### Proof
- Vendor's claim: Rapid7 states more than 11,500 customers. ([source](https://www.rapid7.com/about/), read 10 Nov 2026)
- Vendor's claim: Rapid7 was placed in the upper-right quadrant of the 2025 Gartner Magic Quadrant (vendor's claim) for Exposure Assessment Platforms. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
- Vendor's claim: Americor customer story: Rapid7 universal agent gave up-to-date vulnerability understanding. ([source](https://www.rapid7.com/customers/americor/), read 10 Nov 2026)
- Vendor's claim: Rapid7 publishes a quarterly threat landscape report and Metasploit wrap-ups as research output. ([source](https://www.rapid7.com/blog/), read 10 Nov 2026)
## Profile facts
- Vendor's claim: Rapid7 is an exposure and detection company with Exposure Command (including an Essentials tier) and Surface Command on its Command Platform. ([source](https://www.rapid7.com/products/command/pricing/), read 10 Nov 2026)
- Vendor's claim: Pricing: no list prices on the pricing page read; it describes usage-based pricing by asset type. ([source](https://www.rapid7.com/products/command/pricing/), read 10 Nov 2026)
- Vendor's claim: InsightVM is folded into the Exposure Command packaging, with a page asking whether InsightVM is still available. ([source](https://www.rapid7.com/products/insightvm/), read 10 Nov 2026)
- Vendor's claim: Rapid7 was recognized by the Boston Business Journal as one of the Boston Business Journal's listed Places to Work for the 14th consecutive year (headquarters not stated on the page). ([source](https://www.rapid7.com/about/news/), read 10 Nov 2026)
- None found on 10 Nov 2026: Founded year, funding, headcount, acquisitions: none found on the Rapid7 pages read. ([source](https://www.rapid7.com/about/), read 10 Nov 2026)
## Links
- [Side by side](/compare/): Pairs of platforms, with the sourced facts in the same rows.
- [Rapid7 on its own site](https://www.rapid7.com/)
## Related pages
- [The 14 platforms, listed alphabetically](/platforms/)
- [Rival Security: what it is, what it does well and where it is limited](/platforms/rival/)
- [Qualys: what it is, what it does well and where it is limited](/platforms/qualys/)
- [Seemplicity: what it is, what it does well and where it is limited](/platforms/seemplicity/)
## Sources
- Rapid7: www.rapid7.com/products/command/exposure-management/: https://www.rapid7.com/products/command/exposure-management/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/products/command/pricing/: https://www.rapid7.com/products/command/pricing/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/blog/post/ai-gartner-report-attack-paths-closing-faster-than-patc: https://www.rapid7.com/blog/post/ai-gartner-report-attack-paths-closing-faster-than-patchable/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/blog/post/etr-additional-ivanti-connect-secure-zero-days-exploite: https://www.rapid7.com/blog/post/etr-additional-ivanti-connect-secure-zero-days-exploited-in-the-wild-cve-2026-111357-cve-2026-118527/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/blog/tag/emergent-threat-response/: https://www.rapid7.com/blog/tag/emergent-threat-response/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/blog/post/tr-q3-2026-threat-update-attackers-exploiting-vulnerabi: https://www.rapid7.com/blog/post/tr-q3-2026-threat-update-attackers-exploiting-vulnerabilities-within-3-days/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/solutions/ai-powered-security-operations-soc/: https://www.rapid7.com/solutions/ai-powered-security-operations-soc/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/about/: https://www.rapid7.com/about/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/customers/americor/: https://www.rapid7.com/customers/americor/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/blog/: https://www.rapid7.com/blog/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/products/insightvm/: https://www.rapid7.com/products/insightvm/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/about/news/: https://www.rapid7.com/about/news/ (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/platforms/rapid7/
---
# Rival Security: what it is, what it does well and where it is limited
Platform profile, read 10 Nov 2026
**The short answer.** Rival Security sells agentic security platform / agent harness for vulnerability management, code and cloud security, as its pages read on 10 Nov 2026 describe it. 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.
## What it is
Agentic security platform / agent harness for vulnerability management, code and cloud security.
## What it 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.
## Where it is 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.
## Facts read, by topic
Each line below carries a label, the page it was read on and the date. A vendor's claim is the vendor's own statement about itself; a third-party source is one that is not the vendor; a line that starts with none found says nothing was published on that date. Rival Security has 40 lines on file, read up to 10 Nov 2026; the Rival Security pages behind them are listed under Sources.
### Proves exploitability in your environment
- Vendor's claim: Home page lists a Triage Exploitability agent that determines what is actually exploitable in the customer environment. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: Use-cases page says Rival reads every scanner finding against the real environment and keeps only those that can cause harm; it cites a 94.6% reduction in findings. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: Home page reports 98% of findings proven unexploitable, 87% faster remediation and 1.5 hours to first value (no method given on the page). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: In its PHP2Shell write-up, Rival says agents ordered services to fix by reachability, internet-exposed unauthenticated workloads first. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: Home page lists red team simulation as a subagent in the harness. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
### Ships the fix
- Vendor's claim: Home page lists an Autonomous Remediation agent that generates and ships tested fixes. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: Use-cases page describes the remediation flow as plan, test, and open a pull request for human review. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: Rival lists a WAF mitigation agent that checks whether a WAF blocks exploitation and adjusts it. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: Rival describes an alternative-remediation agent for legacy apps that plans a fix without upgrading libraries. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: The PHP2Shell write-up says agents can open pull requests, suggest WAF rules and apply configurations. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: Use-cases page shows a CI/CD agent that blocks only exploitable issues in pull requests and image pushes. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
### Finds the owner
- Vendor's claim: Home page lists an Ownership Resolution agent that maps each finding to the team that can fix it. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: Use-cases page says the owner-finding agent weighs root cause, team structure and past history (memories). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: PHP2Shell write-up says agents can message the relevant employees, and the harness lists human follow-ups. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
### Speed on a new disclosure
- Vendor's claim: Home page lists a 0-day Fast Response agent covering triage through remediation. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: Use-cases page describes 0-day rapid response as finding exposure across code, images and cloud and prioritizing what to do first (page also claims a drop from days to minutes). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: Published response write-up: for PHP2Shell, agents were triaging customer environments hours before scanners could detect the CVEs. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: The same write-up reports scanning more than 80,000 repositories within hours. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: In one unnamed customer, the PHP2Shell triage agent found 60 PHP repositories, 29 potentially vulnerable. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
### Agents you can shape
- Vendor's claim: Rival offers ready-made agents that can be customized and extended. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: Rival engineers build custom agents for the customer environment at no additional cost (Partner tier). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: Customers can build their own agents on the harness. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: Home page says 64+ more agents are available beyond the five featured. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: Guardrail: agents run in a sandbox hosted by Rival or self-hosted by the customer. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: Published docs are not readable: docs.rival.security returns a password prompt, so approval-gate and permission controls could not be verified. ([source](https://docs.rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
### Works on the stack you have
- Vendor's claim: Home page names cloud, code host and infrastructure integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: Home page names scanner, control and task integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: Use-cases table shows findings sourced from Wiz, Qualys, GitHub, a pentest, and Rival's own SCA and Code scanners. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: Agents combine connected services with a Rival Security Knowledge Graph. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
### Proof
- Vendor's claim: Use-cases page claims 13M+ agent runs. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: Rival published SASTBench, a benchmark for SAST triage using real CVEs as true positives and filtered SAST findings as noise. ([source](https://rival.security/blog/sastbench-measuring-ai-security-automation?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: Research blog post claims Rival workflows outperform current frontier models on the Spider 2.0 benchmark. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: Published incident write-up (PHP2Shell, Nov 2, 2026) with unnamed customer results. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- None found on 10 Nov 2026: Named customers, logos, case studies or testimonials on the home page, use-cases page, blog index or guides. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
## Profile facts
- Vendor's claim: Tagline and category: Rival describes itself as an agent harness for cybersecurity. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- Vendor's claim: Research blog launched Feb 2025 describing early experiments building AI systems for cybersecurity. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- None found on 10 Nov 2026: Pricing (rival.security/pricing returns 404; book-a-demo form only). ([source](https://rival.security/book-a-demo-form?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- None found on 10 Nov 2026: Funding, investors, founders, headcount, HQ or founding year on home, blog, careers, book-a-demo pages. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- None found on 10 Nov 2026: Open roles on the careers page (application form only). ([source](https://rival.security/careers?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
- None found on 10 Nov 2026: Customer count or total module count (home page cites 64+ additional agents). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform), read 10 Nov 2026)
## Links
- [Side by side](/compare/): Pairs of platforms, with the sourced facts in the same rows.
- [Rival Security on its own site](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=platform)
## Related pages
- [The 14 platforms, listed alphabetically](/platforms/)
- [Seemplicity: what it is, what it does well and where it is limited](/platforms/seemplicity/)
- [Rapid7: what it is, what it does well and where it is limited](/platforms/rapid7/)
- [Tenable: what it is, what it does well and where it is limited](/platforms/tenable/)
## Sources
- Rival Security: rival.security/: https://rival.security/ (read 10 Nov 2026)
- Rival Security: rival.security/use-cases: https://rival.security/use-cases (read 10 Nov 2026)
- Rival Security: rival.security/blog/php2shell-black-october-2026: https://rival.security/blog/php2shell-black-october-2026 (read 10 Nov 2026)
- Rival Security: docs.rival.security: https://docs.rival.security (read 10 Nov 2026)
- Rival Security: rival.security/blog/sastbench-measuring-ai-security-automation: https://rival.security/blog/sastbench-measuring-ai-security-automation (read 10 Nov 2026)
- Rival Security: rival.security/blog: https://rival.security/blog (read 10 Nov 2026)
- Rival Security: rival.security/book-a-demo-form: https://rival.security/book-a-demo-form (read 10 Nov 2026)
- Rival Security: rival.security/careers: https://rival.security/careers (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/platforms/rival/
---
# Seemplicity: what it is, what it does well and where it is limited
Platform profile, read 10 Nov 2026
**The short answer.** Seemplicity sells agentic exposure management and response (RBVM/CTEM workflow with AI analysts), as its pages read on 10 Nov 2026 describe it. 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.
## What it is
Agentic exposure management and response (RBVM/CTEM workflow with AI analysts).
## What it 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.
## Where it is 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.
## Facts read, by topic
Each line below carries a label, the page it was read on and the date. A vendor's claim is the vendor's own statement about itself; a third-party source is one that is not the vendor; a line that starts with none found says nothing was published on that date. Seemplicity has 41 lines on file, read up to 10 Nov 2026; the Seemplicity pages behind them are listed under Sources.
### Proves exploitability in your environment
- Vendor's claim: AI Analysts run structured exploitability investigations inside the remediation workflow. ([source](https://seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/), read 10 Nov 2026)
- Vendor's claim: Inputs: live runtime configuration, exploit prerequisites, network reachability, code and dependency usage, compensating controls. ([source](https://seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/), read 10 Nov 2026)
- Vendor's claim: Live EDR telemetry from CrowdStrike and Microsoft Defender evaluates protections per asset (Jun 3, 2026). ([source](https://seemplicity.ai/news/live-edr-context-agentic-exposure-management/), read 10 Nov 2026)
- Vendor's claim: Preliminary deployments: majority of high-severity findings judged not exploitable (no counts given). ([source](https://seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/), read 10 Nov 2026)
- Vendor's claim: Validation agents determine realistic exploitability. ([source](https://seemplicity.ai/platform/agentic-workforce/), read 10 Nov 2026)
### Ships the fix
- Vendor's claim: Response Options (Sep 2, 2026) give alternatives to a full patch: compensating controls and targeted configuration changes. ([source](https://seemplicity.ai/news/response-options/), read 10 Nov 2026)
- Vendor's claim: Each option carries a Readiness Indicator (deploy now or review first); AI Analysts pre-select a recommendation and all alternatives stay visible. ([source](https://seemplicity.ai/news/response-options/), read 10 Nov 2026)
- Vendor's claim: Code Analyst reads source from GitHub, GitLab and other repositories and hands developers a scoped, ready-to-apply fix. ([source](https://seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/), read 10 Nov 2026)
- Vendor's claim: Remediation agents provide step-by-step guidance and ownership mapping; delivery is into existing workflows (guidance and tickets). ([source](https://seemplicity.ai/platform/agentic-workforce/), read 10 Nov 2026)
- Vendor's claim: Fix verification and SLA tracking automated. ([source](https://seemplicity.ai/automated-vulnerability-remediation/), read 10 Nov 2026)
### Finds the owner
- Vendor's claim: Automatically assigns remediation to owners and delivers fix-ready guidance into existing workflows. ([source](https://seemplicity.ai/), read 10 Nov 2026)
- Vendor's claim: Hertz: unknown asset ownership fell from 20% to 2% in six months. ([source](https://seemplicity.ai/resource/hertz-case-study/), read 10 Nov 2026)
- Vendor's claim: Owners and criticality identified by syncing with CMDBs. ([source](https://seemplicity.ai/automated-vulnerability-remediation/), read 10 Nov 2026)
- Vendor's claim: Host Analyst surfaces the likely owner. ([source](https://seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/), read 10 Nov 2026)
- Vendor's claim: Tickets updated or expired as ephemeral resources change. ([source](https://seemplicity.ai/automated-vulnerability-remediation/), read 10 Nov 2026)
### Speed on a new disclosure
- Vendor's claim: SCA Analyst powers SBOM-driven zero-day response before scanner signatures exist. ([source](https://seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/), read 10 Nov 2026)
- Vendor's claim: Home page claims discovery to remediation in seconds (no method). ([source](https://seemplicity.ai/), read 10 Nov 2026)
- Vendor's claim: MTTR reduction claim of 90% on the remediation workflow page. ([source](https://seemplicity.ai/automated-vulnerability-remediation/), read 10 Nov 2026)
- None found on 10 Nov 2026: A published time-to-answer measurement for a specific new CVE disclosure on seemplicity.ai pages read ([source](https://seemplicity.ai/news/), read 10 Nov 2026)
### Agents you can shape
- Vendor's claim: Ready-made autonomous SAST, SCA and Host Analysts work around the clock. ([source](https://seemplicity.ai/platform/agentic-workforce/), read 10 Nov 2026)
- Vendor's claim: Four agent families: validation, context, strategy, remediation. ([source](https://seemplicity.ai/platform/agentic-workforce/), read 10 Nov 2026)
- Vendor's claim: Seema conversational assistant for exposure questions. ([source](https://seemplicity.ai/), read 10 Nov 2026)
- Vendor's claim: Controls: transparent reasoning trails, visible alternatives, and customer-built approval gates in workflows. ([source](https://seemplicity.ai/customers/), read 10 Nov 2026)
- Vendor's claim: Customer-configurable workflows from ready-to-use templates. ([source](https://seemplicity.ai/automated-vulnerability-remediation/), read 10 Nov 2026)
- None found on 10 Nov 2026: Customer-authored custom AI agents on seemplicity.ai pages read ([source](https://seemplicity.ai/platform/agentic-workforce/), read 10 Nov 2026)
### Works on the stack you have
- Vendor's claim: Integration page claims hundreds of integrations. ([source](https://seemplicity.ai/integrations/), read 10 Nov 2026)
- Vendor's claim: Scanners and CNAPP named: Qualys, Rapid7, Tenable products, Wiz, Orca, Prisma Cloud. ([source](https://seemplicity.ai/integrations/), read 10 Nov 2026)
- Vendor's claim: Ticketing and dev tooling named in the integrations list include Azure DevOps (also GitHub, GitLab, Jira per the same list). ([source](https://seemplicity.ai/integrations/), read 10 Nov 2026)
- Vendor's claim: ServiceNow CMDB is a named integration (list also includes ServiceNow, Slack, Teams, Snyk, SentinelOne Singularity). ([source](https://seemplicity.ai/integrations/), read 10 Nov 2026)
### Proof
- Vendor's claim: Hertz case study: critical remediation up 400%. ([source](https://seemplicity.ai/resource/hertz-case-study/), read 10 Nov 2026)
- Vendor's claim: Named customer quotes: Omnissa, OpenWeb, X-Press Feeders; OpenWeb reports 85% fewer tickets. ([source](https://seemplicity.ai/customers/), read 10 Nov 2026)
- Vendor's claim: Average claims: 57% scanner noise reduction and $1.7M annual savings (aggregate, method not on page). ([source](https://seemplicity.ai/), read 10 Nov 2026)
- Vendor's claim: Research: 2026 Exposure Action Report on 2025 customer data; April 2026 survey report (88% use AI, 31% trust it). ([source](https://seemplicity.ai/), read 10 Nov 2026)
- Vendor's claim: Gartner recognition across four 2026 reports (per vendor). ([source](https://seemplicity.ai/news/), read 10 Nov 2026)
## Profile facts
- Vendor's claim: Founded 2020 by Yoran Sirkis, Ravid Circus, Rotem Cohen Gadol. ([source](https://seemplicity.ai/about/), read 10 Nov 2026)
- Vendor's claim: Funding: $26M Series A and $50M Series B led by Sienna Venture Capital; more than $63M raised per the CEO bio. ([source](https://seemplicity.ai/about/), read 10 Nov 2026)
- Vendor's claim: Series A $26M backed by Glilot Capital, NTTVC, Atlantic Bridge, S Capital, Rain Capital. ([source](https://seemplicity.ai/about/), read 10 Nov 2026)
- Vendor's claim: HQ address San Jose, CA, with Tel Aviv office. ([source](https://seemplicity.ai/platform/agentic-workforce/), read 10 Nov 2026)
- Vendor's claim: Platform names: Agentic Exposure Action Platform, AI Analysts, Seema; processes up to 1.5 billion findings daily. ([source](https://seemplicity.ai/), read 10 Nov 2026)
- Vendor's claim: Domain note: seemplicity.io redirects to seemplicity.ai; page title shows current branding. ([source](https://seemplicity.ai/), read 10 Nov 2026)
- None found on 10 Nov 2026: Pricing and headcount on seemplicity.ai pages read ([source](https://seemplicity.ai/platform/agentic-workforce/), read 10 Nov 2026)
## Links
- [Side by side](/compare/): Pairs of platforms, with the sourced facts in the same rows.
- [Seemplicity on its own site](https://seemplicity.ai/)
## Related pages
- [The 14 platforms, listed alphabetically](/platforms/)
- [Tenable: what it is, what it does well and where it is limited](/platforms/tenable/)
- [Rival Security: what it is, what it does well and where it is limited](/platforms/rival/)
- [Vicarius: what it is, what it does well and where it is limited](/platforms/vicarius/)
## Sources
- Seemplicity: seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/: https://seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/news/live-edr-context-agentic-exposure-management/: https://seemplicity.ai/news/live-edr-context-agentic-exposure-management/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/platform/agentic-workforce/: https://seemplicity.ai/platform/agentic-workforce/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/news/response-options/: https://seemplicity.ai/news/response-options/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/automated-vulnerability-remediation/: https://seemplicity.ai/automated-vulnerability-remediation/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/: https://seemplicity.ai/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/resource/hertz-case-study/: https://seemplicity.ai/resource/hertz-case-study/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/news/: https://seemplicity.ai/news/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/customers/: https://seemplicity.ai/customers/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/integrations/: https://seemplicity.ai/integrations/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/about/: https://seemplicity.ai/about/ (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/platforms/seemplicity/
---
# Tenable: what it is, what it does well and where it is limited
Platform profile, read 10 Nov 2026
**The short answer.** Tenable sells exposure management platform with remediation and agentic orchestration, as its pages read on 10 Nov 2026 describe it. 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.
## What it is
Exposure management platform with remediation and agentic orchestration.
## What it 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.
## Where it is 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.
## Facts read, by topic
Each line below carries a label, the page it was read on and the date. A vendor's claim is the vendor's own statement about itself; a third-party source is one that is not the vendor; a line that starts with none found says nothing was published on that date. Tenable has 39 lines on file, read up to 10 Nov 2026; the Tenable pages behind them are listed under Sources.
### Proves exploitability in your environment
- Vendor's claim: Tenable One attack path analysis shows how attackers could move across the customer's environment, with more than 150 supported attack techniques. ([source](https://www.tenable.com/products/tenable-one), read 10 Nov 2026)
- Vendor's claim: Exposure prioritization claims to weigh business context and compensating control visibility, not just a generic score. ([source](https://www.tenable.com/products/tenable-one/capabilities/exposure-prioritization), read 10 Nov 2026)
- Vendor's claim: Tenable uses a vendor-built Vulnerability Priority Rating (VPR) that incorporates threat intelligence and weaponization signals. ([source](https://www.tenable.com/products/vulnerability-management), read 10 Nov 2026)
- Vendor's claim: Tenable says its patented machine learning models focus teams on the small share of vulnerabilities most likely to be exploited. ([source](https://www.tenable.com/products/tenable-one), read 10 Nov 2026)
- Vendor's claim: Tenable One normalizes risk scores across domains and identifies toxic risk combinations and choke points on attack paths to critical assets. ([source](https://www.tenable.com/products/tenable-one/capabilities/exposure-prioritization), read 10 Nov 2026)
### Ships the fix
- Vendor's claim: Tenable Hexa AI automated remediation schedules reason through vulnerabilities, create tickets, connect with patch tools, and trigger a scan when a ticket closes. ([source](https://www.tenable.com/products/tenable-one/capabilities/hexa-ai), read 10 Nov 2026)
- Vendor's claim: Tenable Patch Management applies policy-based autonomous patching with the ability to schedule, pause, or roll back deployments. ([source](https://www.tenable.com/products/patch-management), read 10 Nov 2026)
- Vendor's claim: Patch policies set the level of autonomy and can use different SLAs by criticality and exploitability. ([source](https://www.tenable.com/products/patch-management), read 10 Nov 2026)
- Vendor's claim: Tenable Patch Management cites 250k+ patches covered and correlates each vulnerability to the most suitable superseding patch. ([source](https://www.tenable.com/products/patch-management), read 10 Nov 2026)
- Vendor's claim: Tenable Patch Management requires an existing license for a Tenable vulnerability or exposure product. ([source](https://www.tenable.com/products/vulnerability-management), read 10 Nov 2026)
- Vendor's claim: Tenable says Hexa AI keeps experts in control with built-in human-in-the-loop approvals. ([source](https://www.tenable.com/data-sheets/tenable-hexa-ai-the-agentic-engine-for-tenable-one-exposure-management), read 10 Nov 2026)
### Finds the owner
- Vendor's claim: Tenable One integrates exposure alerts with manual or automated ticketing workflows to improve accountability among IT, cloud, and security teams. ([source](https://www.tenable.com/products/tenable-one/pricing), read 10 Nov 2026)
- Vendor's claim: Tenable Patch Management gives a separate console so each team can see remediation progress and compliance status. ([source](https://www.tenable.com/products/patch-management), read 10 Nov 2026)
- None found on 10 Nov 2026: No documented feature that resolves each finding to a named owning team (for example from CODEOWNERS or cloud tags) was found; the owner-related claim is ticketing integration only. ([source](https://www.tenable.com/about-tenable/about-us), read 10 Nov 2026)
### Speed on a new disclosure
- Third-party source: Tenable publishes a CVE page of newly disclosed vulnerabilities with exploitation status and patch guidance, for example OpenSSH exploitation attempts within hours of disclosure. ([source](https://www.tenable.com/cve), read 10 Nov 2026)
- Vendor's claim: Tenable Hexa AI can run scheduled agent fleets for daily vulnerability triage without human delay. ([source](https://www.tenable.com/products/tenable-one/capabilities/hexa-ai), read 10 Nov 2026)
- Vendor's claim: Tenable ties its agentic push to shrinking time between disclosure and exploit; no measured time-to-answer for a new CVE was found. ([source](https://www.tenable.com/press-releases/tenable-partners-with-anthropic-for-ai-driven-exposure-management), read 10 Nov 2026)
### Agents you can shape
- Vendor's claim: Tenable Hexa AI is the agentic engine of Tenable One and orchestrates a fleet of specialized AI agents. ([source](https://www.tenable.com/products/tenable-one/capabilities/hexa-ai), read 10 Nov 2026)
- Vendor's claim: Tenable One offers built-in, third-party, and customer-built agents. ([source](https://www.tenable.com/products/tenable-one), read 10 Nov 2026)
- Vendor's claim: Hexa AI MCP server lets customers bring their own LLMs and build custom workflows over Tenable tools. ([source](https://www.tenable.com/products/tenable-one/capabilities/hexa-ai), read 10 Nov 2026)
- Vendor's claim: Guardrails: Hexa AI operates within established guardrails, human-in-the-loop design, and logs every action for audit. ([source](https://www.tenable.com/products/tenable-one/capabilities/hexa-ai), read 10 Nov 2026)
- Vendor's claim: Tenable runs the CyberAgents Exchange, a free open-source directory of agents, skills, MCP servers, and playbooks; Tenable One Foundation or Advanced customers can deploy agents using the Hexa AI MCP server. ([source](https://www.tenable.com/cyberagents-exchange), read 10 Nov 2026)
- Vendor's claim: Tenable announced a partnership with Anthropic for Claude-powered workflows in Hexa AI covering prioritization, remediation orchestration, and exposure analysis. ([source](https://www.tenable.com/press-releases/tenable-partners-with-anthropic-for-ai-driven-exposure-management), read 10 Nov 2026)
### Works on the stack you have
- Vendor's claim: Tenable One connectors consolidate third-party data including CrowdStrike, Qualys, Rapid7, Wiz, Armis, and Cortex XDR. ([source](https://www.tenable.com/products/tenable-one/connectors), read 10 Nov 2026)
- Vendor's claim: Tenable One ingests Rapid7 asset and vulnerability data through a connector. ([source](https://www.tenable.com/products/tenable-one/connectors), read 10 Nov 2026)
- Vendor's claim: Tenable One coverage spans IT, OT/IoT, cloud, AI assets, containers, web apps, code repositories, and identity systems. ([source](https://www.tenable.com/products/tenable-one), read 10 Nov 2026)
- Vendor's claim: An Open Connector ingests data from additional tools, internal systems, spreadsheets, or files. ([source](https://www.tenable.com/products/tenable-one/connectors), read 10 Nov 2026)
### Proof
- Vendor's claim: Tenable cites more than 40,000 customers. ([source](https://www.tenable.com/about-tenable/about-us), read 10 Nov 2026)
- Vendor's claim: Bernalillo County case study: freed 75% of its cybersecurity team from manual patching. ([source](https://www.tenable.com/customers), read 10 Nov 2026)
- Vendor's claim: Tenable's customers page lists Volpara Health Technologies, Virginia Tech, Chubu Electric Power Grid, and Public Utility District No. 1 of Whatcom County among others. ([source](https://www.tenable.com/customers), read 10 Nov 2026)
- Vendor's claim: Tenable cites a Gainwell Technologies CISO testimonial on Tenable One. ([source](https://www.tenable.com/products/tenable-one), read 10 Nov 2026)
- Vendor's claim: Tenable product page cites measured outcomes without a published method (reduction in tickets via contextual prioritization). ([source](https://www.tenable.com/products/tenable-one), read 10 Nov 2026)
## Profile facts
- Vendor's claim: Tenable Holdings, Inc. is publicly traded on NASDAQ as TENB. ([source](https://www.tenable.com/press-releases/tenable-partners-with-anthropic-for-ai-driven-exposure-management), read 10 Nov 2026)
- Vendor's claim: Tenable calls itself the exposure management company; flagship product is Tenable One, with Hexa AI as its agentic engine. ([source](https://www.tenable.com/press-releases/tenable-partners-with-anthropic-for-ai-driven-exposure-management), read 10 Nov 2026)
- Vendor's claim: Tenable has co-CEOs Steve Vintz and Mark Thurmond. ([source](https://www.tenable.com/about-tenable/about-us), read 10 Nov 2026)
- Vendor's claim: Product line includes Tenable One, Vulnerability Management, Security Center, Patch Management, Enclave Security, Cloud Exposure, Identity Exposure, and Attack Surface Management. ([source](https://www.tenable.com/customers), read 10 Nov 2026)
- Vendor's claim: Tenable One pricing page lists capabilities and add-ons (cloud-native application protection, AI user and app governance, identity security) but no prices; pricing none found on the page read. ([source](https://www.tenable.com/products/tenable-one/pricing), read 10 Nov 2026)
- None found on 10 Nov 2026: ExposureAI: the name ExposureAI did not appear on the Tenable pages read; the current agentic product name on the site is Tenable Hexa AI (a rename is not stated on these pages). ([source](https://www.tenable.com/products/tenable-one/capabilities/hexa-ai), read 10 Nov 2026)
- None found on 10 Nov 2026: Founded year, headquarters, funding, and headcount: none found on the Tenable About page read. ([source](https://www.tenable.com/about-tenable/about-us), read 10 Nov 2026)
## Links
- [Side by side](/compare/): Pairs of platforms, with the sourced facts in the same rows.
- [Tenable on its own site](https://www.tenable.com/)
## Related pages
- [The 14 platforms, listed alphabetically](/platforms/)
- [Vicarius: what it is, what it does well and where it is limited](/platforms/vicarius/)
- [Seemplicity: what it is, what it does well and where it is limited](/platforms/seemplicity/)
- [Zafran: what it is, what it does well and where it is limited](/platforms/zafran/)
## Sources
- Tenable: www.tenable.com/products/tenable-one: https://www.tenable.com/products/tenable-one (read 10 Nov 2026)
- Tenable: www.tenable.com/products/tenable-one/capabilities/exposure-prioritization: https://www.tenable.com/products/tenable-one/capabilities/exposure-prioritization (read 10 Nov 2026)
- Tenable: www.tenable.com/products/vulnerability-management: https://www.tenable.com/products/vulnerability-management (read 10 Nov 2026)
- Tenable: www.tenable.com/products/tenable-one/capabilities/hexa-ai: https://www.tenable.com/products/tenable-one/capabilities/hexa-ai (read 10 Nov 2026)
- Tenable: www.tenable.com/products/patch-management: https://www.tenable.com/products/patch-management (read 10 Nov 2026)
- Tenable: www.tenable.com/data-sheets/tenable-hexa-ai-the-agentic-engine-for-tenable-one-e: https://www.tenable.com/data-sheets/tenable-hexa-ai-the-agentic-engine-for-tenable-one-exposure-management (read 10 Nov 2026)
- Tenable: www.tenable.com/products/tenable-one/pricing: https://www.tenable.com/products/tenable-one/pricing (read 10 Nov 2026)
- Tenable: www.tenable.com/about-tenable/about-us: https://www.tenable.com/about-tenable/about-us (read 10 Nov 2026)
- Tenable: www.tenable.com/cve: https://www.tenable.com/cve (read 10 Nov 2026)
- Tenable: www.tenable.com/press-releases/tenable-partners-with-anthropic-for-ai-driven-exp: https://www.tenable.com/press-releases/tenable-partners-with-anthropic-for-ai-driven-exposure-management (read 10 Nov 2026)
- Tenable: www.tenable.com/cyberagents-exchange: https://www.tenable.com/cyberagents-exchange (read 10 Nov 2026)
- Tenable: www.tenable.com/products/tenable-one/connectors: https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026)
- Tenable: www.tenable.com/customers: https://www.tenable.com/customers (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/platforms/tenable/
---
# Vicarius: what it is, what it does well and where it is limited
Platform profile, read 10 Nov 2026
**The short answer.** Vicarius sells remediation-first exposure platform (patching, scripting, patchless protection), as its pages read on 10 Nov 2026 describe it. 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. Every line below carries its source and the date it was read.
## What it is
Remediation-first exposure platform (patching, scripting, patchless protection).
## What it 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.
## Where it is 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.
## Facts read, by topic
Each line below carries a label, the page it was read on and the date. A vendor's claim is the vendor's own statement about itself; a third-party source is one that is not the vendor; a line that starts with none found says nothing was published on that date. Vicarius has 38 lines on file, read up to 10 Nov 2026; the Vicarius pages behind them are listed under Sources.
### Proves exploitability in your environment
- Vendor's claim: VScore adds exploit simulation, asset criticality and business context in addition to CVSS, EPSS and KEV. ([source](https://www.vicarius.io/features/vrx-analysis), read 10 Nov 2026)
- Vendor's claim: Vendor says vScore confirms every queued item is exploitable. ([source](https://www.vicarius.io/features/vrx-analysis), read 10 Nov 2026)
- Vendor's claim: Agentic AI validation of which vulnerabilities attackers can exploit. ([source](https://www.vicarius.io/), read 10 Nov 2026)
- Vendor's claim: Claims 95% of false positives removed by agentic exposure validation (no method shown). ([source](https://www.vicarius.io/features/vrx-analysis), read 10 Nov 2026)
- Vendor's claim: Re-validates each asset after a fix. ([source](https://www.vicarius.io/features/vrx-analysis), read 10 Nov 2026)
### Ships the fix
- Vendor's claim: Core pitch: finds vulnerabilities and fixes them via patch management, scripting and patchless protection. ([source](https://www.vicarius.io/), read 10 Nov 2026)
- Vendor's claim: Patching on demand, scheduled or by rule across Windows, macOS, Linux and 20,000+ third-party apps. ([source](https://www.vicarius.io/features/patch-management), read 10 Nov 2026)
- Vendor's claim: VShield blocks exploit paths in memory without touching the application or a reboot (virtual patch style mitigation). ([source](https://www.vicarius.io/features/patchless-protection), read 10 Nov 2026)
- Vendor's claim: Remediation is executed and then verified; for patching vRx compares detected version with the target version. ([source](https://www.vicarius.io/solution/vulnerability-remediation), read 10 Nov 2026)
- Vendor's claim: Control on AI scripts: drafts only until a team member reviews and approves. ([source](https://www.vicarius.io/features/scriptai), read 10 Nov 2026)
### Finds the owner
- Vendor's claim: Orchestration and automation to coordinate remediation across teams and tools (feature named in navigation; little detail on owner resolution). ([source](https://www.vicarius.io/), read 10 Nov 2026)
- None found on 10 Nov 2026: Automatic mapping of findings to the owning team or CMDB/ticketing owner resolution on vicarius.io pages read ([source](https://www.vicarius.io/), read 10 Nov 2026)
### Speed on a new disclosure
- Vendor's claim: VShield protects at disclosure before a vendor patch exists. ([source](https://www.vicarius.io/features/patchless-protection), read 10 Nov 2026)
- Vendor's claim: ScriptAI watches for exploited-in-the-wild threats before an official identifier exists and generates detection scripts. ([source](https://www.vicarius.io/features/scriptai), read 10 Nov 2026)
- Vendor's claim: Detection scripts run immediately to show which assets are affected while remediation is validated. ([source](https://www.vicarius.io/features/scriptai), read 10 Nov 2026)
- Vendor's claim: Average time to rescan stated as 15 seconds. ([source](https://www.vicarius.io/about-us), read 10 Nov 2026)
- Vendor's claim: MTTR claim: months to hours (no method). ([source](https://www.vicarius.io/features/patchless-protection), read 10 Nov 2026)
### Agents you can shape
- Vendor's claim: ScriptAI and AI grouping are labeled agentic AI features (new): LLM-written remediation scripts and AI-powered dynamic groups. ([source](https://www.vicarius.io/), read 10 Nov 2026)
- Vendor's claim: VIntelligence AI search assistant answers plain-English questions on live data with threat intelligence. ([source](https://www.vicarius.io/features/ai-search-assistant), read 10 Nov 2026)
- Vendor's claim: Script library of 1000+ community and AI-generated scripts; custom scripts supported. ([source](https://www.vicarius.io/features/scriptai), read 10 Nov 2026)
- Vendor's claim: Newsroom lists an October 2026 release "Vicarius revamps AI platform to unify cybersecurity workflows" (vRx 2.0 launch the same month). ([source](https://www.vicarius.io/vicarius-resources-newsroom), read 10 Nov 2026)
### Works on the stack you have
- Vendor's claim: Feeds from EDR, SIEM, CSPM and scanners into one ordered list. ([source](https://www.vicarius.io/features/vrx-analysis), read 10 Nov 2026)
- Vendor's claim: Endpoint coverage: Windows, macOS, Linux and 20,000+ third-party apps; agent and agentless detection. ([source](https://www.vicarius.io/), read 10 Nov 2026)
- None found on 10 Nov 2026: A named list of scanner, cloud, code host or ticketing integrations on the vicarius.io pages read ([source](https://www.vicarius.io/), read 10 Nov 2026)
### Proof
- Vendor's claim: Customer count claims differ by page: 1,000+ deployments (home) versus over 500 customers in 50 countries (about). ([source](https://www.vicarius.io/), read 10 Nov 2026)
- Vendor's claim: Case study: Jamaica Broilers Group remediates 70% faster (vendor-published). ([source](https://www.vicarius.io/case-studies/jamaica-broilers-group), read 10 Nov 2026)
- Vendor's claim: Customer outcome: Charter School Associates saved 100+ hours on patch management. ([source](https://www.vicarius.io/), read 10 Nov 2026)
- Vendor's claim: Recognized in the Gartner 2025 Magic Quadrant for Exposure Assessment Platforms (per vendor). ([source](https://www.vicarius.io/), read 10 Nov 2026)
- Vendor's claim: Research: 2026 state of remediation report finds 79% of organizations vulnerable to known exploits (survey method not read). ([source](https://www.vicarius.io/vicarius-resources-newsroom), read 10 Nov 2026)
- Vendor's claim: VSociety publishes original CVE disclosures and exploit analysis. ([source](https://www.vicarius.io/), read 10 Nov 2026)
## Profile facts
- Vendor's claim: Founded 2016. ([source](https://www.vicarius.io/about-us), read 10 Nov 2026)
- Vendor's claim: Funding: $24M Series A (2022) and $30M Series B (2023). ([source](https://www.vicarius.io/about-us), read 10 Nov 2026)
- Vendor's claim: Series A amount. ([source](https://www.vicarius.io/about-us), read 10 Nov 2026)
- Vendor's claim: HQ New York; offices in Israel, Australia, Brazil, Chile, Germany, India, Singapore, UK. ([source](https://www.vicarius.io/about-us), read 10 Nov 2026)
- Vendor's claim: Pricing: annual subscription by managed endpoint asset count; no list prices on page (none found for amounts). ([source](https://www.vicarius.io/pricing), read 10 Nov 2026)
- Vendor's claim: Customers: 500+ in 60+ countries, 2M+ assets (2024 milestone). ([source](https://www.vicarius.io/about-us), read 10 Nov 2026)
- Vendor's claim: Product modules: vRx, vScore, vPatch, vShield, vScript, vComply, vIntelligence; vRx 2.0 launched October 2026. ([source](https://www.vicarius.io/vicarius-resources-newsroom), read 10 Nov 2026)
- Vendor's claim: Investors include Bright Pixel Capital, AlleyCorp, GoldBell, JVP, Future Energy, AllegisCyber. ([source](https://www.vicarius.io/about-us), read 10 Nov 2026)
## Links
- [Side by side](/compare/): Pairs of platforms, with the sourced facts in the same rows.
- [Vicarius on its own site](https://www.vicarius.io/)
## Related pages
- [The 14 platforms, listed alphabetically](/platforms/)
- [Zafran: what it is, what it does well and where it is limited](/platforms/zafran/)
- [Tenable: what it is, what it does well and where it is limited](/platforms/tenable/)
- [Astelia Security: what it is, what it does well and where it is limited](/platforms/astelia/)
## Sources
- Vicarius: www.vicarius.io/features/vrx-analysis: https://www.vicarius.io/features/vrx-analysis (read 10 Nov 2026)
- Vicarius: www.vicarius.io/: https://www.vicarius.io/ (read 10 Nov 2026)
- Vicarius: www.vicarius.io/features/patch-management: https://www.vicarius.io/features/patch-management (read 10 Nov 2026)
- Vicarius: www.vicarius.io/features/patchless-protection: https://www.vicarius.io/features/patchless-protection (read 10 Nov 2026)
- Vicarius: www.vicarius.io/solution/vulnerability-remediation: https://www.vicarius.io/solution/vulnerability-remediation (read 10 Nov 2026)
- Vicarius: www.vicarius.io/features/scriptai: https://www.vicarius.io/features/scriptai (read 10 Nov 2026)
- Vicarius: www.vicarius.io/about-us: https://www.vicarius.io/about-us (read 10 Nov 2026)
- Vicarius: www.vicarius.io/features/ai-search-assistant: https://www.vicarius.io/features/ai-search-assistant (read 10 Nov 2026)
- Vicarius: www.vicarius.io/vicarius-resources-newsroom: https://www.vicarius.io/vicarius-resources-newsroom (read 10 Nov 2026)
- Vicarius: www.vicarius.io/case-studies/jamaica-broilers-group: https://www.vicarius.io/case-studies/jamaica-broilers-group (read 10 Nov 2026)
- Vicarius: www.vicarius.io/pricing: https://www.vicarius.io/pricing (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/platforms/vicarius/
---
# Zafran: what it is, what it does well and where it is limited
Platform profile, read 10 Nov 2026
**The short answer.** Zafran sells exposure management platform with mitigation via existing controls (agentic features), as its pages read on 10 Nov 2026 describe it. 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.
## What it is
Exposure management platform with mitigation via existing controls (agentic features).
## What it 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.
## Where it is 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.
## Facts read, by topic
Each line below carries a label, the page it was read on and the date. A vendor's claim is the vendor's own statement about itself; a third-party source is one that is not the vendor; a line that starts with none found says nothing was published on that date. Zafran has 38 lines on file, read up to 10 Nov 2026; the Zafran pages behind them are listed under Sources.
### Proves exploitability in your environment
- Vendor's claim: Exposure Graph links each finding to asset, network path, runtime status and threat activity, then reads live control configuration to see what already protects the asset. ([source](https://www.zafran.io/), read 10 Nov 2026)
- Vendor's claim: Prioritization weighs runtime, reachability, active exploitation, controls and business criticality. ([source](https://www.zafran.io/), read 10 Nov 2026)
- Vendor's claim: Control assessment reads firewall, WAF, cloud security group and EDR configurations to show which vulnerabilities are already blocked. ([source](https://www.zafran.io/solutions/use-cases/mitigate-risk), read 10 Nov 2026)
- Vendor's claim: Customer evidence: Sallie Mae says Zafran checks control configuration per device and adjusts risk accordingly. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
- Vendor's claim: Attack Chains maps paths from an exposed foothold to crown jewels across cloud and on-prem, built with Google Threat Intelligence (Aug 3, 2026). ([source](https://www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration-with-google-threat-intelligence), read 10 Nov 2026)
### Ships the fix
- Vendor's claim: Mitigation first: uses existing firewall, WAF and EDR to reduce risk before a patch exists. ([source](https://www.zafran.io/), read 10 Nov 2026)
- Vendor's claim: Attack Chains offers a compensating control (such as a WAF rule) applied in a few clicks at the choke point. ([source](https://www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration-with-google-threat-intelligence), read 10 Nov 2026)
- Vendor's claim: Workflow example: one flow opens a ServiceNow ticket, pushes a WAF rule and tracks the SLA. ([source](https://www.zafran.io/), read 10 Nov 2026)
- Vendor's claim: Patch/upgrade remediation is delivered as a Work Item routed to the owner in the ticketing tool, not as a pull request. ([source](https://www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration-with-google-threat-intelligence), read 10 Nov 2026)
- Vendor's claim: RemOps uses generative AI to build a get-well plan and route work through existing ticketing. ([source](https://www.zafran.io/platform), read 10 Nov 2026)
- Vendor's claim: Vendor analysis claim: about 90% of vulnerabilities can be mitigated with controls already in place. ([source](https://www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-reports-for-unified-exposure-management-platforms-and-autonomous-exposure-remediation-categories), read 10 Nov 2026)
### Finds the owner
- Vendor's claim: Collapses overlapping findings into one fix and routes it to the right team and owner. ([source](https://www.zafran.io/), read 10 Nov 2026)
- Vendor's claim: Auto-assigns fixes to the owner in Jira, Slack and ServiceNow. ([source](https://www.zafran.io/platform), read 10 Nov 2026)
- Vendor's claim: Example: 700 findings collapse into one OpenSSL upgrade ticket routed to the Platform team. ([source](https://www.zafran.io/), read 10 Nov 2026)
- Vendor's claim: Progress tracking with shared visibility across Security and IT. ([source](https://www.zafran.io/platform), read 10 Nov 2026)
### Speed on a new disclosure
- Vendor's claim: Zero Day Agent scenario: matches a pre-announced OpenSSL flaw to live software inventory in 88 seconds before any CVE is published (illustrative scenario on the home page). ([source](https://www.zafran.io/), read 10 Nov 2026)
- Vendor's claim: Proactive Exposure Hunting for new CVEs and zero-days, including which affected assets are internet-exposed. ([source](https://www.zafran.io/platform), read 10 Nov 2026)
- Vendor's claim: Customer quote: assess exposure before CVEs are defined. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
- Vendor's claim: Customer-reported time to answer "are we exposed?" is minutes. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
- Vendor's claim: Zero-day example (PHP2Shell): control policies mitigate it and risk drops from 9.2 to 3.8. ([source](https://www.zafran.io/), read 10 Nov 2026)
### Agents you can shape
- Vendor's claim: Ready-made Zero Day Agent and Zafran AI assistant; AI can build dashboards from prompts. ([source](https://www.zafran.io/), read 10 Nov 2026)
- Vendor's claim: Customer-built agents: user prompts create a scheduled report agent that emails a daily report. ([source](https://www.zafran.io/), read 10 Nov 2026)
- Vendor's claim: Zafran AI answers plain-language questions grounded in correlated asset and findings data (Sallie Mae case study). ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
- Vendor's claim: Gartner definition of autonomous exposure remediation, which Zafran cites as a category it was named a Sample Vendor for. ([source](https://www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-reports-for-unified-exposure-management-platforms-and-autonomous-exposure-remediation-categories), read 10 Nov 2026)
- None found on 10 Nov 2026: Documented approval gates or guardrail controls per Zafran agent on the pages read ([source](https://www.zafran.io/), read 10 Nov 2026)
### Works on the stack you have
- Vendor's claim: Named sources on the home page: Zafran Discover, Tenable, Rapid7, Wiz, AWS, Snyk and 100+ more integrations. ([source](https://www.zafran.io/), read 10 Nov 2026)
- Vendor's claim: Platform page: cloud and AppSec from Wiz, Palo Alto Networks, Upwind, AWS, Snyk; on-prem from Tenable, Qualys, Rapid7. ([source](https://www.zafran.io/platform), read 10 Nov 2026)
- Vendor's claim: Controls read: CrowdStrike Falcon, Akamai WAF, Palo Alto NGFW (example policies). ([source](https://www.zafran.io/), read 10 Nov 2026)
- Vendor's claim: Ticketing and chat: Jira, Slack, ServiceNow (see owner facts); no new agents to deploy for ingestion. ([source](https://www.zafran.io/), read 10 Nov 2026)
### Proof
- Vendor's claim: Sallie Mae case study: 96% reduction in CVSS Criticals and 23K vulnerabilities identified for mitigation with existing controls. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
- Vendor's claim: Named CISO testimonial (Kraft Heinz). ([source](https://www.zafran.io/platform), read 10 Nov 2026)
- Vendor's claim: Analyst recognition: KuppingerCole 2026 Leadership Compass banner on the home page. ([source](https://www.zafran.io/), read 10 Nov 2026)
- Vendor's claim: Gartner Emerging Tech report mentions (Sept 11, 2026 and Apr 3, 2026), as reported by Zafran. ([source](https://www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-reports-for-unified-exposure-management-platforms-and-autonomous-exposure-remediation-categories), read 10 Nov 2026)
## Profile facts
- Vendor's claim: Founders: Sanaz Yashar (CEO) and Ben Seri (CTO). ([source](https://www.zafran.io/about), read 10 Nov 2026)
- Vendor's claim: Investors named: Menlo Ventures, Sequoia Capital, Cyberstarts, plus strategic investment from Amex Ventures (Feb 24, 2026). ([source](https://www.zafran.io/resources/zafran-announces-strategic-investment-from-amex-ventures), read 10 Nov 2026)
- Vendor's claim: Strategic investment from Cisco Investments announced Jul 22, 2026 (headline on news index). ([source](https://www.zafran.io/news), read 10 Nov 2026)
- None found on 10 Nov 2026: Round amounts, founding year, headquarters, headcount, customer count and pricing on the pages read ([source](https://www.zafran.io/platform), read 10 Nov 2026)
- Vendor's claim: Products: Threat Exposure Management Platform, Exposure Graph, Zero Day Agent, Attack Chain Killswitch, Zafran AIR (Apr 28, 2026). ([source](https://www.zafran.io/news), read 10 Nov 2026)
## Links
- [Side by side](/compare/): Pairs of platforms, with the sourced facts in the same rows.
- [Zafran on its own site](https://www.zafran.io/)
## Related pages
- [The 14 platforms, listed alphabetically](/platforms/)
- [Astelia Security: what it is, what it does well and where it is limited](/platforms/astelia/)
- [Vicarius: what it is, what it does well and where it is limited](/platforms/vicarius/)
- [Averlon: what it is, what it does well and where it is limited](/platforms/averlon/)
## Sources
- Zafran: www.zafran.io/: https://www.zafran.io/ (read 10 Nov 2026)
- Zafran: www.zafran.io/solutions/use-cases/mitigate-risk: https://www.zafran.io/solutions/use-cases/mitigate-risk (read 10 Nov 2026)
- Zafran: www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-: https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes (read 10 Nov 2026)
- Zafran: www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration: https://www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration-with-google-threat-intelligence (read 10 Nov 2026)
- Zafran: www.zafran.io/platform: https://www.zafran.io/platform (read 10 Nov 2026)
- Zafran: www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-re: https://www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-reports-for-unified-exposure-management-platforms-and-autonomous-exposure-remediation-categories (read 10 Nov 2026)
- Zafran: www.zafran.io/about: https://www.zafran.io/about (read 10 Nov 2026)
- Zafran: www.zafran.io/resources/zafran-announces-strategic-investment-from-amex-ventures: https://www.zafran.io/resources/zafran-announces-strategic-investment-from-amex-ventures (read 10 Nov 2026)
- Zafran: www.zafran.io/news: https://www.zafran.io/news (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/platforms/zafran/
---
# 24 pairs of platforms, side by side
Side by side, read 10 Nov 2026
**The short answer.** The side-by-side pages put the sourced facts of two platforms in the same rows, under the same seven topics, with the read date of 10 Nov 2026 on each. Pairs are named alphabetically. Each page ends with the facts and no conclusion, so the reader decides which rows matter for the stack.
| Pair | First is | Second is |
| --- | --- | --- |
| [Astelia Security vs Onit Security](/compare/astelia-vs-onit/) | AI-native exposure management with reachability analysis and agentic remediation | Agentic exposure management / remediation (decision-based) |
| [Astelia Security vs Rival Security](/compare/astelia-vs-rival/) | AI-native exposure management with reachability analysis and agentic remediation | Agentic security platform / agent harness for vulnerability management, code and cloud security |
| [Averlon vs Dux Security](/compare/averlon-vs-dux/) | Agentic remediation (exposure/attack-chain analysis with fixes delivered into developer workflows) | Agentic exposure management (exploitability analysis, mitigation, remediation acceleration) |
| [Averlon vs Rival Security](/compare/averlon-vs-rival/) | Agentic remediation (exposure/attack-chain analysis with fixes delivered into developer workflows) | Agentic security platform / agent harness for vulnerability management, code and cloud security |
| [Backline Security vs Dux Security](/compare/backline-vs-dux/) | Agentic remediation (Autonomous Exposure Remediation) | Agentic exposure management (exploitability analysis, mitigation, remediation acceleration) |
| [Backline Security vs Rival Security](/compare/backline-vs-rival/) | Agentic remediation (Autonomous Exposure Remediation) | Agentic security platform / agent harness for vulnerability management, code and cloud security |
| [Cogent Security vs Rival Security](/compare/cogent-vs-rival/) | Agentic vulnerability management and remediation (AI agents across the full vulnerability lifecycle) | Agentic security platform / agent harness for vulnerability management, code and cloud security |
| [Cogent Security vs Zafran](/compare/cogent-vs-zafran/) | Agentic vulnerability management and remediation (AI agents across the full vulnerability lifecycle) | Exposure management platform with mitigation via existing controls (agentic features) |
| [Dux Security vs Rival Security](/compare/dux-vs-rival/) | Agentic exposure management (exploitability analysis, mitigation, remediation acceleration) | Agentic security platform / agent harness for vulnerability management, code and cloud security |
| [Maze vs Rival Security](/compare/maze-vs-rival/) | Agentic vulnerability investigation and remediation (code and cloud) | Agentic security platform / agent harness for vulnerability management, code and cloud security |
| [Maze vs Zafran](/compare/maze-vs-zafran/) | Agentic vulnerability investigation and remediation (code and cloud) | Exposure management platform with mitigation via existing controls (agentic features) |
| [Onit Security vs Rival Security](/compare/onit-vs-rival/) | Agentic exposure management / remediation (decision-based) | Agentic security platform / agent harness for vulnerability management, code and cloud security |
| [Onit Security vs Zafran](/compare/onit-vs-zafran/) | Agentic exposure management / remediation (decision-based) | Exposure management platform with mitigation via existing controls (agentic features) |
| [Qualys vs Rapid7](/compare/qualys-vs-rapid7/) | Exposure/RBVM platform with remediation and agentic AI | Exposure/RBVM platform with remediation workflows |
| [Qualys vs Rival Security](/compare/qualys-vs-rival/) | Exposure/RBVM platform with remediation and agentic AI | Agentic security platform / agent harness for vulnerability management, code and cloud security |
| [Qualys vs Tenable](/compare/qualys-vs-tenable/) | Exposure/RBVM platform with remediation and agentic AI | Exposure management platform with remediation and agentic orchestration |
| [Rapid7 vs Rival Security](/compare/rapid7-vs-rival/) | Exposure/RBVM platform with remediation workflows | Agentic security platform / agent harness for vulnerability management, code and cloud security |
| [Rapid7 vs Tenable](/compare/rapid7-vs-tenable/) | Exposure/RBVM platform with remediation workflows | Exposure management platform with remediation and agentic orchestration |
| [Rival Security vs Seemplicity](/compare/rival-vs-seemplicity/) | Agentic security platform / agent harness for vulnerability management, code and cloud security | Agentic exposure management and response (RBVM/CTEM workflow with AI analysts) |
| [Rival Security vs Tenable](/compare/rival-vs-tenable/) | Agentic security platform / agent harness for vulnerability management, code and cloud security | Exposure management platform with remediation and agentic orchestration |
| [Rival Security vs Vicarius](/compare/rival-vs-vicarius/) | Agentic security platform / agent harness for vulnerability management, code and cloud security | Remediation-first exposure platform (patching, scripting, patchless protection) |
| [Rival Security vs Zafran](/compare/rival-vs-zafran/) | Agentic security platform / agent harness for vulnerability management, code and cloud security | Exposure management platform with mitigation via existing controls (agentic features) |
| [Seemplicity vs Zafran](/compare/seemplicity-vs-zafran/) | Agentic exposure management and response (RBVM/CTEM workflow with AI analysts) | Exposure management platform with mitigation via existing controls (agentic features) |
| [Vicarius vs Zafran](/compare/vicarius-vs-zafran/) | Remediation-first exposure platform (patching, scripting, patchless protection) | Exposure management platform with mitigation via existing controls (agentic features) |
Alphabetical by the two names; inside a pair the names are alphabetical too.
## Related pages
- [Astelia Security vs Onit Security: the sourced facts side by side](/compare/astelia-vs-onit/)
- [Astelia Security vs Rival Security: the sourced facts side by side](/compare/astelia-vs-rival/)
- [Averlon vs Dux Security: the sourced facts side by side](/compare/averlon-vs-dux/)
- [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)
- Cogent Security: www.cogent.com/platform/assess: https://www.cogent.com/platform/assess (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/compare/
---
# Astelia Security vs Onit Security: the sourced facts side by side
Side by side, read 10 Nov 2026
**The short answer.** Astelia Security and Onit Security. Astelia Security has 41 fact lines (1 third-party) and Onit Security has 37 (1 third-party). Fixes: Astelia Security, patches through patch tools and mitigations; Onit Security, mitigations and pull requests. None found: Astelia Security on fix; Onit Security on agents. The rows below set the sourced facts side by side; the page names no pick.
## The same rows for both
| Row | Astelia Security | Onit Security |
| --- | --- | --- |
| What it is | AI-native exposure management with reachability analysis and agentic remediation | Agentic exposure management / remediation (decision-based) |
| What it 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. | 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. |
| Where it is 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. | 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. |
| Proves exploitability in your environment | Vendor's claim: Platform maps network topology and uses agentic AI to analyze exploit requirements per vulnerability. ([source](https://www.astelia.io/platform), read 10 Nov 2026)
Vendor's claim: Reachability classification correlates topology, asset context and runtime data. ([source](https://www.astelia.io/platform), read 10 Nov 2026)
Vendor's claim: Every finding, including deprioritized ones, carries evidence of exposure or its absence. ([source](https://www.astelia.io/use-cases/identify-true-exposure), read 10 Nov 2026)
Vendor's claim: Vendor claim from funding release: in some deployments about 30 of nearly 3 million vulnerabilities were genuinely exploitable. ([source](https://www.astelia.io/newsroom/astelia-raises-35m-to-turn-exposure-management-from-guesswork-into-ai-powered-precision), read 10 Nov 2026)
1 more on the [profile](/platforms/astelia/) | Vendor's claim: Platform layer that validates whether each exposure is reachable and exploitable in the customer environment, so only real risk continues. ([source](https://onit.security/platform/), read 10 Nov 2026)
Vendor's claim: Exploitability signals named: network reachability, runtime and loaded status, and live exploit intelligence such as KEV and weaponization. ([source](https://onit.security/platform/), read 10 Nov 2026)
Vendor's claim: A Reachability Agent returns a per-asset finding (reachable, restricted, internal, not reachable, unknown) with the path or the blocker as evidence, read-only. ([source](https://onit.security/blog/reachable-vulnerabilities/), read 10 Nov 2026)
Vendor's claim: An Exploitability Agent checks host conditions (component present, loaded, configured in the exploitable way); failed findings are kept with the reason. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
1 more on the [profile](/platforms/onit/) |
| Ships the fix | Vendor's claim: Remediation includes non-patch routes when patching is not an option. ([source](https://www.astelia.io/use-cases/streamline-remediation), read 10 Nov 2026)
Vendor's claim: Agents pick the fastest fix (patch, firewall or IPS rule) and implement it via the existing stack with a human in the loop. ([source](https://www.astelia.io/use-cases/deploy-astelia-agents), read 10 Nov 2026)
Vendor's claim: Example workflow: drafted ticket and firewall rule wait in an approval queue for a human click. ([source](https://www.astelia.io/post/closing-the-exposure-loop), read 10 Nov 2026)
Vendor's claim: Where a patch exists the workflow drives it through the patch management tool. ([source](https://www.astelia.io/post/closing-the-exposure-loop), read 10 Nov 2026)
2 more on the [profile](/platforms/astelia/) | Vendor's claim: A Remediation Agent builds a step-by-step remediation plan (patch/version, deployment path, restart and validation steps, rollback) per asset; the published text describes a plan, not an automatically opened pull request. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
Vendor's claim: A Mitigation Agent proposes interim mitigations (disable a feature, tighten a firewall rule, compensating control), tagged by time, complexity and operational impact. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
Vendor's claim: Human approval gate on every agent action, with audit trail and one-step reversal, for both remediations and mitigations. ([source](https://onit.security/platform/), read 10 Nov 2026)
Vendor's claim: Vendor states nothing executes without approval. ([source](https://onit.security/platform/), read 10 Nov 2026) |
| Finds the owner | Vendor's claim: Example workflow opens a ticket for the asset owner and proposes an interim network mitigation. ([source](https://www.astelia.io/post/closing-the-exposure-loop), read 10 Nov 2026)
Vendor's claim: Agents cover routing ownership and driving remediation. ([source](https://www.astelia.io/ai-info-page), read 10 Nov 2026)
Vendor's claim: Investigator agent coordinates next steps across the tech stack. ([source](https://www.astelia.io/use-cases/deploy-astelia-agents), read 10 Nov 2026) | Vendor's claim: Resolves the owner from CMDB, ticketing and communication tools rather than leaving owner guessing to the customer. ([source](https://onit.security/), read 10 Nov 2026)
Vendor's claim: Ownership inferred from commit authorship, historical patterns and service maps, and re-resolved after reorganizations. ([source](https://onit.security/platform/), read 10 Nov 2026)
Vendor's claim: After assigning, it nudges, escalates and tracks the work to closure. ([source](https://onit.security/platform/), read 10 Nov 2026)
Vendor's claim: Vendor reports roughly half of remediation tickets bounce because the owner is wrong on arrival (its own field observation, no published method). ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026) |
| Speed on a new disclosure | Vendor's claim: Hunter agent checks new and zero-day vulnerabilities against the SBOM before scanners detect them. ([source](https://www.astelia.io/use-cases/deploy-astelia-agents), read 10 Nov 2026)
Vendor's claim: Zero-day and new-CVE detection matches against software inventory before the next scanner cycle. ([source](https://www.astelia.io/ai-info-page), read 10 Nov 2026)
Vendor's claim: Workflows trigger automatically on each new advisory. ([source](https://www.astelia.io/post/closing-the-exposure-loop), read 10 Nov 2026)
None found on 10 Nov 2026: A numeric time-to-answer claim or a published response write-up for a named CVE. ([source](https://www.astelia.io/use-cases/deploy-astelia-agents), read 10 Nov 2026) | Vendor's claim: A Zero-Day Agent is described as catching a zero-day as it breaks, finding every exposed asset and proving which are exploitable, in minutes (blog dated Oct 23, 2026). ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
Vendor's claim: The Zero-Day Agent was announced ahead of general availability as of the blog date. ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
Vendor's claim: Published write-up of the PHP2Shell zero-day (leak Oct 20, 2026) walks through the four questions the agent answers. ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
Vendor's claim: Zero-Day Agent limits: no live exploits against production, no new endpoint agent, no disruptive action without approval. ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
1 more on the [profile](/platforms/onit/) |
| Agents you can shape | Vendor's claim: Three named vendor-built agents: Hunter (zero-day detection), Investigator (triage), Fixer (remediation). ([source](https://www.astelia.io/use-cases/deploy-astelia-agents), read 10 Nov 2026)
Vendor's claim: Customers write a workflow spec in natural language and a Planner agent builds it. ([source](https://www.astelia.io/post/closing-the-exposure-loop), read 10 Nov 2026)
Vendor's claim: Marketplace of ready-made agents and skills. ([source](https://www.astelia.io/post/closing-the-exposure-loop), read 10 Nov 2026)
Vendor's claim: Controls: approval queues, role-based access control, audit and execution logs. ([source](https://www.astelia.io/ai-info-page), read 10 Nov 2026)
2 more on the [profile](/platforms/astelia/) | Vendor's claim: Ready-made specialized agents (discovery, ownership, exploitability, threat intel, prioritization, resolution, remediation, mitigation) run in parallel on one shared context. ([source](https://onit.security/platform/), read 10 Nov 2026)
Vendor's claim: Named agents in the Decision Center: Reachability, Exploitability, Context, Ownership, Prioritization, Remediation, Mitigation. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
Vendor's claim: Guardrail model: a person reviews each decision once; approved decisions become standing rules covering matching exposures, logged and reversible. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
Vendor's claim: Agent controls: customer can adjust one agent without touching the others. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
1 more on the [profile](/platforms/onit/) |
| Works on the stack you have | Vendor's claim: Named firewalls and scanners read through read-only integrations. ([source](https://www.astelia.io/ai-info-page), read 10 Nov 2026)
Vendor's claim: Threat intel sources: CISA KEV, NVD, advisories, public PoCs and EPSS. ([source](https://www.astelia.io/ai-info-page), read 10 Nov 2026)
Vendor's claim: Agents connect through 100+ MCP integrations to ticketing, CMDB, patch management and communication tools. ([source](https://www.astelia.io/ai-info-page), read 10 Nov 2026)
Vendor's claim: Sits above scanners the customer already runs. ([source](https://www.astelia.io/ai-info-page), read 10 Nov 2026)
1 more on the [profile](/platforms/astelia/) | Vendor's claim: Sources are described by category: security tools, cloud, CMDBs, ticketing and collaboration systems (scanners, CSPM, EDR/XDR). ([source](https://onit.security/platform/), read 10 Nov 2026)
Vendor's claim: Knowledge sources include asset inventories, ticketing and change history, wikis, Slack and Teams threads, email, cloud tags, directories and code repositories. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
Vendor's claim: Zero-Day Agent reads scanners, cloud accounts, EDR and CMDB already connected, and checks exploitability read-only through the EDR. ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
None found on 10 Nov 2026: A list of named scanner, cloud, code host or ticketing product integrations on onit.security ([source](https://onit.security/), read 10 Nov 2026) |
| Proof | Vendor's claim: Named customer quote: Justin Dellaportas, CISO at Syniverse. ([source](https://www.astelia.io/platform), read 10 Nov 2026)
Vendor's claim: Named customer quotes also from AlphaSense and Bilfinger CISOs. ([source](https://www.astelia.io/platform), read 10 Nov 2026)
Vendor's claim: Funding release states dozens of customers including Fortune 500 companies. ([source](https://www.astelia.io/newsroom/astelia-raises-35m-to-turn-exposure-management-from-guesswork-into-ai-powered-precision), read 10 Nov 2026)
Vendor's claim: Newsroom lists Fortune Cyber 60 (2026-2027) and Fast Company Next Big Things in Tech recognition. ([source](https://www.astelia.io/newsroom), read 10 Nov 2026)
1 more on the [profile](/platforms/astelia/) | Vendor's claim: Named-person testimonials appear on the home page (titles only, employers not named in the quote block). ([source](https://onit.security/), read 10 Nov 2026)
Vendor's claim: Anecdote of an unnamed Fortune 500 customer where three tools showed no findings and Onit found two devices on a KEV-listed product. ([source](https://onit.security/blog/reachable-vulnerabilities/), read 10 Nov 2026)
Vendor's claim: Research and thought-leadership blog cadence (posts Jul to Nov 2026) citing Mandiant M-Trends and Verizon DBIR; no original measured study seen. ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
None found on 10 Nov 2026: Named customer case studies or a published measurement method for the 55 days to 2.7 hours claim ([source](https://onit.security/), read 10 Nov 2026) |
| Profile facts | Vendor's claim: Funding: $35M combined seed and Series A led by Index Ventures and Team8, Feb 24, 2026. ([source](https://www.astelia.io/newsroom/astelia-raises-35m-to-turn-exposure-management-from-guesswork-into-ai-powered-precision), read 10 Nov 2026)
Third-party source: SecurityWeek confirms $35 million seed and Series A led by Index Ventures and Team8 (Feb 25, 2026). ([source](https://www.securityweek.com/astelia-raises-35-million-for-exposure-management/), read 10 Nov 2026)
Vendor's claim: Founded 2024 by former Israeli National Red Team members (SecurityWeek text says 2014, likely a typo). ([source](https://www.astelia.io/ai-info-page), read 10 Nov 2026)
Vendor's claim: HQ: New York, NY. ([source](https://www.astelia.io/about), read 10 Nov 2026) | Vendor's claim: Founders: Elad Ben Meir (CEO), Ofer Amitai (CPO), Tom Winter (CTO). ([source](https://onit.security/company/), read 10 Nov 2026)
Vendor's claim: CEO background: previously CEO of SCADAfence (acquired by Honeywell). ([source](https://onit.security/company/), read 10 Nov 2026)
Vendor's claim: Funding: seed round closed in 2025; amount not stated on the page. ([source](https://onit.security/company/), read 10 Nov 2026)
None found on 10 Nov 2026: Headquarters address, headcount, seed amount, pricing and customer count on onit.security ([source](https://onit.security/company/), read 10 Nov 2026) |
Alphabetical by name. Each line is one fact with its label, source and read date.
## Profiles
- [Astelia Security profile](/platforms/astelia/): AI-native exposure management
- [Onit Security profile](/platforms/onit/): agentic exposure management
## Related pages
- [24 pairs, side by side](/compare/)
- [Astelia Security vs Rival Security: the sourced facts side by side](/compare/astelia-vs-rival/)
- [Vicarius vs Zafran: the sourced facts side by side](/compare/vicarius-vs-zafran/)
- [Averlon vs Dux Security: the sourced facts side by side](/compare/averlon-vs-dux/)
## Sources
- Astelia Security: www.astelia.io/platform: https://www.astelia.io/platform (read 10 Nov 2026)
- Astelia Security: www.astelia.io/use-cases/identify-true-exposure: https://www.astelia.io/use-cases/identify-true-exposure (read 10 Nov 2026)
- Astelia Security: www.astelia.io/newsroom/astelia-raises-35m-to-turn-exposure-management-from-gues: https://www.astelia.io/newsroom/astelia-raises-35m-to-turn-exposure-management-from-guesswork-into-ai-powered-precision (read 10 Nov 2026)
- Astelia Security: www.astelia.io/use-cases/streamline-remediation: https://www.astelia.io/use-cases/streamline-remediation (read 10 Nov 2026)
- Astelia Security: www.astelia.io/use-cases/deploy-astelia-agents: https://www.astelia.io/use-cases/deploy-astelia-agents (read 10 Nov 2026)
- Astelia Security: www.astelia.io/post/closing-the-exposure-loop: https://www.astelia.io/post/closing-the-exposure-loop (read 10 Nov 2026)
- Astelia Security: www.astelia.io/ai-info-page: https://www.astelia.io/ai-info-page (read 10 Nov 2026)
- Astelia Security: www.astelia.io/newsroom: https://www.astelia.io/newsroom (read 10 Nov 2026)
- Onit Security: onit.security/platform/: https://onit.security/platform/ (read 10 Nov 2026)
- Onit Security: onit.security/blog/reachable-vulnerabilities/: https://onit.security/blog/reachable-vulnerabilities/ (read 10 Nov 2026)
- Onit Security: onit.security/blog/ai-agents-vulnerability-management/: https://onit.security/blog/ai-agents-vulnerability-management/ (read 10 Nov 2026)
- Onit Security: onit.security/: https://onit.security/ (read 10 Nov 2026)
- Onit Security: onit.security/blog/zero-day-response/: https://onit.security/blog/zero-day-response/ (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/compare/astelia-vs-onit/
---
# Astelia Security vs Rival Security: the sourced facts side by side
Side by side, read 10 Nov 2026
**The short answer.** Astelia Security and Rival Security, on the same rows. Astelia Security has 41 fact lines (1 third-party) and Rival Security has 40 (0 third-party). Fixes: Astelia Security, patches through patch tools; Rival Security, pull requests. None found: Astelia Security on fix; Rival Security on proof. The rows below set the sourced facts side by side; the page names no pick.
## The same rows for both
| Row | Astelia Security | Rival Security |
| --- | --- | --- |
| What it is | AI-native exposure management with reachability analysis and agentic remediation | Agentic security platform / agent harness for vulnerability management, code and cloud security |
| What it 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. | 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. |
| Where it is 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. | 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. |
| Proves exploitability in your environment | Vendor's claim: Platform maps network topology and uses agentic AI to analyze exploit requirements per vulnerability. ([source](https://www.astelia.io/platform), read 10 Nov 2026)
Vendor's claim: Reachability classification correlates topology, asset context and runtime data. ([source](https://www.astelia.io/platform), read 10 Nov 2026)
Vendor's claim: Every finding, including deprioritized ones, carries evidence of exposure or its absence. ([source](https://www.astelia.io/use-cases/identify-true-exposure), read 10 Nov 2026)
Vendor's claim: Vendor claim from funding release: in some deployments about 30 of nearly 3 million vulnerabilities were genuinely exploitable. ([source](https://www.astelia.io/newsroom/astelia-raises-35m-to-turn-exposure-management-from-guesswork-into-ai-powered-precision), read 10 Nov 2026)
1 more on the [profile](/platforms/astelia/) | Vendor's claim: Home page lists a Triage Exploitability agent that determines what is actually exploitable in the customer environment. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page says Rival reads every scanner finding against the real environment and keeps only those that can cause harm; it cites a 94.6% reduction in findings. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page reports 98% of findings proven unexploitable, 87% faster remediation and 1.5 hours to first value (no method given on the page). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: In its PHP2Shell write-up, Rival says agents ordered services to fix by reachability, internet-exposed unauthenticated workloads first. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Ships the fix | Vendor's claim: Remediation includes non-patch routes when patching is not an option. ([source](https://www.astelia.io/use-cases/streamline-remediation), read 10 Nov 2026)
Vendor's claim: Agents pick the fastest fix (patch, firewall or IPS rule) and implement it via the existing stack with a human in the loop. ([source](https://www.astelia.io/use-cases/deploy-astelia-agents), read 10 Nov 2026)
Vendor's claim: Example workflow: drafted ticket and firewall rule wait in an approval queue for a human click. ([source](https://www.astelia.io/post/closing-the-exposure-loop), read 10 Nov 2026)
Vendor's claim: Where a patch exists the workflow drives it through the patch management tool. ([source](https://www.astelia.io/post/closing-the-exposure-loop), read 10 Nov 2026)
2 more on the [profile](/platforms/astelia/) | Vendor's claim: Home page lists an Autonomous Remediation agent that generates and ships tested fixes. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page describes the remediation flow as plan, test, and open a pull request for human review. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival lists a WAF mitigation agent that checks whether a WAF blocks exploitation and adjusts it. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival describes an alternative-remediation agent for legacy apps that plans a fix without upgrading libraries. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
2 more on the [profile](/platforms/rival/) |
| Finds the owner | Vendor's claim: Example workflow opens a ticket for the asset owner and proposes an interim network mitigation. ([source](https://www.astelia.io/post/closing-the-exposure-loop), read 10 Nov 2026)
Vendor's claim: Agents cover routing ownership and driving remediation. ([source](https://www.astelia.io/ai-info-page), read 10 Nov 2026)
Vendor's claim: Investigator agent coordinates next steps across the tech stack. ([source](https://www.astelia.io/use-cases/deploy-astelia-agents), read 10 Nov 2026) | Vendor's claim: Home page lists an Ownership Resolution agent that maps each finding to the team that can fix it. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page says the owner-finding agent weighs root cause, team structure and past history (memories). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: PHP2Shell write-up says agents can message the relevant employees, and the harness lists human follow-ups. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
| Speed on a new disclosure | Vendor's claim: Hunter agent checks new and zero-day vulnerabilities against the SBOM before scanners detect them. ([source](https://www.astelia.io/use-cases/deploy-astelia-agents), read 10 Nov 2026)
Vendor's claim: Zero-day and new-CVE detection matches against software inventory before the next scanner cycle. ([source](https://www.astelia.io/ai-info-page), read 10 Nov 2026)
Vendor's claim: Workflows trigger automatically on each new advisory. ([source](https://www.astelia.io/post/closing-the-exposure-loop), read 10 Nov 2026)
None found on 10 Nov 2026: A numeric time-to-answer claim or a published response write-up for a named CVE. ([source](https://www.astelia.io/use-cases/deploy-astelia-agents), read 10 Nov 2026) | Vendor's claim: Home page lists a 0-day Fast Response agent covering triage through remediation. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page describes 0-day rapid response as finding exposure across code, images and cloud and prioritizing what to do first (page also claims a drop from days to minutes). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Published response write-up: for PHP2Shell, agents were triaging customer environments hours before scanners could detect the CVEs. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: The same write-up reports scanning more than 80,000 repositories within hours. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Agents you can shape | Vendor's claim: Three named vendor-built agents: Hunter (zero-day detection), Investigator (triage), Fixer (remediation). ([source](https://www.astelia.io/use-cases/deploy-astelia-agents), read 10 Nov 2026)
Vendor's claim: Customers write a workflow spec in natural language and a Planner agent builds it. ([source](https://www.astelia.io/post/closing-the-exposure-loop), read 10 Nov 2026)
Vendor's claim: Marketplace of ready-made agents and skills. ([source](https://www.astelia.io/post/closing-the-exposure-loop), read 10 Nov 2026)
Vendor's claim: Controls: approval queues, role-based access control, audit and execution logs. ([source](https://www.astelia.io/ai-info-page), read 10 Nov 2026)
2 more on the [profile](/platforms/astelia/) | Vendor's claim: Rival offers ready-made agents that can be customized and extended. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival engineers build custom agents for the customer environment at no additional cost (Partner tier). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Customers can build their own agents on the harness. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page says 64+ more agents are available beyond the five featured. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
2 more on the [profile](/platforms/rival/) |
| Works on the stack you have | Vendor's claim: Named firewalls and scanners read through read-only integrations. ([source](https://www.astelia.io/ai-info-page), read 10 Nov 2026)
Vendor's claim: Threat intel sources: CISA KEV, NVD, advisories, public PoCs and EPSS. ([source](https://www.astelia.io/ai-info-page), read 10 Nov 2026)
Vendor's claim: Agents connect through 100+ MCP integrations to ticketing, CMDB, patch management and communication tools. ([source](https://www.astelia.io/ai-info-page), read 10 Nov 2026)
Vendor's claim: Sits above scanners the customer already runs. ([source](https://www.astelia.io/ai-info-page), read 10 Nov 2026)
1 more on the [profile](/platforms/astelia/) | Vendor's claim: Home page names cloud, code host and infrastructure integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page names scanner, control and task integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases table shows findings sourced from Wiz, Qualys, GitHub, a pentest, and Rival's own SCA and Code scanners. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Agents combine connected services with a Rival Security Knowledge Graph. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
| Proof | Vendor's claim: Named customer quote: Justin Dellaportas, CISO at Syniverse. ([source](https://www.astelia.io/platform), read 10 Nov 2026)
Vendor's claim: Named customer quotes also from AlphaSense and Bilfinger CISOs. ([source](https://www.astelia.io/platform), read 10 Nov 2026)
Vendor's claim: Funding release states dozens of customers including Fortune 500 companies. ([source](https://www.astelia.io/newsroom/astelia-raises-35m-to-turn-exposure-management-from-guesswork-into-ai-powered-precision), read 10 Nov 2026)
Vendor's claim: Newsroom lists Fortune Cyber 60 (2026-2027) and Fast Company Next Big Things in Tech recognition. ([source](https://www.astelia.io/newsroom), read 10 Nov 2026)
1 more on the [profile](/platforms/astelia/) | Vendor's claim: Use-cases page claims 13M+ agent runs. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival published SASTBench, a benchmark for SAST triage using real CVEs as true positives and filtered SAST findings as noise. ([source](https://rival.security/blog/sastbench-measuring-ai-security-automation?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Research blog post claims Rival workflows outperform current frontier models on the Spider 2.0 benchmark. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Published incident write-up (PHP2Shell, Nov 2, 2026) with unnamed customer results. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Profile facts | Vendor's claim: Funding: $35M combined seed and Series A led by Index Ventures and Team8, Feb 24, 2026. ([source](https://www.astelia.io/newsroom/astelia-raises-35m-to-turn-exposure-management-from-guesswork-into-ai-powered-precision), read 10 Nov 2026)
Third-party source: SecurityWeek confirms $35 million seed and Series A led by Index Ventures and Team8 (Feb 25, 2026). ([source](https://www.securityweek.com/astelia-raises-35-million-for-exposure-management/), read 10 Nov 2026)
Vendor's claim: Founded 2024 by former Israeli National Red Team members (SecurityWeek text says 2014, likely a typo). ([source](https://www.astelia.io/ai-info-page), read 10 Nov 2026)
Vendor's claim: HQ: New York, NY. ([source](https://www.astelia.io/about), read 10 Nov 2026) | Vendor's claim: Tagline and category: Rival describes itself as an agent harness for cybersecurity. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Research blog launched Feb 2025 describing early experiments building AI systems for cybersecurity. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
None found on 10 Nov 2026: Pricing (rival.security/pricing returns 404; book-a-demo form only). ([source](https://rival.security/book-a-demo-form?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
None found on 10 Nov 2026: Funding, investors, founders, headcount, HQ or founding year on home, blog, careers, book-a-demo pages. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
Alphabetical by name. Each line is one fact with its label, source and read date.
## Profiles
- [Astelia Security profile](/platforms/astelia/): AI-native exposure management
- [Rival Security profile](/platforms/rival/): agentic security platform
## Related pages
- [24 pairs, side by side](/compare/)
- [Averlon vs Dux Security: the sourced facts side by side](/compare/averlon-vs-dux/)
- [Astelia Security vs Onit Security: the sourced facts side by side](/compare/astelia-vs-onit/)
- [Averlon vs Rival Security: the sourced facts side by side](/compare/averlon-vs-rival/)
## Sources
- Astelia Security: www.astelia.io/platform: https://www.astelia.io/platform (read 10 Nov 2026)
- Astelia Security: www.astelia.io/use-cases/identify-true-exposure: https://www.astelia.io/use-cases/identify-true-exposure (read 10 Nov 2026)
- Astelia Security: www.astelia.io/newsroom/astelia-raises-35m-to-turn-exposure-management-from-gues: https://www.astelia.io/newsroom/astelia-raises-35m-to-turn-exposure-management-from-guesswork-into-ai-powered-precision (read 10 Nov 2026)
- Astelia Security: www.astelia.io/use-cases/streamline-remediation: https://www.astelia.io/use-cases/streamline-remediation (read 10 Nov 2026)
- Astelia Security: www.astelia.io/use-cases/deploy-astelia-agents: https://www.astelia.io/use-cases/deploy-astelia-agents (read 10 Nov 2026)
- Astelia Security: www.astelia.io/post/closing-the-exposure-loop: https://www.astelia.io/post/closing-the-exposure-loop (read 10 Nov 2026)
- Astelia Security: www.astelia.io/ai-info-page: https://www.astelia.io/ai-info-page (read 10 Nov 2026)
- Astelia Security: www.astelia.io/newsroom: https://www.astelia.io/newsroom (read 10 Nov 2026)
- Rival Security: rival.security/: https://rival.security/ (read 10 Nov 2026)
- Rival Security: rival.security/use-cases: https://rival.security/use-cases (read 10 Nov 2026)
- Rival Security: rival.security/blog/php2shell-black-october-2026: https://rival.security/blog/php2shell-black-october-2026 (read 10 Nov 2026)
- Rival Security: docs.rival.security: https://docs.rival.security (read 10 Nov 2026)
- Rival Security: rival.security/blog/sastbench-measuring-ai-security-automation: https://rival.security/blog/sastbench-measuring-ai-security-automation (read 10 Nov 2026)
- Rival Security: rival.security/blog: https://rival.security/blog (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/compare/astelia-vs-rival/
---
# Averlon vs Dux Security: the sourced facts side by side
Side by side, read 10 Nov 2026
**The short answer.** Averlon and Dux Security are set side by side on the same rows. Averlon has 40 fact lines (0 third-party) and Dux Security has 28 (0 third-party). Fixes: Averlon, pull requests; Dux Security, mitigations. Averlon has a none-found line on speed; Dux Security on exploitability. The rows below set the sourced facts side by side; the page names no pick.
## The same rows for both
| Row | Averlon | Dux Security |
| --- | --- | --- |
| What it is | Agentic remediation (exposure/attack-chain analysis with fixes delivered into developer workflows) | Agentic exposure management (exploitability analysis, mitigation, remediation acceleration) |
| What it 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. | 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. |
| Where it is 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. | 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. |
| Proves exploitability in your environment | Vendor's claim: Averlon says it checks applicability against the customer's own environment and tests reachability across network configuration, IAM policies and Kubernetes RBAC. ([source](https://www.averlon.ai/platform), read 10 Nov 2026)
Vendor's claim: Attack chains are mapped to MITRE ATT&CK, with blast radius, and fixes that break the most chains are placed first. ([source](https://www.averlon.ai/platform), read 10 Nov 2026)
Vendor's claim: The homepage demo shows per-finding evidence fields (network exploitability, external exposure, known exploits, access to critical data, attack-chain membership) behind each triage decision. ([source](https://www.averlon.ai/), read 10 Nov 2026)
Vendor's claim: Averlon lists compensating-control assessment as a capability, to find controls already limiting risk. ([source](https://www.averlon.ai/why-averlon), read 10 Nov 2026) | Vendor's claim: Dux maps how vulnerabilities, assets and controls connect to judge exploitability. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Stated aim: separate reachable from truly exploitable risk. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Home page lead: AI agents for instant exploitability analysis. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Exploitability stage answers where the customer is already protected. ([source](https://dux.io/), read 10 Nov 2026)
1 more on the [profile](/platforms/dux/) |
| Ships the fix | Vendor's claim: Averlon says it delivers context-aware fixes inside IDEs, source control and CLI, and applies the same reasoning before merge. ([source](https://www.averlon.ai/), read 10 Nov 2026)
Vendor's claim: Its GitHub Actions generate ready-to-merge pull requests for application and infrastructure issues. ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
Vendor's claim: Fix actions cover container images, Terraform and Pulumi IaC, and Kubernetes Helm charts. ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
Vendor's claim: The vendor's example flow expects a human developer to review each generated fix (about 15 minutes per fix in its example). ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
2 more on the [profile](/platforms/averlon/) | Vendor's claim: Dux favors lightweight mitigations such as a missing control or config change instead of a patch. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Mitigations are ones the customer deploys on its own. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Remediation stage speeds up the fix process by tagging assets and tying data sources together. ([source](https://dux.io/), read 10 Nov 2026)
None found on 10 Nov 2026: Generated pull requests, tested code fixes or approval-gated automated changes. ([source](https://dux.io/), read 10 Nov 2026) |
| Finds the owner | Vendor's claim: Averlon traces a base-image vulnerability to the Dockerfile and routes it to the team that owns it. ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
Vendor's claim: For each fix group it creates a pull request plus a ticket for that PR assigned to the developer who owns the code. ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
Vendor's claim: In the vendor's customer example, issues were mapped to their source (base image or dependency) and grouped, instead of being assigned individually. ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026) | Vendor's claim: Remediation stage poses the question of who should remediate. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Auto-tagging of every asset is the ownership mechanism described. ([source](https://dux.io/), read 10 Nov 2026)
None found on 10 Nov 2026: Ticket routing, follow-up or escalation features. ([source](https://dux.io/), read 10 Nov 2026) |
| Speed on a new disclosure | Vendor's claim: A customer quote on the vendor site credits Averlon with saving time in 0-day incident response for the libWebp vulnerability. ([source](https://www.averlon.ai/), read 10 Nov 2026)
Vendor's claim: Averlon published a response write-up dated Nov 2, 2026 on CVE-2026-98432, about 18 days after the CVE was published on October 15, 2026, covering which network paths expose a host. ([source](https://www.averlon.ai/blog/cve-2026-98432-linux-kernel-tcp-use-after-free), read 10 Nov 2026)
Vendor's claim: It also published an explainer for React2Shell (CVE-2025-55182) on Dec 4, 2025, updated as new CVEs followed. ([source](https://www.averlon.ai/blog/react2shell-cve-2025-55182-explained), read 10 Nov 2026)
Vendor's claim: Averlon runs a vulnerability intelligence site (research.averlon.ai); its page content was not readable in a plain fetch beyond the title. ([source](https://research.averlon.ai/vulnerability-intelligence), read 10 Nov 2026)
1 more on the [profile](/platforms/averlon/) | Vendor's claim: Positioning is speed against attackers. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Home page frames time-to-exploit collapsing from weeks to minutes. ([source](https://dux.io/), read 10 Nov 2026)
None found on 10 Nov 2026: Zero-day response feature, time-to-answer number or published response write-up. ([source](https://dux.io/), read 10 Nov 2026) |
| Agents you can shape | Vendor's claim: The platform lists Mitigation Agents and Remediation Agents as ready-made components. ([source](https://www.averlon.ai/platform), read 10 Nov 2026)
Vendor's claim: The homepage demo shows a 'Remediation Agent' proposing a pull request that waits for merge, and 'Autonomous AI Triage' on each finding. ([source](https://www.averlon.ai/), read 10 Nov 2026)
Vendor's claim: Guardrail described: fixes arrive as pull requests that pass checks and are reviewed by developers before merge. ([source](https://www.averlon.ai/), read 10 Nov 2026)
Vendor's claim: Averlon also runs Cynos, a separate inference platform giving API access to models from several providers (not described as a customer agent builder). ([source](https://www.averlon.ai/), read 10 Nov 2026)
1 more on the [profile](/platforms/averlon/) | Vendor's claim: Dux uses AI agents across analysis, mitigation and remediation acceleration. ([source](https://dux.io/), read 10 Nov 2026)
None found on 10 Nov 2026: Named ready-made agents, customer-built agents, or controls and guardrails. ([source](https://dux.io/), read 10 Nov 2026) |
| Works on the stack you have | Vendor's claim: Averlon integrates with scanners including Wiz, Tenable, Upwind, Qualys and Snyk. ([source](https://www.averlon.ai/platform), read 10 Nov 2026)
Vendor's claim: It ingests findings from posture, identity, runtime, vulnerability scanners and code. ([source](https://www.averlon.ai/platform), read 10 Nov 2026)
Vendor's claim: A Wiz integration post describes Wiz supplying risk context while Averlon does triage and remediation. ([source](https://www.averlon.ai/blog/averlon-and-wiz-accelerate-remediation-and-reduce-exposure), read 10 Nov 2026)
Vendor's claim: Remediation actions are published on the GitHub Marketplace; Terraform, Pulumi and Helm are read. ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
1 more on the [profile](/platforms/averlon/) | Vendor's claim: Mitigation stage works from the customer's existing stack. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Dux reviews the whole security posture to find mitigations. ([source](https://dux.io/), read 10 Nov 2026)
None found on 10 Nov 2026: Named scanner, cloud, code host or ticketing integrations. ([source](https://dux.io/), read 10 Nov 2026) |
| Proof | Vendor's claim: A vendor-published customer example: 110,000 critical and high issues, 3,400 tickets, became 260 pull requests; MTTR fell from 45 days to 6 days (customer unnamed). ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
Vendor's claim: The same example reports mean time to remediate down from 45 days to 6 days. ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
Vendor's claim: The Why Averlon page shows a noise-reduction example (140K issues on 28K assets reduced to 6,924 critical issues on 310 assets); customer unnamed, method not stated on the page. ([source](https://www.averlon.ai/why-averlon), read 10 Nov 2026)
Vendor's claim: Homepage headline metrics (90% faster remediation, 95% fewer false positives) are stated without a method on the page. ([source](https://www.averlon.ai/), read 10 Nov 2026)
2 more on the [profile](/platforms/averlon/) | Vendor's claim: Quote from Mille Gandelsman (CPO at Opti, ex-VP at Tenable) on the home page. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Quote from Andrew Wilder (CSO at Vetcor, ex-Nestle) on the home page. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Quote from Rinki Sethi (CSO at Upwind, ex-BILL). ([source](https://dux.io/), read 10 Nov 2026)
None found on 10 Nov 2026: Named customers, case studies, published results or research publications (quotes above are from named security executives, not stated customers). ([source](https://dux.io/), read 10 Nov 2026) |
| Profile facts | Vendor's claim: Averlon came out of stealth May 23, 2024 with $8M led by Voyager Capital (Salesforce Ventures, Outpost Ventures), for $10.5M total funding. ([source](https://www.averlon.ai/blog/averlon-comes-out-of-stealth-mode-with-10m-in-funding-to-advance-ai-powered-cloud-security), read 10 Nov 2026)
Vendor's claim: The investment was led by Voyager Capital with Salesforce Ventures and Outpost Ventures. ([source](https://www.averlon.ai/blog/averlon-comes-out-of-stealth-mode-with-10m-in-funding-to-advance-ai-powered-cloud-security), read 10 Nov 2026)
Vendor's claim: Founded in 2022 by Sunil Gottumukkala (CEO) and Vishal Agarwal (CTO). ([source](https://www.averlon.ai/blog/averlon-comes-out-of-stealth-mode-with-10m-in-funding-to-advance-ai-powered-cloud-security), read 10 Nov 2026)
Vendor's claim: Product names: Averlon Agentic Remediation Operations platform, Precog (pre-merge), Cynos (inference platform). ([source](https://www.averlon.ai/), read 10 Nov 2026) | Vendor's claim: Product category on page title and heading: Agentic Exposure Management. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Company legal name in footer: Dux, Inc. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Company description: built by security veterans. ([source](https://dux.io/), read 10 Nov 2026)
None found on 10 Nov 2026: Pricing, funding, investors (a Backed by section shows logos only, no text), founders, HQ, headcount, careers (dux.io/about and /careers return 404). ([source](https://dux.io/), read 10 Nov 2026) |
Alphabetical by name. Each line is one fact with its label, source and read date.
## Profiles
- [Averlon profile](/platforms/averlon/): agentic remediation
- [Dux Security profile](/platforms/dux/): agentic exposure management
## Related pages
- [24 pairs, side by side](/compare/)
- [Averlon vs Rival Security: the sourced facts side by side](/compare/averlon-vs-rival/)
- [Astelia Security vs Rival Security: the sourced facts side by side](/compare/astelia-vs-rival/)
- [Backline Security vs Dux Security: the sourced facts side by side](/compare/backline-vs-dux/)
## Sources
- Averlon: www.averlon.ai/platform: https://www.averlon.ai/platform (read 10 Nov 2026)
- Averlon: www.averlon.ai/: https://www.averlon.ai/ (read 10 Nov 2026)
- Averlon: www.averlon.ai/why-averlon: https://www.averlon.ai/why-averlon (read 10 Nov 2026)
- Averlon: www.averlon.ai/blog/automating-remediation-application-infrastructure-security-i: https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues (read 10 Nov 2026)
- Averlon: www.averlon.ai/blog/cve-2026-98432-linux-kernel-tcp-use-after-free: https://www.averlon.ai/blog/cve-2026-98432-linux-kernel-tcp-use-after-free (read 10 Nov 2026)
- Averlon: www.averlon.ai/blog/react2shell-cve-2025-55182-explained: https://www.averlon.ai/blog/react2shell-cve-2025-55182-explained (read 10 Nov 2026)
- Averlon: research.averlon.ai/vulnerability-intelligence: https://research.averlon.ai/vulnerability-intelligence (read 10 Nov 2026)
- Averlon: www.averlon.ai/blog/averlon-and-wiz-accelerate-remediation-and-reduce-exposure: https://www.averlon.ai/blog/averlon-and-wiz-accelerate-remediation-and-reduce-exposure (read 10 Nov 2026)
- Dux Security: dux.io/: https://dux.io/ (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/compare/averlon-vs-dux/
---
# Averlon vs Rival Security: the sourced facts side by side
Side by side, read 10 Nov 2026
**The short answer.** Averlon and Rival Security, on the same rows. Fact lines: Averlon 40, Rival Security 40. Third-party: 0 and 0. Fixes: Averlon, pull requests and patches through patch tools; Rival Security, pull requests and mitigations. Averlon has a none-found line on speed; Rival Security on proof. The rows below set the sourced facts side by side; the page names no pick.
## The same rows for both
| Row | Averlon | Rival Security |
| --- | --- | --- |
| What it is | Agentic remediation (exposure/attack-chain analysis with fixes delivered into developer workflows) | Agentic security platform / agent harness for vulnerability management, code and cloud security |
| What it 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. | 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. |
| Where it is 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. | 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. |
| Proves exploitability in your environment | Vendor's claim: Averlon says it checks applicability against the customer's own environment and tests reachability across network configuration, IAM policies and Kubernetes RBAC. ([source](https://www.averlon.ai/platform), read 10 Nov 2026)
Vendor's claim: Attack chains are mapped to MITRE ATT&CK, with blast radius, and fixes that break the most chains are placed first. ([source](https://www.averlon.ai/platform), read 10 Nov 2026)
Vendor's claim: The homepage demo shows per-finding evidence fields (network exploitability, external exposure, known exploits, access to critical data, attack-chain membership) behind each triage decision. ([source](https://www.averlon.ai/), read 10 Nov 2026)
Vendor's claim: Averlon lists compensating-control assessment as a capability, to find controls already limiting risk. ([source](https://www.averlon.ai/why-averlon), read 10 Nov 2026) | Vendor's claim: Home page lists a Triage Exploitability agent that determines what is actually exploitable in the customer environment. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page says Rival reads every scanner finding against the real environment and keeps only those that can cause harm; it cites a 94.6% reduction in findings. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page reports 98% of findings proven unexploitable, 87% faster remediation and 1.5 hours to first value (no method given on the page). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: In its PHP2Shell write-up, Rival says agents ordered services to fix by reachability, internet-exposed unauthenticated workloads first. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Ships the fix | Vendor's claim: Averlon says it delivers context-aware fixes inside IDEs, source control and CLI, and applies the same reasoning before merge. ([source](https://www.averlon.ai/), read 10 Nov 2026)
Vendor's claim: Its GitHub Actions generate ready-to-merge pull requests for application and infrastructure issues. ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
Vendor's claim: Fix actions cover container images, Terraform and Pulumi IaC, and Kubernetes Helm charts. ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
Vendor's claim: The vendor's example flow expects a human developer to review each generated fix (about 15 minutes per fix in its example). ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
2 more on the [profile](/platforms/averlon/) | Vendor's claim: Home page lists an Autonomous Remediation agent that generates and ships tested fixes. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page describes the remediation flow as plan, test, and open a pull request for human review. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival lists a WAF mitigation agent that checks whether a WAF blocks exploitation and adjusts it. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival describes an alternative-remediation agent for legacy apps that plans a fix without upgrading libraries. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
2 more on the [profile](/platforms/rival/) |
| Finds the owner | Vendor's claim: Averlon traces a base-image vulnerability to the Dockerfile and routes it to the team that owns it. ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
Vendor's claim: For each fix group it creates a pull request plus a ticket for that PR assigned to the developer who owns the code. ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
Vendor's claim: In the vendor's customer example, issues were mapped to their source (base image or dependency) and grouped, instead of being assigned individually. ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026) | Vendor's claim: Home page lists an Ownership Resolution agent that maps each finding to the team that can fix it. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page says the owner-finding agent weighs root cause, team structure and past history (memories). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: PHP2Shell write-up says agents can message the relevant employees, and the harness lists human follow-ups. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
| Speed on a new disclosure | Vendor's claim: A customer quote on the vendor site credits Averlon with saving time in 0-day incident response for the libWebp vulnerability. ([source](https://www.averlon.ai/), read 10 Nov 2026)
Vendor's claim: Averlon published a response write-up dated Nov 2, 2026 on CVE-2026-98432, about 18 days after the CVE was published on October 15, 2026, covering which network paths expose a host. ([source](https://www.averlon.ai/blog/cve-2026-98432-linux-kernel-tcp-use-after-free), read 10 Nov 2026)
Vendor's claim: It also published an explainer for React2Shell (CVE-2025-55182) on Dec 4, 2025, updated as new CVEs followed. ([source](https://www.averlon.ai/blog/react2shell-cve-2025-55182-explained), read 10 Nov 2026)
Vendor's claim: Averlon runs a vulnerability intelligence site (research.averlon.ai); its page content was not readable in a plain fetch beyond the title. ([source](https://research.averlon.ai/vulnerability-intelligence), read 10 Nov 2026)
1 more on the [profile](/platforms/averlon/) | Vendor's claim: Home page lists a 0-day Fast Response agent covering triage through remediation. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page describes 0-day rapid response as finding exposure across code, images and cloud and prioritizing what to do first (page also claims a drop from days to minutes). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Published response write-up: for PHP2Shell, agents were triaging customer environments hours before scanners could detect the CVEs. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: The same write-up reports scanning more than 80,000 repositories within hours. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Agents you can shape | Vendor's claim: The platform lists Mitigation Agents and Remediation Agents as ready-made components. ([source](https://www.averlon.ai/platform), read 10 Nov 2026)
Vendor's claim: The homepage demo shows a 'Remediation Agent' proposing a pull request that waits for merge, and 'Autonomous AI Triage' on each finding. ([source](https://www.averlon.ai/), read 10 Nov 2026)
Vendor's claim: Guardrail described: fixes arrive as pull requests that pass checks and are reviewed by developers before merge. ([source](https://www.averlon.ai/), read 10 Nov 2026)
Vendor's claim: Averlon also runs Cynos, a separate inference platform giving API access to models from several providers (not described as a customer agent builder). ([source](https://www.averlon.ai/), read 10 Nov 2026)
1 more on the [profile](/platforms/averlon/) | Vendor's claim: Rival offers ready-made agents that can be customized and extended. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival engineers build custom agents for the customer environment at no additional cost (Partner tier). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Customers can build their own agents on the harness. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page says 64+ more agents are available beyond the five featured. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
2 more on the [profile](/platforms/rival/) |
| Works on the stack you have | Vendor's claim: Averlon integrates with scanners including Wiz, Tenable, Upwind, Qualys and Snyk. ([source](https://www.averlon.ai/platform), read 10 Nov 2026)
Vendor's claim: It ingests findings from posture, identity, runtime, vulnerability scanners and code. ([source](https://www.averlon.ai/platform), read 10 Nov 2026)
Vendor's claim: A Wiz integration post describes Wiz supplying risk context while Averlon does triage and remediation. ([source](https://www.averlon.ai/blog/averlon-and-wiz-accelerate-remediation-and-reduce-exposure), read 10 Nov 2026)
Vendor's claim: Remediation actions are published on the GitHub Marketplace; Terraform, Pulumi and Helm are read. ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
1 more on the [profile](/platforms/averlon/) | Vendor's claim: Home page names cloud, code host and infrastructure integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page names scanner, control and task integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases table shows findings sourced from Wiz, Qualys, GitHub, a pentest, and Rival's own SCA and Code scanners. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Agents combine connected services with a Rival Security Knowledge Graph. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
| Proof | Vendor's claim: A vendor-published customer example: 110,000 critical and high issues, 3,400 tickets, became 260 pull requests; MTTR fell from 45 days to 6 days (customer unnamed). ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
Vendor's claim: The same example reports mean time to remediate down from 45 days to 6 days. ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
Vendor's claim: The Why Averlon page shows a noise-reduction example (140K issues on 28K assets reduced to 6,924 critical issues on 310 assets); customer unnamed, method not stated on the page. ([source](https://www.averlon.ai/why-averlon), read 10 Nov 2026)
Vendor's claim: Homepage headline metrics (90% faster remediation, 95% fewer false positives) are stated without a method on the page. ([source](https://www.averlon.ai/), read 10 Nov 2026)
2 more on the [profile](/platforms/averlon/) | Vendor's claim: Use-cases page claims 13M+ agent runs. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival published SASTBench, a benchmark for SAST triage using real CVEs as true positives and filtered SAST findings as noise. ([source](https://rival.security/blog/sastbench-measuring-ai-security-automation?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Research blog post claims Rival workflows outperform current frontier models on the Spider 2.0 benchmark. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Published incident write-up (PHP2Shell, Nov 2, 2026) with unnamed customer results. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Profile facts | Vendor's claim: Averlon came out of stealth May 23, 2024 with $8M led by Voyager Capital (Salesforce Ventures, Outpost Ventures), for $10.5M total funding. ([source](https://www.averlon.ai/blog/averlon-comes-out-of-stealth-mode-with-10m-in-funding-to-advance-ai-powered-cloud-security), read 10 Nov 2026)
Vendor's claim: The investment was led by Voyager Capital with Salesforce Ventures and Outpost Ventures. ([source](https://www.averlon.ai/blog/averlon-comes-out-of-stealth-mode-with-10m-in-funding-to-advance-ai-powered-cloud-security), read 10 Nov 2026)
Vendor's claim: Founded in 2022 by Sunil Gottumukkala (CEO) and Vishal Agarwal (CTO). ([source](https://www.averlon.ai/blog/averlon-comes-out-of-stealth-mode-with-10m-in-funding-to-advance-ai-powered-cloud-security), read 10 Nov 2026)
Vendor's claim: Product names: Averlon Agentic Remediation Operations platform, Precog (pre-merge), Cynos (inference platform). ([source](https://www.averlon.ai/), read 10 Nov 2026) | Vendor's claim: Tagline and category: Rival describes itself as an agent harness for cybersecurity. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Research blog launched Feb 2025 describing early experiments building AI systems for cybersecurity. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
None found on 10 Nov 2026: Pricing (rival.security/pricing returns 404; book-a-demo form only). ([source](https://rival.security/book-a-demo-form?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
None found on 10 Nov 2026: Funding, investors, founders, headcount, HQ or founding year on home, blog, careers, book-a-demo pages. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
Alphabetical by name. Each line is one fact with its label, source and read date.
## Profiles
- [Averlon profile](/platforms/averlon/): agentic remediation
- [Rival Security profile](/platforms/rival/): agentic security platform
## Related pages
- [24 pairs, side by side](/compare/)
- [Backline Security vs Dux Security: the sourced facts side by side](/compare/backline-vs-dux/)
- [Averlon vs Dux Security: the sourced facts side by side](/compare/averlon-vs-dux/)
- [Backline Security vs Rival Security: the sourced facts side by side](/compare/backline-vs-rival/)
## Sources
- Averlon: www.averlon.ai/platform: https://www.averlon.ai/platform (read 10 Nov 2026)
- Averlon: www.averlon.ai/: https://www.averlon.ai/ (read 10 Nov 2026)
- Averlon: www.averlon.ai/why-averlon: https://www.averlon.ai/why-averlon (read 10 Nov 2026)
- Averlon: www.averlon.ai/blog/automating-remediation-application-infrastructure-security-i: https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues (read 10 Nov 2026)
- Averlon: www.averlon.ai/blog/cve-2026-98432-linux-kernel-tcp-use-after-free: https://www.averlon.ai/blog/cve-2026-98432-linux-kernel-tcp-use-after-free (read 10 Nov 2026)
- Averlon: www.averlon.ai/blog/react2shell-cve-2025-55182-explained: https://www.averlon.ai/blog/react2shell-cve-2025-55182-explained (read 10 Nov 2026)
- Averlon: research.averlon.ai/vulnerability-intelligence: https://research.averlon.ai/vulnerability-intelligence (read 10 Nov 2026)
- Averlon: www.averlon.ai/blog/averlon-and-wiz-accelerate-remediation-and-reduce-exposure: https://www.averlon.ai/blog/averlon-and-wiz-accelerate-remediation-and-reduce-exposure (read 10 Nov 2026)
- Rival Security: rival.security/: https://rival.security/ (read 10 Nov 2026)
- Rival Security: rival.security/use-cases: https://rival.security/use-cases (read 10 Nov 2026)
- Rival Security: rival.security/blog/php2shell-black-october-2026: https://rival.security/blog/php2shell-black-october-2026 (read 10 Nov 2026)
- Rival Security: docs.rival.security: https://docs.rival.security (read 10 Nov 2026)
- Rival Security: rival.security/blog/sastbench-measuring-ai-security-automation: https://rival.security/blog/sastbench-measuring-ai-security-automation (read 10 Nov 2026)
- Rival Security: rival.security/blog: https://rival.security/blog (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/compare/averlon-vs-rival/
---
# Backline Security vs Dux Security: the sourced facts side by side
Side by side, read 10 Nov 2026
**The short answer.** Backline Security and Dux Security. Backline Security has 44 fact lines (3 third-party) and Dux Security has 28 (0 third-party). Fixes: Backline Security, pull requests and tickets; Dux Security, mitigations and patches through patch tools. None found: Backline Security on speed; Dux Security on exploitability. The rows below set the sourced facts side by side; the page names no pick.
## The same rows for both
| Row | Backline Security | Dux Security |
| --- | --- | --- |
| What it is | Agentic remediation (Autonomous Exposure Remediation) | Agentic exposure management (exploitability analysis, mitigation, remediation acceleration) |
| What it 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. | 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. |
| Where it is 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. | 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. |
| Proves exploitability in your environment | Vendor's claim: Product FAQ says agents analyze actual exploitability in the customer runtime environment. ([source](https://backline.ai/product/), read 10 Nov 2026)
Vendor's claim: Agents check code reachability and cloud configuration to separate active threats from dormant packages. ([source](https://backline.ai/product/), read 10 Nov 2026)
Vendor's claim: Telecom case study: exploitability and reachability analysis per vulnerability in under two minutes. ([source](https://backline.ai/case-studies/hands-off-fully-fixed/), read 10 Nov 2026)
Vendor's claim: Data-analytics case study: reachability, exploitability and fixability analysis layered over existing tools. ([source](https://backline.ai/case-studies/five-weeks-to-under-a-day/), read 10 Nov 2026)
1 more on the [profile](/platforms/backline/) | Vendor's claim: Dux maps how vulnerabilities, assets and controls connect to judge exploitability. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Stated aim: separate reachable from truly exploitable risk. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Home page lead: AI agents for instant exploitability analysis. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Exploitability stage answers where the customer is already protected. ([source](https://dux.io/), read 10 Nov 2026)
1 more on the [profile](/platforms/dux/) |
| Ships the fix | Vendor's claim: Backline generates, tests and delivers production-ready fixes rather than tickets. ([source](https://backline.ai/), read 10 Nov 2026)
Vendor's claim: Each remediation includes a plan and a ready-to-review PR linked to the originating findings. ([source](https://backline.ai/product/), read 10 Nov 2026)
Vendor's claim: Fix types covered: SCA dependency, container image CVEs and IaC misconfigurations. ([source](https://backline.ai/product/), read 10 Nov 2026)
Vendor's claim: Validation before delivery: existing unit tests and dependency checks are run before a fix is proposed. ([source](https://backline.ai/product/), read 10 Nov 2026)
3 more on the [profile](/platforms/backline/) | Vendor's claim: Dux favors lightweight mitigations such as a missing control or config change instead of a patch. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Mitigations are ones the customer deploys on its own. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Remediation stage speeds up the fix process by tagging assets and tying data sources together. ([source](https://dux.io/), read 10 Nov 2026)
None found on 10 Nov 2026: Generated pull requests, tested code fixes or approval-gated automated changes. ([source](https://dux.io/), read 10 Nov 2026) |
| Finds the owner | Vendor's claim: Owner post: Backline brings each remediation to the responsible people in Slack, Microsoft Teams and Jira and stays in the conversation until the finding is gone. ([source](https://backline.ai/blog/finding-and-chasing-the-owner-of-a-fix-in-jira-teams-or-slack/), read 10 Nov 2026)
Vendor's claim: It follows up and escalates when nothing moves. ([source](https://backline.ai/blog/finding-and-chasing-the-owner-of-a-fix-in-jira-teams-or-slack/), read 10 Nov 2026)
Vendor's claim: In Jira it opens and maintains a ticket in the team's own project. ([source](https://backline.ai/blog/finding-and-chasing-the-owner-of-a-fix-in-jira-teams-or-slack/), read 10 Nov 2026)
Vendor's claim: Routing runs inside policies the customer sets. ([source](https://backline.ai/blog/finding-and-chasing-the-owner-of-a-fix-in-jira-teams-or-slack/), read 10 Nov 2026) | Vendor's claim: Remediation stage poses the question of who should remediate. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Auto-tagging of every asset is the ownership mechanism described. ([source](https://dux.io/), read 10 Nov 2026)
None found on 10 Nov 2026: Ticket routing, follow-up or escalation features. ([source](https://dux.io/), read 10 Nov 2026) |
| Speed on a new disclosure | Vendor's claim: Published response write-up on HTTP2Shell (Node.js Brotli CVE): it reached Backline customers via container image scans, so detection depends on the connected scanner. ([source](https://backline.ai/blog/http2shell-three-images-one-cve/), read 10 Nov 2026)
Vendor's claim: Remediation-speed claim: MTTR down to one hour from more than two weeks per vulnerability at a Fortune 500 manufacturer (unnamed). ([source](https://backline.ai/case-studies/case-study-closing-the-exposure-window/), read 10 Nov 2026)
Vendor's claim: Remediation-speed claim: average time to fix went from 5 weeks to 2 hours at a data-analytics company (unnamed). ([source](https://backline.ai/case-studies/five-weeks-to-under-a-day/), read 10 Nov 2026)
None found on 10 Nov 2026: A dedicated zero-day or new-CVE exposure lookup feature, or a time-to-answer claim for new disclosures, on the home or product pages. ([source](https://backline.ai/product/), read 10 Nov 2026) | Vendor's claim: Positioning is speed against attackers. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Home page frames time-to-exploit collapsing from weeks to minutes. ([source](https://dux.io/), read 10 Nov 2026)
None found on 10 Nov 2026: Zero-day response feature, time-to-answer number or published response write-up. ([source](https://dux.io/), read 10 Nov 2026) |
| Agents you can shape | Vendor's claim: Four named vendor-built agents: Analyst (Andy), Planner (Polly), Coder (Codie), Verifier (Vera). ([source](https://backline.ai/), read 10 Nov 2026)
Vendor's claim: Verifier agent validates every fix through testing. ([source](https://backline.ai/), read 10 Nov 2026)
Vendor's claim: Autonomy split: 80% auto fix handled end to end, 20% hybrid with human-in-the-loop input. ([source](https://backline.ai/), read 10 Nov 2026)
Vendor's claim: Vendor-built custom behavior: agent behavior tuned to the customer SDLC (build conventions, release rules). ([source](https://backline.ai/case-studies/hands-off-fully-fixed/), read 10 Nov 2026)
2 more on the [profile](/platforms/backline/) | Vendor's claim: Dux uses AI agents across analysis, mitigation and remediation acceleration. ([source](https://dux.io/), read 10 Nov 2026)
None found on 10 Nov 2026: Named ready-made agents, customer-built agents, or controls and guardrails. ([source](https://dux.io/), read 10 Nov 2026) |
| Works on the stack you have | Third-party source: TechCrunch (Jan 2025): takes notifications from other security tools and remediates. ([source](https://techcrunch.com/2025/01/30/backline-automatically-remediates-security-vulnerabilities/), read 10 Nov 2026)
Vendor's claim: Ingests findings from the customer's existing production scanners. ([source](https://backline.ai/product/), read 10 Nov 2026)
Vendor's claim: Integrates with security stack, communication platforms and code repositories (no named list in page text). ([source](https://backline.ai/), read 10 Nov 2026)
Vendor's claim: Named ticketing and chat: Slack, Microsoft Teams, Jira. ([source](https://backline.ai/blog/finding-and-chasing-the-owner-of-a-fix-in-jira-teams-or-slack/), read 10 Nov 2026)
1 more on the [profile](/platforms/backline/) | Vendor's claim: Mitigation stage works from the customer's existing stack. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Dux reviews the whole security posture to find mitigations. ([source](https://dux.io/), read 10 Nov 2026)
None found on 10 Nov 2026: Named scanner, cloud, code host or ticketing integrations. ([source](https://dux.io/), read 10 Nov 2026) |
| Proof | Vendor's claim: Named customer quote: Arkose Labs senior security architect. ([source](https://backline.ai/), read 10 Nov 2026)
Vendor's claim: Named customer quotes also from Cockroach Labs, Celanese and Thetaray on the home page. ([source](https://backline.ai/), read 10 Nov 2026)
Vendor's claim: Case study: Fortune 500 manufacturer, 20x remediation capacity and 100% auto-merged fixes (customer unnamed). ([source](https://backline.ai/case-studies/case-study-closing-the-exposure-window/), read 10 Nov 2026)
Vendor's claim: Case study: telecom provider, 95% of fixes with zero manual code changes (customer unnamed). ([source](https://backline.ai/case-studies/hands-off-fully-fixed/), read 10 Nov 2026)
2 more on the [profile](/platforms/backline/) | Vendor's claim: Quote from Mille Gandelsman (CPO at Opti, ex-VP at Tenable) on the home page. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Quote from Andrew Wilder (CSO at Vetcor, ex-Nestle) on the home page. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Quote from Rinki Sethi (CSO at Upwind, ex-BILL). ([source](https://dux.io/), read 10 Nov 2026)
None found on 10 Nov 2026: Named customers, case studies, published results or research publications (quotes above are from named security executives, not stated customers). ([source](https://dux.io/), read 10 Nov 2026) |
| Profile facts | Third-party source: Funding: $9 million seed round led by StageOne Ventures, announced Jan 30, 2025. ([source](https://techcrunch.com/2025/01/30/backline-automatically-remediates-security-vulnerabilities/), read 10 Nov 2026)
Vendor's claim: Founders and leadership listed on company page. ([source](https://backline.ai/company/), read 10 Nov 2026)
Third-party source: CEO previously co-founded Whitebox Security (sold to SailPoint) and Apolicy (acquired by Sysdig). ([source](https://techcrunch.com/2025/01/30/backline-automatically-remediates-security-vulnerabilities/), read 10 Nov 2026)
Vendor's claim: Category: Autonomous Exposure Remediation, which it says Gartner named in June 2026. ([source](https://backline.ai/product/), read 10 Nov 2026) | Vendor's claim: Product category on page title and heading: Agentic Exposure Management. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Company legal name in footer: Dux, Inc. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Company description: built by security veterans. ([source](https://dux.io/), read 10 Nov 2026)
None found on 10 Nov 2026: Pricing, funding, investors (a Backed by section shows logos only, no text), founders, HQ, headcount, careers (dux.io/about and /careers return 404). ([source](https://dux.io/), read 10 Nov 2026) |
Alphabetical by name. Each line is one fact with its label, source and read date.
## Profiles
- [Backline Security profile](/platforms/backline/): agentic remediation
- [Dux Security profile](/platforms/dux/): agentic exposure management
## Related pages
- [24 pairs, side by side](/compare/)
- [Backline Security vs Rival Security: the sourced facts side by side](/compare/backline-vs-rival/)
- [Averlon vs Rival Security: the sourced facts side by side](/compare/averlon-vs-rival/)
- [Cogent Security vs Rival Security: the sourced facts side by side](/compare/cogent-vs-rival/)
## Sources
- Backline Security: backline.ai/product/: https://backline.ai/product/ (read 10 Nov 2026)
- Backline Security: backline.ai/case-studies/hands-off-fully-fixed/: https://backline.ai/case-studies/hands-off-fully-fixed/ (read 10 Nov 2026)
- Backline Security: backline.ai/case-studies/five-weeks-to-under-a-day/: https://backline.ai/case-studies/five-weeks-to-under-a-day/ (read 10 Nov 2026)
- Backline Security: backline.ai/blog/http2shell-three-images-one-cve/: https://backline.ai/blog/http2shell-three-images-one-cve/ (read 10 Nov 2026)
- Backline Security: backline.ai/: https://backline.ai/ (read 10 Nov 2026)
- Backline Security: backline.ai/fixaition/: https://backline.ai/fixaition/ (read 10 Nov 2026)
- Backline Security: backline.ai/blog/finding-and-chasing-the-owner-of-a-fix-in-jira-teams-or-slack/: https://backline.ai/blog/finding-and-chasing-the-owner-of-a-fix-in-jira-teams-or-slack/ (read 10 Nov 2026)
- Backline Security: backline.ai/case-studies/case-study-closing-the-exposure-window/: https://backline.ai/case-studies/case-study-closing-the-exposure-window/ (read 10 Nov 2026)
- techcrunch.com: /2025/01/30/backline-automatically-remediates-security-vulnerabilities: https://techcrunch.com/2025/01/30/backline-automatically-remediates-security-vulnerabilities/ (read 10 Nov 2026)
- Dux Security: dux.io/: https://dux.io/ (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/compare/backline-vs-dux/
---
# Backline Security vs Rival Security: the sourced facts side by side
Side by side, read 10 Nov 2026
**The short answer.** Backline Security and Rival Security are set side by side on the same rows. Fact lines: Backline Security 44, Rival Security 40. Third-party: 3 and 0. Fixes: Backline Security, pull requests; Rival Security, pull requests. None found: Backline Security on speed; Rival Security on proof. The rows below set the sourced facts side by side; the page names no pick.
## The same rows for both
| Row | Backline Security | Rival Security |
| --- | --- | --- |
| What it is | Agentic remediation (Autonomous Exposure Remediation) | Agentic security platform / agent harness for vulnerability management, code and cloud security |
| What it 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. | 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. |
| Where it is 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. | 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. |
| Proves exploitability in your environment | Vendor's claim: Product FAQ says agents analyze actual exploitability in the customer runtime environment. ([source](https://backline.ai/product/), read 10 Nov 2026)
Vendor's claim: Agents check code reachability and cloud configuration to separate active threats from dormant packages. ([source](https://backline.ai/product/), read 10 Nov 2026)
Vendor's claim: Telecom case study: exploitability and reachability analysis per vulnerability in under two minutes. ([source](https://backline.ai/case-studies/hands-off-fully-fixed/), read 10 Nov 2026)
Vendor's claim: Data-analytics case study: reachability, exploitability and fixability analysis layered over existing tools. ([source](https://backline.ai/case-studies/five-weeks-to-under-a-day/), read 10 Nov 2026)
1 more on the [profile](/platforms/backline/) | Vendor's claim: Home page lists a Triage Exploitability agent that determines what is actually exploitable in the customer environment. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page says Rival reads every scanner finding against the real environment and keeps only those that can cause harm; it cites a 94.6% reduction in findings. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page reports 98% of findings proven unexploitable, 87% faster remediation and 1.5 hours to first value (no method given on the page). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: In its PHP2Shell write-up, Rival says agents ordered services to fix by reachability, internet-exposed unauthenticated workloads first. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Ships the fix | Vendor's claim: Backline generates, tests and delivers production-ready fixes rather than tickets. ([source](https://backline.ai/), read 10 Nov 2026)
Vendor's claim: Each remediation includes a plan and a ready-to-review PR linked to the originating findings. ([source](https://backline.ai/product/), read 10 Nov 2026)
Vendor's claim: Fix types covered: SCA dependency, container image CVEs and IaC misconfigurations. ([source](https://backline.ai/product/), read 10 Nov 2026)
Vendor's claim: Validation before delivery: existing unit tests and dependency checks are run before a fix is proposed. ([source](https://backline.ai/product/), read 10 Nov 2026)
3 more on the [profile](/platforms/backline/) | Vendor's claim: Home page lists an Autonomous Remediation agent that generates and ships tested fixes. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page describes the remediation flow as plan, test, and open a pull request for human review. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival lists a WAF mitigation agent that checks whether a WAF blocks exploitation and adjusts it. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival describes an alternative-remediation agent for legacy apps that plans a fix without upgrading libraries. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
2 more on the [profile](/platforms/rival/) |
| Finds the owner | Vendor's claim: Owner post: Backline brings each remediation to the responsible people in Slack, Microsoft Teams and Jira and stays in the conversation until the finding is gone. ([source](https://backline.ai/blog/finding-and-chasing-the-owner-of-a-fix-in-jira-teams-or-slack/), read 10 Nov 2026)
Vendor's claim: It follows up and escalates when nothing moves. ([source](https://backline.ai/blog/finding-and-chasing-the-owner-of-a-fix-in-jira-teams-or-slack/), read 10 Nov 2026)
Vendor's claim: In Jira it opens and maintains a ticket in the team's own project. ([source](https://backline.ai/blog/finding-and-chasing-the-owner-of-a-fix-in-jira-teams-or-slack/), read 10 Nov 2026)
Vendor's claim: Routing runs inside policies the customer sets. ([source](https://backline.ai/blog/finding-and-chasing-the-owner-of-a-fix-in-jira-teams-or-slack/), read 10 Nov 2026) | Vendor's claim: Home page lists an Ownership Resolution agent that maps each finding to the team that can fix it. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page says the owner-finding agent weighs root cause, team structure and past history (memories). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: PHP2Shell write-up says agents can message the relevant employees, and the harness lists human follow-ups. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
| Speed on a new disclosure | Vendor's claim: Published response write-up on HTTP2Shell (Node.js Brotli CVE): it reached Backline customers via container image scans, so detection depends on the connected scanner. ([source](https://backline.ai/blog/http2shell-three-images-one-cve/), read 10 Nov 2026)
Vendor's claim: Remediation-speed claim: MTTR down to one hour from more than two weeks per vulnerability at a Fortune 500 manufacturer (unnamed). ([source](https://backline.ai/case-studies/case-study-closing-the-exposure-window/), read 10 Nov 2026)
Vendor's claim: Remediation-speed claim: average time to fix went from 5 weeks to 2 hours at a data-analytics company (unnamed). ([source](https://backline.ai/case-studies/five-weeks-to-under-a-day/), read 10 Nov 2026)
None found on 10 Nov 2026: A dedicated zero-day or new-CVE exposure lookup feature, or a time-to-answer claim for new disclosures, on the home or product pages. ([source](https://backline.ai/product/), read 10 Nov 2026) | Vendor's claim: Home page lists a 0-day Fast Response agent covering triage through remediation. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page describes 0-day rapid response as finding exposure across code, images and cloud and prioritizing what to do first (page also claims a drop from days to minutes). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Published response write-up: for PHP2Shell, agents were triaging customer environments hours before scanners could detect the CVEs. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: The same write-up reports scanning more than 80,000 repositories within hours. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Agents you can shape | Vendor's claim: Four named vendor-built agents: Analyst (Andy), Planner (Polly), Coder (Codie), Verifier (Vera). ([source](https://backline.ai/), read 10 Nov 2026)
Vendor's claim: Verifier agent validates every fix through testing. ([source](https://backline.ai/), read 10 Nov 2026)
Vendor's claim: Autonomy split: 80% auto fix handled end to end, 20% hybrid with human-in-the-loop input. ([source](https://backline.ai/), read 10 Nov 2026)
Vendor's claim: Vendor-built custom behavior: agent behavior tuned to the customer SDLC (build conventions, release rules). ([source](https://backline.ai/case-studies/hands-off-fully-fixed/), read 10 Nov 2026)
2 more on the [profile](/platforms/backline/) | Vendor's claim: Rival offers ready-made agents that can be customized and extended. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival engineers build custom agents for the customer environment at no additional cost (Partner tier). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Customers can build their own agents on the harness. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page says 64+ more agents are available beyond the five featured. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
2 more on the [profile](/platforms/rival/) |
| Works on the stack you have | Third-party source: TechCrunch (Jan 2025): takes notifications from other security tools and remediates. ([source](https://techcrunch.com/2025/01/30/backline-automatically-remediates-security-vulnerabilities/), read 10 Nov 2026)
Vendor's claim: Ingests findings from the customer's existing production scanners. ([source](https://backline.ai/product/), read 10 Nov 2026)
Vendor's claim: Integrates with security stack, communication platforms and code repositories (no named list in page text). ([source](https://backline.ai/), read 10 Nov 2026)
Vendor's claim: Named ticketing and chat: Slack, Microsoft Teams, Jira. ([source](https://backline.ai/blog/finding-and-chasing-the-owner-of-a-fix-in-jira-teams-or-slack/), read 10 Nov 2026)
1 more on the [profile](/platforms/backline/) | Vendor's claim: Home page names cloud, code host and infrastructure integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page names scanner, control and task integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases table shows findings sourced from Wiz, Qualys, GitHub, a pentest, and Rival's own SCA and Code scanners. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Agents combine connected services with a Rival Security Knowledge Graph. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
| Proof | Vendor's claim: Named customer quote: Arkose Labs senior security architect. ([source](https://backline.ai/), read 10 Nov 2026)
Vendor's claim: Named customer quotes also from Cockroach Labs, Celanese and Thetaray on the home page. ([source](https://backline.ai/), read 10 Nov 2026)
Vendor's claim: Case study: Fortune 500 manufacturer, 20x remediation capacity and 100% auto-merged fixes (customer unnamed). ([source](https://backline.ai/case-studies/case-study-closing-the-exposure-window/), read 10 Nov 2026)
Vendor's claim: Case study: telecom provider, 95% of fixes with zero manual code changes (customer unnamed). ([source](https://backline.ai/case-studies/hands-off-fully-fixed/), read 10 Nov 2026)
2 more on the [profile](/platforms/backline/) | Vendor's claim: Use-cases page claims 13M+ agent runs. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival published SASTBench, a benchmark for SAST triage using real CVEs as true positives and filtered SAST findings as noise. ([source](https://rival.security/blog/sastbench-measuring-ai-security-automation?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Research blog post claims Rival workflows outperform current frontier models on the Spider 2.0 benchmark. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Published incident write-up (PHP2Shell, Nov 2, 2026) with unnamed customer results. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Profile facts | Third-party source: Funding: $9 million seed round led by StageOne Ventures, announced Jan 30, 2025. ([source](https://techcrunch.com/2025/01/30/backline-automatically-remediates-security-vulnerabilities/), read 10 Nov 2026)
Vendor's claim: Founders and leadership listed on company page. ([source](https://backline.ai/company/), read 10 Nov 2026)
Third-party source: CEO previously co-founded Whitebox Security (sold to SailPoint) and Apolicy (acquired by Sysdig). ([source](https://techcrunch.com/2025/01/30/backline-automatically-remediates-security-vulnerabilities/), read 10 Nov 2026)
Vendor's claim: Category: Autonomous Exposure Remediation, which it says Gartner named in June 2026. ([source](https://backline.ai/product/), read 10 Nov 2026) | Vendor's claim: Tagline and category: Rival describes itself as an agent harness for cybersecurity. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Research blog launched Feb 2025 describing early experiments building AI systems for cybersecurity. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
None found on 10 Nov 2026: Pricing (rival.security/pricing returns 404; book-a-demo form only). ([source](https://rival.security/book-a-demo-form?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
None found on 10 Nov 2026: Funding, investors, founders, headcount, HQ or founding year on home, blog, careers, book-a-demo pages. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
Alphabetical by name. Each line is one fact with its label, source and read date.
## Profiles
- [Backline Security profile](/platforms/backline/): agentic remediation
- [Rival Security profile](/platforms/rival/): agentic security platform
## Related pages
- [24 pairs, side by side](/compare/)
- [Cogent Security vs Rival Security: the sourced facts side by side](/compare/cogent-vs-rival/)
- [Backline Security vs Dux Security: the sourced facts side by side](/compare/backline-vs-dux/)
- [Cogent Security vs Zafran: the sourced facts side by side](/compare/cogent-vs-zafran/)
## Sources
- Backline Security: backline.ai/product/: https://backline.ai/product/ (read 10 Nov 2026)
- Backline Security: backline.ai/case-studies/hands-off-fully-fixed/: https://backline.ai/case-studies/hands-off-fully-fixed/ (read 10 Nov 2026)
- Backline Security: backline.ai/case-studies/five-weeks-to-under-a-day/: https://backline.ai/case-studies/five-weeks-to-under-a-day/ (read 10 Nov 2026)
- Backline Security: backline.ai/blog/http2shell-three-images-one-cve/: https://backline.ai/blog/http2shell-three-images-one-cve/ (read 10 Nov 2026)
- Backline Security: backline.ai/: https://backline.ai/ (read 10 Nov 2026)
- Backline Security: backline.ai/fixaition/: https://backline.ai/fixaition/ (read 10 Nov 2026)
- Backline Security: backline.ai/blog/finding-and-chasing-the-owner-of-a-fix-in-jira-teams-or-slack/: https://backline.ai/blog/finding-and-chasing-the-owner-of-a-fix-in-jira-teams-or-slack/ (read 10 Nov 2026)
- Backline Security: backline.ai/case-studies/case-study-closing-the-exposure-window/: https://backline.ai/case-studies/case-study-closing-the-exposure-window/ (read 10 Nov 2026)
- techcrunch.com: /2025/01/30/backline-automatically-remediates-security-vulnerabilities: https://techcrunch.com/2025/01/30/backline-automatically-remediates-security-vulnerabilities/ (read 10 Nov 2026)
- Rival Security: rival.security/: https://rival.security/ (read 10 Nov 2026)
- Rival Security: rival.security/use-cases: https://rival.security/use-cases (read 10 Nov 2026)
- Rival Security: rival.security/blog/php2shell-black-october-2026: https://rival.security/blog/php2shell-black-october-2026 (read 10 Nov 2026)
- Rival Security: docs.rival.security: https://docs.rival.security (read 10 Nov 2026)
- Rival Security: rival.security/blog/sastbench-measuring-ai-security-automation: https://rival.security/blog/sastbench-measuring-ai-security-automation (read 10 Nov 2026)
- Rival Security: rival.security/blog: https://rival.security/blog (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/compare/backline-vs-rival/
---
# Cogent Security vs Rival Security: the sourced facts side by side
Side by side, read 10 Nov 2026
**The short answer.** Cogent Security and Rival Security, on the same rows. Cogent Security has 40 fact lines (10 third-party) and Rival Security has 40 (0 third-party). Fixes: Cogent Security, patches through patch tools; Rival Security, pull requests. None found: Cogent Security on agents; Rival Security on proof. The rows below set the sourced facts side by side; the page names no pick.
## The same rows for both
| Row | Cogent Security | Rival Security |
| --- | --- | --- |
| What it is | Agentic vulnerability management and remediation (AI agents across the full vulnerability lifecycle) | Agentic security platform / agent harness for vulnerability management, code and cloud security |
| What it 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). | 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. |
| Where it is 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. | 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. |
| Proves exploitability in your environment | Vendor's claim: Cogent says it prioritizes by real exploitability and business impact, not only CVSS. ([source](https://www.cogent.com/platform/assess), read 10 Nov 2026)
Vendor's claim: On PHP2Shell, Cogent says it narrowed 2,266 affected assets (Fortune 500 average) to 16 using runtime exposure, internet reachability and business criticality. ([source](https://www.cogent.com/blog/cogent-expands-its-ai-cyber-defense-factory-with-specular-acquisition), read 10 Nov 2026)
Vendor's claim: A knowledge graph links assets to owners, business functions, network exposure and compensating controls. ([source](https://www.cogent.com/ai/cogent-ai-engine), read 10 Nov 2026)
Vendor's claim: Every output shows its chain of logic: data sources, agents involved and why that path was chosen. ([source](https://www.cogent.com/ai/cogent-ai-engine), read 10 Nov 2026)
1 more on the [profile](/platforms/cogent/) | Vendor's claim: Home page lists a Triage Exploitability agent that determines what is actually exploitable in the customer environment. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page says Rival reads every scanner finding against the real environment and keeps only those that can cause harm; it cites a 94.6% reduction in findings. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page reports 98% of findings proven unexploitable, 87% faster remediation and 1.5 hours to first value (no method given on the page). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: In its PHP2Shell write-up, Rival says agents ordered services to fix by reachability, internet-exposed unauthenticated workloads first. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Ships the fix | Third-party source: Its VR-1.1 model writes fixes for newly disclosed vulnerabilities; each patch goes to a separate review that tries to bypass it. ([source](https://siliconangle.com/2026/11/03/exclusive-cogent-securitys-vr-1-1-model-outscores-claude-code-and-codex-on-vulnerability-repair/), read 10 Nov 2026)
Third-party source: VR-1.1 also writes regression tests intended to fail if a later change reopens the flaw. ([source](https://siliconangle.com/2026/11/03/exclusive-cogent-securitys-vr-1-1-model-outscores-claude-code-and-codex-on-vulnerability-repair/), read 10 Nov 2026)
Vendor's claim: Cogent finds the fix, assesses impact and executes through existing tools, from assisted to fully autonomous. ([source](https://www.cogent.com/), read 10 Nov 2026)
Vendor's claim: High-impact changes require human approval and an audit trail. ([source](https://www.cogent.com/ai/autonomy-levels), read 10 Nov 2026)
1 more on the [profile](/platforms/cogent/) | Vendor's claim: Home page lists an Autonomous Remediation agent that generates and ships tested fixes. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page describes the remediation flow as plan, test, and open a pull request for human review. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival lists a WAF mitigation agent that checks whether a WAF blocks exploitation and adjusts it. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival describes an alternative-remediation agent for legacy apps that plans a fix without upgrading libraries. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
2 more on the [profile](/platforms/rival/) |
| Finds the owner | Third-party source: Per SiliconANGLE, agents determine asset ownership and map vulnerabilities to affected services. ([source](https://siliconangle.com/2026/02/18/cogent-security-raises-42m-scale-ai-agents-enterprise-vulnerability-remediation/), read 10 Nov 2026)
Third-party source: Per SiliconANGLE, agents track remediation status and verify completion after patches or config changes. ([source](https://siliconangle.com/2026/02/18/cogent-security-raises-42m-scale-ai-agents-enterprise-vulnerability-remediation/), read 10 Nov 2026)
Vendor's claim: The Discover page demo shows agents resolving an asset owner from ServiceNow CMDB and checking Jira ticket history. ([source](https://www.cogent.com/platform/discover), read 10 Nov 2026)
Vendor's claim: The CSC Generation case study says the team previously mapped owners, routed tickets and tracked SLAs manually. ([source](https://www.cogent.com/customers/csc-generation), read 10 Nov 2026) | Vendor's claim: Home page lists an Ownership Resolution agent that maps each finding to the team that can fix it. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page says the owner-finding agent weighs root cause, team structure and past history (memories). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: PHP2Shell write-up says agents can message the relevant employees, and the harness lists human follow-ups. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
| Speed on a new disclosure | Vendor's claim: Cogent says it identifies vulnerable software within minutes of disclosure. ([source](https://www.cogent.com/platform/discover), read 10 Nov 2026)
Vendor's claim: Homepage claim: identify vulnerable software within minutes of a new disclosure, before scanners can. ([source](https://www.cogent.com/), read 10 Nov 2026)
Vendor's claim: Cogent's Nov 10 post cites its PHP2Shell analysis, listed on the homepage as dated Oct 21, 2026, the same day as the disclosure. ([source](https://www.cogent.com/blog/cogent-expands-its-ai-cyber-defense-factory-with-specular-acquisition), read 10 Nov 2026) | Vendor's claim: Home page lists a 0-day Fast Response agent covering triage through remediation. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page describes 0-day rapid response as finding exposure across code, images and cloud and prioritizing what to do first (page also claims a drop from days to minutes). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Published response write-up: for PHP2Shell, agents were triaging customer environments hours before scanners could detect the CVEs. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: The same write-up reports scanning more than 80,000 repositories within hours. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Agents you can shape | Third-party source: Cogent's VR-1 and VR-1.1 are vendor-built reasoning models for vulnerability repair. ([source](https://siliconangle.com/2026/11/03/exclusive-cogent-securitys-vr-1-1-model-outscores-claude-code-and-codex-on-vulnerability-repair/), read 10 Nov 2026)
Vendor's claim: Ready-made specialized agents handle normalization, enrichment, risk assessment and remediation planning. ([source](https://www.cogent.com/ai/cogent-ai-engine), read 10 Nov 2026)
Vendor's claim: Agents check customer-defined guardrails before every action. ([source](https://www.cogent.com/ai/cogent-ai-engine), read 10 Nov 2026)
Vendor's claim: Autonomy is staged: start with recommendations and review, then expand. ([source](https://www.cogent.com/ai/autonomy-levels), read 10 Nov 2026)
1 more on the [profile](/platforms/cogent/) | Vendor's claim: Rival offers ready-made agents that can be customized and extended. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival engineers build custom agents for the customer environment at no additional cost (Partner tier). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Customers can build their own agents on the harness. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page says 64+ more agents are available beyond the five featured. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
2 more on the [profile](/platforms/rival/) |
| Works on the stack you have | Vendor's claim: Scanner integrations include Qualys, Rapid7 and Tenable. ([source](https://www.cogent.com/platform/integrations), read 10 Nov 2026)
Vendor's claim: Cloud security ingestion: AWS, Lacework, Orca, Upwind, Wiz. ([source](https://www.cogent.com/platform/integrations), read 10 Nov 2026)
Vendor's claim: Ticketing integrations: Jira and ServiceNow ITSM (push and track tickets). ([source](https://www.cogent.com/platform/integrations), read 10 Nov 2026)
Vendor's claim: Endpoint integrations: CrowdStrike, Microsoft Defender for Endpoint, SentinelOne. ([source](https://www.cogent.com/platform/integrations), read 10 Nov 2026)
2 more on the [profile](/platforms/cogent/) | Vendor's claim: Home page names cloud, code host and infrastructure integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page names scanner, control and task integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases table shows findings sourced from Wiz, Qualys, GitHub, a pentest, and Rival's own SCA and Code scanners. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Agents combine connected services with a Rival Security Knowledge Graph. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
| Proof | Third-party source: VR-1.1 passed 57.9% of 190 LiveCVEBench tasks; Claude Code and Codex scored 45.3% (vendor-run test, reported by SiliconANGLE). ([source](https://siliconangle.com/2026/11/03/exclusive-cogent-securitys-vr-1-1-model-outscores-claude-code-and-codex-on-vulnerability-repair/), read 10 Nov 2026)
Third-party source: Method notes: outbound network blocked during repairs and grading tests hidden; inference budgets differed across systems. ([source](https://siliconangle.com/2026/11/03/exclusive-cogent-securitys-vr-1-1-model-outscores-claude-code-and-codex-on-vulnerability-repair/), read 10 Nov 2026)
Third-party source: SiliconANGLE names Upwind, Alteryx and CSC Generation as customers and says Cogent works with dozens of Fortune 1000 companies. ([source](https://siliconangle.com/2026/02/18/cogent-security-raises-42m-scale-ai-agents-enterprise-vulnerability-remediation/), read 10 Nov 2026)
Vendor's claim: CSC Generation case study: 3 hours to full assessment, 100% of vulnerabilities managed autonomously (vendor-published). ([source](https://www.cogent.com/customers/csc-generation), read 10 Nov 2026)
2 more on the [profile](/platforms/cogent/) | Vendor's claim: Use-cases page claims 13M+ agent runs. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival published SASTBench, a benchmark for SAST triage using real CVEs as true positives and filtered SAST findings as noise. ([source](https://rival.security/blog/sastbench-measuring-ai-security-automation?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Research blog post claims Rival workflows outperform current frontier models on the Spider 2.0 benchmark. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Published incident write-up (PHP2Shell, Nov 2, 2026) with unnamed customer results. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Profile facts | Third-party source: Series A of $42M led by Bain Capital with Greylock Partners and Definition Capital, announced Feb 18, 2026. ([source](https://siliconangle.com/2026/02/18/cogent-security-raises-42m-scale-ai-agents-enterprise-vulnerability-remediation/), read 10 Nov 2026)
Third-party source: Founded in 2025, formally launched July 2025; works with dozens of Fortune 1000 companies (per SiliconANGLE). ([source](https://siliconangle.com/2026/02/18/cogent-security-raises-42m-scale-ai-agents-enterprise-vulnerability-remediation/), read 10 Nov 2026)
Vendor's claim: Acquired Specular (Google-backed AI security platform) on 10 Nov 2026. ([source](https://www.cogent.com/blog/cogent-expands-its-ai-cyber-defense-factory-with-specular-acquisition), read 10 Nov 2026)
Vendor's claim: Co-founders: Vineet Edupuganti (CEO), Thanos Baskous (VP Engineering), Geng Sng (CTO). ([source](https://www.cogent.com/company/about), read 10 Nov 2026) | Vendor's claim: Tagline and category: Rival describes itself as an agent harness for cybersecurity. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Research blog launched Feb 2025 describing early experiments building AI systems for cybersecurity. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
None found on 10 Nov 2026: Pricing (rival.security/pricing returns 404; book-a-demo form only). ([source](https://rival.security/book-a-demo-form?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
None found on 10 Nov 2026: Funding, investors, founders, headcount, HQ or founding year on home, blog, careers, book-a-demo pages. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
Alphabetical by name. Each line is one fact with its label, source and read date.
## Profiles
- [Cogent Security profile](/platforms/cogent/): agentic vulnerability management
- [Rival Security profile](/platforms/rival/): agentic security platform
## Related pages
- [24 pairs, side by side](/compare/)
- [Cogent Security vs Zafran: the sourced facts side by side](/compare/cogent-vs-zafran/)
- [Backline Security vs Rival Security: the sourced facts side by side](/compare/backline-vs-rival/)
- [Dux Security vs Rival Security: the sourced facts side by side](/compare/dux-vs-rival/)
## Sources
- Cogent Security: www.cogent.com/platform/assess: https://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: https://www.cogent.com/blog/cogent-expands-its-ai-cyber-defense-factory-with-specular-acquisition (read 10 Nov 2026)
- Cogent Security: www.cogent.com/ai/cogent-ai-engine: https://www.cogent.com/ai/cogent-ai-engine (read 10 Nov 2026)
- Cogent Security: www.cogent.com/platform/cyber-defense-factory: https://www.cogent.com/platform/cyber-defense-factory (read 10 Nov 2026)
- Cogent Security: www.cogent.com/: https://www.cogent.com/ (read 10 Nov 2026)
- siliconangle.com: /2026/11/03/exclusive-cogent-securitys-vr-1-1-model-outscores-claude-c: https://siliconangle.com/2026/11/03/exclusive-cogent-securitys-vr-1-1-model-outscores-claude-code-and-codex-on-vulnerability-repair/ (read 10 Nov 2026)
- Cogent Security: www.cogent.com/ai/autonomy-levels: https://www.cogent.com/ai/autonomy-levels (read 10 Nov 2026)
- siliconangle.com: /2026/02/18/cogent-security-raises-42m-scale-ai-agents-enterprise-vuln: https://siliconangle.com/2026/02/18/cogent-security-raises-42m-scale-ai-agents-enterprise-vulnerability-remediation/ (read 10 Nov 2026)
- Cogent Security: www.cogent.com/platform/discover: https://www.cogent.com/platform/discover (read 10 Nov 2026)
- Cogent Security: www.cogent.com/customers/csc-generation: https://www.cogent.com/customers/csc-generation (read 10 Nov 2026)
- Cogent Security: www.cogent.com/platform/integrations: https://www.cogent.com/platform/integrations (read 10 Nov 2026)
- Rival Security: rival.security/: https://rival.security/ (read 10 Nov 2026)
- Rival Security: rival.security/use-cases: https://rival.security/use-cases (read 10 Nov 2026)
- Rival Security: rival.security/blog/php2shell-black-october-2026: https://rival.security/blog/php2shell-black-october-2026 (read 10 Nov 2026)
- Rival Security: docs.rival.security: https://docs.rival.security (read 10 Nov 2026)
- Rival Security: rival.security/blog/sastbench-measuring-ai-security-automation: https://rival.security/blog/sastbench-measuring-ai-security-automation (read 10 Nov 2026)
- Rival Security: rival.security/blog: https://rival.security/blog (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/compare/cogent-vs-rival/
---
# Cogent Security vs Zafran: the sourced facts side by side
Side by side, read 10 Nov 2026
**The short answer.** Cogent Security and Zafran are set side by side on the same rows. Cogent Security has 40 fact lines (10 third-party) and Zafran has 38 (0 third-party). Fixes: Cogent Security, patches through patch tools; Zafran, mitigations. None found: Cogent Security on agents; Zafran on agents. The rows below set the sourced facts side by side; the page names no pick.
## The same rows for both
| Row | Cogent Security | Zafran |
| --- | --- | --- |
| What it is | Agentic vulnerability management and remediation (AI agents across the full vulnerability lifecycle) | Exposure management platform with mitigation via existing controls (agentic features) |
| What it 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). | 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. |
| Where it is 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. | 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. |
| Proves exploitability in your environment | Vendor's claim: Cogent says it prioritizes by real exploitability and business impact, not only CVSS. ([source](https://www.cogent.com/platform/assess), read 10 Nov 2026)
Vendor's claim: On PHP2Shell, Cogent says it narrowed 2,266 affected assets (Fortune 500 average) to 16 using runtime exposure, internet reachability and business criticality. ([source](https://www.cogent.com/blog/cogent-expands-its-ai-cyber-defense-factory-with-specular-acquisition), read 10 Nov 2026)
Vendor's claim: A knowledge graph links assets to owners, business functions, network exposure and compensating controls. ([source](https://www.cogent.com/ai/cogent-ai-engine), read 10 Nov 2026)
Vendor's claim: Every output shows its chain of logic: data sources, agents involved and why that path was chosen. ([source](https://www.cogent.com/ai/cogent-ai-engine), read 10 Nov 2026)
1 more on the [profile](/platforms/cogent/) | Vendor's claim: Exposure Graph links each finding to asset, network path, runtime status and threat activity, then reads live control configuration to see what already protects the asset. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Prioritization weighs runtime, reachability, active exploitation, controls and business criticality. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Control assessment reads firewall, WAF, cloud security group and EDR configurations to show which vulnerabilities are already blocked. ([source](https://www.zafran.io/solutions/use-cases/mitigate-risk), read 10 Nov 2026)
Vendor's claim: Customer evidence: Sallie Mae says Zafran checks control configuration per device and adjusts risk accordingly. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
1 more on the [profile](/platforms/zafran/) |
| Ships the fix | Third-party source: Its VR-1.1 model writes fixes for newly disclosed vulnerabilities; each patch goes to a separate review that tries to bypass it. ([source](https://siliconangle.com/2026/11/03/exclusive-cogent-securitys-vr-1-1-model-outscores-claude-code-and-codex-on-vulnerability-repair/), read 10 Nov 2026)
Third-party source: VR-1.1 also writes regression tests intended to fail if a later change reopens the flaw. ([source](https://siliconangle.com/2026/11/03/exclusive-cogent-securitys-vr-1-1-model-outscores-claude-code-and-codex-on-vulnerability-repair/), read 10 Nov 2026)
Vendor's claim: Cogent finds the fix, assesses impact and executes through existing tools, from assisted to fully autonomous. ([source](https://www.cogent.com/), read 10 Nov 2026)
Vendor's claim: High-impact changes require human approval and an audit trail. ([source](https://www.cogent.com/ai/autonomy-levels), read 10 Nov 2026)
1 more on the [profile](/platforms/cogent/) | Vendor's claim: Mitigation first: uses existing firewall, WAF and EDR to reduce risk before a patch exists. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Attack Chains offers a compensating control (such as a WAF rule) applied in a few clicks at the choke point. ([source](https://www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration-with-google-threat-intelligence), read 10 Nov 2026)
Vendor's claim: Workflow example: one flow opens a ServiceNow ticket, pushes a WAF rule and tracks the SLA. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Patch/upgrade remediation is delivered as a Work Item routed to the owner in the ticketing tool, not as a pull request. ([source](https://www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration-with-google-threat-intelligence), read 10 Nov 2026)
2 more on the [profile](/platforms/zafran/) |
| Finds the owner | Third-party source: Per SiliconANGLE, agents determine asset ownership and map vulnerabilities to affected services. ([source](https://siliconangle.com/2026/02/18/cogent-security-raises-42m-scale-ai-agents-enterprise-vulnerability-remediation/), read 10 Nov 2026)
Third-party source: Per SiliconANGLE, agents track remediation status and verify completion after patches or config changes. ([source](https://siliconangle.com/2026/02/18/cogent-security-raises-42m-scale-ai-agents-enterprise-vulnerability-remediation/), read 10 Nov 2026)
Vendor's claim: The Discover page demo shows agents resolving an asset owner from ServiceNow CMDB and checking Jira ticket history. ([source](https://www.cogent.com/platform/discover), read 10 Nov 2026)
Vendor's claim: The CSC Generation case study says the team previously mapped owners, routed tickets and tracked SLAs manually. ([source](https://www.cogent.com/customers/csc-generation), read 10 Nov 2026) | Vendor's claim: Collapses overlapping findings into one fix and routes it to the right team and owner. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Auto-assigns fixes to the owner in Jira, Slack and ServiceNow. ([source](https://www.zafran.io/platform), read 10 Nov 2026)
Vendor's claim: Example: 700 findings collapse into one OpenSSL upgrade ticket routed to the Platform team. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Progress tracking with shared visibility across Security and IT. ([source](https://www.zafran.io/platform), read 10 Nov 2026) |
| Speed on a new disclosure | Vendor's claim: Cogent says it identifies vulnerable software within minutes of disclosure. ([source](https://www.cogent.com/platform/discover), read 10 Nov 2026)
Vendor's claim: Homepage claim: identify vulnerable software within minutes of a new disclosure, before scanners can. ([source](https://www.cogent.com/), read 10 Nov 2026)
Vendor's claim: Cogent's Nov 10 post cites its PHP2Shell analysis, listed on the homepage as dated Oct 21, 2026, the same day as the disclosure. ([source](https://www.cogent.com/blog/cogent-expands-its-ai-cyber-defense-factory-with-specular-acquisition), read 10 Nov 2026) | Vendor's claim: Zero Day Agent scenario: matches a pre-announced OpenSSL flaw to live software inventory in 88 seconds before any CVE is published (illustrative scenario on the home page). ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Proactive Exposure Hunting for new CVEs and zero-days, including which affected assets are internet-exposed. ([source](https://www.zafran.io/platform), read 10 Nov 2026)
Vendor's claim: Customer quote: assess exposure before CVEs are defined. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
Vendor's claim: Customer-reported time to answer "are we exposed?" is minutes. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
1 more on the [profile](/platforms/zafran/) |
| Agents you can shape | Third-party source: Cogent's VR-1 and VR-1.1 are vendor-built reasoning models for vulnerability repair. ([source](https://siliconangle.com/2026/11/03/exclusive-cogent-securitys-vr-1-1-model-outscores-claude-code-and-codex-on-vulnerability-repair/), read 10 Nov 2026)
Vendor's claim: Ready-made specialized agents handle normalization, enrichment, risk assessment and remediation planning. ([source](https://www.cogent.com/ai/cogent-ai-engine), read 10 Nov 2026)
Vendor's claim: Agents check customer-defined guardrails before every action. ([source](https://www.cogent.com/ai/cogent-ai-engine), read 10 Nov 2026)
Vendor's claim: Autonomy is staged: start with recommendations and review, then expand. ([source](https://www.cogent.com/ai/autonomy-levels), read 10 Nov 2026)
1 more on the [profile](/platforms/cogent/) | Vendor's claim: Ready-made Zero Day Agent and Zafran AI assistant; AI can build dashboards from prompts. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Customer-built agents: user prompts create a scheduled report agent that emails a daily report. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Zafran AI answers plain-language questions grounded in correlated asset and findings data (Sallie Mae case study). ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
Vendor's claim: Gartner definition of autonomous exposure remediation, which Zafran cites as a category it was named a Sample Vendor for. ([source](https://www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-reports-for-unified-exposure-management-platforms-and-autonomous-exposure-remediation-categories), read 10 Nov 2026)
1 more on the [profile](/platforms/zafran/) |
| Works on the stack you have | Vendor's claim: Scanner integrations include Qualys, Rapid7 and Tenable. ([source](https://www.cogent.com/platform/integrations), read 10 Nov 2026)
Vendor's claim: Cloud security ingestion: AWS, Lacework, Orca, Upwind, Wiz. ([source](https://www.cogent.com/platform/integrations), read 10 Nov 2026)
Vendor's claim: Ticketing integrations: Jira and ServiceNow ITSM (push and track tickets). ([source](https://www.cogent.com/platform/integrations), read 10 Nov 2026)
Vendor's claim: Endpoint integrations: CrowdStrike, Microsoft Defender for Endpoint, SentinelOne. ([source](https://www.cogent.com/platform/integrations), read 10 Nov 2026)
2 more on the [profile](/platforms/cogent/) | Vendor's claim: Named sources on the home page: Zafran Discover, Tenable, Rapid7, Wiz, AWS, Snyk and 100+ more integrations. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Platform page: cloud and AppSec from Wiz, Palo Alto Networks, Upwind, AWS, Snyk; on-prem from Tenable, Qualys, Rapid7. ([source](https://www.zafran.io/platform), read 10 Nov 2026)
Vendor's claim: Controls read: CrowdStrike Falcon, Akamai WAF, Palo Alto NGFW (example policies). ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Ticketing and chat: Jira, Slack, ServiceNow (see owner facts); no new agents to deploy for ingestion. ([source](https://www.zafran.io/), read 10 Nov 2026) |
| Proof | Third-party source: VR-1.1 passed 57.9% of 190 LiveCVEBench tasks; Claude Code and Codex scored 45.3% (vendor-run test, reported by SiliconANGLE). ([source](https://siliconangle.com/2026/11/03/exclusive-cogent-securitys-vr-1-1-model-outscores-claude-code-and-codex-on-vulnerability-repair/), read 10 Nov 2026)
Third-party source: Method notes: outbound network blocked during repairs and grading tests hidden; inference budgets differed across systems. ([source](https://siliconangle.com/2026/11/03/exclusive-cogent-securitys-vr-1-1-model-outscores-claude-code-and-codex-on-vulnerability-repair/), read 10 Nov 2026)
Third-party source: SiliconANGLE names Upwind, Alteryx and CSC Generation as customers and says Cogent works with dozens of Fortune 1000 companies. ([source](https://siliconangle.com/2026/02/18/cogent-security-raises-42m-scale-ai-agents-enterprise-vulnerability-remediation/), read 10 Nov 2026)
Vendor's claim: CSC Generation case study: 3 hours to full assessment, 100% of vulnerabilities managed autonomously (vendor-published). ([source](https://www.cogent.com/customers/csc-generation), read 10 Nov 2026)
2 more on the [profile](/platforms/cogent/) | Vendor's claim: Sallie Mae case study: 96% reduction in CVSS Criticals and 23K vulnerabilities identified for mitigation with existing controls. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
Vendor's claim: Named CISO testimonial (Kraft Heinz). ([source](https://www.zafran.io/platform), read 10 Nov 2026)
Vendor's claim: Analyst recognition: KuppingerCole 2026 Leadership Compass banner on the home page. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Gartner Emerging Tech report mentions (Sept 11, 2026 and Apr 3, 2026), as reported by Zafran. ([source](https://www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-reports-for-unified-exposure-management-platforms-and-autonomous-exposure-remediation-categories), read 10 Nov 2026) |
| Profile facts | Third-party source: Series A of $42M led by Bain Capital with Greylock Partners and Definition Capital, announced Feb 18, 2026. ([source](https://siliconangle.com/2026/02/18/cogent-security-raises-42m-scale-ai-agents-enterprise-vulnerability-remediation/), read 10 Nov 2026)
Third-party source: Founded in 2025, formally launched July 2025; works with dozens of Fortune 1000 companies (per SiliconANGLE). ([source](https://siliconangle.com/2026/02/18/cogent-security-raises-42m-scale-ai-agents-enterprise-vulnerability-remediation/), read 10 Nov 2026)
Vendor's claim: Acquired Specular (Google-backed AI security platform) on 10 Nov 2026. ([source](https://www.cogent.com/blog/cogent-expands-its-ai-cyber-defense-factory-with-specular-acquisition), read 10 Nov 2026)
Vendor's claim: Co-founders: Vineet Edupuganti (CEO), Thanos Baskous (VP Engineering), Geng Sng (CTO). ([source](https://www.cogent.com/company/about), read 10 Nov 2026) | Vendor's claim: Founders: Sanaz Yashar (CEO) and Ben Seri (CTO). ([source](https://www.zafran.io/about), read 10 Nov 2026)
Vendor's claim: Investors named: Menlo Ventures, Sequoia Capital, Cyberstarts, plus strategic investment from Amex Ventures (Feb 24, 2026). ([source](https://www.zafran.io/resources/zafran-announces-strategic-investment-from-amex-ventures), read 10 Nov 2026)
Vendor's claim: Strategic investment from Cisco Investments announced Jul 22, 2026 (headline on news index). ([source](https://www.zafran.io/news), read 10 Nov 2026)
None found on 10 Nov 2026: Round amounts, founding year, headquarters, headcount, customer count and pricing on the pages read ([source](https://www.zafran.io/platform), read 10 Nov 2026) |
Alphabetical by name. Each line is one fact with its label, source and read date.
## Profiles
- [Cogent Security profile](/platforms/cogent/): agentic vulnerability management
- [Zafran profile](/platforms/zafran/): exposure management platform with
## Related pages
- [24 pairs, side by side](/compare/)
- [Dux Security vs Rival Security: the sourced facts side by side](/compare/dux-vs-rival/)
- [Cogent Security vs Rival Security: the sourced facts side by side](/compare/cogent-vs-rival/)
- [Maze vs Rival Security: the sourced facts side by side](/compare/maze-vs-rival/)
## Sources
- Cogent Security: www.cogent.com/platform/assess: https://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: https://www.cogent.com/blog/cogent-expands-its-ai-cyber-defense-factory-with-specular-acquisition (read 10 Nov 2026)
- Cogent Security: www.cogent.com/ai/cogent-ai-engine: https://www.cogent.com/ai/cogent-ai-engine (read 10 Nov 2026)
- Cogent Security: www.cogent.com/platform/cyber-defense-factory: https://www.cogent.com/platform/cyber-defense-factory (read 10 Nov 2026)
- Cogent Security: www.cogent.com/: https://www.cogent.com/ (read 10 Nov 2026)
- siliconangle.com: /2026/11/03/exclusive-cogent-securitys-vr-1-1-model-outscores-claude-c: https://siliconangle.com/2026/11/03/exclusive-cogent-securitys-vr-1-1-model-outscores-claude-code-and-codex-on-vulnerability-repair/ (read 10 Nov 2026)
- Cogent Security: www.cogent.com/ai/autonomy-levels: https://www.cogent.com/ai/autonomy-levels (read 10 Nov 2026)
- siliconangle.com: /2026/02/18/cogent-security-raises-42m-scale-ai-agents-enterprise-vuln: https://siliconangle.com/2026/02/18/cogent-security-raises-42m-scale-ai-agents-enterprise-vulnerability-remediation/ (read 10 Nov 2026)
- Cogent Security: www.cogent.com/platform/discover: https://www.cogent.com/platform/discover (read 10 Nov 2026)
- Cogent Security: www.cogent.com/customers/csc-generation: https://www.cogent.com/customers/csc-generation (read 10 Nov 2026)
- Cogent Security: www.cogent.com/platform/integrations: https://www.cogent.com/platform/integrations (read 10 Nov 2026)
- Zafran: www.zafran.io/: https://www.zafran.io/ (read 10 Nov 2026)
- Zafran: www.zafran.io/solutions/use-cases/mitigate-risk: https://www.zafran.io/solutions/use-cases/mitigate-risk (read 10 Nov 2026)
- Zafran: www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-: https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes (read 10 Nov 2026)
- Zafran: www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration: https://www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration-with-google-threat-intelligence (read 10 Nov 2026)
- Zafran: www.zafran.io/platform: https://www.zafran.io/platform (read 10 Nov 2026)
- Zafran: www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-re: https://www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-reports-for-unified-exposure-management-platforms-and-autonomous-exposure-remediation-categories (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/compare/cogent-vs-zafran/
---
# Dux Security vs Rival Security: the sourced facts side by side
Side by side, read 10 Nov 2026
**The short answer.** Dux Security and Rival Security. Dux Security has 28 fact lines (0 third-party) and Rival Security has 40 (0 third-party). Fixes: Dux Security, mitigations and patches through patch tools; Rival Security, pull requests and mitigations. None found: Dux Security on exploitability; Rival Security on proof. The rows below set the sourced facts side by side; the page names no pick.
## The same rows for both
| Row | Dux Security | Rival Security |
| --- | --- | --- |
| What it is | Agentic exposure management (exploitability analysis, mitigation, remediation acceleration) | Agentic security platform / agent harness for vulnerability management, code and cloud security |
| What it 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. | 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. |
| Where it is 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. | 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. |
| Proves exploitability in your environment | Vendor's claim: Dux maps how vulnerabilities, assets and controls connect to judge exploitability. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Stated aim: separate reachable from truly exploitable risk. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Home page lead: AI agents for instant exploitability analysis. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Exploitability stage answers where the customer is already protected. ([source](https://dux.io/), read 10 Nov 2026)
1 more on the [profile](/platforms/dux/) | Vendor's claim: Home page lists a Triage Exploitability agent that determines what is actually exploitable in the customer environment. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page says Rival reads every scanner finding against the real environment and keeps only those that can cause harm; it cites a 94.6% reduction in findings. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page reports 98% of findings proven unexploitable, 87% faster remediation and 1.5 hours to first value (no method given on the page). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: In its PHP2Shell write-up, Rival says agents ordered services to fix by reachability, internet-exposed unauthenticated workloads first. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Ships the fix | Vendor's claim: Dux favors lightweight mitigations such as a missing control or config change instead of a patch. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Mitigations are ones the customer deploys on its own. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Remediation stage speeds up the fix process by tagging assets and tying data sources together. ([source](https://dux.io/), read 10 Nov 2026)
None found on 10 Nov 2026: Generated pull requests, tested code fixes or approval-gated automated changes. ([source](https://dux.io/), read 10 Nov 2026) | Vendor's claim: Home page lists an Autonomous Remediation agent that generates and ships tested fixes. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page describes the remediation flow as plan, test, and open a pull request for human review. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival lists a WAF mitigation agent that checks whether a WAF blocks exploitation and adjusts it. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival describes an alternative-remediation agent for legacy apps that plans a fix without upgrading libraries. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
2 more on the [profile](/platforms/rival/) |
| Finds the owner | Vendor's claim: Remediation stage poses the question of who should remediate. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Auto-tagging of every asset is the ownership mechanism described. ([source](https://dux.io/), read 10 Nov 2026)
None found on 10 Nov 2026: Ticket routing, follow-up or escalation features. ([source](https://dux.io/), read 10 Nov 2026) | Vendor's claim: Home page lists an Ownership Resolution agent that maps each finding to the team that can fix it. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page says the owner-finding agent weighs root cause, team structure and past history (memories). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: PHP2Shell write-up says agents can message the relevant employees, and the harness lists human follow-ups. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
| Speed on a new disclosure | Vendor's claim: Positioning is speed against attackers. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Home page frames time-to-exploit collapsing from weeks to minutes. ([source](https://dux.io/), read 10 Nov 2026)
None found on 10 Nov 2026: Zero-day response feature, time-to-answer number or published response write-up. ([source](https://dux.io/), read 10 Nov 2026) | Vendor's claim: Home page lists a 0-day Fast Response agent covering triage through remediation. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page describes 0-day rapid response as finding exposure across code, images and cloud and prioritizing what to do first (page also claims a drop from days to minutes). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Published response write-up: for PHP2Shell, agents were triaging customer environments hours before scanners could detect the CVEs. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: The same write-up reports scanning more than 80,000 repositories within hours. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Agents you can shape | Vendor's claim: Dux uses AI agents across analysis, mitigation and remediation acceleration. ([source](https://dux.io/), read 10 Nov 2026)
None found on 10 Nov 2026: Named ready-made agents, customer-built agents, or controls and guardrails. ([source](https://dux.io/), read 10 Nov 2026) | Vendor's claim: Rival offers ready-made agents that can be customized and extended. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival engineers build custom agents for the customer environment at no additional cost (Partner tier). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Customers can build their own agents on the harness. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page says 64+ more agents are available beyond the five featured. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
2 more on the [profile](/platforms/rival/) |
| Works on the stack you have | Vendor's claim: Mitigation stage works from the customer's existing stack. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Dux reviews the whole security posture to find mitigations. ([source](https://dux.io/), read 10 Nov 2026)
None found on 10 Nov 2026: Named scanner, cloud, code host or ticketing integrations. ([source](https://dux.io/), read 10 Nov 2026) | Vendor's claim: Home page names cloud, code host and infrastructure integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page names scanner, control and task integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases table shows findings sourced from Wiz, Qualys, GitHub, a pentest, and Rival's own SCA and Code scanners. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Agents combine connected services with a Rival Security Knowledge Graph. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
| Proof | Vendor's claim: Quote from Mille Gandelsman (CPO at Opti, ex-VP at Tenable) on the home page. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Quote from Andrew Wilder (CSO at Vetcor, ex-Nestle) on the home page. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Quote from Rinki Sethi (CSO at Upwind, ex-BILL). ([source](https://dux.io/), read 10 Nov 2026)
None found on 10 Nov 2026: Named customers, case studies, published results or research publications (quotes above are from named security executives, not stated customers). ([source](https://dux.io/), read 10 Nov 2026) | Vendor's claim: Use-cases page claims 13M+ agent runs. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival published SASTBench, a benchmark for SAST triage using real CVEs as true positives and filtered SAST findings as noise. ([source](https://rival.security/blog/sastbench-measuring-ai-security-automation?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Research blog post claims Rival workflows outperform current frontier models on the Spider 2.0 benchmark. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Published incident write-up (PHP2Shell, Nov 2, 2026) with unnamed customer results. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Profile facts | Vendor's claim: Product category on page title and heading: Agentic Exposure Management. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Company legal name in footer: Dux, Inc. ([source](https://dux.io/), read 10 Nov 2026)
Vendor's claim: Company description: built by security veterans. ([source](https://dux.io/), read 10 Nov 2026)
None found on 10 Nov 2026: Pricing, funding, investors (a Backed by section shows logos only, no text), founders, HQ, headcount, careers (dux.io/about and /careers return 404). ([source](https://dux.io/), read 10 Nov 2026) | Vendor's claim: Tagline and category: Rival describes itself as an agent harness for cybersecurity. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Research blog launched Feb 2025 describing early experiments building AI systems for cybersecurity. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
None found on 10 Nov 2026: Pricing (rival.security/pricing returns 404; book-a-demo form only). ([source](https://rival.security/book-a-demo-form?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
None found on 10 Nov 2026: Funding, investors, founders, headcount, HQ or founding year on home, blog, careers, book-a-demo pages. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
Alphabetical by name. Each line is one fact with its label, source and read date.
## Profiles
- [Dux Security profile](/platforms/dux/): agentic exposure management
- [Rival Security profile](/platforms/rival/): agentic security platform
## Related pages
- [24 pairs, side by side](/compare/)
- [Maze vs Rival Security: the sourced facts side by side](/compare/maze-vs-rival/)
- [Cogent Security vs Zafran: the sourced facts side by side](/compare/cogent-vs-zafran/)
- [Maze vs Zafran: the sourced facts side by side](/compare/maze-vs-zafran/)
## Sources
- Dux Security: dux.io/: https://dux.io/ (read 10 Nov 2026)
- Rival Security: rival.security/: https://rival.security/ (read 10 Nov 2026)
- Rival Security: rival.security/use-cases: https://rival.security/use-cases (read 10 Nov 2026)
- Rival Security: rival.security/blog/php2shell-black-october-2026: https://rival.security/blog/php2shell-black-october-2026 (read 10 Nov 2026)
- Rival Security: docs.rival.security: https://docs.rival.security (read 10 Nov 2026)
- Rival Security: rival.security/blog/sastbench-measuring-ai-security-automation: https://rival.security/blog/sastbench-measuring-ai-security-automation (read 10 Nov 2026)
- Rival Security: rival.security/blog: https://rival.security/blog (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/compare/dux-vs-rival/
---
# Maze vs Rival Security: the sourced facts side by side
Side by side, read 10 Nov 2026
**The short answer.** Maze and Rival Security are set side by side on the same rows. Fact lines: Maze 37, Rival Security 40. Third-party: 0 and 0. Fixes: Maze, patches through patch tools; Rival Security, pull requests. Maze has a none-found line on owner; Rival Security on proof. The rows below set the sourced facts side by side; the page names no pick.
## The same rows for both
| Row | Maze | Rival Security |
| --- | --- | --- |
| What it is | Agentic vulnerability investigation and remediation (code and cloud) | Agentic security platform / agent harness for vulnerability management, code and cloud security |
| What it 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. | 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. |
| Where it is 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. | 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. |
| Proves exploitability in your environment | Vendor's claim: Maze defines exploitable relative to the customer's own configuration, controls and context, not CVSS or exploit-in-the-wild status. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
Vendor's claim: Every recommendation is said to carry the evidence and reasoning behind it. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
Vendor's claim: Maze says 90% of vulnerabilities it analyzes are not exploitable when investigated. ([source](https://mazehq.com/), read 10 Nov 2026)
Vendor's claim: Runtime context is gathered without installing sensors. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
2 more on the [profile](/platforms/maze/) | Vendor's claim: Home page lists a Triage Exploitability agent that determines what is actually exploitable in the customer environment. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page says Rival reads every scanner finding against the real environment and keeps only those that can cause harm; it cites a 94.6% reduction in findings. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page reports 98% of findings proven unexploitable, 87% faster remediation and 1.5 hours to first value (no method given on the page). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: In its PHP2Shell write-up, Rival says agents ordered services to fix by reachability, internet-exposed unauthenticated workloads first. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Ships the fix | Vendor's claim: Agents verify that a fix resolves the vulnerability without introducing new ones. ([source](https://mazehq.com/solutions/remediation), read 10 Nov 2026)
Vendor's claim: Maze generates and validates fixes but the customer's team controls what gets merged. ([source](https://mazehq.com/solutions/remediation), read 10 Nov 2026)
Vendor's claim: Where patching is not possible, Maze suggests mitigations that break the exploitability chain. ([source](https://mazehq.com/solutions/remediation), read 10 Nov 2026)
Vendor's claim: Agents bundle proven-exploitable CVEs into single fixes, so one ticket can close 30 or more. ([source](https://mazehq.com/solutions/remediation), read 10 Nov 2026)
1 more on the [profile](/platforms/maze/) | Vendor's claim: Home page lists an Autonomous Remediation agent that generates and ships tested fixes. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page describes the remediation flow as plan, test, and open a pull request for human review. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival lists a WAF mitigation agent that checks whether a WAF blocks exploitation and adjusts it. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival describes an alternative-remediation agent for legacy apps that plans a fix without upgrading libraries. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
2 more on the [profile](/platforms/rival/) |
| Finds the owner | Vendor's claim: Agents infer the owner from commit history and code, then route the fix to the developer or coding agent. ([source](https://mazehq.com/solutions/remediation), read 10 Nov 2026)
Vendor's claim: Fixes are delivered into ticketing platforms or coding agents (Slack or Teams optional). ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
None found on 10 Nov 2026: Follow-up after routing (reminders, SLA tracking, escalation): none found on 2026-11-10: owner follow-up or SLA tracking on remediation, platform/cloud and platform/code pages ([source](https://mazehq.com/solutions/remediation), read 10 Nov 2026) | Vendor's claim: Home page lists an Ownership Resolution agent that maps each finding to the team that can fix it. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page says the owner-finding agent weighs root cause, team structure and past history (memories). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: PHP2Shell write-up says agents can message the relevant employees, and the harness lists human follow-ups. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
| Speed on a new disclosure | Vendor's claim: Maze says agents sweep every instance for a new zero-day in hours, before scanners have a signature. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
Vendor's claim: Maze claims agents recognize zero-day vulnerabilities and triage them before scanners see them. ([source](https://mazehq.com/), read 10 Nov 2026)
Vendor's claim: Maze published a response write-up on PHP2Shell dated Oct 22, 2026, one day after the Oct 21 patch release. ([source](https://mazehq.com/blog/php2shell), read 10 Nov 2026) | Vendor's claim: Home page lists a 0-day Fast Response agent covering triage through remediation. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page describes 0-day rapid response as finding exposure across code, images and cloud and prioritizing what to do first (page also claims a drop from days to minutes). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Published response write-up: for PHP2Shell, agents were triaging customer environments hours before scanners could detect the CVEs. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: The same write-up reports scanning more than 80,000 repositories within hours. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Agents you can shape | Vendor's claim: Maze Cloud and Maze Code are agent-driven products; AI-SCA and AI-SAST are named agent modules. ([source](https://mazehq.com/), read 10 Nov 2026)
Vendor's claim: Vendor-built agents run on custom infrastructure, trained on domain tasks and checked by multiple validation layers. ([source](https://mazehq.com/platform), read 10 Nov 2026)
Vendor's claim: Maze integrates with coding agents such as Claude and Cursor. ([source](https://mazehq.com/platform), read 10 Nov 2026)
Vendor's claim: Data control: Maze does not train or fine-tune the underlying models on customer code or findings; single-tenant hosting is offered. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
1 more on the [profile](/platforms/maze/) | Vendor's claim: Rival offers ready-made agents that can be customized and extended. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival engineers build custom agents for the customer environment at no additional cost (Partner tier). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Customers can build their own agents on the harness. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page says 64+ more agents are available beyond the five featured. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
2 more on the [profile](/platforms/rival/) |
| Works on the stack you have | Vendor's claim: Maze needs a read-only cloud role and an API connection to vulnerability scanners. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
Vendor's claim: It pulls and deduplicates findings from existing scanners. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
Vendor's claim: The Cohere Health story lists AWS and containers as the environment. ([source](https://mazehq.com/customer-story/how-cohere-health-cleared-92-of-its-critical-and-high-findings), read 10 Nov 2026)
None found on 10 Nov 2026: Specific scanner, code host and ticketing product names: none found on 2026-11-10: a named integration list on mazehq.com (the FAQ says only that it connects to the scanners customers already have) ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026) | Vendor's claim: Home page names cloud, code host and infrastructure integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page names scanner, control and task integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases table shows findings sourced from Wiz, Qualys, GitHub, a pentest, and Rival's own SCA and Code scanners. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Agents combine connected services with a Rival Security Knowledge Graph. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
| Proof | Vendor's claim: Cohere Health story: 92% of critical and high findings not exploitable, downgraded or remediated. ([source](https://mazehq.com/customer-story/how-cohere-health-cleared-92-of-its-critical-and-high-findings), read 10 Nov 2026)
Vendor's claim: Same story: 87% of critical and high findings were not exploitable or safe to deprioritize. ([source](https://mazehq.com/customer-story/how-cohere-health-cleared-92-of-its-critical-and-high-findings), read 10 Nov 2026)
Vendor's claim: Named customer quotes: Alloy, Cohere Health, Forge, PartsSource. ([source](https://mazehq.com/), read 10 Nov 2026)
Vendor's claim: Maze claims deployment by multiple Fortune 100 organizations. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
1 more on the [profile](/platforms/maze/) | Vendor's claim: Use-cases page claims 13M+ agent runs. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival published SASTBench, a benchmark for SAST triage using real CVEs as true positives and filtered SAST findings as noise. ([source](https://rival.security/blog/sastbench-measuring-ai-security-automation?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Research blog post claims Rival workflows outperform current frontier models on the Spider 2.0 benchmark. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Published incident write-up (PHP2Shell, Nov 2, 2026) with unnamed customer results. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Profile facts | Vendor's claim: Maze was started in 2024. ([source](https://mazehq.com/our-story), read 10 Nov 2026)
Vendor's claim: Pricing is based on the size of the customer's cloud infrastructure; no public price list. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
Vendor's claim: Certifications: ISO 27001 and SOC 2 Type II. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
Vendor's claim: Hosted in AWS with multi-tenant or single-tenant options. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026) | Vendor's claim: Tagline and category: Rival describes itself as an agent harness for cybersecurity. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Research blog launched Feb 2025 describing early experiments building AI systems for cybersecurity. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
None found on 10 Nov 2026: Pricing (rival.security/pricing returns 404; book-a-demo form only). ([source](https://rival.security/book-a-demo-form?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
None found on 10 Nov 2026: Funding, investors, founders, headcount, HQ or founding year on home, blog, careers, book-a-demo pages. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
Alphabetical by name. Each line is one fact with its label, source and read date.
## Profiles
- [Maze profile](/platforms/maze/): agentic vulnerability
- [Rival Security profile](/platforms/rival/): agentic security platform
## Related pages
- [24 pairs, side by side](/compare/)
- [Maze vs Zafran: the sourced facts side by side](/compare/maze-vs-zafran/)
- [Dux Security vs Rival Security: the sourced facts side by side](/compare/dux-vs-rival/)
- [Onit Security vs Rival Security: the sourced facts side by side](/compare/onit-vs-rival/)
## Sources
- Maze: mazehq.com/platform/cloud: https://mazehq.com/platform/cloud (read 10 Nov 2026)
- Maze: mazehq.com/: https://mazehq.com/ (read 10 Nov 2026)
- Maze: mazehq.com/platform/code: https://mazehq.com/platform/code (read 10 Nov 2026)
- Maze: mazehq.com/customer-story/how-cohere-health-cleared-92-of-its-critical-and-high-: https://mazehq.com/customer-story/how-cohere-health-cleared-92-of-its-critical-and-high-findings (read 10 Nov 2026)
- Maze: mazehq.com/solutions/remediation: https://mazehq.com/solutions/remediation (read 10 Nov 2026)
- Maze: mazehq.com/blog/php2shell: https://mazehq.com/blog/php2shell (read 10 Nov 2026)
- Maze: mazehq.com/platform: https://mazehq.com/platform (read 10 Nov 2026)
- Rival Security: rival.security/: https://rival.security/ (read 10 Nov 2026)
- Rival Security: rival.security/use-cases: https://rival.security/use-cases (read 10 Nov 2026)
- Rival Security: rival.security/blog/php2shell-black-october-2026: https://rival.security/blog/php2shell-black-october-2026 (read 10 Nov 2026)
- Rival Security: docs.rival.security: https://docs.rival.security (read 10 Nov 2026)
- Rival Security: rival.security/blog/sastbench-measuring-ai-security-automation: https://rival.security/blog/sastbench-measuring-ai-security-automation (read 10 Nov 2026)
- Rival Security: rival.security/blog: https://rival.security/blog (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/compare/maze-vs-rival/
---
# Maze vs Zafran: the sourced facts side by side
Side by side, read 10 Nov 2026
**The short answer.** Maze and Zafran are set side by side on the same rows. Fact lines: Maze 37, Zafran 38. Third-party: 0 and 0. Fixes: Maze, patches through patch tools and tickets; Zafran, mitigations and patches through patch tools. None found: Maze on owner; Zafran on agents. The rows below set the sourced facts side by side; the page names no pick.
## The same rows for both
| Row | Maze | Zafran |
| --- | --- | --- |
| What it is | Agentic vulnerability investigation and remediation (code and cloud) | Exposure management platform with mitigation via existing controls (agentic features) |
| What it 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. | 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. |
| Where it is 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. | 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. |
| Proves exploitability in your environment | Vendor's claim: Maze defines exploitable relative to the customer's own configuration, controls and context, not CVSS or exploit-in-the-wild status. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
Vendor's claim: Every recommendation is said to carry the evidence and reasoning behind it. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
Vendor's claim: Maze says 90% of vulnerabilities it analyzes are not exploitable when investigated. ([source](https://mazehq.com/), read 10 Nov 2026)
Vendor's claim: Runtime context is gathered without installing sensors. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
2 more on the [profile](/platforms/maze/) | Vendor's claim: Exposure Graph links each finding to asset, network path, runtime status and threat activity, then reads live control configuration to see what already protects the asset. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Prioritization weighs runtime, reachability, active exploitation, controls and business criticality. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Control assessment reads firewall, WAF, cloud security group and EDR configurations to show which vulnerabilities are already blocked. ([source](https://www.zafran.io/solutions/use-cases/mitigate-risk), read 10 Nov 2026)
Vendor's claim: Customer evidence: Sallie Mae says Zafran checks control configuration per device and adjusts risk accordingly. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
1 more on the [profile](/platforms/zafran/) |
| Ships the fix | Vendor's claim: Agents verify that a fix resolves the vulnerability without introducing new ones. ([source](https://mazehq.com/solutions/remediation), read 10 Nov 2026)
Vendor's claim: Maze generates and validates fixes but the customer's team controls what gets merged. ([source](https://mazehq.com/solutions/remediation), read 10 Nov 2026)
Vendor's claim: Where patching is not possible, Maze suggests mitigations that break the exploitability chain. ([source](https://mazehq.com/solutions/remediation), read 10 Nov 2026)
Vendor's claim: Agents bundle proven-exploitable CVEs into single fixes, so one ticket can close 30 or more. ([source](https://mazehq.com/solutions/remediation), read 10 Nov 2026)
1 more on the [profile](/platforms/maze/) | Vendor's claim: Mitigation first: uses existing firewall, WAF and EDR to reduce risk before a patch exists. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Attack Chains offers a compensating control (such as a WAF rule) applied in a few clicks at the choke point. ([source](https://www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration-with-google-threat-intelligence), read 10 Nov 2026)
Vendor's claim: Workflow example: one flow opens a ServiceNow ticket, pushes a WAF rule and tracks the SLA. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Patch/upgrade remediation is delivered as a Work Item routed to the owner in the ticketing tool, not as a pull request. ([source](https://www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration-with-google-threat-intelligence), read 10 Nov 2026)
2 more on the [profile](/platforms/zafran/) |
| Finds the owner | Vendor's claim: Agents infer the owner from commit history and code, then route the fix to the developer or coding agent. ([source](https://mazehq.com/solutions/remediation), read 10 Nov 2026)
Vendor's claim: Fixes are delivered into ticketing platforms or coding agents (Slack or Teams optional). ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
None found on 10 Nov 2026: Follow-up after routing (reminders, SLA tracking, escalation): none found on 2026-11-10: owner follow-up or SLA tracking on remediation, platform/cloud and platform/code pages ([source](https://mazehq.com/solutions/remediation), read 10 Nov 2026) | Vendor's claim: Collapses overlapping findings into one fix and routes it to the right team and owner. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Auto-assigns fixes to the owner in Jira, Slack and ServiceNow. ([source](https://www.zafran.io/platform), read 10 Nov 2026)
Vendor's claim: Example: 700 findings collapse into one OpenSSL upgrade ticket routed to the Platform team. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Progress tracking with shared visibility across Security and IT. ([source](https://www.zafran.io/platform), read 10 Nov 2026) |
| Speed on a new disclosure | Vendor's claim: Maze says agents sweep every instance for a new zero-day in hours, before scanners have a signature. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
Vendor's claim: Maze claims agents recognize zero-day vulnerabilities and triage them before scanners see them. ([source](https://mazehq.com/), read 10 Nov 2026)
Vendor's claim: Maze published a response write-up on PHP2Shell dated Oct 22, 2026, one day after the Oct 21 patch release. ([source](https://mazehq.com/blog/php2shell), read 10 Nov 2026) | Vendor's claim: Zero Day Agent scenario: matches a pre-announced OpenSSL flaw to live software inventory in 88 seconds before any CVE is published (illustrative scenario on the home page). ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Proactive Exposure Hunting for new CVEs and zero-days, including which affected assets are internet-exposed. ([source](https://www.zafran.io/platform), read 10 Nov 2026)
Vendor's claim: Customer quote: assess exposure before CVEs are defined. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
Vendor's claim: Customer-reported time to answer "are we exposed?" is minutes. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
1 more on the [profile](/platforms/zafran/) |
| Agents you can shape | Vendor's claim: Maze Cloud and Maze Code are agent-driven products; AI-SCA and AI-SAST are named agent modules. ([source](https://mazehq.com/), read 10 Nov 2026)
Vendor's claim: Vendor-built agents run on custom infrastructure, trained on domain tasks and checked by multiple validation layers. ([source](https://mazehq.com/platform), read 10 Nov 2026)
Vendor's claim: Maze integrates with coding agents such as Claude and Cursor. ([source](https://mazehq.com/platform), read 10 Nov 2026)
Vendor's claim: Data control: Maze does not train or fine-tune the underlying models on customer code or findings; single-tenant hosting is offered. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
1 more on the [profile](/platforms/maze/) | Vendor's claim: Ready-made Zero Day Agent and Zafran AI assistant; AI can build dashboards from prompts. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Customer-built agents: user prompts create a scheduled report agent that emails a daily report. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Zafran AI answers plain-language questions grounded in correlated asset and findings data (Sallie Mae case study). ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
Vendor's claim: Gartner definition of autonomous exposure remediation, which Zafran cites as a category it was named a Sample Vendor for. ([source](https://www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-reports-for-unified-exposure-management-platforms-and-autonomous-exposure-remediation-categories), read 10 Nov 2026)
1 more on the [profile](/platforms/zafran/) |
| Works on the stack you have | Vendor's claim: Maze needs a read-only cloud role and an API connection to vulnerability scanners. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
Vendor's claim: It pulls and deduplicates findings from existing scanners. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
Vendor's claim: The Cohere Health story lists AWS and containers as the environment. ([source](https://mazehq.com/customer-story/how-cohere-health-cleared-92-of-its-critical-and-high-findings), read 10 Nov 2026)
None found on 10 Nov 2026: Specific scanner, code host and ticketing product names: none found on 2026-11-10: a named integration list on mazehq.com (the FAQ says only that it connects to the scanners customers already have) ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026) | Vendor's claim: Named sources on the home page: Zafran Discover, Tenable, Rapid7, Wiz, AWS, Snyk and 100+ more integrations. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Platform page: cloud and AppSec from Wiz, Palo Alto Networks, Upwind, AWS, Snyk; on-prem from Tenable, Qualys, Rapid7. ([source](https://www.zafran.io/platform), read 10 Nov 2026)
Vendor's claim: Controls read: CrowdStrike Falcon, Akamai WAF, Palo Alto NGFW (example policies). ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Ticketing and chat: Jira, Slack, ServiceNow (see owner facts); no new agents to deploy for ingestion. ([source](https://www.zafran.io/), read 10 Nov 2026) |
| Proof | Vendor's claim: Cohere Health story: 92% of critical and high findings not exploitable, downgraded or remediated. ([source](https://mazehq.com/customer-story/how-cohere-health-cleared-92-of-its-critical-and-high-findings), read 10 Nov 2026)
Vendor's claim: Same story: 87% of critical and high findings were not exploitable or safe to deprioritize. ([source](https://mazehq.com/customer-story/how-cohere-health-cleared-92-of-its-critical-and-high-findings), read 10 Nov 2026)
Vendor's claim: Named customer quotes: Alloy, Cohere Health, Forge, PartsSource. ([source](https://mazehq.com/), read 10 Nov 2026)
Vendor's claim: Maze claims deployment by multiple Fortune 100 organizations. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
1 more on the [profile](/platforms/maze/) | Vendor's claim: Sallie Mae case study: 96% reduction in CVSS Criticals and 23K vulnerabilities identified for mitigation with existing controls. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
Vendor's claim: Named CISO testimonial (Kraft Heinz). ([source](https://www.zafran.io/platform), read 10 Nov 2026)
Vendor's claim: Analyst recognition: KuppingerCole 2026 Leadership Compass banner on the home page. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Gartner Emerging Tech report mentions (Sept 11, 2026 and Apr 3, 2026), as reported by Zafran. ([source](https://www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-reports-for-unified-exposure-management-platforms-and-autonomous-exposure-remediation-categories), read 10 Nov 2026) |
| Profile facts | Vendor's claim: Maze was started in 2024. ([source](https://mazehq.com/our-story), read 10 Nov 2026)
Vendor's claim: Pricing is based on the size of the customer's cloud infrastructure; no public price list. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
Vendor's claim: Certifications: ISO 27001 and SOC 2 Type II. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
Vendor's claim: Hosted in AWS with multi-tenant or single-tenant options. ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026) | Vendor's claim: Founders: Sanaz Yashar (CEO) and Ben Seri (CTO). ([source](https://www.zafran.io/about), read 10 Nov 2026)
Vendor's claim: Investors named: Menlo Ventures, Sequoia Capital, Cyberstarts, plus strategic investment from Amex Ventures (Feb 24, 2026). ([source](https://www.zafran.io/resources/zafran-announces-strategic-investment-from-amex-ventures), read 10 Nov 2026)
Vendor's claim: Strategic investment from Cisco Investments announced Jul 22, 2026 (headline on news index). ([source](https://www.zafran.io/news), read 10 Nov 2026)
None found on 10 Nov 2026: Round amounts, founding year, headquarters, headcount, customer count and pricing on the pages read ([source](https://www.zafran.io/platform), read 10 Nov 2026) |
Alphabetical by name. Each line is one fact with its label, source and read date.
## Profiles
- [Maze profile](/platforms/maze/): agentic vulnerability
- [Zafran profile](/platforms/zafran/): exposure management platform with
## Related pages
- [24 pairs, side by side](/compare/)
- [Onit Security vs Rival Security: the sourced facts side by side](/compare/onit-vs-rival/)
- [Maze vs Rival Security: the sourced facts side by side](/compare/maze-vs-rival/)
- [Onit Security vs Zafran: the sourced facts side by side](/compare/onit-vs-zafran/)
## Sources
- Maze: mazehq.com/platform/cloud: https://mazehq.com/platform/cloud (read 10 Nov 2026)
- Maze: mazehq.com/: https://mazehq.com/ (read 10 Nov 2026)
- Maze: mazehq.com/platform/code: https://mazehq.com/platform/code (read 10 Nov 2026)
- Maze: mazehq.com/customer-story/how-cohere-health-cleared-92-of-its-critical-and-high-: https://mazehq.com/customer-story/how-cohere-health-cleared-92-of-its-critical-and-high-findings (read 10 Nov 2026)
- Maze: mazehq.com/solutions/remediation: https://mazehq.com/solutions/remediation (read 10 Nov 2026)
- Maze: mazehq.com/blog/php2shell: https://mazehq.com/blog/php2shell (read 10 Nov 2026)
- Maze: mazehq.com/platform: https://mazehq.com/platform (read 10 Nov 2026)
- Zafran: www.zafran.io/: https://www.zafran.io/ (read 10 Nov 2026)
- Zafran: www.zafran.io/solutions/use-cases/mitigate-risk: https://www.zafran.io/solutions/use-cases/mitigate-risk (read 10 Nov 2026)
- Zafran: www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-: https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes (read 10 Nov 2026)
- Zafran: www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration: https://www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration-with-google-threat-intelligence (read 10 Nov 2026)
- Zafran: www.zafran.io/platform: https://www.zafran.io/platform (read 10 Nov 2026)
- Zafran: www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-re: https://www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-reports-for-unified-exposure-management-platforms-and-autonomous-exposure-remediation-categories (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/compare/maze-vs-zafran/
---
# Onit Security vs Rival Security: the sourced facts side by side
Side by side, read 10 Nov 2026
**The short answer.** Onit Security and Rival Security. Onit Security has 37 fact lines (1 third-party) and Rival Security has 40 (0 third-party). Fixes: Onit Security, mitigations and pull requests; Rival Security, pull requests and mitigations. Onit Security has a none-found line on agents; Rival Security on proof. The rows below set the sourced facts side by side; the page names no pick.
## The same rows for both
| Row | Onit Security | Rival Security |
| --- | --- | --- |
| What it is | Agentic exposure management / remediation (decision-based) | Agentic security platform / agent harness for vulnerability management, code and cloud security |
| What it 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. | 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. |
| Where it is 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. | 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. |
| Proves exploitability in your environment | Vendor's claim: Platform layer that validates whether each exposure is reachable and exploitable in the customer environment, so only real risk continues. ([source](https://onit.security/platform/), read 10 Nov 2026)
Vendor's claim: Exploitability signals named: network reachability, runtime and loaded status, and live exploit intelligence such as KEV and weaponization. ([source](https://onit.security/platform/), read 10 Nov 2026)
Vendor's claim: A Reachability Agent returns a per-asset finding (reachable, restricted, internal, not reachable, unknown) with the path or the blocker as evidence, read-only. ([source](https://onit.security/blog/reachable-vulnerabilities/), read 10 Nov 2026)
Vendor's claim: An Exploitability Agent checks host conditions (component present, loaded, configured in the exploitable way); failed findings are kept with the reason. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
1 more on the [profile](/platforms/onit/) | Vendor's claim: Home page lists a Triage Exploitability agent that determines what is actually exploitable in the customer environment. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page says Rival reads every scanner finding against the real environment and keeps only those that can cause harm; it cites a 94.6% reduction in findings. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page reports 98% of findings proven unexploitable, 87% faster remediation and 1.5 hours to first value (no method given on the page). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: In its PHP2Shell write-up, Rival says agents ordered services to fix by reachability, internet-exposed unauthenticated workloads first. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Ships the fix | Vendor's claim: A Remediation Agent builds a step-by-step remediation plan (patch/version, deployment path, restart and validation steps, rollback) per asset; the published text describes a plan, not an automatically opened pull request. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
Vendor's claim: A Mitigation Agent proposes interim mitigations (disable a feature, tighten a firewall rule, compensating control), tagged by time, complexity and operational impact. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
Vendor's claim: Human approval gate on every agent action, with audit trail and one-step reversal, for both remediations and mitigations. ([source](https://onit.security/platform/), read 10 Nov 2026)
Vendor's claim: Vendor states nothing executes without approval. ([source](https://onit.security/platform/), read 10 Nov 2026) | Vendor's claim: Home page lists an Autonomous Remediation agent that generates and ships tested fixes. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page describes the remediation flow as plan, test, and open a pull request for human review. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival lists a WAF mitigation agent that checks whether a WAF blocks exploitation and adjusts it. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival describes an alternative-remediation agent for legacy apps that plans a fix without upgrading libraries. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
2 more on the [profile](/platforms/rival/) |
| Finds the owner | Vendor's claim: Resolves the owner from CMDB, ticketing and communication tools rather than leaving owner guessing to the customer. ([source](https://onit.security/), read 10 Nov 2026)
Vendor's claim: Ownership inferred from commit authorship, historical patterns and service maps, and re-resolved after reorganizations. ([source](https://onit.security/platform/), read 10 Nov 2026)
Vendor's claim: After assigning, it nudges, escalates and tracks the work to closure. ([source](https://onit.security/platform/), read 10 Nov 2026)
Vendor's claim: Vendor reports roughly half of remediation tickets bounce because the owner is wrong on arrival (its own field observation, no published method). ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026) | Vendor's claim: Home page lists an Ownership Resolution agent that maps each finding to the team that can fix it. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page says the owner-finding agent weighs root cause, team structure and past history (memories). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: PHP2Shell write-up says agents can message the relevant employees, and the harness lists human follow-ups. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
| Speed on a new disclosure | Vendor's claim: A Zero-Day Agent is described as catching a zero-day as it breaks, finding every exposed asset and proving which are exploitable, in minutes (blog dated Oct 23, 2026). ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
Vendor's claim: The Zero-Day Agent was announced ahead of general availability as of the blog date. ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
Vendor's claim: Published write-up of the PHP2Shell zero-day (leak Oct 20, 2026) walks through the four questions the agent answers. ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
Vendor's claim: Zero-Day Agent limits: no live exploits against production, no new endpoint agent, no disruptive action without approval. ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
1 more on the [profile](/platforms/onit/) | Vendor's claim: Home page lists a 0-day Fast Response agent covering triage through remediation. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page describes 0-day rapid response as finding exposure across code, images and cloud and prioritizing what to do first (page also claims a drop from days to minutes). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Published response write-up: for PHP2Shell, agents were triaging customer environments hours before scanners could detect the CVEs. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: The same write-up reports scanning more than 80,000 repositories within hours. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Agents you can shape | Vendor's claim: Ready-made specialized agents (discovery, ownership, exploitability, threat intel, prioritization, resolution, remediation, mitigation) run in parallel on one shared context. ([source](https://onit.security/platform/), read 10 Nov 2026)
Vendor's claim: Named agents in the Decision Center: Reachability, Exploitability, Context, Ownership, Prioritization, Remediation, Mitigation. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
Vendor's claim: Guardrail model: a person reviews each decision once; approved decisions become standing rules covering matching exposures, logged and reversible. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
Vendor's claim: Agent controls: customer can adjust one agent without touching the others. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
1 more on the [profile](/platforms/onit/) | Vendor's claim: Rival offers ready-made agents that can be customized and extended. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival engineers build custom agents for the customer environment at no additional cost (Partner tier). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Customers can build their own agents on the harness. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page says 64+ more agents are available beyond the five featured. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
2 more on the [profile](/platforms/rival/) |
| Works on the stack you have | Vendor's claim: Sources are described by category: security tools, cloud, CMDBs, ticketing and collaboration systems (scanners, CSPM, EDR/XDR). ([source](https://onit.security/platform/), read 10 Nov 2026)
Vendor's claim: Knowledge sources include asset inventories, ticketing and change history, wikis, Slack and Teams threads, email, cloud tags, directories and code repositories. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
Vendor's claim: Zero-Day Agent reads scanners, cloud accounts, EDR and CMDB already connected, and checks exploitability read-only through the EDR. ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
None found on 10 Nov 2026: A list of named scanner, cloud, code host or ticketing product integrations on onit.security ([source](https://onit.security/), read 10 Nov 2026) | Vendor's claim: Home page names cloud, code host and infrastructure integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page names scanner, control and task integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases table shows findings sourced from Wiz, Qualys, GitHub, a pentest, and Rival's own SCA and Code scanners. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Agents combine connected services with a Rival Security Knowledge Graph. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
| Proof | Vendor's claim: Named-person testimonials appear on the home page (titles only, employers not named in the quote block). ([source](https://onit.security/), read 10 Nov 2026)
Vendor's claim: Anecdote of an unnamed Fortune 500 customer where three tools showed no findings and Onit found two devices on a KEV-listed product. ([source](https://onit.security/blog/reachable-vulnerabilities/), read 10 Nov 2026)
Vendor's claim: Research and thought-leadership blog cadence (posts Jul to Nov 2026) citing Mandiant M-Trends and Verizon DBIR; no original measured study seen. ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
None found on 10 Nov 2026: Named customer case studies or a published measurement method for the 55 days to 2.7 hours claim ([source](https://onit.security/), read 10 Nov 2026) | Vendor's claim: Use-cases page claims 13M+ agent runs. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival published SASTBench, a benchmark for SAST triage using real CVEs as true positives and filtered SAST findings as noise. ([source](https://rival.security/blog/sastbench-measuring-ai-security-automation?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Research blog post claims Rival workflows outperform current frontier models on the Spider 2.0 benchmark. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Published incident write-up (PHP2Shell, Nov 2, 2026) with unnamed customer results. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Profile facts | Vendor's claim: Founders: Elad Ben Meir (CEO), Ofer Amitai (CPO), Tom Winter (CTO). ([source](https://onit.security/company/), read 10 Nov 2026)
Vendor's claim: CEO background: previously CEO of SCADAfence (acquired by Honeywell). ([source](https://onit.security/company/), read 10 Nov 2026)
Vendor's claim: Funding: seed round closed in 2025; amount not stated on the page. ([source](https://onit.security/company/), read 10 Nov 2026)
None found on 10 Nov 2026: Headquarters address, headcount, seed amount, pricing and customer count on onit.security ([source](https://onit.security/company/), read 10 Nov 2026) | Vendor's claim: Tagline and category: Rival describes itself as an agent harness for cybersecurity. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Research blog launched Feb 2025 describing early experiments building AI systems for cybersecurity. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
None found on 10 Nov 2026: Pricing (rival.security/pricing returns 404; book-a-demo form only). ([source](https://rival.security/book-a-demo-form?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
None found on 10 Nov 2026: Funding, investors, founders, headcount, HQ or founding year on home, blog, careers, book-a-demo pages. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
Alphabetical by name. Each line is one fact with its label, source and read date.
## Profiles
- [Onit Security profile](/platforms/onit/): agentic exposure management
- [Rival Security profile](/platforms/rival/): agentic security platform
## Related pages
- [24 pairs, side by side](/compare/)
- [Onit Security vs Zafran: the sourced facts side by side](/compare/onit-vs-zafran/)
- [Maze vs Zafran: the sourced facts side by side](/compare/maze-vs-zafran/)
- [Qualys vs Rapid7: the sourced facts side by side](/compare/qualys-vs-rapid7/)
## Sources
- Onit Security: onit.security/platform/: https://onit.security/platform/ (read 10 Nov 2026)
- Onit Security: onit.security/blog/reachable-vulnerabilities/: https://onit.security/blog/reachable-vulnerabilities/ (read 10 Nov 2026)
- Onit Security: onit.security/blog/ai-agents-vulnerability-management/: https://onit.security/blog/ai-agents-vulnerability-management/ (read 10 Nov 2026)
- Onit Security: onit.security/: https://onit.security/ (read 10 Nov 2026)
- Onit Security: onit.security/blog/zero-day-response/: https://onit.security/blog/zero-day-response/ (read 10 Nov 2026)
- Rival Security: rival.security/: https://rival.security/ (read 10 Nov 2026)
- Rival Security: rival.security/use-cases: https://rival.security/use-cases (read 10 Nov 2026)
- Rival Security: rival.security/blog/php2shell-black-october-2026: https://rival.security/blog/php2shell-black-october-2026 (read 10 Nov 2026)
- Rival Security: docs.rival.security: https://docs.rival.security (read 10 Nov 2026)
- Rival Security: rival.security/blog/sastbench-measuring-ai-security-automation: https://rival.security/blog/sastbench-measuring-ai-security-automation (read 10 Nov 2026)
- Rival Security: rival.security/blog: https://rival.security/blog (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/compare/onit-vs-rival/
---
# Onit Security vs Zafran: the sourced facts side by side
Side by side, read 10 Nov 2026
**The short answer.** Onit Security and Zafran, on the same rows. Onit Security has 37 fact lines (1 third-party) and Zafran has 38 (0 third-party). Fixes: Onit Security, mitigations and pull requests; Zafran, mitigations and patches through patch tools. None found: Onit Security on agents; Zafran on agents. The rows below set the sourced facts side by side; the page names no pick.
## The same rows for both
| Row | Onit Security | Zafran |
| --- | --- | --- |
| What it is | Agentic exposure management / remediation (decision-based) | Exposure management platform with mitigation via existing controls (agentic features) |
| What it 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. | 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. |
| Where it is 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. | 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. |
| Proves exploitability in your environment | Vendor's claim: Platform layer that validates whether each exposure is reachable and exploitable in the customer environment, so only real risk continues. ([source](https://onit.security/platform/), read 10 Nov 2026)
Vendor's claim: Exploitability signals named: network reachability, runtime and loaded status, and live exploit intelligence such as KEV and weaponization. ([source](https://onit.security/platform/), read 10 Nov 2026)
Vendor's claim: A Reachability Agent returns a per-asset finding (reachable, restricted, internal, not reachable, unknown) with the path or the blocker as evidence, read-only. ([source](https://onit.security/blog/reachable-vulnerabilities/), read 10 Nov 2026)
Vendor's claim: An Exploitability Agent checks host conditions (component present, loaded, configured in the exploitable way); failed findings are kept with the reason. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
1 more on the [profile](/platforms/onit/) | Vendor's claim: Exposure Graph links each finding to asset, network path, runtime status and threat activity, then reads live control configuration to see what already protects the asset. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Prioritization weighs runtime, reachability, active exploitation, controls and business criticality. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Control assessment reads firewall, WAF, cloud security group and EDR configurations to show which vulnerabilities are already blocked. ([source](https://www.zafran.io/solutions/use-cases/mitigate-risk), read 10 Nov 2026)
Vendor's claim: Customer evidence: Sallie Mae says Zafran checks control configuration per device and adjusts risk accordingly. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
1 more on the [profile](/platforms/zafran/) |
| Ships the fix | Vendor's claim: A Remediation Agent builds a step-by-step remediation plan (patch/version, deployment path, restart and validation steps, rollback) per asset; the published text describes a plan, not an automatically opened pull request. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
Vendor's claim: A Mitigation Agent proposes interim mitigations (disable a feature, tighten a firewall rule, compensating control), tagged by time, complexity and operational impact. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
Vendor's claim: Human approval gate on every agent action, with audit trail and one-step reversal, for both remediations and mitigations. ([source](https://onit.security/platform/), read 10 Nov 2026)
Vendor's claim: Vendor states nothing executes without approval. ([source](https://onit.security/platform/), read 10 Nov 2026) | Vendor's claim: Mitigation first: uses existing firewall, WAF and EDR to reduce risk before a patch exists. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Attack Chains offers a compensating control (such as a WAF rule) applied in a few clicks at the choke point. ([source](https://www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration-with-google-threat-intelligence), read 10 Nov 2026)
Vendor's claim: Workflow example: one flow opens a ServiceNow ticket, pushes a WAF rule and tracks the SLA. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Patch/upgrade remediation is delivered as a Work Item routed to the owner in the ticketing tool, not as a pull request. ([source](https://www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration-with-google-threat-intelligence), read 10 Nov 2026)
2 more on the [profile](/platforms/zafran/) |
| Finds the owner | Vendor's claim: Resolves the owner from CMDB, ticketing and communication tools rather than leaving owner guessing to the customer. ([source](https://onit.security/), read 10 Nov 2026)
Vendor's claim: Ownership inferred from commit authorship, historical patterns and service maps, and re-resolved after reorganizations. ([source](https://onit.security/platform/), read 10 Nov 2026)
Vendor's claim: After assigning, it nudges, escalates and tracks the work to closure. ([source](https://onit.security/platform/), read 10 Nov 2026)
Vendor's claim: Vendor reports roughly half of remediation tickets bounce because the owner is wrong on arrival (its own field observation, no published method). ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026) | Vendor's claim: Collapses overlapping findings into one fix and routes it to the right team and owner. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Auto-assigns fixes to the owner in Jira, Slack and ServiceNow. ([source](https://www.zafran.io/platform), read 10 Nov 2026)
Vendor's claim: Example: 700 findings collapse into one OpenSSL upgrade ticket routed to the Platform team. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Progress tracking with shared visibility across Security and IT. ([source](https://www.zafran.io/platform), read 10 Nov 2026) |
| Speed on a new disclosure | Vendor's claim: A Zero-Day Agent is described as catching a zero-day as it breaks, finding every exposed asset and proving which are exploitable, in minutes (blog dated Oct 23, 2026). ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
Vendor's claim: The Zero-Day Agent was announced ahead of general availability as of the blog date. ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
Vendor's claim: Published write-up of the PHP2Shell zero-day (leak Oct 20, 2026) walks through the four questions the agent answers. ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
Vendor's claim: Zero-Day Agent limits: no live exploits against production, no new endpoint agent, no disruptive action without approval. ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
1 more on the [profile](/platforms/onit/) | Vendor's claim: Zero Day Agent scenario: matches a pre-announced OpenSSL flaw to live software inventory in 88 seconds before any CVE is published (illustrative scenario on the home page). ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Proactive Exposure Hunting for new CVEs and zero-days, including which affected assets are internet-exposed. ([source](https://www.zafran.io/platform), read 10 Nov 2026)
Vendor's claim: Customer quote: assess exposure before CVEs are defined. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
Vendor's claim: Customer-reported time to answer "are we exposed?" is minutes. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
1 more on the [profile](/platforms/zafran/) |
| Agents you can shape | Vendor's claim: Ready-made specialized agents (discovery, ownership, exploitability, threat intel, prioritization, resolution, remediation, mitigation) run in parallel on one shared context. ([source](https://onit.security/platform/), read 10 Nov 2026)
Vendor's claim: Named agents in the Decision Center: Reachability, Exploitability, Context, Ownership, Prioritization, Remediation, Mitigation. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
Vendor's claim: Guardrail model: a person reviews each decision once; approved decisions become standing rules covering matching exposures, logged and reversible. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
Vendor's claim: Agent controls: customer can adjust one agent without touching the others. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
1 more on the [profile](/platforms/onit/) | Vendor's claim: Ready-made Zero Day Agent and Zafran AI assistant; AI can build dashboards from prompts. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Customer-built agents: user prompts create a scheduled report agent that emails a daily report. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Zafran AI answers plain-language questions grounded in correlated asset and findings data (Sallie Mae case study). ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
Vendor's claim: Gartner definition of autonomous exposure remediation, which Zafran cites as a category it was named a Sample Vendor for. ([source](https://www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-reports-for-unified-exposure-management-platforms-and-autonomous-exposure-remediation-categories), read 10 Nov 2026)
1 more on the [profile](/platforms/zafran/) |
| Works on the stack you have | Vendor's claim: Sources are described by category: security tools, cloud, CMDBs, ticketing and collaboration systems (scanners, CSPM, EDR/XDR). ([source](https://onit.security/platform/), read 10 Nov 2026)
Vendor's claim: Knowledge sources include asset inventories, ticketing and change history, wikis, Slack and Teams threads, email, cloud tags, directories and code repositories. ([source](https://onit.security/blog/ai-agents-vulnerability-management/), read 10 Nov 2026)
Vendor's claim: Zero-Day Agent reads scanners, cloud accounts, EDR and CMDB already connected, and checks exploitability read-only through the EDR. ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
None found on 10 Nov 2026: A list of named scanner, cloud, code host or ticketing product integrations on onit.security ([source](https://onit.security/), read 10 Nov 2026) | Vendor's claim: Named sources on the home page: Zafran Discover, Tenable, Rapid7, Wiz, AWS, Snyk and 100+ more integrations. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Platform page: cloud and AppSec from Wiz, Palo Alto Networks, Upwind, AWS, Snyk; on-prem from Tenable, Qualys, Rapid7. ([source](https://www.zafran.io/platform), read 10 Nov 2026)
Vendor's claim: Controls read: CrowdStrike Falcon, Akamai WAF, Palo Alto NGFW (example policies). ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Ticketing and chat: Jira, Slack, ServiceNow (see owner facts); no new agents to deploy for ingestion. ([source](https://www.zafran.io/), read 10 Nov 2026) |
| Proof | Vendor's claim: Named-person testimonials appear on the home page (titles only, employers not named in the quote block). ([source](https://onit.security/), read 10 Nov 2026)
Vendor's claim: Anecdote of an unnamed Fortune 500 customer where three tools showed no findings and Onit found two devices on a KEV-listed product. ([source](https://onit.security/blog/reachable-vulnerabilities/), read 10 Nov 2026)
Vendor's claim: Research and thought-leadership blog cadence (posts Jul to Nov 2026) citing Mandiant M-Trends and Verizon DBIR; no original measured study seen. ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
None found on 10 Nov 2026: Named customer case studies or a published measurement method for the 55 days to 2.7 hours claim ([source](https://onit.security/), read 10 Nov 2026) | Vendor's claim: Sallie Mae case study: 96% reduction in CVSS Criticals and 23K vulnerabilities identified for mitigation with existing controls. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
Vendor's claim: Named CISO testimonial (Kraft Heinz). ([source](https://www.zafran.io/platform), read 10 Nov 2026)
Vendor's claim: Analyst recognition: KuppingerCole 2026 Leadership Compass banner on the home page. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Gartner Emerging Tech report mentions (Sept 11, 2026 and Apr 3, 2026), as reported by Zafran. ([source](https://www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-reports-for-unified-exposure-management-platforms-and-autonomous-exposure-remediation-categories), read 10 Nov 2026) |
| Profile facts | Vendor's claim: Founders: Elad Ben Meir (CEO), Ofer Amitai (CPO), Tom Winter (CTO). ([source](https://onit.security/company/), read 10 Nov 2026)
Vendor's claim: CEO background: previously CEO of SCADAfence (acquired by Honeywell). ([source](https://onit.security/company/), read 10 Nov 2026)
Vendor's claim: Funding: seed round closed in 2025; amount not stated on the page. ([source](https://onit.security/company/), read 10 Nov 2026)
None found on 10 Nov 2026: Headquarters address, headcount, seed amount, pricing and customer count on onit.security ([source](https://onit.security/company/), read 10 Nov 2026) | Vendor's claim: Founders: Sanaz Yashar (CEO) and Ben Seri (CTO). ([source](https://www.zafran.io/about), read 10 Nov 2026)
Vendor's claim: Investors named: Menlo Ventures, Sequoia Capital, Cyberstarts, plus strategic investment from Amex Ventures (Feb 24, 2026). ([source](https://www.zafran.io/resources/zafran-announces-strategic-investment-from-amex-ventures), read 10 Nov 2026)
Vendor's claim: Strategic investment from Cisco Investments announced Jul 22, 2026 (headline on news index). ([source](https://www.zafran.io/news), read 10 Nov 2026)
None found on 10 Nov 2026: Round amounts, founding year, headquarters, headcount, customer count and pricing on the pages read ([source](https://www.zafran.io/platform), read 10 Nov 2026) |
Alphabetical by name. Each line is one fact with its label, source and read date.
## Profiles
- [Onit Security profile](/platforms/onit/): agentic exposure management
- [Zafran profile](/platforms/zafran/): exposure management platform with
## Related pages
- [24 pairs, side by side](/compare/)
- [Qualys vs Rapid7: the sourced facts side by side](/compare/qualys-vs-rapid7/)
- [Onit Security vs Rival Security: the sourced facts side by side](/compare/onit-vs-rival/)
- [Qualys vs Rival Security: the sourced facts side by side](/compare/qualys-vs-rival/)
## Sources
- Onit Security: onit.security/platform/: https://onit.security/platform/ (read 10 Nov 2026)
- Onit Security: onit.security/blog/reachable-vulnerabilities/: https://onit.security/blog/reachable-vulnerabilities/ (read 10 Nov 2026)
- Onit Security: onit.security/blog/ai-agents-vulnerability-management/: https://onit.security/blog/ai-agents-vulnerability-management/ (read 10 Nov 2026)
- Onit Security: onit.security/: https://onit.security/ (read 10 Nov 2026)
- Onit Security: onit.security/blog/zero-day-response/: https://onit.security/blog/zero-day-response/ (read 10 Nov 2026)
- Zafran: www.zafran.io/: https://www.zafran.io/ (read 10 Nov 2026)
- Zafran: www.zafran.io/solutions/use-cases/mitigate-risk: https://www.zafran.io/solutions/use-cases/mitigate-risk (read 10 Nov 2026)
- Zafran: www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-: https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes (read 10 Nov 2026)
- Zafran: www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration: https://www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration-with-google-threat-intelligence (read 10 Nov 2026)
- Zafran: www.zafran.io/platform: https://www.zafran.io/platform (read 10 Nov 2026)
- Zafran: www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-re: https://www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-reports-for-unified-exposure-management-platforms-and-autonomous-exposure-remediation-categories (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/compare/onit-vs-zafran/
---
# Qualys vs Rapid7: the sourced facts side by side
Side by side, read 10 Nov 2026
**The short answer.** Qualys and Rapid7, on the same rows. Qualys has 37 fact lines (0 third-party) and Rapid7 has 31 (0 third-party). Fix form on file: Qualys, patches through patch tools and tickets; Rapid7, automated workflows and pull requests. None found: Qualys on agents; Rapid7 on owner. The rows below set the sourced facts side by side; the page names no pick.
## The same rows for both
| Row | Qualys | Rapid7 |
| --- | --- | --- |
| What it is | Exposure/RBVM platform with remediation and agentic AI | Exposure/RBVM platform with remediation workflows |
| What it 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. | 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. |
| Where it is 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'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. |
| Proves exploitability in your environment | Vendor's claim: Agent Val uses TruConfirm to test whether an exposure is reachable and weaponizable by an attacker in the customer's environment. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: After mitigation, the agent re-checks exploit validation and keeps an audit trail. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: Qualys says validated exploitability narrows a large backlog to the 1% to fix now. ([source](https://www.qualys.com/apps/trurisk-eliminate/), read 10 Nov 2026)
Vendor's claim: Agent Nyra maps weaponized CVEs to impacted assets and re-orders the risk backlog by active exploitation. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
1 more on the [profile](/platforms/qualys/) | Vendor's claim: Exposure Command prioritizes using exploit likelihood, reachability, severity, and business context. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Exposure Command tier adds attack path analysis and contextual risk prioritization. ([source](https://www.rapid7.com/products/command/pricing/), read 10 Nov 2026)
Vendor's claim: Exposure Command provides a risk score based on toxic combinations plus internal and external views. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Rapid7 describes a threat-aware active risk score in the Essentials tier. ([source](https://www.rapid7.com/products/command/pricing/), read 10 Nov 2026)
1 more on the [profile](/platforms/rapid7/) |
| Ships the fix | Vendor's claim: TruRisk Eliminate 2.0 Agent Sara coordinates remediation across Qualys and third-party ecosystems to patch, mitigate, uninstall, or isolate hosts. ([source](https://www.qualys.com/apps/trurisk-eliminate/), read 10 Nov 2026)
Vendor's claim: AI patch reliability scoring decides deployment approach: zero-touch for high confidence, ring-staged for medium, manual CAB for low. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: When no patch exists, it runs patchless strategies such as mitigate, uninstall, custom script, fix, and isolate. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: Automatic rollback if a deployment causes issues, and verification that the vulnerability is fixed rather than only the ticket closed. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
2 more on the [profile](/platforms/qualys/) | Vendor's claim: Exposure Command offers no-code native automation for automated remediation. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Exposure Command lists automated remediation workflows and automated cloud remediation as tier features. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Rapid7 says built-in remediation workflows give AI-powered remediation guidance, automation, and team workflows; the page does not say a tested PR or virtual patch is produced. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Rapid7's own analysis says reducing exposure still requires teams to choose the remediation or compensating control and verify the result. ([source](https://www.rapid7.com/blog/post/ai-gartner-report-attack-paths-closing-faster-than-patchable/), read 10 Nov 2026) |
| Finds the owner | Vendor's claim: Qualys Patch Management lists bidirectional integrations with CMDB and ITSM tools. ([source](https://www.qualys.com/apps/patch-management/), read 10 Nov 2026)
Vendor's claim: ETM positions remediation workflows with automated patching, IT tickets, and real-time alerts; no per-finding owner resolution (code owner or team mapping) was found. ([source](https://www.qualys.com/apps/enterprise-trurisk-management), read 10 Nov 2026)
Vendor's claim: Cloud Workflow Automation is described as automating remediation workflows using asset criticality and blast radius. ([source](https://www.qualys.com/apps/enterprise-trurisk-management), read 10 Nov 2026) | Vendor's claim: Essentials tier includes remediation projects and SLAs. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Automated notification and ticketing gives developers real-time feedback. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
None found on 10 Nov 2026: Per-finding resolution to an owning team (for example from code owners or cloud tags): none found on 2026-11-10 on the Exposure Command page read. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026) |
| Speed on a new disclosure | Vendor's claim: Agent Insta (scanless detection) claims real exposure within minutes of disclosure by correlating existing telemetry. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: Qualys cites time-to-exploit collapsing from weeks to hours and positions its Risk Operations Center around that. ([source](https://www.qualys.com/post-mythos-autonomous-remediation), read 10 Nov 2026)
Vendor's claim: Qualys published a blog on zero-day remediation and operational resiliency with TruRisk Eliminate (dated 2026-08-03 in URL). ([source](https://blog.qualys.com/product-tech/2026/08/03/zero-day-remediation-operational-resiliency-trurisk-eliminate), read 10 Nov 2026)
Vendor's claim: Qualys cites Cintas patching the most severe threats automatically in under 24 hours. ([source](https://www.qualys.com/customers/success-stories/cintas-replaces-manual-patching-tasks-with-risk-based-from-qualys-enterprise-trurisk-platform), read 10 Nov 2026) | Vendor's claim: For Ivanti Connect Secure zero-days, Rapid7 stated authenticated vulnerability checks were available since the 2026-10-30 content release (the day CISA added them to KEV). ([source](https://www.rapid7.com/blog/post/etr-additional-ivanti-connect-secure-zero-days-exploited-in-the-wild-cve-2026-111357-cve-2026-118527/), read 10 Nov 2026)
Vendor's claim: Rapid7 runs an Emergent Threat Response blog stream for high-priority threats. ([source](https://www.rapid7.com/blog/tag/emergent-threat-response/), read 10 Nov 2026)
Vendor's claim: Rapid7 Q3 2026 threat update says three days is the average time from high-severity vulnerability disclosure to exploitation. ([source](https://www.rapid7.com/blog/post/tr-q3-2026-threat-update-attackers-exploiting-vulnerabilities-within-3-days/), read 10 Nov 2026) |
| Agents you can shape | Vendor's claim: Qualys ships ready-made AI agents inside ETM: Agent Insta (detection), Agent Val (validation), Agent Sara (remediation), Agent Nyra (threat prioritization). ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: ROCky is a conversational AI interface in the Risk Operations Center that queries exposure data and navigates remediation workflows. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: Guardrails: confidence-gated waves, staged rollout, CAB for low-reliability patches, and automatic rollback. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: Operational Resiliency watches system health through Qualys checks or partner integrations such as Dynatrace, pausing and rolling back if something looks wrong. ([source](https://www.qualys.com/apps/trurisk-eliminate/), read 10 Nov 2026)
1 more on the [profile](/platforms/qualys/) | Vendor's claim: Rapid7 references AI-powered remediation guidance in Exposure Command and human-centric AI in its SOC offering; no controls model for agents was documented. ([source](https://www.rapid7.com/solutions/ai-powered-security-operations-soc/), read 10 Nov 2026)
Vendor's claim: Rapid7 reports internal practitioner exploration of Claude Mythos Preview through Project Glasswing. ([source](https://www.rapid7.com/blog/post/ai-gartner-report-attack-paths-closing-faster-than-patchable/), read 10 Nov 2026)
None found on 10 Nov 2026: Agentic remediation features, Remediation Hub, or ready-made or customer-built AI agents for exposure management: none found on 2026-11-10 on the Exposure Command, InsightVM, pricing, or AI-SOC pages read (the word agentic did not appear). ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026) |
| Works on the stack you have | Vendor's claim: Qualys ETM consolidates data from on-premises, cloud, containers, identities, and applications. ([source](https://www.qualys.com/apps/enterprise-trurisk-management), read 10 Nov 2026)
Vendor's claim: Qualys platform covers VMDR, CSAM, EASM, CSPM, KCS, CWP, IaC security, CIEM, SSPM, DSPM, and software supply chain risk. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: Named integrations seen: ServiceNow (change) and Dynatrace (health checks). ([source](https://www.qualys.com/apps/trurisk-eliminate/), read 10 Nov 2026)
Vendor's claim: Single-agent architecture covering on-premises, cloud and web applications. ([source](https://www.qualys.com/about-qualys), read 10 Nov 2026) | Vendor's claim: Exposure Command lists 500+ integrations across cloud, identity, ITSM, ticketing, EDR, and CI/CD. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Cloud coverage includes AWS, Azure, GCP, and Kubernetes, plus Oracle Cloud and Alibaba Cloud in the extended tier. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Exposure Command adds infrastructure-as-code scanning and DAST. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Exposure Command correlates third-party findings with Rapid7 vulnerability telemetry. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026) |
| Proof | Vendor's claim: Cintas case study: replaced manual patching with Qualys VMDR, Patch Management, TruRisk and CSAM. ([source](https://www.qualys.com/customers/success-stories/cintas-replaces-manual-patching-tasks-with-risk-based-from-qualys-enterprise-trurisk-platform), read 10 Nov 2026)
Vendor's claim: Qualys states 10,000+ subscription customers in 130+ countries. ([source](https://www.qualys.com/about-qualys), read 10 Nov 2026)
Vendor's claim: Qualys states it participates in Project Glasswing with Anthropic's Claude Mythos Preview. ([source](https://www.qualys.com/about-qualys), read 10 Nov 2026)
Vendor's claim: Qualys cites a customer cutting remediation times from weeks to minutes (unnamed, no method published on the page). ([source](https://www.qualys.com/apps/trurisk-eliminate/), read 10 Nov 2026)
1 more on the [profile](/platforms/qualys/) | Vendor's claim: Rapid7 states more than 11,500 customers. ([source](https://www.rapid7.com/about/), read 10 Nov 2026)
Vendor's claim: Rapid7 was placed in the upper-right quadrant of the 2025 Gartner Magic Quadrant (vendor's claim) for Exposure Assessment Platforms. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Americor customer story: Rapid7 universal agent gave up-to-date vulnerability understanding. ([source](https://www.rapid7.com/customers/americor/), read 10 Nov 2026)
Vendor's claim: Rapid7 publishes a quarterly threat landscape report and Metasploit wrap-ups as research output. ([source](https://www.rapid7.com/blog/), read 10 Nov 2026) |
| Profile facts | Vendor's claim: Qualys, Inc. is publicly traded on NASDAQ as QLYS and still operates under the Qualys name. ([source](https://www.qualys.com/about-qualys), read 10 Nov 2026)
Vendor's claim: Qualys says it is one of the first SaaS security vendors, since 1999. ([source](https://www.qualys.com/about-qualys), read 10 Nov 2026)
Vendor's claim: Qualys describes itself as a unified platform to power a risk operations center, with a majority of the Forbes Global 100 and Fortune 100 as customers. ([source](https://www.qualys.com/about-qualys), read 10 Nov 2026)
Vendor's claim: Products: Enterprise TruRisk Management (ETM), TruRisk Eliminate 2.0, Patch Management, TruConfidence engine, ROCky, Agent Insta/Val/Sara/Nyra. ([source](https://www.qualys.com/apps/trurisk-eliminate/), read 10 Nov 2026) | Vendor's claim: Rapid7 is an exposure and detection company with Exposure Command (including an Essentials tier) and Surface Command on its Command Platform. ([source](https://www.rapid7.com/products/command/pricing/), read 10 Nov 2026)
Vendor's claim: Pricing: no list prices on the pricing page read; it describes usage-based pricing by asset type. ([source](https://www.rapid7.com/products/command/pricing/), read 10 Nov 2026)
Vendor's claim: InsightVM is folded into the Exposure Command packaging, with a page asking whether InsightVM is still available. ([source](https://www.rapid7.com/products/insightvm/), read 10 Nov 2026)
Vendor's claim: Rapid7 was recognized by the Boston Business Journal as one of the Boston Business Journal's listed Places to Work for the 14th consecutive year (headquarters not stated on the page). ([source](https://www.rapid7.com/about/news/), read 10 Nov 2026) |
Alphabetical by name. Each line is one fact with its label, source and read date.
## Profiles
- [Qualys profile](/platforms/qualys/): exposure
- [Rapid7 profile](/platforms/rapid7/): exposure
## Related pages
- [24 pairs, side by side](/compare/)
- [Qualys vs Rival Security: the sourced facts side by side](/compare/qualys-vs-rival/)
- [Onit Security vs Zafran: the sourced facts side by side](/compare/onit-vs-zafran/)
- [Qualys vs Tenable: the sourced facts side by side](/compare/qualys-vs-tenable/)
## Sources
- Qualys: www.qualys.com/apps/agentic-ai: https://www.qualys.com/apps/agentic-ai (read 10 Nov 2026)
- Qualys: www.qualys.com/apps/trurisk-eliminate/: https://www.qualys.com/apps/trurisk-eliminate/ (read 10 Nov 2026)
- Qualys: www.qualys.com/post-mythos-autonomous-remediation: https://www.qualys.com/post-mythos-autonomous-remediation (read 10 Nov 2026)
- Qualys: blog.qualys.com/product-tech/2026/08/03/zero-day-remediation-operational-resilie: https://blog.qualys.com/product-tech/2026/08/03/zero-day-remediation-operational-resiliency-trurisk-eliminate (read 10 Nov 2026)
- Qualys: www.qualys.com/apps/patch-management/: https://www.qualys.com/apps/patch-management/ (read 10 Nov 2026)
- Qualys: www.qualys.com/apps/enterprise-trurisk-management: https://www.qualys.com/apps/enterprise-trurisk-management (read 10 Nov 2026)
- Qualys: www.qualys.com/customers/success-stories/cintas-replaces-manual-patching-tasks-w: https://www.qualys.com/customers/success-stories/cintas-replaces-manual-patching-tasks-with-risk-based-from-qualys-enterprise-trurisk-platform (read 10 Nov 2026)
- Qualys: www.qualys.com/about-qualys: https://www.qualys.com/about-qualys (read 10 Nov 2026)
- Rapid7: www.rapid7.com/products/command/exposure-management/: https://www.rapid7.com/products/command/exposure-management/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/products/command/pricing/: https://www.rapid7.com/products/command/pricing/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/blog/post/ai-gartner-report-attack-paths-closing-faster-than-patc: https://www.rapid7.com/blog/post/ai-gartner-report-attack-paths-closing-faster-than-patchable/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/blog/post/etr-additional-ivanti-connect-secure-zero-days-exploite: https://www.rapid7.com/blog/post/etr-additional-ivanti-connect-secure-zero-days-exploited-in-the-wild-cve-2026-111357-cve-2026-118527/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/blog/tag/emergent-threat-response/: https://www.rapid7.com/blog/tag/emergent-threat-response/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/blog/post/tr-q3-2026-threat-update-attackers-exploiting-vulnerabi: https://www.rapid7.com/blog/post/tr-q3-2026-threat-update-attackers-exploiting-vulnerabilities-within-3-days/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/solutions/ai-powered-security-operations-soc/: https://www.rapid7.com/solutions/ai-powered-security-operations-soc/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/about/: https://www.rapid7.com/about/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/customers/americor/: https://www.rapid7.com/customers/americor/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/blog/: https://www.rapid7.com/blog/ (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/compare/qualys-vs-rapid7/
---
# Qualys vs Rival Security: the sourced facts side by side
Side by side, read 10 Nov 2026
**The short answer.** Qualys and Rival Security are set side by side on the same rows. Fact lines: Qualys 37, Rival Security 40. Third-party: 0 and 0. Fixes: Qualys, patches through patch tools; Rival Security, pull requests. Qualys has a none-found line on agents; Rival Security on proof. The rows below set the sourced facts side by side; the page names no pick.
## The same rows for both
| Row | Qualys | Rival Security |
| --- | --- | --- |
| What it is | Exposure/RBVM platform with remediation and agentic AI | Agentic security platform / agent harness for vulnerability management, code and cloud security |
| What it 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. | 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. |
| Where it is 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. | 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. |
| Proves exploitability in your environment | Vendor's claim: Agent Val uses TruConfirm to test whether an exposure is reachable and weaponizable by an attacker in the customer's environment. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: After mitigation, the agent re-checks exploit validation and keeps an audit trail. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: Qualys says validated exploitability narrows a large backlog to the 1% to fix now. ([source](https://www.qualys.com/apps/trurisk-eliminate/), read 10 Nov 2026)
Vendor's claim: Agent Nyra maps weaponized CVEs to impacted assets and re-orders the risk backlog by active exploitation. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
1 more on the [profile](/platforms/qualys/) | Vendor's claim: Home page lists a Triage Exploitability agent that determines what is actually exploitable in the customer environment. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page says Rival reads every scanner finding against the real environment and keeps only those that can cause harm; it cites a 94.6% reduction in findings. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page reports 98% of findings proven unexploitable, 87% faster remediation and 1.5 hours to first value (no method given on the page). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: In its PHP2Shell write-up, Rival says agents ordered services to fix by reachability, internet-exposed unauthenticated workloads first. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Ships the fix | Vendor's claim: TruRisk Eliminate 2.0 Agent Sara coordinates remediation across Qualys and third-party ecosystems to patch, mitigate, uninstall, or isolate hosts. ([source](https://www.qualys.com/apps/trurisk-eliminate/), read 10 Nov 2026)
Vendor's claim: AI patch reliability scoring decides deployment approach: zero-touch for high confidence, ring-staged for medium, manual CAB for low. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: When no patch exists, it runs patchless strategies such as mitigate, uninstall, custom script, fix, and isolate. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: Automatic rollback if a deployment causes issues, and verification that the vulnerability is fixed rather than only the ticket closed. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
2 more on the [profile](/platforms/qualys/) | Vendor's claim: Home page lists an Autonomous Remediation agent that generates and ships tested fixes. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page describes the remediation flow as plan, test, and open a pull request for human review. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival lists a WAF mitigation agent that checks whether a WAF blocks exploitation and adjusts it. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival describes an alternative-remediation agent for legacy apps that plans a fix without upgrading libraries. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
2 more on the [profile](/platforms/rival/) |
| Finds the owner | Vendor's claim: Qualys Patch Management lists bidirectional integrations with CMDB and ITSM tools. ([source](https://www.qualys.com/apps/patch-management/), read 10 Nov 2026)
Vendor's claim: ETM positions remediation workflows with automated patching, IT tickets, and real-time alerts; no per-finding owner resolution (code owner or team mapping) was found. ([source](https://www.qualys.com/apps/enterprise-trurisk-management), read 10 Nov 2026)
Vendor's claim: Cloud Workflow Automation is described as automating remediation workflows using asset criticality and blast radius. ([source](https://www.qualys.com/apps/enterprise-trurisk-management), read 10 Nov 2026) | Vendor's claim: Home page lists an Ownership Resolution agent that maps each finding to the team that can fix it. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page says the owner-finding agent weighs root cause, team structure and past history (memories). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: PHP2Shell write-up says agents can message the relevant employees, and the harness lists human follow-ups. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
| Speed on a new disclosure | Vendor's claim: Agent Insta (scanless detection) claims real exposure within minutes of disclosure by correlating existing telemetry. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: Qualys cites time-to-exploit collapsing from weeks to hours and positions its Risk Operations Center around that. ([source](https://www.qualys.com/post-mythos-autonomous-remediation), read 10 Nov 2026)
Vendor's claim: Qualys published a blog on zero-day remediation and operational resiliency with TruRisk Eliminate (dated 2026-08-03 in URL). ([source](https://blog.qualys.com/product-tech/2026/08/03/zero-day-remediation-operational-resiliency-trurisk-eliminate), read 10 Nov 2026)
Vendor's claim: Qualys cites Cintas patching the most severe threats automatically in under 24 hours. ([source](https://www.qualys.com/customers/success-stories/cintas-replaces-manual-patching-tasks-with-risk-based-from-qualys-enterprise-trurisk-platform), read 10 Nov 2026) | Vendor's claim: Home page lists a 0-day Fast Response agent covering triage through remediation. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page describes 0-day rapid response as finding exposure across code, images and cloud and prioritizing what to do first (page also claims a drop from days to minutes). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Published response write-up: for PHP2Shell, agents were triaging customer environments hours before scanners could detect the CVEs. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: The same write-up reports scanning more than 80,000 repositories within hours. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Agents you can shape | Vendor's claim: Qualys ships ready-made AI agents inside ETM: Agent Insta (detection), Agent Val (validation), Agent Sara (remediation), Agent Nyra (threat prioritization). ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: ROCky is a conversational AI interface in the Risk Operations Center that queries exposure data and navigates remediation workflows. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: Guardrails: confidence-gated waves, staged rollout, CAB for low-reliability patches, and automatic rollback. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: Operational Resiliency watches system health through Qualys checks or partner integrations such as Dynatrace, pausing and rolling back if something looks wrong. ([source](https://www.qualys.com/apps/trurisk-eliminate/), read 10 Nov 2026)
1 more on the [profile](/platforms/qualys/) | Vendor's claim: Rival offers ready-made agents that can be customized and extended. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival engineers build custom agents for the customer environment at no additional cost (Partner tier). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Customers can build their own agents on the harness. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page says 64+ more agents are available beyond the five featured. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
2 more on the [profile](/platforms/rival/) |
| Works on the stack you have | Vendor's claim: Qualys ETM consolidates data from on-premises, cloud, containers, identities, and applications. ([source](https://www.qualys.com/apps/enterprise-trurisk-management), read 10 Nov 2026)
Vendor's claim: Qualys platform covers VMDR, CSAM, EASM, CSPM, KCS, CWP, IaC security, CIEM, SSPM, DSPM, and software supply chain risk. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: Named integrations seen: ServiceNow (change) and Dynatrace (health checks). ([source](https://www.qualys.com/apps/trurisk-eliminate/), read 10 Nov 2026)
Vendor's claim: Single-agent architecture covering on-premises, cloud and web applications. ([source](https://www.qualys.com/about-qualys), read 10 Nov 2026) | Vendor's claim: Home page names cloud, code host and infrastructure integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page names scanner, control and task integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases table shows findings sourced from Wiz, Qualys, GitHub, a pentest, and Rival's own SCA and Code scanners. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Agents combine connected services with a Rival Security Knowledge Graph. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
| Proof | Vendor's claim: Cintas case study: replaced manual patching with Qualys VMDR, Patch Management, TruRisk and CSAM. ([source](https://www.qualys.com/customers/success-stories/cintas-replaces-manual-patching-tasks-with-risk-based-from-qualys-enterprise-trurisk-platform), read 10 Nov 2026)
Vendor's claim: Qualys states 10,000+ subscription customers in 130+ countries. ([source](https://www.qualys.com/about-qualys), read 10 Nov 2026)
Vendor's claim: Qualys states it participates in Project Glasswing with Anthropic's Claude Mythos Preview. ([source](https://www.qualys.com/about-qualys), read 10 Nov 2026)
Vendor's claim: Qualys cites a customer cutting remediation times from weeks to minutes (unnamed, no method published on the page). ([source](https://www.qualys.com/apps/trurisk-eliminate/), read 10 Nov 2026)
1 more on the [profile](/platforms/qualys/) | Vendor's claim: Use-cases page claims 13M+ agent runs. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival published SASTBench, a benchmark for SAST triage using real CVEs as true positives and filtered SAST findings as noise. ([source](https://rival.security/blog/sastbench-measuring-ai-security-automation?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Research blog post claims Rival workflows outperform current frontier models on the Spider 2.0 benchmark. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Published incident write-up (PHP2Shell, Nov 2, 2026) with unnamed customer results. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Profile facts | Vendor's claim: Qualys, Inc. is publicly traded on NASDAQ as QLYS and still operates under the Qualys name. ([source](https://www.qualys.com/about-qualys), read 10 Nov 2026)
Vendor's claim: Qualys says it is one of the first SaaS security vendors, since 1999. ([source](https://www.qualys.com/about-qualys), read 10 Nov 2026)
Vendor's claim: Qualys describes itself as a unified platform to power a risk operations center, with a majority of the Forbes Global 100 and Fortune 100 as customers. ([source](https://www.qualys.com/about-qualys), read 10 Nov 2026)
Vendor's claim: Products: Enterprise TruRisk Management (ETM), TruRisk Eliminate 2.0, Patch Management, TruConfidence engine, ROCky, Agent Insta/Val/Sara/Nyra. ([source](https://www.qualys.com/apps/trurisk-eliminate/), read 10 Nov 2026) | Vendor's claim: Tagline and category: Rival describes itself as an agent harness for cybersecurity. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Research blog launched Feb 2025 describing early experiments building AI systems for cybersecurity. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
None found on 10 Nov 2026: Pricing (rival.security/pricing returns 404; book-a-demo form only). ([source](https://rival.security/book-a-demo-form?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
None found on 10 Nov 2026: Funding, investors, founders, headcount, HQ or founding year on home, blog, careers, book-a-demo pages. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
Alphabetical by name. Each line is one fact with its label, source and read date.
## Profiles
- [Qualys profile](/platforms/qualys/): exposure
- [Rival Security profile](/platforms/rival/): agentic security platform
## Related pages
- [24 pairs, side by side](/compare/)
- [Qualys vs Tenable: the sourced facts side by side](/compare/qualys-vs-tenable/)
- [Qualys vs Rapid7: the sourced facts side by side](/compare/qualys-vs-rapid7/)
- [Rapid7 vs Rival Security: the sourced facts side by side](/compare/rapid7-vs-rival/)
## Sources
- Qualys: www.qualys.com/apps/agentic-ai: https://www.qualys.com/apps/agentic-ai (read 10 Nov 2026)
- Qualys: www.qualys.com/apps/trurisk-eliminate/: https://www.qualys.com/apps/trurisk-eliminate/ (read 10 Nov 2026)
- Qualys: www.qualys.com/post-mythos-autonomous-remediation: https://www.qualys.com/post-mythos-autonomous-remediation (read 10 Nov 2026)
- Qualys: blog.qualys.com/product-tech/2026/08/03/zero-day-remediation-operational-resilie: https://blog.qualys.com/product-tech/2026/08/03/zero-day-remediation-operational-resiliency-trurisk-eliminate (read 10 Nov 2026)
- Qualys: www.qualys.com/apps/patch-management/: https://www.qualys.com/apps/patch-management/ (read 10 Nov 2026)
- Qualys: www.qualys.com/apps/enterprise-trurisk-management: https://www.qualys.com/apps/enterprise-trurisk-management (read 10 Nov 2026)
- Qualys: www.qualys.com/customers/success-stories/cintas-replaces-manual-patching-tasks-w: https://www.qualys.com/customers/success-stories/cintas-replaces-manual-patching-tasks-with-risk-based-from-qualys-enterprise-trurisk-platform (read 10 Nov 2026)
- Qualys: www.qualys.com/about-qualys: https://www.qualys.com/about-qualys (read 10 Nov 2026)
- Rival Security: rival.security/: https://rival.security/ (read 10 Nov 2026)
- Rival Security: rival.security/use-cases: https://rival.security/use-cases (read 10 Nov 2026)
- Rival Security: rival.security/blog/php2shell-black-october-2026: https://rival.security/blog/php2shell-black-october-2026 (read 10 Nov 2026)
- Rival Security: docs.rival.security: https://docs.rival.security (read 10 Nov 2026)
- Rival Security: rival.security/blog/sastbench-measuring-ai-security-automation: https://rival.security/blog/sastbench-measuring-ai-security-automation (read 10 Nov 2026)
- Rival Security: rival.security/blog: https://rival.security/blog (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/compare/qualys-vs-rival/
---
# Qualys vs Tenable: the sourced facts side by side
Side by side, read 10 Nov 2026
**The short answer.** Qualys and Tenable are set side by side on the same rows. Fact lines: Qualys 37, Tenable 39. Third-party: 0 and 1. Fixes: Qualys, patches through patch tools and tickets; Tenable, patches through patch tools and tickets. None found: Qualys on agents; Tenable on owner. The rows below set the sourced facts side by side; the page names no pick.
## The same rows for both
| Row | Qualys | Tenable |
| --- | --- | --- |
| What it is | Exposure/RBVM platform with remediation and agentic AI | Exposure management platform with remediation and agentic orchestration |
| What it 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. | 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. |
| Where it is 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. | 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. |
| Proves exploitability in your environment | Vendor's claim: Agent Val uses TruConfirm to test whether an exposure is reachable and weaponizable by an attacker in the customer's environment. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: After mitigation, the agent re-checks exploit validation and keeps an audit trail. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: Qualys says validated exploitability narrows a large backlog to the 1% to fix now. ([source](https://www.qualys.com/apps/trurisk-eliminate/), read 10 Nov 2026)
Vendor's claim: Agent Nyra maps weaponized CVEs to impacted assets and re-orders the risk backlog by active exploitation. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
1 more on the [profile](/platforms/qualys/) | Vendor's claim: Tenable One attack path analysis shows how attackers could move across the customer's environment, with more than 150 supported attack techniques. ([source](https://www.tenable.com/products/tenable-one), read 10 Nov 2026)
Vendor's claim: Exposure prioritization claims to weigh business context and compensating control visibility, not just a generic score. ([source](https://www.tenable.com/products/tenable-one/capabilities/exposure-prioritization), read 10 Nov 2026)
Vendor's claim: Tenable uses a vendor-built Vulnerability Priority Rating (VPR) that incorporates threat intelligence and weaponization signals. ([source](https://www.tenable.com/products/vulnerability-management), read 10 Nov 2026)
Vendor's claim: Tenable says its patented machine learning models focus teams on the small share of vulnerabilities most likely to be exploited. ([source](https://www.tenable.com/products/tenable-one), read 10 Nov 2026)
1 more on the [profile](/platforms/tenable/) |
| Ships the fix | Vendor's claim: TruRisk Eliminate 2.0 Agent Sara coordinates remediation across Qualys and third-party ecosystems to patch, mitigate, uninstall, or isolate hosts. ([source](https://www.qualys.com/apps/trurisk-eliminate/), read 10 Nov 2026)
Vendor's claim: AI patch reliability scoring decides deployment approach: zero-touch for high confidence, ring-staged for medium, manual CAB for low. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: When no patch exists, it runs patchless strategies such as mitigate, uninstall, custom script, fix, and isolate. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: Automatic rollback if a deployment causes issues, and verification that the vulnerability is fixed rather than only the ticket closed. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
2 more on the [profile](/platforms/qualys/) | Vendor's claim: Tenable Hexa AI automated remediation schedules reason through vulnerabilities, create tickets, connect with patch tools, and trigger a scan when a ticket closes. ([source](https://www.tenable.com/products/tenable-one/capabilities/hexa-ai), read 10 Nov 2026)
Vendor's claim: Tenable Patch Management applies policy-based autonomous patching with the ability to schedule, pause, or roll back deployments. ([source](https://www.tenable.com/products/patch-management), read 10 Nov 2026)
Vendor's claim: Patch policies set the level of autonomy and can use different SLAs by criticality and exploitability. ([source](https://www.tenable.com/products/patch-management), read 10 Nov 2026)
Vendor's claim: Tenable Patch Management cites 250k+ patches covered and correlates each vulnerability to the most suitable superseding patch. ([source](https://www.tenable.com/products/patch-management), read 10 Nov 2026)
2 more on the [profile](/platforms/tenable/) |
| Finds the owner | Vendor's claim: Qualys Patch Management lists bidirectional integrations with CMDB and ITSM tools. ([source](https://www.qualys.com/apps/patch-management/), read 10 Nov 2026)
Vendor's claim: ETM positions remediation workflows with automated patching, IT tickets, and real-time alerts; no per-finding owner resolution (code owner or team mapping) was found. ([source](https://www.qualys.com/apps/enterprise-trurisk-management), read 10 Nov 2026)
Vendor's claim: Cloud Workflow Automation is described as automating remediation workflows using asset criticality and blast radius. ([source](https://www.qualys.com/apps/enterprise-trurisk-management), read 10 Nov 2026) | Vendor's claim: Tenable One integrates exposure alerts with manual or automated ticketing workflows to improve accountability among IT, cloud, and security teams. ([source](https://www.tenable.com/products/tenable-one/pricing), read 10 Nov 2026)
Vendor's claim: Tenable Patch Management gives a separate console so each team can see remediation progress and compliance status. ([source](https://www.tenable.com/products/patch-management), read 10 Nov 2026)
None found on 10 Nov 2026: No documented feature that resolves each finding to a named owning team (for example from CODEOWNERS or cloud tags) was found; the owner-related claim is ticketing integration only. ([source](https://www.tenable.com/about-tenable/about-us), read 10 Nov 2026) |
| Speed on a new disclosure | Vendor's claim: Agent Insta (scanless detection) claims real exposure within minutes of disclosure by correlating existing telemetry. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: Qualys cites time-to-exploit collapsing from weeks to hours and positions its Risk Operations Center around that. ([source](https://www.qualys.com/post-mythos-autonomous-remediation), read 10 Nov 2026)
Vendor's claim: Qualys published a blog on zero-day remediation and operational resiliency with TruRisk Eliminate (dated 2026-08-03 in URL). ([source](https://blog.qualys.com/product-tech/2026/08/03/zero-day-remediation-operational-resiliency-trurisk-eliminate), read 10 Nov 2026)
Vendor's claim: Qualys cites Cintas patching the most severe threats automatically in under 24 hours. ([source](https://www.qualys.com/customers/success-stories/cintas-replaces-manual-patching-tasks-with-risk-based-from-qualys-enterprise-trurisk-platform), read 10 Nov 2026) | Third-party source: Tenable publishes a CVE page of newly disclosed vulnerabilities with exploitation status and patch guidance, for example OpenSSH exploitation attempts within hours of disclosure. ([source](https://www.tenable.com/cve), read 10 Nov 2026)
Vendor's claim: Tenable Hexa AI can run scheduled agent fleets for daily vulnerability triage without human delay. ([source](https://www.tenable.com/products/tenable-one/capabilities/hexa-ai), read 10 Nov 2026)
Vendor's claim: Tenable ties its agentic push to shrinking time between disclosure and exploit; no measured time-to-answer for a new CVE was found. ([source](https://www.tenable.com/press-releases/tenable-partners-with-anthropic-for-ai-driven-exposure-management), read 10 Nov 2026) |
| Agents you can shape | Vendor's claim: Qualys ships ready-made AI agents inside ETM: Agent Insta (detection), Agent Val (validation), Agent Sara (remediation), Agent Nyra (threat prioritization). ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: ROCky is a conversational AI interface in the Risk Operations Center that queries exposure data and navigates remediation workflows. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: Guardrails: confidence-gated waves, staged rollout, CAB for low-reliability patches, and automatic rollback. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: Operational Resiliency watches system health through Qualys checks or partner integrations such as Dynatrace, pausing and rolling back if something looks wrong. ([source](https://www.qualys.com/apps/trurisk-eliminate/), read 10 Nov 2026)
1 more on the [profile](/platforms/qualys/) | Vendor's claim: Tenable Hexa AI is the agentic engine of Tenable One and orchestrates a fleet of specialized AI agents. ([source](https://www.tenable.com/products/tenable-one/capabilities/hexa-ai), read 10 Nov 2026)
Vendor's claim: Tenable One offers built-in, third-party, and customer-built agents. ([source](https://www.tenable.com/products/tenable-one), read 10 Nov 2026)
Vendor's claim: Hexa AI MCP server lets customers bring their own LLMs and build custom workflows over Tenable tools. ([source](https://www.tenable.com/products/tenable-one/capabilities/hexa-ai), read 10 Nov 2026)
Vendor's claim: Guardrails: Hexa AI operates within established guardrails, human-in-the-loop design, and logs every action for audit. ([source](https://www.tenable.com/products/tenable-one/capabilities/hexa-ai), read 10 Nov 2026)
2 more on the [profile](/platforms/tenable/) |
| Works on the stack you have | Vendor's claim: Qualys ETM consolidates data from on-premises, cloud, containers, identities, and applications. ([source](https://www.qualys.com/apps/enterprise-trurisk-management), read 10 Nov 2026)
Vendor's claim: Qualys platform covers VMDR, CSAM, EASM, CSPM, KCS, CWP, IaC security, CIEM, SSPM, DSPM, and software supply chain risk. ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
Vendor's claim: Named integrations seen: ServiceNow (change) and Dynatrace (health checks). ([source](https://www.qualys.com/apps/trurisk-eliminate/), read 10 Nov 2026)
Vendor's claim: Single-agent architecture covering on-premises, cloud and web applications. ([source](https://www.qualys.com/about-qualys), read 10 Nov 2026) | Vendor's claim: Tenable One connectors consolidate third-party data including CrowdStrike, Qualys, Rapid7, Wiz, Armis, and Cortex XDR. ([source](https://www.tenable.com/products/tenable-one/connectors), read 10 Nov 2026)
Vendor's claim: Tenable One ingests Rapid7 asset and vulnerability data through a connector. ([source](https://www.tenable.com/products/tenable-one/connectors), read 10 Nov 2026)
Vendor's claim: Tenable One coverage spans IT, OT/IoT, cloud, AI assets, containers, web apps, code repositories, and identity systems. ([source](https://www.tenable.com/products/tenable-one), read 10 Nov 2026)
Vendor's claim: An Open Connector ingests data from additional tools, internal systems, spreadsheets, or files. ([source](https://www.tenable.com/products/tenable-one/connectors), read 10 Nov 2026) |
| Proof | Vendor's claim: Cintas case study: replaced manual patching with Qualys VMDR, Patch Management, TruRisk and CSAM. ([source](https://www.qualys.com/customers/success-stories/cintas-replaces-manual-patching-tasks-with-risk-based-from-qualys-enterprise-trurisk-platform), read 10 Nov 2026)
Vendor's claim: Qualys states 10,000+ subscription customers in 130+ countries. ([source](https://www.qualys.com/about-qualys), read 10 Nov 2026)
Vendor's claim: Qualys states it participates in Project Glasswing with Anthropic's Claude Mythos Preview. ([source](https://www.qualys.com/about-qualys), read 10 Nov 2026)
Vendor's claim: Qualys cites a customer cutting remediation times from weeks to minutes (unnamed, no method published on the page). ([source](https://www.qualys.com/apps/trurisk-eliminate/), read 10 Nov 2026)
1 more on the [profile](/platforms/qualys/) | Vendor's claim: Tenable cites more than 40,000 customers. ([source](https://www.tenable.com/about-tenable/about-us), read 10 Nov 2026)
Vendor's claim: Bernalillo County case study: freed 75% of its cybersecurity team from manual patching. ([source](https://www.tenable.com/customers), read 10 Nov 2026)
Vendor's claim: Tenable's customers page lists Volpara Health Technologies, Virginia Tech, Chubu Electric Power Grid, and Public Utility District No. 1 of Whatcom County among others. ([source](https://www.tenable.com/customers), read 10 Nov 2026)
Vendor's claim: Tenable cites a Gainwell Technologies CISO testimonial on Tenable One. ([source](https://www.tenable.com/products/tenable-one), read 10 Nov 2026)
1 more on the [profile](/platforms/tenable/) |
| Profile facts | Vendor's claim: Qualys, Inc. is publicly traded on NASDAQ as QLYS and still operates under the Qualys name. ([source](https://www.qualys.com/about-qualys), read 10 Nov 2026)
Vendor's claim: Qualys says it is one of the first SaaS security vendors, since 1999. ([source](https://www.qualys.com/about-qualys), read 10 Nov 2026)
Vendor's claim: Qualys describes itself as a unified platform to power a risk operations center, with a majority of the Forbes Global 100 and Fortune 100 as customers. ([source](https://www.qualys.com/about-qualys), read 10 Nov 2026)
Vendor's claim: Products: Enterprise TruRisk Management (ETM), TruRisk Eliminate 2.0, Patch Management, TruConfidence engine, ROCky, Agent Insta/Val/Sara/Nyra. ([source](https://www.qualys.com/apps/trurisk-eliminate/), read 10 Nov 2026) | Vendor's claim: Tenable Holdings, Inc. is publicly traded on NASDAQ as TENB. ([source](https://www.tenable.com/press-releases/tenable-partners-with-anthropic-for-ai-driven-exposure-management), read 10 Nov 2026)
Vendor's claim: Tenable calls itself the exposure management company; flagship product is Tenable One, with Hexa AI as its agentic engine. ([source](https://www.tenable.com/press-releases/tenable-partners-with-anthropic-for-ai-driven-exposure-management), read 10 Nov 2026)
Vendor's claim: Tenable has co-CEOs Steve Vintz and Mark Thurmond. ([source](https://www.tenable.com/about-tenable/about-us), read 10 Nov 2026)
Vendor's claim: Product line includes Tenable One, Vulnerability Management, Security Center, Patch Management, Enclave Security, Cloud Exposure, Identity Exposure, and Attack Surface Management. ([source](https://www.tenable.com/customers), read 10 Nov 2026) |
Alphabetical by name. Each line is one fact with its label, source and read date.
## Profiles
- [Qualys profile](/platforms/qualys/): exposure
- [Tenable profile](/platforms/tenable/): exposure management platform with
## Related pages
- [24 pairs, side by side](/compare/)
- [Rapid7 vs Rival Security: the sourced facts side by side](/compare/rapid7-vs-rival/)
- [Qualys vs Rival Security: the sourced facts side by side](/compare/qualys-vs-rival/)
- [Rapid7 vs Tenable: the sourced facts side by side](/compare/rapid7-vs-tenable/)
## Sources
- Qualys: www.qualys.com/apps/agentic-ai: https://www.qualys.com/apps/agentic-ai (read 10 Nov 2026)
- Qualys: www.qualys.com/apps/trurisk-eliminate/: https://www.qualys.com/apps/trurisk-eliminate/ (read 10 Nov 2026)
- Qualys: www.qualys.com/post-mythos-autonomous-remediation: https://www.qualys.com/post-mythos-autonomous-remediation (read 10 Nov 2026)
- Qualys: blog.qualys.com/product-tech/2026/08/03/zero-day-remediation-operational-resilie: https://blog.qualys.com/product-tech/2026/08/03/zero-day-remediation-operational-resiliency-trurisk-eliminate (read 10 Nov 2026)
- Qualys: www.qualys.com/apps/patch-management/: https://www.qualys.com/apps/patch-management/ (read 10 Nov 2026)
- Qualys: www.qualys.com/apps/enterprise-trurisk-management: https://www.qualys.com/apps/enterprise-trurisk-management (read 10 Nov 2026)
- Qualys: www.qualys.com/customers/success-stories/cintas-replaces-manual-patching-tasks-w: https://www.qualys.com/customers/success-stories/cintas-replaces-manual-patching-tasks-with-risk-based-from-qualys-enterprise-trurisk-platform (read 10 Nov 2026)
- Qualys: www.qualys.com/about-qualys: https://www.qualys.com/about-qualys (read 10 Nov 2026)
- Tenable: www.tenable.com/products/tenable-one: https://www.tenable.com/products/tenable-one (read 10 Nov 2026)
- Tenable: www.tenable.com/products/tenable-one/capabilities/exposure-prioritization: https://www.tenable.com/products/tenable-one/capabilities/exposure-prioritization (read 10 Nov 2026)
- Tenable: www.tenable.com/products/vulnerability-management: https://www.tenable.com/products/vulnerability-management (read 10 Nov 2026)
- Tenable: www.tenable.com/products/tenable-one/capabilities/hexa-ai: https://www.tenable.com/products/tenable-one/capabilities/hexa-ai (read 10 Nov 2026)
- Tenable: www.tenable.com/products/patch-management: https://www.tenable.com/products/patch-management (read 10 Nov 2026)
- Tenable: www.tenable.com/data-sheets/tenable-hexa-ai-the-agentic-engine-for-tenable-one-e: https://www.tenable.com/data-sheets/tenable-hexa-ai-the-agentic-engine-for-tenable-one-exposure-management (read 10 Nov 2026)
- Tenable: www.tenable.com/products/tenable-one/pricing: https://www.tenable.com/products/tenable-one/pricing (read 10 Nov 2026)
- Tenable: www.tenable.com/about-tenable/about-us: https://www.tenable.com/about-tenable/about-us (read 10 Nov 2026)
- Tenable: www.tenable.com/cve: https://www.tenable.com/cve (read 10 Nov 2026)
- Tenable: www.tenable.com/press-releases/tenable-partners-with-anthropic-for-ai-driven-exp: https://www.tenable.com/press-releases/tenable-partners-with-anthropic-for-ai-driven-exposure-management (read 10 Nov 2026)
- Tenable: www.tenable.com/cyberagents-exchange: https://www.tenable.com/cyberagents-exchange (read 10 Nov 2026)
- Tenable: www.tenable.com/products/tenable-one/connectors: https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026)
- Tenable: www.tenable.com/customers: https://www.tenable.com/customers (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/compare/qualys-vs-tenable/
---
# Rapid7 vs Rival Security: the sourced facts side by side
Side by side, read 10 Nov 2026
**The short answer.** Rapid7 and Rival Security. Rapid7 has 31 fact lines (0 third-party) and Rival Security has 40 (0 third-party). Fix form on file: Rapid7, automated workflows and pull requests; Rival Security, pull requests and mitigations. Rapid7 has a none-found line on owner; Rival Security on proof. The rows below set the sourced facts side by side; the page names no pick.
## The same rows for both
| Row | Rapid7 | Rival Security |
| --- | --- | --- |
| What it is | Exposure/RBVM platform with remediation workflows | Agentic security platform / agent harness for vulnerability management, code and cloud security |
| What it 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. | 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. |
| Where it is 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'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. |
| Proves exploitability in your environment | Vendor's claim: Exposure Command prioritizes using exploit likelihood, reachability, severity, and business context. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Exposure Command tier adds attack path analysis and contextual risk prioritization. ([source](https://www.rapid7.com/products/command/pricing/), read 10 Nov 2026)
Vendor's claim: Exposure Command provides a risk score based on toxic combinations plus internal and external views. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Rapid7 describes a threat-aware active risk score in the Essentials tier. ([source](https://www.rapid7.com/products/command/pricing/), read 10 Nov 2026)
1 more on the [profile](/platforms/rapid7/) | Vendor's claim: Home page lists a Triage Exploitability agent that determines what is actually exploitable in the customer environment. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page says Rival reads every scanner finding against the real environment and keeps only those that can cause harm; it cites a 94.6% reduction in findings. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page reports 98% of findings proven unexploitable, 87% faster remediation and 1.5 hours to first value (no method given on the page). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: In its PHP2Shell write-up, Rival says agents ordered services to fix by reachability, internet-exposed unauthenticated workloads first. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Ships the fix | Vendor's claim: Exposure Command offers no-code native automation for automated remediation. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Exposure Command lists automated remediation workflows and automated cloud remediation as tier features. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Rapid7 says built-in remediation workflows give AI-powered remediation guidance, automation, and team workflows; the page does not say a tested PR or virtual patch is produced. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Rapid7's own analysis says reducing exposure still requires teams to choose the remediation or compensating control and verify the result. ([source](https://www.rapid7.com/blog/post/ai-gartner-report-attack-paths-closing-faster-than-patchable/), read 10 Nov 2026) | Vendor's claim: Home page lists an Autonomous Remediation agent that generates and ships tested fixes. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page describes the remediation flow as plan, test, and open a pull request for human review. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival lists a WAF mitigation agent that checks whether a WAF blocks exploitation and adjusts it. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival describes an alternative-remediation agent for legacy apps that plans a fix without upgrading libraries. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
2 more on the [profile](/platforms/rival/) |
| Finds the owner | Vendor's claim: Essentials tier includes remediation projects and SLAs. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Automated notification and ticketing gives developers real-time feedback. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
None found on 10 Nov 2026: Per-finding resolution to an owning team (for example from code owners or cloud tags): none found on 2026-11-10 on the Exposure Command page read. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026) | Vendor's claim: Home page lists an Ownership Resolution agent that maps each finding to the team that can fix it. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page says the owner-finding agent weighs root cause, team structure and past history (memories). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: PHP2Shell write-up says agents can message the relevant employees, and the harness lists human follow-ups. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
| Speed on a new disclosure | Vendor's claim: For Ivanti Connect Secure zero-days, Rapid7 stated authenticated vulnerability checks were available since the 2026-10-30 content release (the day CISA added them to KEV). ([source](https://www.rapid7.com/blog/post/etr-additional-ivanti-connect-secure-zero-days-exploited-in-the-wild-cve-2026-111357-cve-2026-118527/), read 10 Nov 2026)
Vendor's claim: Rapid7 runs an Emergent Threat Response blog stream for high-priority threats. ([source](https://www.rapid7.com/blog/tag/emergent-threat-response/), read 10 Nov 2026)
Vendor's claim: Rapid7 Q3 2026 threat update says three days is the average time from high-severity vulnerability disclosure to exploitation. ([source](https://www.rapid7.com/blog/post/tr-q3-2026-threat-update-attackers-exploiting-vulnerabilities-within-3-days/), read 10 Nov 2026) | Vendor's claim: Home page lists a 0-day Fast Response agent covering triage through remediation. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page describes 0-day rapid response as finding exposure across code, images and cloud and prioritizing what to do first (page also claims a drop from days to minutes). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Published response write-up: for PHP2Shell, agents were triaging customer environments hours before scanners could detect the CVEs. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: The same write-up reports scanning more than 80,000 repositories within hours. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Agents you can shape | Vendor's claim: Rapid7 references AI-powered remediation guidance in Exposure Command and human-centric AI in its SOC offering; no controls model for agents was documented. ([source](https://www.rapid7.com/solutions/ai-powered-security-operations-soc/), read 10 Nov 2026)
Vendor's claim: Rapid7 reports internal practitioner exploration of Claude Mythos Preview through Project Glasswing. ([source](https://www.rapid7.com/blog/post/ai-gartner-report-attack-paths-closing-faster-than-patchable/), read 10 Nov 2026)
None found on 10 Nov 2026: Agentic remediation features, Remediation Hub, or ready-made or customer-built AI agents for exposure management: none found on 2026-11-10 on the Exposure Command, InsightVM, pricing, or AI-SOC pages read (the word agentic did not appear). ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026) | Vendor's claim: Rival offers ready-made agents that can be customized and extended. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival engineers build custom agents for the customer environment at no additional cost (Partner tier). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Customers can build their own agents on the harness. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page says 64+ more agents are available beyond the five featured. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
2 more on the [profile](/platforms/rival/) |
| Works on the stack you have | Vendor's claim: Exposure Command lists 500+ integrations across cloud, identity, ITSM, ticketing, EDR, and CI/CD. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Cloud coverage includes AWS, Azure, GCP, and Kubernetes, plus Oracle Cloud and Alibaba Cloud in the extended tier. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Exposure Command adds infrastructure-as-code scanning and DAST. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Exposure Command correlates third-party findings with Rapid7 vulnerability telemetry. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026) | Vendor's claim: Home page names cloud, code host and infrastructure integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page names scanner, control and task integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases table shows findings sourced from Wiz, Qualys, GitHub, a pentest, and Rival's own SCA and Code scanners. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Agents combine connected services with a Rival Security Knowledge Graph. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
| Proof | Vendor's claim: Rapid7 states more than 11,500 customers. ([source](https://www.rapid7.com/about/), read 10 Nov 2026)
Vendor's claim: Rapid7 was placed in the upper-right quadrant of the 2025 Gartner Magic Quadrant (vendor's claim) for Exposure Assessment Platforms. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Americor customer story: Rapid7 universal agent gave up-to-date vulnerability understanding. ([source](https://www.rapid7.com/customers/americor/), read 10 Nov 2026)
Vendor's claim: Rapid7 publishes a quarterly threat landscape report and Metasploit wrap-ups as research output. ([source](https://www.rapid7.com/blog/), read 10 Nov 2026) | Vendor's claim: Use-cases page claims 13M+ agent runs. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival published SASTBench, a benchmark for SAST triage using real CVEs as true positives and filtered SAST findings as noise. ([source](https://rival.security/blog/sastbench-measuring-ai-security-automation?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Research blog post claims Rival workflows outperform current frontier models on the Spider 2.0 benchmark. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Published incident write-up (PHP2Shell, Nov 2, 2026) with unnamed customer results. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) |
| Profile facts | Vendor's claim: Rapid7 is an exposure and detection company with Exposure Command (including an Essentials tier) and Surface Command on its Command Platform. ([source](https://www.rapid7.com/products/command/pricing/), read 10 Nov 2026)
Vendor's claim: Pricing: no list prices on the pricing page read; it describes usage-based pricing by asset type. ([source](https://www.rapid7.com/products/command/pricing/), read 10 Nov 2026)
Vendor's claim: InsightVM is folded into the Exposure Command packaging, with a page asking whether InsightVM is still available. ([source](https://www.rapid7.com/products/insightvm/), read 10 Nov 2026)
Vendor's claim: Rapid7 was recognized by the Boston Business Journal as one of the Boston Business Journal's listed Places to Work for the 14th consecutive year (headquarters not stated on the page). ([source](https://www.rapid7.com/about/news/), read 10 Nov 2026) | Vendor's claim: Tagline and category: Rival describes itself as an agent harness for cybersecurity. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Research blog launched Feb 2025 describing early experiments building AI systems for cybersecurity. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
None found on 10 Nov 2026: Pricing (rival.security/pricing returns 404; book-a-demo form only). ([source](https://rival.security/book-a-demo-form?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
None found on 10 Nov 2026: Funding, investors, founders, headcount, HQ or founding year on home, blog, careers, book-a-demo pages. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) |
Alphabetical by name. Each line is one fact with its label, source and read date.
## Profiles
- [Rapid7 profile](/platforms/rapid7/): exposure
- [Rival Security profile](/platforms/rival/): agentic security platform
## Related pages
- [24 pairs, side by side](/compare/)
- [Rapid7 vs Tenable: the sourced facts side by side](/compare/rapid7-vs-tenable/)
- [Qualys vs Tenable: the sourced facts side by side](/compare/qualys-vs-tenable/)
- [Rival Security vs Seemplicity: the sourced facts side by side](/compare/rival-vs-seemplicity/)
## Sources
- Rapid7: www.rapid7.com/products/command/exposure-management/: https://www.rapid7.com/products/command/exposure-management/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/products/command/pricing/: https://www.rapid7.com/products/command/pricing/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/blog/post/ai-gartner-report-attack-paths-closing-faster-than-patc: https://www.rapid7.com/blog/post/ai-gartner-report-attack-paths-closing-faster-than-patchable/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/blog/post/etr-additional-ivanti-connect-secure-zero-days-exploite: https://www.rapid7.com/blog/post/etr-additional-ivanti-connect-secure-zero-days-exploited-in-the-wild-cve-2026-111357-cve-2026-118527/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/blog/tag/emergent-threat-response/: https://www.rapid7.com/blog/tag/emergent-threat-response/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/blog/post/tr-q3-2026-threat-update-attackers-exploiting-vulnerabi: https://www.rapid7.com/blog/post/tr-q3-2026-threat-update-attackers-exploiting-vulnerabilities-within-3-days/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/solutions/ai-powered-security-operations-soc/: https://www.rapid7.com/solutions/ai-powered-security-operations-soc/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/about/: https://www.rapid7.com/about/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/customers/americor/: https://www.rapid7.com/customers/americor/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/blog/: https://www.rapid7.com/blog/ (read 10 Nov 2026)
- Rival Security: rival.security/: https://rival.security/ (read 10 Nov 2026)
- Rival Security: rival.security/use-cases: https://rival.security/use-cases (read 10 Nov 2026)
- Rival Security: rival.security/blog/php2shell-black-october-2026: https://rival.security/blog/php2shell-black-october-2026 (read 10 Nov 2026)
- Rival Security: docs.rival.security: https://docs.rival.security (read 10 Nov 2026)
- Rival Security: rival.security/blog/sastbench-measuring-ai-security-automation: https://rival.security/blog/sastbench-measuring-ai-security-automation (read 10 Nov 2026)
- Rival Security: rival.security/blog: https://rival.security/blog (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/compare/rapid7-vs-rival/
---
# Rapid7 vs Tenable: the sourced facts side by side
Side by side, read 10 Nov 2026
**The short answer.** Rapid7 and Tenable, on the same rows. Rapid7 has 31 fact lines (0 third-party) and Tenable has 39 (1 third-party). Fix form on file: Rapid7, automated workflows and pull requests; Tenable, patches through patch tools and tickets. None found: Rapid7 on owner; Tenable on owner. The rows below set the sourced facts side by side; the page names no pick.
## The same rows for both
| Row | Rapid7 | Tenable |
| --- | --- | --- |
| What it is | Exposure/RBVM platform with remediation workflows | Exposure management platform with remediation and agentic orchestration |
| What it 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. | 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. |
| Where it is 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. | 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. |
| Proves exploitability in your environment | Vendor's claim: Exposure Command prioritizes using exploit likelihood, reachability, severity, and business context. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Exposure Command tier adds attack path analysis and contextual risk prioritization. ([source](https://www.rapid7.com/products/command/pricing/), read 10 Nov 2026)
Vendor's claim: Exposure Command provides a risk score based on toxic combinations plus internal and external views. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Rapid7 describes a threat-aware active risk score in the Essentials tier. ([source](https://www.rapid7.com/products/command/pricing/), read 10 Nov 2026)
1 more on the [profile](/platforms/rapid7/) | Vendor's claim: Tenable One attack path analysis shows how attackers could move across the customer's environment, with more than 150 supported attack techniques. ([source](https://www.tenable.com/products/tenable-one), read 10 Nov 2026)
Vendor's claim: Exposure prioritization claims to weigh business context and compensating control visibility, not just a generic score. ([source](https://www.tenable.com/products/tenable-one/capabilities/exposure-prioritization), read 10 Nov 2026)
Vendor's claim: Tenable uses a vendor-built Vulnerability Priority Rating (VPR) that incorporates threat intelligence and weaponization signals. ([source](https://www.tenable.com/products/vulnerability-management), read 10 Nov 2026)
Vendor's claim: Tenable says its patented machine learning models focus teams on the small share of vulnerabilities most likely to be exploited. ([source](https://www.tenable.com/products/tenable-one), read 10 Nov 2026)
1 more on the [profile](/platforms/tenable/) |
| Ships the fix | Vendor's claim: Exposure Command offers no-code native automation for automated remediation. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Exposure Command lists automated remediation workflows and automated cloud remediation as tier features. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Rapid7 says built-in remediation workflows give AI-powered remediation guidance, automation, and team workflows; the page does not say a tested PR or virtual patch is produced. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Rapid7's own analysis says reducing exposure still requires teams to choose the remediation or compensating control and verify the result. ([source](https://www.rapid7.com/blog/post/ai-gartner-report-attack-paths-closing-faster-than-patchable/), read 10 Nov 2026) | Vendor's claim: Tenable Hexa AI automated remediation schedules reason through vulnerabilities, create tickets, connect with patch tools, and trigger a scan when a ticket closes. ([source](https://www.tenable.com/products/tenable-one/capabilities/hexa-ai), read 10 Nov 2026)
Vendor's claim: Tenable Patch Management applies policy-based autonomous patching with the ability to schedule, pause, or roll back deployments. ([source](https://www.tenable.com/products/patch-management), read 10 Nov 2026)
Vendor's claim: Patch policies set the level of autonomy and can use different SLAs by criticality and exploitability. ([source](https://www.tenable.com/products/patch-management), read 10 Nov 2026)
Vendor's claim: Tenable Patch Management cites 250k+ patches covered and correlates each vulnerability to the most suitable superseding patch. ([source](https://www.tenable.com/products/patch-management), read 10 Nov 2026)
2 more on the [profile](/platforms/tenable/) |
| Finds the owner | Vendor's claim: Essentials tier includes remediation projects and SLAs. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Automated notification and ticketing gives developers real-time feedback. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
None found on 10 Nov 2026: Per-finding resolution to an owning team (for example from code owners or cloud tags): none found on 2026-11-10 on the Exposure Command page read. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026) | Vendor's claim: Tenable One integrates exposure alerts with manual or automated ticketing workflows to improve accountability among IT, cloud, and security teams. ([source](https://www.tenable.com/products/tenable-one/pricing), read 10 Nov 2026)
Vendor's claim: Tenable Patch Management gives a separate console so each team can see remediation progress and compliance status. ([source](https://www.tenable.com/products/patch-management), read 10 Nov 2026)
None found on 10 Nov 2026: No documented feature that resolves each finding to a named owning team (for example from CODEOWNERS or cloud tags) was found; the owner-related claim is ticketing integration only. ([source](https://www.tenable.com/about-tenable/about-us), read 10 Nov 2026) |
| Speed on a new disclosure | Vendor's claim: For Ivanti Connect Secure zero-days, Rapid7 stated authenticated vulnerability checks were available since the 2026-10-30 content release (the day CISA added them to KEV). ([source](https://www.rapid7.com/blog/post/etr-additional-ivanti-connect-secure-zero-days-exploited-in-the-wild-cve-2026-111357-cve-2026-118527/), read 10 Nov 2026)
Vendor's claim: Rapid7 runs an Emergent Threat Response blog stream for high-priority threats. ([source](https://www.rapid7.com/blog/tag/emergent-threat-response/), read 10 Nov 2026)
Vendor's claim: Rapid7 Q3 2026 threat update says three days is the average time from high-severity vulnerability disclosure to exploitation. ([source](https://www.rapid7.com/blog/post/tr-q3-2026-threat-update-attackers-exploiting-vulnerabilities-within-3-days/), read 10 Nov 2026) | Third-party source: Tenable publishes a CVE page of newly disclosed vulnerabilities with exploitation status and patch guidance, for example OpenSSH exploitation attempts within hours of disclosure. ([source](https://www.tenable.com/cve), read 10 Nov 2026)
Vendor's claim: Tenable Hexa AI can run scheduled agent fleets for daily vulnerability triage without human delay. ([source](https://www.tenable.com/products/tenable-one/capabilities/hexa-ai), read 10 Nov 2026)
Vendor's claim: Tenable ties its agentic push to shrinking time between disclosure and exploit; no measured time-to-answer for a new CVE was found. ([source](https://www.tenable.com/press-releases/tenable-partners-with-anthropic-for-ai-driven-exposure-management), read 10 Nov 2026) |
| Agents you can shape | Vendor's claim: Rapid7 references AI-powered remediation guidance in Exposure Command and human-centric AI in its SOC offering; no controls model for agents was documented. ([source](https://www.rapid7.com/solutions/ai-powered-security-operations-soc/), read 10 Nov 2026)
Vendor's claim: Rapid7 reports internal practitioner exploration of Claude Mythos Preview through Project Glasswing. ([source](https://www.rapid7.com/blog/post/ai-gartner-report-attack-paths-closing-faster-than-patchable/), read 10 Nov 2026)
None found on 10 Nov 2026: Agentic remediation features, Remediation Hub, or ready-made or customer-built AI agents for exposure management: none found on 2026-11-10 on the Exposure Command, InsightVM, pricing, or AI-SOC pages read (the word agentic did not appear). ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026) | Vendor's claim: Tenable Hexa AI is the agentic engine of Tenable One and orchestrates a fleet of specialized AI agents. ([source](https://www.tenable.com/products/tenable-one/capabilities/hexa-ai), read 10 Nov 2026)
Vendor's claim: Tenable One offers built-in, third-party, and customer-built agents. ([source](https://www.tenable.com/products/tenable-one), read 10 Nov 2026)
Vendor's claim: Hexa AI MCP server lets customers bring their own LLMs and build custom workflows over Tenable tools. ([source](https://www.tenable.com/products/tenable-one/capabilities/hexa-ai), read 10 Nov 2026)
Vendor's claim: Guardrails: Hexa AI operates within established guardrails, human-in-the-loop design, and logs every action for audit. ([source](https://www.tenable.com/products/tenable-one/capabilities/hexa-ai), read 10 Nov 2026)
2 more on the [profile](/platforms/tenable/) |
| Works on the stack you have | Vendor's claim: Exposure Command lists 500+ integrations across cloud, identity, ITSM, ticketing, EDR, and CI/CD. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Cloud coverage includes AWS, Azure, GCP, and Kubernetes, plus Oracle Cloud and Alibaba Cloud in the extended tier. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Exposure Command adds infrastructure-as-code scanning and DAST. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Exposure Command correlates third-party findings with Rapid7 vulnerability telemetry. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026) | Vendor's claim: Tenable One connectors consolidate third-party data including CrowdStrike, Qualys, Rapid7, Wiz, Armis, and Cortex XDR. ([source](https://www.tenable.com/products/tenable-one/connectors), read 10 Nov 2026)
Vendor's claim: Tenable One ingests Rapid7 asset and vulnerability data through a connector. ([source](https://www.tenable.com/products/tenable-one/connectors), read 10 Nov 2026)
Vendor's claim: Tenable One coverage spans IT, OT/IoT, cloud, AI assets, containers, web apps, code repositories, and identity systems. ([source](https://www.tenable.com/products/tenable-one), read 10 Nov 2026)
Vendor's claim: An Open Connector ingests data from additional tools, internal systems, spreadsheets, or files. ([source](https://www.tenable.com/products/tenable-one/connectors), read 10 Nov 2026) |
| Proof | Vendor's claim: Rapid7 states more than 11,500 customers. ([source](https://www.rapid7.com/about/), read 10 Nov 2026)
Vendor's claim: Rapid7 was placed in the upper-right quadrant of the 2025 Gartner Magic Quadrant (vendor's claim) for Exposure Assessment Platforms. ([source](https://www.rapid7.com/products/command/exposure-management/), read 10 Nov 2026)
Vendor's claim: Americor customer story: Rapid7 universal agent gave up-to-date vulnerability understanding. ([source](https://www.rapid7.com/customers/americor/), read 10 Nov 2026)
Vendor's claim: Rapid7 publishes a quarterly threat landscape report and Metasploit wrap-ups as research output. ([source](https://www.rapid7.com/blog/), read 10 Nov 2026) | Vendor's claim: Tenable cites more than 40,000 customers. ([source](https://www.tenable.com/about-tenable/about-us), read 10 Nov 2026)
Vendor's claim: Bernalillo County case study: freed 75% of its cybersecurity team from manual patching. ([source](https://www.tenable.com/customers), read 10 Nov 2026)
Vendor's claim: Tenable's customers page lists Volpara Health Technologies, Virginia Tech, Chubu Electric Power Grid, and Public Utility District No. 1 of Whatcom County among others. ([source](https://www.tenable.com/customers), read 10 Nov 2026)
Vendor's claim: Tenable cites a Gainwell Technologies CISO testimonial on Tenable One. ([source](https://www.tenable.com/products/tenable-one), read 10 Nov 2026)
1 more on the [profile](/platforms/tenable/) |
| Profile facts | Vendor's claim: Rapid7 is an exposure and detection company with Exposure Command (including an Essentials tier) and Surface Command on its Command Platform. ([source](https://www.rapid7.com/products/command/pricing/), read 10 Nov 2026)
Vendor's claim: Pricing: no list prices on the pricing page read; it describes usage-based pricing by asset type. ([source](https://www.rapid7.com/products/command/pricing/), read 10 Nov 2026)
Vendor's claim: InsightVM is folded into the Exposure Command packaging, with a page asking whether InsightVM is still available. ([source](https://www.rapid7.com/products/insightvm/), read 10 Nov 2026)
Vendor's claim: Rapid7 was recognized by the Boston Business Journal as one of the Boston Business Journal's listed Places to Work for the 14th consecutive year (headquarters not stated on the page). ([source](https://www.rapid7.com/about/news/), read 10 Nov 2026) | Vendor's claim: Tenable Holdings, Inc. is publicly traded on NASDAQ as TENB. ([source](https://www.tenable.com/press-releases/tenable-partners-with-anthropic-for-ai-driven-exposure-management), read 10 Nov 2026)
Vendor's claim: Tenable calls itself the exposure management company; flagship product is Tenable One, with Hexa AI as its agentic engine. ([source](https://www.tenable.com/press-releases/tenable-partners-with-anthropic-for-ai-driven-exposure-management), read 10 Nov 2026)
Vendor's claim: Tenable has co-CEOs Steve Vintz and Mark Thurmond. ([source](https://www.tenable.com/about-tenable/about-us), read 10 Nov 2026)
Vendor's claim: Product line includes Tenable One, Vulnerability Management, Security Center, Patch Management, Enclave Security, Cloud Exposure, Identity Exposure, and Attack Surface Management. ([source](https://www.tenable.com/customers), read 10 Nov 2026) |
Alphabetical by name. Each line is one fact with its label, source and read date.
## Profiles
- [Rapid7 profile](/platforms/rapid7/): exposure
- [Tenable profile](/platforms/tenable/): exposure management platform with
## Related pages
- [24 pairs, side by side](/compare/)
- [Rival Security vs Seemplicity: the sourced facts side by side](/compare/rival-vs-seemplicity/)
- [Rapid7 vs Rival Security: the sourced facts side by side](/compare/rapid7-vs-rival/)
- [Rival Security vs Tenable: the sourced facts side by side](/compare/rival-vs-tenable/)
## Sources
- Rapid7: www.rapid7.com/products/command/exposure-management/: https://www.rapid7.com/products/command/exposure-management/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/products/command/pricing/: https://www.rapid7.com/products/command/pricing/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/blog/post/ai-gartner-report-attack-paths-closing-faster-than-patc: https://www.rapid7.com/blog/post/ai-gartner-report-attack-paths-closing-faster-than-patchable/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/blog/post/etr-additional-ivanti-connect-secure-zero-days-exploite: https://www.rapid7.com/blog/post/etr-additional-ivanti-connect-secure-zero-days-exploited-in-the-wild-cve-2026-111357-cve-2026-118527/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/blog/tag/emergent-threat-response/: https://www.rapid7.com/blog/tag/emergent-threat-response/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/blog/post/tr-q3-2026-threat-update-attackers-exploiting-vulnerabi: https://www.rapid7.com/blog/post/tr-q3-2026-threat-update-attackers-exploiting-vulnerabilities-within-3-days/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/solutions/ai-powered-security-operations-soc/: https://www.rapid7.com/solutions/ai-powered-security-operations-soc/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/about/: https://www.rapid7.com/about/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/customers/americor/: https://www.rapid7.com/customers/americor/ (read 10 Nov 2026)
- Rapid7: www.rapid7.com/blog/: https://www.rapid7.com/blog/ (read 10 Nov 2026)
- Tenable: www.tenable.com/products/tenable-one: https://www.tenable.com/products/tenable-one (read 10 Nov 2026)
- Tenable: www.tenable.com/products/tenable-one/capabilities/exposure-prioritization: https://www.tenable.com/products/tenable-one/capabilities/exposure-prioritization (read 10 Nov 2026)
- Tenable: www.tenable.com/products/vulnerability-management: https://www.tenable.com/products/vulnerability-management (read 10 Nov 2026)
- Tenable: www.tenable.com/products/tenable-one/capabilities/hexa-ai: https://www.tenable.com/products/tenable-one/capabilities/hexa-ai (read 10 Nov 2026)
- Tenable: www.tenable.com/products/patch-management: https://www.tenable.com/products/patch-management (read 10 Nov 2026)
- Tenable: www.tenable.com/data-sheets/tenable-hexa-ai-the-agentic-engine-for-tenable-one-e: https://www.tenable.com/data-sheets/tenable-hexa-ai-the-agentic-engine-for-tenable-one-exposure-management (read 10 Nov 2026)
- Tenable: www.tenable.com/products/tenable-one/pricing: https://www.tenable.com/products/tenable-one/pricing (read 10 Nov 2026)
- Tenable: www.tenable.com/about-tenable/about-us: https://www.tenable.com/about-tenable/about-us (read 10 Nov 2026)
- Tenable: www.tenable.com/cve: https://www.tenable.com/cve (read 10 Nov 2026)
- Tenable: www.tenable.com/press-releases/tenable-partners-with-anthropic-for-ai-driven-exp: https://www.tenable.com/press-releases/tenable-partners-with-anthropic-for-ai-driven-exposure-management (read 10 Nov 2026)
- Tenable: www.tenable.com/cyberagents-exchange: https://www.tenable.com/cyberagents-exchange (read 10 Nov 2026)
- Tenable: www.tenable.com/products/tenable-one/connectors: https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026)
- Tenable: www.tenable.com/customers: https://www.tenable.com/customers (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/compare/rapid7-vs-tenable/
---
# Rival Security vs Seemplicity: the sourced facts side by side
Side by side, read 10 Nov 2026
**The short answer.** Rival Security and Seemplicity, on the same rows. Fact lines: Rival Security 40, Seemplicity 41. Third-party: 0 and 0. Fixes: Rival Security, pull requests and mitigations; Seemplicity, automated workflows and patches through patch tools. Rival Security has a none-found line on proof; Seemplicity on speed. The rows below set the sourced facts side by side; the page names no pick.
## The same rows for both
| Row | Rival Security | Seemplicity |
| --- | --- | --- |
| What it is | Agentic security platform / agent harness for vulnerability management, code and cloud security | Agentic exposure management and response (RBVM/CTEM workflow with AI analysts) |
| What it 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. | 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. |
| Where it is 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 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. |
| Proves exploitability in your environment | Vendor's claim: Home page lists a Triage Exploitability agent that determines what is actually exploitable in the customer environment. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page says Rival reads every scanner finding against the real environment and keeps only those that can cause harm; it cites a 94.6% reduction in findings. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page reports 98% of findings proven unexploitable, 87% faster remediation and 1.5 hours to first value (no method given on the page). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: In its PHP2Shell write-up, Rival says agents ordered services to fix by reachability, internet-exposed unauthenticated workloads first. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) | Vendor's claim: AI Analysts run structured exploitability investigations inside the remediation workflow. ([source](https://seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/), read 10 Nov 2026)
Vendor's claim: Inputs: live runtime configuration, exploit prerequisites, network reachability, code and dependency usage, compensating controls. ([source](https://seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/), read 10 Nov 2026)
Vendor's claim: Live EDR telemetry from CrowdStrike and Microsoft Defender evaluates protections per asset (Jun 3, 2026). ([source](https://seemplicity.ai/news/live-edr-context-agentic-exposure-management/), read 10 Nov 2026)
Vendor's claim: Preliminary deployments: majority of high-severity findings judged not exploitable (no counts given). ([source](https://seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/), read 10 Nov 2026)
1 more on the [profile](/platforms/seemplicity/) |
| Ships the fix | Vendor's claim: Home page lists an Autonomous Remediation agent that generates and ships tested fixes. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page describes the remediation flow as plan, test, and open a pull request for human review. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival lists a WAF mitigation agent that checks whether a WAF blocks exploitation and adjusts it. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival describes an alternative-remediation agent for legacy apps that plans a fix without upgrading libraries. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
2 more on the [profile](/platforms/rival/) | Vendor's claim: Response Options (Sep 2, 2026) give alternatives to a full patch: compensating controls and targeted configuration changes. ([source](https://seemplicity.ai/news/response-options/), read 10 Nov 2026)
Vendor's claim: Each option carries a Readiness Indicator (deploy now or review first); AI Analysts pre-select a recommendation and all alternatives stay visible. ([source](https://seemplicity.ai/news/response-options/), read 10 Nov 2026)
Vendor's claim: Code Analyst reads source from GitHub, GitLab and other repositories and hands developers a scoped, ready-to-apply fix. ([source](https://seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/), read 10 Nov 2026)
Vendor's claim: Remediation agents provide step-by-step guidance and ownership mapping; delivery is into existing workflows (guidance and tickets). ([source](https://seemplicity.ai/platform/agentic-workforce/), read 10 Nov 2026)
1 more on the [profile](/platforms/seemplicity/) |
| Finds the owner | Vendor's claim: Home page lists an Ownership Resolution agent that maps each finding to the team that can fix it. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page says the owner-finding agent weighs root cause, team structure and past history (memories). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: PHP2Shell write-up says agents can message the relevant employees, and the harness lists human follow-ups. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) | Vendor's claim: Automatically assigns remediation to owners and delivers fix-ready guidance into existing workflows. ([source](https://seemplicity.ai/), read 10 Nov 2026)
Vendor's claim: Hertz: unknown asset ownership fell from 20% to 2% in six months. ([source](https://seemplicity.ai/resource/hertz-case-study/), read 10 Nov 2026)
Vendor's claim: Owners and criticality identified by syncing with CMDBs. ([source](https://seemplicity.ai/automated-vulnerability-remediation/), read 10 Nov 2026)
Vendor's claim: Host Analyst surfaces the likely owner. ([source](https://seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/), read 10 Nov 2026)
1 more on the [profile](/platforms/seemplicity/) |
| Speed on a new disclosure | Vendor's claim: Home page lists a 0-day Fast Response agent covering triage through remediation. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page describes 0-day rapid response as finding exposure across code, images and cloud and prioritizing what to do first (page also claims a drop from days to minutes). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Published response write-up: for PHP2Shell, agents were triaging customer environments hours before scanners could detect the CVEs. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: The same write-up reports scanning more than 80,000 repositories within hours. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) | Vendor's claim: SCA Analyst powers SBOM-driven zero-day response before scanner signatures exist. ([source](https://seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/), read 10 Nov 2026)
Vendor's claim: Home page claims discovery to remediation in seconds (no method). ([source](https://seemplicity.ai/), read 10 Nov 2026)
Vendor's claim: MTTR reduction claim of 90% on the remediation workflow page. ([source](https://seemplicity.ai/automated-vulnerability-remediation/), read 10 Nov 2026)
None found on 10 Nov 2026: A published time-to-answer measurement for a specific new CVE disclosure on seemplicity.ai pages read ([source](https://seemplicity.ai/news/), read 10 Nov 2026) |
| Agents you can shape | Vendor's claim: Rival offers ready-made agents that can be customized and extended. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival engineers build custom agents for the customer environment at no additional cost (Partner tier). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Customers can build their own agents on the harness. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page says 64+ more agents are available beyond the five featured. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
2 more on the [profile](/platforms/rival/) | Vendor's claim: Ready-made autonomous SAST, SCA and Host Analysts work around the clock. ([source](https://seemplicity.ai/platform/agentic-workforce/), read 10 Nov 2026)
Vendor's claim: Four agent families: validation, context, strategy, remediation. ([source](https://seemplicity.ai/platform/agentic-workforce/), read 10 Nov 2026)
Vendor's claim: Seema conversational assistant for exposure questions. ([source](https://seemplicity.ai/), read 10 Nov 2026)
Vendor's claim: Controls: transparent reasoning trails, visible alternatives, and customer-built approval gates in workflows. ([source](https://seemplicity.ai/customers/), read 10 Nov 2026)
2 more on the [profile](/platforms/seemplicity/) |
| Works on the stack you have | Vendor's claim: Home page names cloud, code host and infrastructure integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page names scanner, control and task integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases table shows findings sourced from Wiz, Qualys, GitHub, a pentest, and Rival's own SCA and Code scanners. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Agents combine connected services with a Rival Security Knowledge Graph. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) | Vendor's claim: Integration page claims hundreds of integrations. ([source](https://seemplicity.ai/integrations/), read 10 Nov 2026)
Vendor's claim: Scanners and CNAPP named: Qualys, Rapid7, Tenable products, Wiz, Orca, Prisma Cloud. ([source](https://seemplicity.ai/integrations/), read 10 Nov 2026)
Vendor's claim: Ticketing and dev tooling named in the integrations list include Azure DevOps (also GitHub, GitLab, Jira per the same list). ([source](https://seemplicity.ai/integrations/), read 10 Nov 2026)
Vendor's claim: ServiceNow CMDB is a named integration (list also includes ServiceNow, Slack, Teams, Snyk, SentinelOne Singularity). ([source](https://seemplicity.ai/integrations/), read 10 Nov 2026) |
| Proof | Vendor's claim: Use-cases page claims 13M+ agent runs. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival published SASTBench, a benchmark for SAST triage using real CVEs as true positives and filtered SAST findings as noise. ([source](https://rival.security/blog/sastbench-measuring-ai-security-automation?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Research blog post claims Rival workflows outperform current frontier models on the Spider 2.0 benchmark. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Published incident write-up (PHP2Shell, Nov 2, 2026) with unnamed customer results. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) | Vendor's claim: Hertz case study: critical remediation up 400%. ([source](https://seemplicity.ai/resource/hertz-case-study/), read 10 Nov 2026)
Vendor's claim: Named customer quotes: Omnissa, OpenWeb, X-Press Feeders; OpenWeb reports 85% fewer tickets. ([source](https://seemplicity.ai/customers/), read 10 Nov 2026)
Vendor's claim: Average claims: 57% scanner noise reduction and $1.7M annual savings (aggregate, method not on page). ([source](https://seemplicity.ai/), read 10 Nov 2026)
Vendor's claim: Research: 2026 Exposure Action Report on 2025 customer data; April 2026 survey report (88% use AI, 31% trust it). ([source](https://seemplicity.ai/), read 10 Nov 2026)
1 more on the [profile](/platforms/seemplicity/) |
| Profile facts | Vendor's claim: Tagline and category: Rival describes itself as an agent harness for cybersecurity. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Research blog launched Feb 2025 describing early experiments building AI systems for cybersecurity. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
None found on 10 Nov 2026: Pricing (rival.security/pricing returns 404; book-a-demo form only). ([source](https://rival.security/book-a-demo-form?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
None found on 10 Nov 2026: Funding, investors, founders, headcount, HQ or founding year on home, blog, careers, book-a-demo pages. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) | Vendor's claim: Founded 2020 by Yoran Sirkis, Ravid Circus, Rotem Cohen Gadol. ([source](https://seemplicity.ai/about/), read 10 Nov 2026)
Vendor's claim: Funding: $26M Series A and $50M Series B led by Sienna Venture Capital; more than $63M raised per the CEO bio. ([source](https://seemplicity.ai/about/), read 10 Nov 2026)
Vendor's claim: Series A $26M backed by Glilot Capital, NTTVC, Atlantic Bridge, S Capital, Rain Capital. ([source](https://seemplicity.ai/about/), read 10 Nov 2026)
Vendor's claim: HQ address San Jose, CA, with Tel Aviv office. ([source](https://seemplicity.ai/platform/agentic-workforce/), read 10 Nov 2026) |
Alphabetical by name. Each line is one fact with its label, source and read date.
## Profiles
- [Rival Security profile](/platforms/rival/): agentic security platform
- [Seemplicity profile](/platforms/seemplicity/): agentic exposure management and
## Related pages
- [24 pairs, side by side](/compare/)
- [Rival Security vs Tenable: the sourced facts side by side](/compare/rival-vs-tenable/)
- [Rapid7 vs Tenable: the sourced facts side by side](/compare/rapid7-vs-tenable/)
- [Rival Security vs Vicarius: the sourced facts side by side](/compare/rival-vs-vicarius/)
## Sources
- Rival Security: rival.security/: https://rival.security/ (read 10 Nov 2026)
- Rival Security: rival.security/use-cases: https://rival.security/use-cases (read 10 Nov 2026)
- Rival Security: rival.security/blog/php2shell-black-october-2026: https://rival.security/blog/php2shell-black-october-2026 (read 10 Nov 2026)
- Rival Security: docs.rival.security: https://docs.rival.security (read 10 Nov 2026)
- Rival Security: rival.security/blog/sastbench-measuring-ai-security-automation: https://rival.security/blog/sastbench-measuring-ai-security-automation (read 10 Nov 2026)
- Rival Security: rival.security/blog: https://rival.security/blog (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/: https://seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/news/live-edr-context-agentic-exposure-management/: https://seemplicity.ai/news/live-edr-context-agentic-exposure-management/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/platform/agentic-workforce/: https://seemplicity.ai/platform/agentic-workforce/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/news/response-options/: https://seemplicity.ai/news/response-options/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/automated-vulnerability-remediation/: https://seemplicity.ai/automated-vulnerability-remediation/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/: https://seemplicity.ai/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/resource/hertz-case-study/: https://seemplicity.ai/resource/hertz-case-study/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/news/: https://seemplicity.ai/news/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/customers/: https://seemplicity.ai/customers/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/integrations/: https://seemplicity.ai/integrations/ (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/compare/rival-vs-seemplicity/
---
# Rival Security vs Tenable: the sourced facts side by side
Side by side, read 10 Nov 2026
**The short answer.** Rival Security and Tenable are set side by side on the same rows. Fact lines: Rival Security 40, Tenable 39. Third-party: 0 and 1. Fixes: Rival Security, pull requests; Tenable, patches through patch tools. Rival Security has a none-found line on proof; Tenable on owner. The rows below set the sourced facts side by side; the page names no pick.
## The same rows for both
| Row | Rival Security | Tenable |
| --- | --- | --- |
| What it is | Agentic security platform / agent harness for vulnerability management, code and cloud security | Exposure management platform with remediation and agentic orchestration |
| What it 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. | 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. |
| Where it is 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. | 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. |
| Proves exploitability in your environment | Vendor's claim: Home page lists a Triage Exploitability agent that determines what is actually exploitable in the customer environment. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page says Rival reads every scanner finding against the real environment and keeps only those that can cause harm; it cites a 94.6% reduction in findings. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page reports 98% of findings proven unexploitable, 87% faster remediation and 1.5 hours to first value (no method given on the page). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: In its PHP2Shell write-up, Rival says agents ordered services to fix by reachability, internet-exposed unauthenticated workloads first. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) | Vendor's claim: Tenable One attack path analysis shows how attackers could move across the customer's environment, with more than 150 supported attack techniques. ([source](https://www.tenable.com/products/tenable-one), read 10 Nov 2026)
Vendor's claim: Exposure prioritization claims to weigh business context and compensating control visibility, not just a generic score. ([source](https://www.tenable.com/products/tenable-one/capabilities/exposure-prioritization), read 10 Nov 2026)
Vendor's claim: Tenable uses a vendor-built Vulnerability Priority Rating (VPR) that incorporates threat intelligence and weaponization signals. ([source](https://www.tenable.com/products/vulnerability-management), read 10 Nov 2026)
Vendor's claim: Tenable says its patented machine learning models focus teams on the small share of vulnerabilities most likely to be exploited. ([source](https://www.tenable.com/products/tenable-one), read 10 Nov 2026)
1 more on the [profile](/platforms/tenable/) |
| Ships the fix | Vendor's claim: Home page lists an Autonomous Remediation agent that generates and ships tested fixes. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page describes the remediation flow as plan, test, and open a pull request for human review. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival lists a WAF mitigation agent that checks whether a WAF blocks exploitation and adjusts it. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival describes an alternative-remediation agent for legacy apps that plans a fix without upgrading libraries. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
2 more on the [profile](/platforms/rival/) | Vendor's claim: Tenable Hexa AI automated remediation schedules reason through vulnerabilities, create tickets, connect with patch tools, and trigger a scan when a ticket closes. ([source](https://www.tenable.com/products/tenable-one/capabilities/hexa-ai), read 10 Nov 2026)
Vendor's claim: Tenable Patch Management applies policy-based autonomous patching with the ability to schedule, pause, or roll back deployments. ([source](https://www.tenable.com/products/patch-management), read 10 Nov 2026)
Vendor's claim: Patch policies set the level of autonomy and can use different SLAs by criticality and exploitability. ([source](https://www.tenable.com/products/patch-management), read 10 Nov 2026)
Vendor's claim: Tenable Patch Management cites 250k+ patches covered and correlates each vulnerability to the most suitable superseding patch. ([source](https://www.tenable.com/products/patch-management), read 10 Nov 2026)
2 more on the [profile](/platforms/tenable/) |
| Finds the owner | Vendor's claim: Home page lists an Ownership Resolution agent that maps each finding to the team that can fix it. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page says the owner-finding agent weighs root cause, team structure and past history (memories). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: PHP2Shell write-up says agents can message the relevant employees, and the harness lists human follow-ups. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) | Vendor's claim: Tenable One integrates exposure alerts with manual or automated ticketing workflows to improve accountability among IT, cloud, and security teams. ([source](https://www.tenable.com/products/tenable-one/pricing), read 10 Nov 2026)
Vendor's claim: Tenable Patch Management gives a separate console so each team can see remediation progress and compliance status. ([source](https://www.tenable.com/products/patch-management), read 10 Nov 2026)
None found on 10 Nov 2026: No documented feature that resolves each finding to a named owning team (for example from CODEOWNERS or cloud tags) was found; the owner-related claim is ticketing integration only. ([source](https://www.tenable.com/about-tenable/about-us), read 10 Nov 2026) |
| Speed on a new disclosure | Vendor's claim: Home page lists a 0-day Fast Response agent covering triage through remediation. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page describes 0-day rapid response as finding exposure across code, images and cloud and prioritizing what to do first (page also claims a drop from days to minutes). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Published response write-up: for PHP2Shell, agents were triaging customer environments hours before scanners could detect the CVEs. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: The same write-up reports scanning more than 80,000 repositories within hours. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) | Third-party source: Tenable publishes a CVE page of newly disclosed vulnerabilities with exploitation status and patch guidance, for example OpenSSH exploitation attempts within hours of disclosure. ([source](https://www.tenable.com/cve), read 10 Nov 2026)
Vendor's claim: Tenable Hexa AI can run scheduled agent fleets for daily vulnerability triage without human delay. ([source](https://www.tenable.com/products/tenable-one/capabilities/hexa-ai), read 10 Nov 2026)
Vendor's claim: Tenable ties its agentic push to shrinking time between disclosure and exploit; no measured time-to-answer for a new CVE was found. ([source](https://www.tenable.com/press-releases/tenable-partners-with-anthropic-for-ai-driven-exposure-management), read 10 Nov 2026) |
| Agents you can shape | Vendor's claim: Rival offers ready-made agents that can be customized and extended. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival engineers build custom agents for the customer environment at no additional cost (Partner tier). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Customers can build their own agents on the harness. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page says 64+ more agents are available beyond the five featured. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
2 more on the [profile](/platforms/rival/) | Vendor's claim: Tenable Hexa AI is the agentic engine of Tenable One and orchestrates a fleet of specialized AI agents. ([source](https://www.tenable.com/products/tenable-one/capabilities/hexa-ai), read 10 Nov 2026)
Vendor's claim: Tenable One offers built-in, third-party, and customer-built agents. ([source](https://www.tenable.com/products/tenable-one), read 10 Nov 2026)
Vendor's claim: Hexa AI MCP server lets customers bring their own LLMs and build custom workflows over Tenable tools. ([source](https://www.tenable.com/products/tenable-one/capabilities/hexa-ai), read 10 Nov 2026)
Vendor's claim: Guardrails: Hexa AI operates within established guardrails, human-in-the-loop design, and logs every action for audit. ([source](https://www.tenable.com/products/tenable-one/capabilities/hexa-ai), read 10 Nov 2026)
2 more on the [profile](/platforms/tenable/) |
| Works on the stack you have | Vendor's claim: Home page names cloud, code host and infrastructure integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page names scanner, control and task integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases table shows findings sourced from Wiz, Qualys, GitHub, a pentest, and Rival's own SCA and Code scanners. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Agents combine connected services with a Rival Security Knowledge Graph. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) | Vendor's claim: Tenable One connectors consolidate third-party data including CrowdStrike, Qualys, Rapid7, Wiz, Armis, and Cortex XDR. ([source](https://www.tenable.com/products/tenable-one/connectors), read 10 Nov 2026)
Vendor's claim: Tenable One ingests Rapid7 asset and vulnerability data through a connector. ([source](https://www.tenable.com/products/tenable-one/connectors), read 10 Nov 2026)
Vendor's claim: Tenable One coverage spans IT, OT/IoT, cloud, AI assets, containers, web apps, code repositories, and identity systems. ([source](https://www.tenable.com/products/tenable-one), read 10 Nov 2026)
Vendor's claim: An Open Connector ingests data from additional tools, internal systems, spreadsheets, or files. ([source](https://www.tenable.com/products/tenable-one/connectors), read 10 Nov 2026) |
| Proof | Vendor's claim: Use-cases page claims 13M+ agent runs. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival published SASTBench, a benchmark for SAST triage using real CVEs as true positives and filtered SAST findings as noise. ([source](https://rival.security/blog/sastbench-measuring-ai-security-automation?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Research blog post claims Rival workflows outperform current frontier models on the Spider 2.0 benchmark. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Published incident write-up (PHP2Shell, Nov 2, 2026) with unnamed customer results. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) | Vendor's claim: Tenable cites more than 40,000 customers. ([source](https://www.tenable.com/about-tenable/about-us), read 10 Nov 2026)
Vendor's claim: Bernalillo County case study: freed 75% of its cybersecurity team from manual patching. ([source](https://www.tenable.com/customers), read 10 Nov 2026)
Vendor's claim: Tenable's customers page lists Volpara Health Technologies, Virginia Tech, Chubu Electric Power Grid, and Public Utility District No. 1 of Whatcom County among others. ([source](https://www.tenable.com/customers), read 10 Nov 2026)
Vendor's claim: Tenable cites a Gainwell Technologies CISO testimonial on Tenable One. ([source](https://www.tenable.com/products/tenable-one), read 10 Nov 2026)
1 more on the [profile](/platforms/tenable/) |
| Profile facts | Vendor's claim: Tagline and category: Rival describes itself as an agent harness for cybersecurity. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Research blog launched Feb 2025 describing early experiments building AI systems for cybersecurity. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
None found on 10 Nov 2026: Pricing (rival.security/pricing returns 404; book-a-demo form only). ([source](https://rival.security/book-a-demo-form?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
None found on 10 Nov 2026: Funding, investors, founders, headcount, HQ or founding year on home, blog, careers, book-a-demo pages. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) | Vendor's claim: Tenable Holdings, Inc. is publicly traded on NASDAQ as TENB. ([source](https://www.tenable.com/press-releases/tenable-partners-with-anthropic-for-ai-driven-exposure-management), read 10 Nov 2026)
Vendor's claim: Tenable calls itself the exposure management company; flagship product is Tenable One, with Hexa AI as its agentic engine. ([source](https://www.tenable.com/press-releases/tenable-partners-with-anthropic-for-ai-driven-exposure-management), read 10 Nov 2026)
Vendor's claim: Tenable has co-CEOs Steve Vintz and Mark Thurmond. ([source](https://www.tenable.com/about-tenable/about-us), read 10 Nov 2026)
Vendor's claim: Product line includes Tenable One, Vulnerability Management, Security Center, Patch Management, Enclave Security, Cloud Exposure, Identity Exposure, and Attack Surface Management. ([source](https://www.tenable.com/customers), read 10 Nov 2026) |
Alphabetical by name. Each line is one fact with its label, source and read date.
## Profiles
- [Rival Security profile](/platforms/rival/): agentic security platform
- [Tenable profile](/platforms/tenable/): exposure management platform with
## Related pages
- [24 pairs, side by side](/compare/)
- [Rival Security vs Vicarius: the sourced facts side by side](/compare/rival-vs-vicarius/)
- [Rival Security vs Seemplicity: the sourced facts side by side](/compare/rival-vs-seemplicity/)
- [Rival Security vs Zafran: the sourced facts side by side](/compare/rival-vs-zafran/)
## Sources
- Rival Security: rival.security/: https://rival.security/ (read 10 Nov 2026)
- Rival Security: rival.security/use-cases: https://rival.security/use-cases (read 10 Nov 2026)
- Rival Security: rival.security/blog/php2shell-black-october-2026: https://rival.security/blog/php2shell-black-october-2026 (read 10 Nov 2026)
- Rival Security: docs.rival.security: https://docs.rival.security (read 10 Nov 2026)
- Rival Security: rival.security/blog/sastbench-measuring-ai-security-automation: https://rival.security/blog/sastbench-measuring-ai-security-automation (read 10 Nov 2026)
- Rival Security: rival.security/blog: https://rival.security/blog (read 10 Nov 2026)
- Tenable: www.tenable.com/products/tenable-one: https://www.tenable.com/products/tenable-one (read 10 Nov 2026)
- Tenable: www.tenable.com/products/tenable-one/capabilities/exposure-prioritization: https://www.tenable.com/products/tenable-one/capabilities/exposure-prioritization (read 10 Nov 2026)
- Tenable: www.tenable.com/products/vulnerability-management: https://www.tenable.com/products/vulnerability-management (read 10 Nov 2026)
- Tenable: www.tenable.com/products/tenable-one/capabilities/hexa-ai: https://www.tenable.com/products/tenable-one/capabilities/hexa-ai (read 10 Nov 2026)
- Tenable: www.tenable.com/products/patch-management: https://www.tenable.com/products/patch-management (read 10 Nov 2026)
- Tenable: www.tenable.com/data-sheets/tenable-hexa-ai-the-agentic-engine-for-tenable-one-e: https://www.tenable.com/data-sheets/tenable-hexa-ai-the-agentic-engine-for-tenable-one-exposure-management (read 10 Nov 2026)
- Tenable: www.tenable.com/products/tenable-one/pricing: https://www.tenable.com/products/tenable-one/pricing (read 10 Nov 2026)
- Tenable: www.tenable.com/about-tenable/about-us: https://www.tenable.com/about-tenable/about-us (read 10 Nov 2026)
- Tenable: www.tenable.com/cve: https://www.tenable.com/cve (read 10 Nov 2026)
- Tenable: www.tenable.com/press-releases/tenable-partners-with-anthropic-for-ai-driven-exp: https://www.tenable.com/press-releases/tenable-partners-with-anthropic-for-ai-driven-exposure-management (read 10 Nov 2026)
- Tenable: www.tenable.com/cyberagents-exchange: https://www.tenable.com/cyberagents-exchange (read 10 Nov 2026)
- Tenable: www.tenable.com/products/tenable-one/connectors: https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026)
- Tenable: www.tenable.com/customers: https://www.tenable.com/customers (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/compare/rival-vs-tenable/
---
# Rival Security vs Vicarius: the sourced facts side by side
Side by side, read 10 Nov 2026
**The short answer.** Rival Security and Vicarius are set side by side on the same rows. Fact lines: Rival Security 40, Vicarius 38. Third-party: 0 and 0. Fixes: Rival Security, pull requests; Vicarius, patches through patch tools. Rival Security has a none-found line on proof; Vicarius on owner. The rows below set the sourced facts side by side; the page names no pick.
## The same rows for both
| Row | Rival Security | Vicarius |
| --- | --- | --- |
| What it is | Agentic security platform / agent harness for vulnerability management, code and cloud security | Remediation-first exposure platform (patching, scripting, patchless protection) |
| What it 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. | 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. |
| Where it is 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. | 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. |
| Proves exploitability in your environment | Vendor's claim: Home page lists a Triage Exploitability agent that determines what is actually exploitable in the customer environment. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page says Rival reads every scanner finding against the real environment and keeps only those that can cause harm; it cites a 94.6% reduction in findings. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page reports 98% of findings proven unexploitable, 87% faster remediation and 1.5 hours to first value (no method given on the page). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: In its PHP2Shell write-up, Rival says agents ordered services to fix by reachability, internet-exposed unauthenticated workloads first. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) | Vendor's claim: VScore adds exploit simulation, asset criticality and business context in addition to CVSS, EPSS and KEV. ([source](https://www.vicarius.io/features/vrx-analysis), read 10 Nov 2026)
Vendor's claim: Vendor says vScore confirms every queued item is exploitable. ([source](https://www.vicarius.io/features/vrx-analysis), read 10 Nov 2026)
Vendor's claim: Agentic AI validation of which vulnerabilities attackers can exploit. ([source](https://www.vicarius.io/), read 10 Nov 2026)
Vendor's claim: Claims 95% of false positives removed by agentic exposure validation (no method shown). ([source](https://www.vicarius.io/features/vrx-analysis), read 10 Nov 2026)
1 more on the [profile](/platforms/vicarius/) |
| Ships the fix | Vendor's claim: Home page lists an Autonomous Remediation agent that generates and ships tested fixes. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page describes the remediation flow as plan, test, and open a pull request for human review. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival lists a WAF mitigation agent that checks whether a WAF blocks exploitation and adjusts it. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival describes an alternative-remediation agent for legacy apps that plans a fix without upgrading libraries. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
2 more on the [profile](/platforms/rival/) | Vendor's claim: Core pitch: finds vulnerabilities and fixes them via patch management, scripting and patchless protection. ([source](https://www.vicarius.io/), read 10 Nov 2026)
Vendor's claim: Patching on demand, scheduled or by rule across Windows, macOS, Linux and 20,000+ third-party apps. ([source](https://www.vicarius.io/features/patch-management), read 10 Nov 2026)
Vendor's claim: VShield blocks exploit paths in memory without touching the application or a reboot (virtual patch style mitigation). ([source](https://www.vicarius.io/features/patchless-protection), read 10 Nov 2026)
Vendor's claim: Remediation is executed and then verified; for patching vRx compares detected version with the target version. ([source](https://www.vicarius.io/solution/vulnerability-remediation), read 10 Nov 2026)
1 more on the [profile](/platforms/vicarius/) |
| Finds the owner | Vendor's claim: Home page lists an Ownership Resolution agent that maps each finding to the team that can fix it. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page says the owner-finding agent weighs root cause, team structure and past history (memories). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: PHP2Shell write-up says agents can message the relevant employees, and the harness lists human follow-ups. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) | Vendor's claim: Orchestration and automation to coordinate remediation across teams and tools (feature named in navigation; little detail on owner resolution). ([source](https://www.vicarius.io/), read 10 Nov 2026)
None found on 10 Nov 2026: Automatic mapping of findings to the owning team or CMDB/ticketing owner resolution on vicarius.io pages read ([source](https://www.vicarius.io/), read 10 Nov 2026) |
| Speed on a new disclosure | Vendor's claim: Home page lists a 0-day Fast Response agent covering triage through remediation. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page describes 0-day rapid response as finding exposure across code, images and cloud and prioritizing what to do first (page also claims a drop from days to minutes). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Published response write-up: for PHP2Shell, agents were triaging customer environments hours before scanners could detect the CVEs. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: The same write-up reports scanning more than 80,000 repositories within hours. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) | Vendor's claim: VShield protects at disclosure before a vendor patch exists. ([source](https://www.vicarius.io/features/patchless-protection), read 10 Nov 2026)
Vendor's claim: ScriptAI watches for exploited-in-the-wild threats before an official identifier exists and generates detection scripts. ([source](https://www.vicarius.io/features/scriptai), read 10 Nov 2026)
Vendor's claim: Detection scripts run immediately to show which assets are affected while remediation is validated. ([source](https://www.vicarius.io/features/scriptai), read 10 Nov 2026)
Vendor's claim: Average time to rescan stated as 15 seconds. ([source](https://www.vicarius.io/about-us), read 10 Nov 2026)
1 more on the [profile](/platforms/vicarius/) |
| Agents you can shape | Vendor's claim: Rival offers ready-made agents that can be customized and extended. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival engineers build custom agents for the customer environment at no additional cost (Partner tier). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Customers can build their own agents on the harness. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page says 64+ more agents are available beyond the five featured. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
2 more on the [profile](/platforms/rival/) | Vendor's claim: ScriptAI and AI grouping are labeled agentic AI features (new): LLM-written remediation scripts and AI-powered dynamic groups. ([source](https://www.vicarius.io/), read 10 Nov 2026)
Vendor's claim: VIntelligence AI search assistant answers plain-English questions on live data with threat intelligence. ([source](https://www.vicarius.io/features/ai-search-assistant), read 10 Nov 2026)
Vendor's claim: Script library of 1000+ community and AI-generated scripts; custom scripts supported. ([source](https://www.vicarius.io/features/scriptai), read 10 Nov 2026)
Vendor's claim: Newsroom lists an October 2026 release "Vicarius revamps AI platform to unify cybersecurity workflows" (vRx 2.0 launch the same month). ([source](https://www.vicarius.io/vicarius-resources-newsroom), read 10 Nov 2026) |
| Works on the stack you have | Vendor's claim: Home page names cloud, code host and infrastructure integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page names scanner, control and task integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases table shows findings sourced from Wiz, Qualys, GitHub, a pentest, and Rival's own SCA and Code scanners. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Agents combine connected services with a Rival Security Knowledge Graph. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) | Vendor's claim: Feeds from EDR, SIEM, CSPM and scanners into one ordered list. ([source](https://www.vicarius.io/features/vrx-analysis), read 10 Nov 2026)
Vendor's claim: Endpoint coverage: Windows, macOS, Linux and 20,000+ third-party apps; agent and agentless detection. ([source](https://www.vicarius.io/), read 10 Nov 2026)
None found on 10 Nov 2026: A named list of scanner, cloud, code host or ticketing integrations on the vicarius.io pages read ([source](https://www.vicarius.io/), read 10 Nov 2026) |
| Proof | Vendor's claim: Use-cases page claims 13M+ agent runs. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival published SASTBench, a benchmark for SAST triage using real CVEs as true positives and filtered SAST findings as noise. ([source](https://rival.security/blog/sastbench-measuring-ai-security-automation?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Research blog post claims Rival workflows outperform current frontier models on the Spider 2.0 benchmark. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Published incident write-up (PHP2Shell, Nov 2, 2026) with unnamed customer results. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) | Vendor's claim: Customer count claims differ by page: 1,000+ deployments (home) versus over 500 customers in 50 countries (about). ([source](https://www.vicarius.io/), read 10 Nov 2026)
Vendor's claim: Case study: Jamaica Broilers Group remediates 70% faster (vendor-published). ([source](https://www.vicarius.io/case-studies/jamaica-broilers-group), read 10 Nov 2026)
Vendor's claim: Customer outcome: Charter School Associates saved 100+ hours on patch management. ([source](https://www.vicarius.io/), read 10 Nov 2026)
Vendor's claim: Recognized in the Gartner 2025 Magic Quadrant for Exposure Assessment Platforms (per vendor). ([source](https://www.vicarius.io/), read 10 Nov 2026)
2 more on the [profile](/platforms/vicarius/) |
| Profile facts | Vendor's claim: Tagline and category: Rival describes itself as an agent harness for cybersecurity. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Research blog launched Feb 2025 describing early experiments building AI systems for cybersecurity. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
None found on 10 Nov 2026: Pricing (rival.security/pricing returns 404; book-a-demo form only). ([source](https://rival.security/book-a-demo-form?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
None found on 10 Nov 2026: Funding, investors, founders, headcount, HQ or founding year on home, blog, careers, book-a-demo pages. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) | Vendor's claim: Founded 2016. ([source](https://www.vicarius.io/about-us), read 10 Nov 2026)
Vendor's claim: Funding: $24M Series A (2022) and $30M Series B (2023). ([source](https://www.vicarius.io/about-us), read 10 Nov 2026)
Vendor's claim: Series A amount. ([source](https://www.vicarius.io/about-us), read 10 Nov 2026)
Vendor's claim: HQ New York; offices in Israel, Australia, Brazil, Chile, Germany, India, Singapore, UK. ([source](https://www.vicarius.io/about-us), read 10 Nov 2026) |
Alphabetical by name. Each line is one fact with its label, source and read date.
## Profiles
- [Rival Security profile](/platforms/rival/): agentic security platform
- [Vicarius profile](/platforms/vicarius/): remediation-first exposure
## Related pages
- [24 pairs, side by side](/compare/)
- [Rival Security vs Zafran: the sourced facts side by side](/compare/rival-vs-zafran/)
- [Rival Security vs Tenable: the sourced facts side by side](/compare/rival-vs-tenable/)
- [Seemplicity vs Zafran: the sourced facts side by side](/compare/seemplicity-vs-zafran/)
## Sources
- Rival Security: rival.security/: https://rival.security/ (read 10 Nov 2026)
- Rival Security: rival.security/use-cases: https://rival.security/use-cases (read 10 Nov 2026)
- Rival Security: rival.security/blog/php2shell-black-october-2026: https://rival.security/blog/php2shell-black-october-2026 (read 10 Nov 2026)
- Rival Security: docs.rival.security: https://docs.rival.security (read 10 Nov 2026)
- Rival Security: rival.security/blog/sastbench-measuring-ai-security-automation: https://rival.security/blog/sastbench-measuring-ai-security-automation (read 10 Nov 2026)
- Rival Security: rival.security/blog: https://rival.security/blog (read 10 Nov 2026)
- Vicarius: www.vicarius.io/features/vrx-analysis: https://www.vicarius.io/features/vrx-analysis (read 10 Nov 2026)
- Vicarius: www.vicarius.io/: https://www.vicarius.io/ (read 10 Nov 2026)
- Vicarius: www.vicarius.io/features/patch-management: https://www.vicarius.io/features/patch-management (read 10 Nov 2026)
- Vicarius: www.vicarius.io/features/patchless-protection: https://www.vicarius.io/features/patchless-protection (read 10 Nov 2026)
- Vicarius: www.vicarius.io/solution/vulnerability-remediation: https://www.vicarius.io/solution/vulnerability-remediation (read 10 Nov 2026)
- Vicarius: www.vicarius.io/features/scriptai: https://www.vicarius.io/features/scriptai (read 10 Nov 2026)
- Vicarius: www.vicarius.io/about-us: https://www.vicarius.io/about-us (read 10 Nov 2026)
- Vicarius: www.vicarius.io/features/ai-search-assistant: https://www.vicarius.io/features/ai-search-assistant (read 10 Nov 2026)
- Vicarius: www.vicarius.io/vicarius-resources-newsroom: https://www.vicarius.io/vicarius-resources-newsroom (read 10 Nov 2026)
- Vicarius: www.vicarius.io/case-studies/jamaica-broilers-group: https://www.vicarius.io/case-studies/jamaica-broilers-group (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/compare/rival-vs-vicarius/
---
# Rival Security vs Zafran: the sourced facts side by side
Side by side, read 10 Nov 2026
**The short answer.** Rival Security and Zafran are set side by side on the same rows. Rival Security has 40 fact lines (0 third-party) and Zafran has 38 (0 third-party). Fixes: Rival Security, pull requests; Zafran, mitigations. Rival Security has a none-found line on proof; Zafran on agents. The rows below set the sourced facts side by side; the page names no pick.
## The same rows for both
| Row | Rival Security | Zafran |
| --- | --- | --- |
| What it is | Agentic security platform / agent harness for vulnerability management, code and cloud security | Exposure management platform with mitigation via existing controls (agentic features) |
| What it 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. | 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. |
| Where it is 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. | 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. |
| Proves exploitability in your environment | Vendor's claim: Home page lists a Triage Exploitability agent that determines what is actually exploitable in the customer environment. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page says Rival reads every scanner finding against the real environment and keeps only those that can cause harm; it cites a 94.6% reduction in findings. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page reports 98% of findings proven unexploitable, 87% faster remediation and 1.5 hours to first value (no method given on the page). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: In its PHP2Shell write-up, Rival says agents ordered services to fix by reachability, internet-exposed unauthenticated workloads first. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) | Vendor's claim: Exposure Graph links each finding to asset, network path, runtime status and threat activity, then reads live control configuration to see what already protects the asset. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Prioritization weighs runtime, reachability, active exploitation, controls and business criticality. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Control assessment reads firewall, WAF, cloud security group and EDR configurations to show which vulnerabilities are already blocked. ([source](https://www.zafran.io/solutions/use-cases/mitigate-risk), read 10 Nov 2026)
Vendor's claim: Customer evidence: Sallie Mae says Zafran checks control configuration per device and adjusts risk accordingly. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
1 more on the [profile](/platforms/zafran/) |
| Ships the fix | Vendor's claim: Home page lists an Autonomous Remediation agent that generates and ships tested fixes. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page describes the remediation flow as plan, test, and open a pull request for human review. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival lists a WAF mitigation agent that checks whether a WAF blocks exploitation and adjusts it. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival describes an alternative-remediation agent for legacy apps that plans a fix without upgrading libraries. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
2 more on the [profile](/platforms/rival/) | Vendor's claim: Mitigation first: uses existing firewall, WAF and EDR to reduce risk before a patch exists. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Attack Chains offers a compensating control (such as a WAF rule) applied in a few clicks at the choke point. ([source](https://www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration-with-google-threat-intelligence), read 10 Nov 2026)
Vendor's claim: Workflow example: one flow opens a ServiceNow ticket, pushes a WAF rule and tracks the SLA. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Patch/upgrade remediation is delivered as a Work Item routed to the owner in the ticketing tool, not as a pull request. ([source](https://www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration-with-google-threat-intelligence), read 10 Nov 2026)
2 more on the [profile](/platforms/zafran/) |
| Finds the owner | Vendor's claim: Home page lists an Ownership Resolution agent that maps each finding to the team that can fix it. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page says the owner-finding agent weighs root cause, team structure and past history (memories). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: PHP2Shell write-up says agents can message the relevant employees, and the harness lists human follow-ups. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) | Vendor's claim: Collapses overlapping findings into one fix and routes it to the right team and owner. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Auto-assigns fixes to the owner in Jira, Slack and ServiceNow. ([source](https://www.zafran.io/platform), read 10 Nov 2026)
Vendor's claim: Example: 700 findings collapse into one OpenSSL upgrade ticket routed to the Platform team. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Progress tracking with shared visibility across Security and IT. ([source](https://www.zafran.io/platform), read 10 Nov 2026) |
| Speed on a new disclosure | Vendor's claim: Home page lists a 0-day Fast Response agent covering triage through remediation. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases page describes 0-day rapid response as finding exposure across code, images and cloud and prioritizing what to do first (page also claims a drop from days to minutes). ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Published response write-up: for PHP2Shell, agents were triaging customer environments hours before scanners could detect the CVEs. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: The same write-up reports scanning more than 80,000 repositories within hours. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) | Vendor's claim: Zero Day Agent scenario: matches a pre-announced OpenSSL flaw to live software inventory in 88 seconds before any CVE is published (illustrative scenario on the home page). ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Proactive Exposure Hunting for new CVEs and zero-days, including which affected assets are internet-exposed. ([source](https://www.zafran.io/platform), read 10 Nov 2026)
Vendor's claim: Customer quote: assess exposure before CVEs are defined. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
Vendor's claim: Customer-reported time to answer "are we exposed?" is minutes. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
1 more on the [profile](/platforms/zafran/) |
| Agents you can shape | Vendor's claim: Rival offers ready-made agents that can be customized and extended. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival engineers build custom agents for the customer environment at no additional cost (Partner tier). ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Customers can build their own agents on the harness. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page says 64+ more agents are available beyond the five featured. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
2 more on the [profile](/platforms/rival/) | Vendor's claim: Ready-made Zero Day Agent and Zafran AI assistant; AI can build dashboards from prompts. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Customer-built agents: user prompts create a scheduled report agent that emails a daily report. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Zafran AI answers plain-language questions grounded in correlated asset and findings data (Sallie Mae case study). ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
Vendor's claim: Gartner definition of autonomous exposure remediation, which Zafran cites as a category it was named a Sample Vendor for. ([source](https://www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-reports-for-unified-exposure-management-platforms-and-autonomous-exposure-remediation-categories), read 10 Nov 2026)
1 more on the [profile](/platforms/zafran/) |
| Works on the stack you have | Vendor's claim: Home page names cloud, code host and infrastructure integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Home page names scanner, control and task integrations. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Use-cases table shows findings sourced from Wiz, Qualys, GitHub, a pentest, and Rival's own SCA and Code scanners. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Agents combine connected services with a Rival Security Knowledge Graph. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) | Vendor's claim: Named sources on the home page: Zafran Discover, Tenable, Rapid7, Wiz, AWS, Snyk and 100+ more integrations. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Platform page: cloud and AppSec from Wiz, Palo Alto Networks, Upwind, AWS, Snyk; on-prem from Tenable, Qualys, Rapid7. ([source](https://www.zafran.io/platform), read 10 Nov 2026)
Vendor's claim: Controls read: CrowdStrike Falcon, Akamai WAF, Palo Alto NGFW (example policies). ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Ticketing and chat: Jira, Slack, ServiceNow (see owner facts); no new agents to deploy for ingestion. ([source](https://www.zafran.io/), read 10 Nov 2026) |
| Proof | Vendor's claim: Use-cases page claims 13M+ agent runs. ([source](https://rival.security/use-cases?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Rival published SASTBench, a benchmark for SAST triage using real CVEs as true positives and filtered SAST findings as noise. ([source](https://rival.security/blog/sastbench-measuring-ai-security-automation?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Research blog post claims Rival workflows outperform current frontier models on the Spider 2.0 benchmark. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Published incident write-up (PHP2Shell, Nov 2, 2026) with unnamed customer results. ([source](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
1 more on the [profile](/platforms/rival/) | Vendor's claim: Sallie Mae case study: 96% reduction in CVSS Criticals and 23K vulnerabilities identified for mitigation with existing controls. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
Vendor's claim: Named CISO testimonial (Kraft Heinz). ([source](https://www.zafran.io/platform), read 10 Nov 2026)
Vendor's claim: Analyst recognition: KuppingerCole 2026 Leadership Compass banner on the home page. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Gartner Emerging Tech report mentions (Sept 11, 2026 and Apr 3, 2026), as reported by Zafran. ([source](https://www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-reports-for-unified-exposure-management-platforms-and-autonomous-exposure-remediation-categories), read 10 Nov 2026) |
| Profile facts | Vendor's claim: Tagline and category: Rival describes itself as an agent harness for cybersecurity. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
Vendor's claim: Research blog launched Feb 2025 describing early experiments building AI systems for cybersecurity. ([source](https://rival.security/blog?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
None found on 10 Nov 2026: Pricing (rival.security/pricing returns 404; book-a-demo form only). ([source](https://rival.security/book-a-demo-form?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026)
None found on 10 Nov 2026: Funding, investors, founders, headcount, HQ or founding year on home, blog, careers, book-a-demo pages. ([source](https://rival.security/?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=compare), read 10 Nov 2026) | Vendor's claim: Founders: Sanaz Yashar (CEO) and Ben Seri (CTO). ([source](https://www.zafran.io/about), read 10 Nov 2026)
Vendor's claim: Investors named: Menlo Ventures, Sequoia Capital, Cyberstarts, plus strategic investment from Amex Ventures (Feb 24, 2026). ([source](https://www.zafran.io/resources/zafran-announces-strategic-investment-from-amex-ventures), read 10 Nov 2026)
Vendor's claim: Strategic investment from Cisco Investments announced Jul 22, 2026 (headline on news index). ([source](https://www.zafran.io/news), read 10 Nov 2026)
None found on 10 Nov 2026: Round amounts, founding year, headquarters, headcount, customer count and pricing on the pages read ([source](https://www.zafran.io/platform), read 10 Nov 2026) |
Alphabetical by name. Each line is one fact with its label, source and read date.
## Profiles
- [Rival Security profile](/platforms/rival/): agentic security platform
- [Zafran profile](/platforms/zafran/): exposure management platform with
## Related pages
- [24 pairs, side by side](/compare/)
- [Seemplicity vs Zafran: the sourced facts side by side](/compare/seemplicity-vs-zafran/)
- [Rival Security vs Vicarius: the sourced facts side by side](/compare/rival-vs-vicarius/)
- [Vicarius vs Zafran: the sourced facts side by side](/compare/vicarius-vs-zafran/)
## Sources
- Rival Security: rival.security/: https://rival.security/ (read 10 Nov 2026)
- Rival Security: rival.security/use-cases: https://rival.security/use-cases (read 10 Nov 2026)
- Rival Security: rival.security/blog/php2shell-black-october-2026: https://rival.security/blog/php2shell-black-october-2026 (read 10 Nov 2026)
- Rival Security: docs.rival.security: https://docs.rival.security (read 10 Nov 2026)
- Rival Security: rival.security/blog/sastbench-measuring-ai-security-automation: https://rival.security/blog/sastbench-measuring-ai-security-automation (read 10 Nov 2026)
- Rival Security: rival.security/blog: https://rival.security/blog (read 10 Nov 2026)
- Zafran: www.zafran.io/: https://www.zafran.io/ (read 10 Nov 2026)
- Zafran: www.zafran.io/solutions/use-cases/mitigate-risk: https://www.zafran.io/solutions/use-cases/mitigate-risk (read 10 Nov 2026)
- Zafran: www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-: https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes (read 10 Nov 2026)
- Zafran: www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration: https://www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration-with-google-threat-intelligence (read 10 Nov 2026)
- Zafran: www.zafran.io/platform: https://www.zafran.io/platform (read 10 Nov 2026)
- Zafran: www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-re: https://www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-reports-for-unified-exposure-management-platforms-and-autonomous-exposure-remediation-categories (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/compare/rival-vs-zafran/
---
# Seemplicity vs Zafran: the sourced facts side by side
Side by side, read 10 Nov 2026
**The short answer.** Seemplicity and Zafran, on the same rows. Seemplicity has 41 fact lines, 0 of them from third-party sources; Zafran has 38 fact lines, 0 of them from third-party sources. Fixes: Seemplicity, automated workflows; Zafran, mitigations. Seemplicity has a none-found line on speed; Zafran on agents. The rows below set the sourced facts side by side; the page names no pick.
## The same rows for both
| Row | Seemplicity | Zafran |
| --- | --- | --- |
| What it is | Agentic exposure management and response (RBVM/CTEM workflow with AI analysts) | Exposure management platform with mitigation via existing controls (agentic features) |
| What it 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. | 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. |
| Where it is 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. | 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. |
| Proves exploitability in your environment | Vendor's claim: AI Analysts run structured exploitability investigations inside the remediation workflow. ([source](https://seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/), read 10 Nov 2026)
Vendor's claim: Inputs: live runtime configuration, exploit prerequisites, network reachability, code and dependency usage, compensating controls. ([source](https://seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/), read 10 Nov 2026)
Vendor's claim: Live EDR telemetry from CrowdStrike and Microsoft Defender evaluates protections per asset (Jun 3, 2026). ([source](https://seemplicity.ai/news/live-edr-context-agentic-exposure-management/), read 10 Nov 2026)
Vendor's claim: Preliminary deployments: majority of high-severity findings judged not exploitable (no counts given). ([source](https://seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/), read 10 Nov 2026)
1 more on the [profile](/platforms/seemplicity/) | Vendor's claim: Exposure Graph links each finding to asset, network path, runtime status and threat activity, then reads live control configuration to see what already protects the asset. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Prioritization weighs runtime, reachability, active exploitation, controls and business criticality. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Control assessment reads firewall, WAF, cloud security group and EDR configurations to show which vulnerabilities are already blocked. ([source](https://www.zafran.io/solutions/use-cases/mitigate-risk), read 10 Nov 2026)
Vendor's claim: Customer evidence: Sallie Mae says Zafran checks control configuration per device and adjusts risk accordingly. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
1 more on the [profile](/platforms/zafran/) |
| Ships the fix | Vendor's claim: Response Options (Sep 2, 2026) give alternatives to a full patch: compensating controls and targeted configuration changes. ([source](https://seemplicity.ai/news/response-options/), read 10 Nov 2026)
Vendor's claim: Each option carries a Readiness Indicator (deploy now or review first); AI Analysts pre-select a recommendation and all alternatives stay visible. ([source](https://seemplicity.ai/news/response-options/), read 10 Nov 2026)
Vendor's claim: Code Analyst reads source from GitHub, GitLab and other repositories and hands developers a scoped, ready-to-apply fix. ([source](https://seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/), read 10 Nov 2026)
Vendor's claim: Remediation agents provide step-by-step guidance and ownership mapping; delivery is into existing workflows (guidance and tickets). ([source](https://seemplicity.ai/platform/agentic-workforce/), read 10 Nov 2026)
1 more on the [profile](/platforms/seemplicity/) | Vendor's claim: Mitigation first: uses existing firewall, WAF and EDR to reduce risk before a patch exists. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Attack Chains offers a compensating control (such as a WAF rule) applied in a few clicks at the choke point. ([source](https://www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration-with-google-threat-intelligence), read 10 Nov 2026)
Vendor's claim: Workflow example: one flow opens a ServiceNow ticket, pushes a WAF rule and tracks the SLA. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Patch/upgrade remediation is delivered as a Work Item routed to the owner in the ticketing tool, not as a pull request. ([source](https://www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration-with-google-threat-intelligence), read 10 Nov 2026)
2 more on the [profile](/platforms/zafran/) |
| Finds the owner | Vendor's claim: Automatically assigns remediation to owners and delivers fix-ready guidance into existing workflows. ([source](https://seemplicity.ai/), read 10 Nov 2026)
Vendor's claim: Hertz: unknown asset ownership fell from 20% to 2% in six months. ([source](https://seemplicity.ai/resource/hertz-case-study/), read 10 Nov 2026)
Vendor's claim: Owners and criticality identified by syncing with CMDBs. ([source](https://seemplicity.ai/automated-vulnerability-remediation/), read 10 Nov 2026)
Vendor's claim: Host Analyst surfaces the likely owner. ([source](https://seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/), read 10 Nov 2026)
1 more on the [profile](/platforms/seemplicity/) | Vendor's claim: Collapses overlapping findings into one fix and routes it to the right team and owner. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Auto-assigns fixes to the owner in Jira, Slack and ServiceNow. ([source](https://www.zafran.io/platform), read 10 Nov 2026)
Vendor's claim: Example: 700 findings collapse into one OpenSSL upgrade ticket routed to the Platform team. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Progress tracking with shared visibility across Security and IT. ([source](https://www.zafran.io/platform), read 10 Nov 2026) |
| Speed on a new disclosure | Vendor's claim: SCA Analyst powers SBOM-driven zero-day response before scanner signatures exist. ([source](https://seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/), read 10 Nov 2026)
Vendor's claim: Home page claims discovery to remediation in seconds (no method). ([source](https://seemplicity.ai/), read 10 Nov 2026)
Vendor's claim: MTTR reduction claim of 90% on the remediation workflow page. ([source](https://seemplicity.ai/automated-vulnerability-remediation/), read 10 Nov 2026)
None found on 10 Nov 2026: A published time-to-answer measurement for a specific new CVE disclosure on seemplicity.ai pages read ([source](https://seemplicity.ai/news/), read 10 Nov 2026) | Vendor's claim: Zero Day Agent scenario: matches a pre-announced OpenSSL flaw to live software inventory in 88 seconds before any CVE is published (illustrative scenario on the home page). ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Proactive Exposure Hunting for new CVEs and zero-days, including which affected assets are internet-exposed. ([source](https://www.zafran.io/platform), read 10 Nov 2026)
Vendor's claim: Customer quote: assess exposure before CVEs are defined. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
Vendor's claim: Customer-reported time to answer "are we exposed?" is minutes. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
1 more on the [profile](/platforms/zafran/) |
| Agents you can shape | Vendor's claim: Ready-made autonomous SAST, SCA and Host Analysts work around the clock. ([source](https://seemplicity.ai/platform/agentic-workforce/), read 10 Nov 2026)
Vendor's claim: Four agent families: validation, context, strategy, remediation. ([source](https://seemplicity.ai/platform/agentic-workforce/), read 10 Nov 2026)
Vendor's claim: Seema conversational assistant for exposure questions. ([source](https://seemplicity.ai/), read 10 Nov 2026)
Vendor's claim: Controls: transparent reasoning trails, visible alternatives, and customer-built approval gates in workflows. ([source](https://seemplicity.ai/customers/), read 10 Nov 2026)
2 more on the [profile](/platforms/seemplicity/) | Vendor's claim: Ready-made Zero Day Agent and Zafran AI assistant; AI can build dashboards from prompts. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Customer-built agents: user prompts create a scheduled report agent that emails a daily report. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Zafran AI answers plain-language questions grounded in correlated asset and findings data (Sallie Mae case study). ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
Vendor's claim: Gartner definition of autonomous exposure remediation, which Zafran cites as a category it was named a Sample Vendor for. ([source](https://www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-reports-for-unified-exposure-management-platforms-and-autonomous-exposure-remediation-categories), read 10 Nov 2026)
1 more on the [profile](/platforms/zafran/) |
| Works on the stack you have | Vendor's claim: Integration page claims hundreds of integrations. ([source](https://seemplicity.ai/integrations/), read 10 Nov 2026)
Vendor's claim: Scanners and CNAPP named: Qualys, Rapid7, Tenable products, Wiz, Orca, Prisma Cloud. ([source](https://seemplicity.ai/integrations/), read 10 Nov 2026)
Vendor's claim: Ticketing and dev tooling named in the integrations list include Azure DevOps (also GitHub, GitLab, Jira per the same list). ([source](https://seemplicity.ai/integrations/), read 10 Nov 2026)
Vendor's claim: ServiceNow CMDB is a named integration (list also includes ServiceNow, Slack, Teams, Snyk, SentinelOne Singularity). ([source](https://seemplicity.ai/integrations/), read 10 Nov 2026) | Vendor's claim: Named sources on the home page: Zafran Discover, Tenable, Rapid7, Wiz, AWS, Snyk and 100+ more integrations. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Platform page: cloud and AppSec from Wiz, Palo Alto Networks, Upwind, AWS, Snyk; on-prem from Tenable, Qualys, Rapid7. ([source](https://www.zafran.io/platform), read 10 Nov 2026)
Vendor's claim: Controls read: CrowdStrike Falcon, Akamai WAF, Palo Alto NGFW (example policies). ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Ticketing and chat: Jira, Slack, ServiceNow (see owner facts); no new agents to deploy for ingestion. ([source](https://www.zafran.io/), read 10 Nov 2026) |
| Proof | Vendor's claim: Hertz case study: critical remediation up 400%. ([source](https://seemplicity.ai/resource/hertz-case-study/), read 10 Nov 2026)
Vendor's claim: Named customer quotes: Omnissa, OpenWeb, X-Press Feeders; OpenWeb reports 85% fewer tickets. ([source](https://seemplicity.ai/customers/), read 10 Nov 2026)
Vendor's claim: Average claims: 57% scanner noise reduction and $1.7M annual savings (aggregate, method not on page). ([source](https://seemplicity.ai/), read 10 Nov 2026)
Vendor's claim: Research: 2026 Exposure Action Report on 2025 customer data; April 2026 survey report (88% use AI, 31% trust it). ([source](https://seemplicity.ai/), read 10 Nov 2026)
1 more on the [profile](/platforms/seemplicity/) | Vendor's claim: Sallie Mae case study: 96% reduction in CVSS Criticals and 23K vulnerabilities identified for mitigation with existing controls. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
Vendor's claim: Named CISO testimonial (Kraft Heinz). ([source](https://www.zafran.io/platform), read 10 Nov 2026)
Vendor's claim: Analyst recognition: KuppingerCole 2026 Leadership Compass banner on the home page. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Gartner Emerging Tech report mentions (Sept 11, 2026 and Apr 3, 2026), as reported by Zafran. ([source](https://www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-reports-for-unified-exposure-management-platforms-and-autonomous-exposure-remediation-categories), read 10 Nov 2026) |
| Profile facts | Vendor's claim: Founded 2020 by Yoran Sirkis, Ravid Circus, Rotem Cohen Gadol. ([source](https://seemplicity.ai/about/), read 10 Nov 2026)
Vendor's claim: Funding: $26M Series A and $50M Series B led by Sienna Venture Capital; more than $63M raised per the CEO bio. ([source](https://seemplicity.ai/about/), read 10 Nov 2026)
Vendor's claim: Series A $26M backed by Glilot Capital, NTTVC, Atlantic Bridge, S Capital, Rain Capital. ([source](https://seemplicity.ai/about/), read 10 Nov 2026)
Vendor's claim: HQ address San Jose, CA, with Tel Aviv office. ([source](https://seemplicity.ai/platform/agentic-workforce/), read 10 Nov 2026) | Vendor's claim: Founders: Sanaz Yashar (CEO) and Ben Seri (CTO). ([source](https://www.zafran.io/about), read 10 Nov 2026)
Vendor's claim: Investors named: Menlo Ventures, Sequoia Capital, Cyberstarts, plus strategic investment from Amex Ventures (Feb 24, 2026). ([source](https://www.zafran.io/resources/zafran-announces-strategic-investment-from-amex-ventures), read 10 Nov 2026)
Vendor's claim: Strategic investment from Cisco Investments announced Jul 22, 2026 (headline on news index). ([source](https://www.zafran.io/news), read 10 Nov 2026)
None found on 10 Nov 2026: Round amounts, founding year, headquarters, headcount, customer count and pricing on the pages read ([source](https://www.zafran.io/platform), read 10 Nov 2026) |
Alphabetical by name. Each line is one fact with its label, source and read date.
## Profiles
- [Seemplicity profile](/platforms/seemplicity/): agentic exposure management and
- [Zafran profile](/platforms/zafran/): exposure management platform with
## Related pages
- [24 pairs, side by side](/compare/)
- [Vicarius vs Zafran: the sourced facts side by side](/compare/vicarius-vs-zafran/)
- [Rival Security vs Zafran: the sourced facts side by side](/compare/rival-vs-zafran/)
- [Astelia Security vs Onit Security: the sourced facts side by side](/compare/astelia-vs-onit/)
## Sources
- Seemplicity: seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/: https://seemplicity.ai/news/ai-analysts-autonomous-vulnerability-response/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/news/live-edr-context-agentic-exposure-management/: https://seemplicity.ai/news/live-edr-context-agentic-exposure-management/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/platform/agentic-workforce/: https://seemplicity.ai/platform/agentic-workforce/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/news/response-options/: https://seemplicity.ai/news/response-options/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/automated-vulnerability-remediation/: https://seemplicity.ai/automated-vulnerability-remediation/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/: https://seemplicity.ai/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/resource/hertz-case-study/: https://seemplicity.ai/resource/hertz-case-study/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/news/: https://seemplicity.ai/news/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/customers/: https://seemplicity.ai/customers/ (read 10 Nov 2026)
- Seemplicity: seemplicity.ai/integrations/: https://seemplicity.ai/integrations/ (read 10 Nov 2026)
- Zafran: www.zafran.io/: https://www.zafran.io/ (read 10 Nov 2026)
- Zafran: www.zafran.io/solutions/use-cases/mitigate-risk: https://www.zafran.io/solutions/use-cases/mitigate-risk (read 10 Nov 2026)
- Zafran: www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-: https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes (read 10 Nov 2026)
- Zafran: www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration: https://www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration-with-google-threat-intelligence (read 10 Nov 2026)
- Zafran: www.zafran.io/platform: https://www.zafran.io/platform (read 10 Nov 2026)
- Zafran: www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-re: https://www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-reports-for-unified-exposure-management-platforms-and-autonomous-exposure-remediation-categories (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/compare/seemplicity-vs-zafran/
---
# Vicarius vs Zafran: the sourced facts side by side
Side by side, read 10 Nov 2026
**The short answer.** Vicarius and Zafran are set side by side on the same rows. Fact lines: Vicarius 38, Zafran 38. Third-party: 0 and 0. Fixes: Vicarius, patches through patch tools and mitigations; Zafran, mitigations and patches through patch tools. None found: Vicarius on owner; Zafran on agents. The rows below set the sourced facts side by side; the page names no pick.
## The same rows for both
| Row | Vicarius | Zafran |
| --- | --- | --- |
| What it is | Remediation-first exposure platform (patching, scripting, patchless protection) | Exposure management platform with mitigation via existing controls (agentic features) |
| What it 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. | 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. |
| Where it is 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 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. |
| Proves exploitability in your environment | Vendor's claim: VScore adds exploit simulation, asset criticality and business context in addition to CVSS, EPSS and KEV. ([source](https://www.vicarius.io/features/vrx-analysis), read 10 Nov 2026)
Vendor's claim: Vendor says vScore confirms every queued item is exploitable. ([source](https://www.vicarius.io/features/vrx-analysis), read 10 Nov 2026)
Vendor's claim: Agentic AI validation of which vulnerabilities attackers can exploit. ([source](https://www.vicarius.io/), read 10 Nov 2026)
Vendor's claim: Claims 95% of false positives removed by agentic exposure validation (no method shown). ([source](https://www.vicarius.io/features/vrx-analysis), read 10 Nov 2026)
1 more on the [profile](/platforms/vicarius/) | Vendor's claim: Exposure Graph links each finding to asset, network path, runtime status and threat activity, then reads live control configuration to see what already protects the asset. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Prioritization weighs runtime, reachability, active exploitation, controls and business criticality. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Control assessment reads firewall, WAF, cloud security group and EDR configurations to show which vulnerabilities are already blocked. ([source](https://www.zafran.io/solutions/use-cases/mitigate-risk), read 10 Nov 2026)
Vendor's claim: Customer evidence: Sallie Mae says Zafran checks control configuration per device and adjusts risk accordingly. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
1 more on the [profile](/platforms/zafran/) |
| Ships the fix | Vendor's claim: Core pitch: finds vulnerabilities and fixes them via patch management, scripting and patchless protection. ([source](https://www.vicarius.io/), read 10 Nov 2026)
Vendor's claim: Patching on demand, scheduled or by rule across Windows, macOS, Linux and 20,000+ third-party apps. ([source](https://www.vicarius.io/features/patch-management), read 10 Nov 2026)
Vendor's claim: VShield blocks exploit paths in memory without touching the application or a reboot (virtual patch style mitigation). ([source](https://www.vicarius.io/features/patchless-protection), read 10 Nov 2026)
Vendor's claim: Remediation is executed and then verified; for patching vRx compares detected version with the target version. ([source](https://www.vicarius.io/solution/vulnerability-remediation), read 10 Nov 2026)
1 more on the [profile](/platforms/vicarius/) | Vendor's claim: Mitigation first: uses existing firewall, WAF and EDR to reduce risk before a patch exists. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Attack Chains offers a compensating control (such as a WAF rule) applied in a few clicks at the choke point. ([source](https://www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration-with-google-threat-intelligence), read 10 Nov 2026)
Vendor's claim: Workflow example: one flow opens a ServiceNow ticket, pushes a WAF rule and tracks the SLA. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Patch/upgrade remediation is delivered as a Work Item routed to the owner in the ticketing tool, not as a pull request. ([source](https://www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration-with-google-threat-intelligence), read 10 Nov 2026)
2 more on the [profile](/platforms/zafran/) |
| Finds the owner | Vendor's claim: Orchestration and automation to coordinate remediation across teams and tools (feature named in navigation; little detail on owner resolution). ([source](https://www.vicarius.io/), read 10 Nov 2026)
None found on 10 Nov 2026: Automatic mapping of findings to the owning team or CMDB/ticketing owner resolution on vicarius.io pages read ([source](https://www.vicarius.io/), read 10 Nov 2026) | Vendor's claim: Collapses overlapping findings into one fix and routes it to the right team and owner. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Auto-assigns fixes to the owner in Jira, Slack and ServiceNow. ([source](https://www.zafran.io/platform), read 10 Nov 2026)
Vendor's claim: Example: 700 findings collapse into one OpenSSL upgrade ticket routed to the Platform team. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Progress tracking with shared visibility across Security and IT. ([source](https://www.zafran.io/platform), read 10 Nov 2026) |
| Speed on a new disclosure | Vendor's claim: VShield protects at disclosure before a vendor patch exists. ([source](https://www.vicarius.io/features/patchless-protection), read 10 Nov 2026)
Vendor's claim: ScriptAI watches for exploited-in-the-wild threats before an official identifier exists and generates detection scripts. ([source](https://www.vicarius.io/features/scriptai), read 10 Nov 2026)
Vendor's claim: Detection scripts run immediately to show which assets are affected while remediation is validated. ([source](https://www.vicarius.io/features/scriptai), read 10 Nov 2026)
Vendor's claim: Average time to rescan stated as 15 seconds. ([source](https://www.vicarius.io/about-us), read 10 Nov 2026)
1 more on the [profile](/platforms/vicarius/) | Vendor's claim: Zero Day Agent scenario: matches a pre-announced OpenSSL flaw to live software inventory in 88 seconds before any CVE is published (illustrative scenario on the home page). ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Proactive Exposure Hunting for new CVEs and zero-days, including which affected assets are internet-exposed. ([source](https://www.zafran.io/platform), read 10 Nov 2026)
Vendor's claim: Customer quote: assess exposure before CVEs are defined. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
Vendor's claim: Customer-reported time to answer "are we exposed?" is minutes. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
1 more on the [profile](/platforms/zafran/) |
| Agents you can shape | Vendor's claim: ScriptAI and AI grouping are labeled agentic AI features (new): LLM-written remediation scripts and AI-powered dynamic groups. ([source](https://www.vicarius.io/), read 10 Nov 2026)
Vendor's claim: VIntelligence AI search assistant answers plain-English questions on live data with threat intelligence. ([source](https://www.vicarius.io/features/ai-search-assistant), read 10 Nov 2026)
Vendor's claim: Script library of 1000+ community and AI-generated scripts; custom scripts supported. ([source](https://www.vicarius.io/features/scriptai), read 10 Nov 2026)
Vendor's claim: Newsroom lists an October 2026 release "Vicarius revamps AI platform to unify cybersecurity workflows" (vRx 2.0 launch the same month). ([source](https://www.vicarius.io/vicarius-resources-newsroom), read 10 Nov 2026) | Vendor's claim: Ready-made Zero Day Agent and Zafran AI assistant; AI can build dashboards from prompts. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Customer-built agents: user prompts create a scheduled report agent that emails a daily report. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Zafran AI answers plain-language questions grounded in correlated asset and findings data (Sallie Mae case study). ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
Vendor's claim: Gartner definition of autonomous exposure remediation, which Zafran cites as a category it was named a Sample Vendor for. ([source](https://www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-reports-for-unified-exposure-management-platforms-and-autonomous-exposure-remediation-categories), read 10 Nov 2026)
1 more on the [profile](/platforms/zafran/) |
| Works on the stack you have | Vendor's claim: Feeds from EDR, SIEM, CSPM and scanners into one ordered list. ([source](https://www.vicarius.io/features/vrx-analysis), read 10 Nov 2026)
Vendor's claim: Endpoint coverage: Windows, macOS, Linux and 20,000+ third-party apps; agent and agentless detection. ([source](https://www.vicarius.io/), read 10 Nov 2026)
None found on 10 Nov 2026: A named list of scanner, cloud, code host or ticketing integrations on the vicarius.io pages read ([source](https://www.vicarius.io/), read 10 Nov 2026) | Vendor's claim: Named sources on the home page: Zafran Discover, Tenable, Rapid7, Wiz, AWS, Snyk and 100+ more integrations. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Platform page: cloud and AppSec from Wiz, Palo Alto Networks, Upwind, AWS, Snyk; on-prem from Tenable, Qualys, Rapid7. ([source](https://www.zafran.io/platform), read 10 Nov 2026)
Vendor's claim: Controls read: CrowdStrike Falcon, Akamai WAF, Palo Alto NGFW (example policies). ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Ticketing and chat: Jira, Slack, ServiceNow (see owner facts); no new agents to deploy for ingestion. ([source](https://www.zafran.io/), read 10 Nov 2026) |
| Proof | Vendor's claim: Customer count claims differ by page: 1,000+ deployments (home) versus over 500 customers in 50 countries (about). ([source](https://www.vicarius.io/), read 10 Nov 2026)
Vendor's claim: Case study: Jamaica Broilers Group remediates 70% faster (vendor-published). ([source](https://www.vicarius.io/case-studies/jamaica-broilers-group), read 10 Nov 2026)
Vendor's claim: Customer outcome: Charter School Associates saved 100+ hours on patch management. ([source](https://www.vicarius.io/), read 10 Nov 2026)
Vendor's claim: Recognized in the Gartner 2025 Magic Quadrant for Exposure Assessment Platforms (per vendor). ([source](https://www.vicarius.io/), read 10 Nov 2026)
2 more on the [profile](/platforms/vicarius/) | Vendor's claim: Sallie Mae case study: 96% reduction in CVSS Criticals and 23K vulnerabilities identified for mitigation with existing controls. ([source](https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes), read 10 Nov 2026)
Vendor's claim: Named CISO testimonial (Kraft Heinz). ([source](https://www.zafran.io/platform), read 10 Nov 2026)
Vendor's claim: Analyst recognition: KuppingerCole 2026 Leadership Compass banner on the home page. ([source](https://www.zafran.io/), read 10 Nov 2026)
Vendor's claim: Gartner Emerging Tech report mentions (Sept 11, 2026 and Apr 3, 2026), as reported by Zafran. ([source](https://www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-reports-for-unified-exposure-management-platforms-and-autonomous-exposure-remediation-categories), read 10 Nov 2026) |
| Profile facts | Vendor's claim: Founded 2016. ([source](https://www.vicarius.io/about-us), read 10 Nov 2026)
Vendor's claim: Funding: $24M Series A (2022) and $30M Series B (2023). ([source](https://www.vicarius.io/about-us), read 10 Nov 2026)
Vendor's claim: Series A amount. ([source](https://www.vicarius.io/about-us), read 10 Nov 2026)
Vendor's claim: HQ New York; offices in Israel, Australia, Brazil, Chile, Germany, India, Singapore, UK. ([source](https://www.vicarius.io/about-us), read 10 Nov 2026) | Vendor's claim: Founders: Sanaz Yashar (CEO) and Ben Seri (CTO). ([source](https://www.zafran.io/about), read 10 Nov 2026)
Vendor's claim: Investors named: Menlo Ventures, Sequoia Capital, Cyberstarts, plus strategic investment from Amex Ventures (Feb 24, 2026). ([source](https://www.zafran.io/resources/zafran-announces-strategic-investment-from-amex-ventures), read 10 Nov 2026)
Vendor's claim: Strategic investment from Cisco Investments announced Jul 22, 2026 (headline on news index). ([source](https://www.zafran.io/news), read 10 Nov 2026)
None found on 10 Nov 2026: Round amounts, founding year, headquarters, headcount, customer count and pricing on the pages read ([source](https://www.zafran.io/platform), read 10 Nov 2026) |
Alphabetical by name. Each line is one fact with its label, source and read date.
## Profiles
- [Vicarius profile](/platforms/vicarius/): remediation-first exposure
- [Zafran profile](/platforms/zafran/): exposure management platform with
## Related pages
- [24 pairs, side by side](/compare/)
- [Astelia Security vs Onit Security: the sourced facts side by side](/compare/astelia-vs-onit/)
- [Seemplicity vs Zafran: the sourced facts side by side](/compare/seemplicity-vs-zafran/)
- [Astelia Security vs Rival Security: the sourced facts side by side](/compare/astelia-vs-rival/)
## Sources
- Vicarius: www.vicarius.io/features/vrx-analysis: https://www.vicarius.io/features/vrx-analysis (read 10 Nov 2026)
- Vicarius: www.vicarius.io/: https://www.vicarius.io/ (read 10 Nov 2026)
- Vicarius: www.vicarius.io/features/patch-management: https://www.vicarius.io/features/patch-management (read 10 Nov 2026)
- Vicarius: www.vicarius.io/features/patchless-protection: https://www.vicarius.io/features/patchless-protection (read 10 Nov 2026)
- Vicarius: www.vicarius.io/solution/vulnerability-remediation: https://www.vicarius.io/solution/vulnerability-remediation (read 10 Nov 2026)
- Vicarius: www.vicarius.io/features/scriptai: https://www.vicarius.io/features/scriptai (read 10 Nov 2026)
- Vicarius: www.vicarius.io/about-us: https://www.vicarius.io/about-us (read 10 Nov 2026)
- Vicarius: www.vicarius.io/features/ai-search-assistant: https://www.vicarius.io/features/ai-search-assistant (read 10 Nov 2026)
- Vicarius: www.vicarius.io/vicarius-resources-newsroom: https://www.vicarius.io/vicarius-resources-newsroom (read 10 Nov 2026)
- Vicarius: www.vicarius.io/case-studies/jamaica-broilers-group: https://www.vicarius.io/case-studies/jamaica-broilers-group (read 10 Nov 2026)
- Zafran: www.zafran.io/: https://www.zafran.io/ (read 10 Nov 2026)
- Zafran: www.zafran.io/solutions/use-cases/mitigate-risk: https://www.zafran.io/solutions/use-cases/mitigate-risk (read 10 Nov 2026)
- Zafran: www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-: https://www.zafran.io/case-studies/how-sallie-mae-went-from-a-hell-week-of-spreadsheets-to-exposure-answers-in-minutes (read 10 Nov 2026)
- Zafran: www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration: https://www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration-with-google-threat-intelligence (read 10 Nov 2026)
- Zafran: www.zafran.io/platform: https://www.zafran.io/platform (read 10 Nov 2026)
- Zafran: www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-re: https://www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-reports-for-unified-exposure-management-platforms-and-autonomous-exposure-remediation-categories (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/compare/vicarius-vs-zafran/
---
# 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/
---
# A vulnerability backlog is measured in analyst hours, and the count of findings is only the first input
Guide, 2 Nov 2026, read 10 Nov 2026
**The short answer.** 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. Measure analysis time per finding first, then the share removed before analysis, then fix time, and keep the three apart.
## Count findings, then convert them to hours
A finding count says little about workload. Ten thousand findings that are duplicates of one base image take an afternoon. Ten thousand distinct findings across a hundred teams take a year. The conversion that makes the count useful is minutes of analyst time per finding.
The Backlog Calculator on this site uses a plain formula: findings left, times minutes per finding, divided by 60, gives analyst hours. Hours divided by (analysts times weekly queue hours divided by 5) gives working days. Its defaults are 20,000 findings, 25 minutes, 3 analysts and 30 queue hours a week, which produce 8,333 hours and 463 working days. The 25 minutes is an input to replace, not a benchmark.
| Open findings | Analyst hours at 25 minutes | Working days, 3 analysts at 30 hours a week |
| --- | --- | --- |
| 5,000 | 2,083 | 116 |
| 20,000 | 8,333 | 463 |
| 50,000 | 20,833 | 1,157 |
## Measure your own minutes per finding
Take a sample of 30 findings that were closed last month and time them from the moment an analyst opened the finding to the moment a decision was recorded: fix, mitigate, accept, or dismiss. Use the median, not the mean, because a few findings that took two days will pull the mean far above what a typical finding costs.
Split the sample by type. A dependency finding in a repository the team owns, an operating system patch on a managed host, and a cloud misconfiguration have different costs, and the split shows where an agent would remove the most time.
- Time to decide is analysis time. It ends when the finding has a recorded disposition.
- Time to fix is engineering or operations time. It belongs to another team and another queue.
- Time to verify is the re-check after the change. Count it only if your process requires one.
## Separate removal from fixing
A platform can reduce the backlog in two different ways. It can remove findings before a person reads them, by showing they cannot be used in your environment or by merging duplicates. Or it can shorten the work on findings that remain, by preparing the fix. The calculator takes the first as a percentage removed before analysis and leaves it at 0 until you set it.
Vendor figures for removal vary and carry different evidence. Maze states that 90% of the vulnerabilities it analyzes are not exploitable, and in one customer story reports 51% of findings judged not exploitable (vendor's claim, read 10 Nov 2026). Cogent states that for one disclosure it narrowed 2,266 affected assets to 16 (vendor's claim). Setting the percent removed to 25 in the calculator cuts the default case from 463 working days to 347. At 90, it falls to 46. Whichever figure you enter, test it on a sample of your own findings in a trial.
## Set the target against a public deadline
Federal agencies under CISA BOD 22-01 must remediate vulnerabilities in the Known Exploited Vulnerabilities catalog within two weeks when the CVE was assigned after 2021, and within six months for older CVEs. Private companies are not bound by it, but the directive gives a dated number to compare a queue against.
If the hours figure is far above the capacity of the team for the next two weeks, the backlog is a staffing and automation question. If it is close, the problem is routing and ownership, and the guide on ownership mapping is the better next read.
## See which lever moves the answer most
Four inputs set the result, and they do not move it equally. Cut the minutes per finding from 25 to 10 and the default case falls from 463 working days to 185. Double the analysts from 3 to 6 and it falls to 231. Remove 25% of findings before analysis and it falls to 347. Remove 90% and it falls to 46.
The comparison is the reason to run the calculator before a vendor meeting. If the lever a platform pulls is minutes per finding, test minutes per finding. If it removes findings, test the evidence for the removal. A platform that does neither is not changing the number that matters to your queue.
## Related pages
- [Guides](/guides/)
- [Automated vulnerability remediation: what an agent can fix without a human](/guides/what-an-agent-can-fix-without-a-human/)
- [AI vulnerability management in the weekly remediation meeting](/guides/ai-vulnerability-management-in-the-weekly-meeting/)
- [How approval should work when an agent changes production](/guides/how-approval-should-work/)
## Sources
- Maze Security, home page: https://mazehq.com/ (read 10 Nov 2026)
- CISA BOD 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities (archived copy): https://web.archive.org/web/2024/https://www.cisa.gov/news-events/directives/bod-22-01-reducing-significant-risk-known-exploited-vulnerabilities (read 10 Nov 2026)
- Cogent Security blog, 10 Nov 2026: https://www.cogent.com/blog/cogent-expands-its-ai-cyber-defense-factory-with-specular-acquisition (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/guides/how-to-measure-a-backlog/
---
# An agent can fix a narrow set of findings without a person, and the set depends on the artifact it produces
Guide, 26 Oct 2026, read 10 Nov 2026
**The short answer.** 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. Each fits a different finding type. Vendor pages read on 10 Nov 2026 show which outputs each platform states.
## Four outputs, four kinds of finding
Automated vulnerability remediation is a loose phrase. The useful question is what the agent hands over. The vendor pages read for the register describe four outputs, and each applies to a different kind of finding.
A dependency, container image or infrastructure-as-code finding in a repository can be fixed by a pull request. An operating system or third-party application finding on a managed host can be fixed by a patch job. A finding with no patch, or in a system nobody will touch this quarter, can be reduced by a firewall or web application firewall rule. Everything else arrives as a ticket, ideally with the plan attached.
| Output | Finding type it fits | Platforms stating it (vendor's claim, read 10 Nov 2026) |
| --- | --- | --- |
| Pull request | Dependencies, container images, infrastructure as code | Averlon, Backline, Rival |
| Patch job through a tool | Operating system and third-party application patches | Astelia, Qualys, Tenable, Vicarius |
| Network or web application firewall rule | Findings with no patch, or no change window | Astelia, Rival, Seemplicity, Zafran |
| Ticket with plan | Anything that needs a person to schedule it | Onit, Rapid7, Seemplicity, Zafran |
## What the vendor pages say about each output
Averlon says its GitHub Actions generate ready-to-merge pull requests for container images, Terraform and Pulumi, and Helm charts, with a ticket per pull request assigned to the code owner. Backline says each remediation includes a plan and a ready-to-review pull request for dependency, container image and infrastructure findings, and that existing unit tests run before delivery. Rival describes a flow of plan, test, and open a pull request for human review.
On patch jobs, Qualys says its TruRisk Eliminate 2.0 chooses between zero-touch, ring-staged and manual change board deployment by patch reliability, and rolls back automatically if a deployment causes issues. Tenable says Patch Management applies policy-based patching that can be scheduled, paused or rolled back. Vicarius lists patching on demand, scheduled or by rule across Windows, macOS, Linux and over 20,000 third-party applications.
On rules, Astelia describes a drafted firewall rule waiting in an approval queue. Zafran describes a compensating control, such as a web application firewall rule, applied in a few clicks at the choke point of an attack chain. Seemplicity added Response Options on 2 Sep 2026, giving compensating controls and configuration changes alongside the full patch.
## Where a person is still in the loop
Every vendor above keeps a person somewhere in the path. Averlon's own example expects a developer to review each generated fix, at about 15 minutes per fix in its example. Backline says fixes ship as standard pull requests, so rollback uses existing Git workflows. Onit states that nothing executes without approval. Cogent states that high-impact changes require human approval and an audit trail.
So the working question is not whether a human is involved, but at which point and for how many items. A reviewer who approves 260 grouped pull requests is doing a different job from one who approves 110,000 findings (the Averlon example, vendor's claim: 3,400 tickets became 260 pull requests).
## Findings an agent should not touch alone
Platforms differ in how they handle the last of these. Onit states that when evidence is missing an agent says unknown with the reason instead of guessing. Check that your platform of choice does the same, and that unknown items land in a queue a person reads.
- A patch to a system with no tested rollback.
- A change to an authentication or network path that many services share.
- A fix that requires an upgrade across a major version of a library.
- Any finding where the platform reports unknown owner or unknown exposure.
## Sort your own backlog by output first
Before reading a profile, take 100 open findings as a sample and sort each by the output that would close it: pull request, patch job, rule, or ticket. The mix tells you which platform output matters to you. A backlog that is mostly container image and dependency findings points to pull requests. One that is mostly operating system patches on managed hosts points to patch jobs.
Most backlogs hold a mix, and the mix changes the question. If 60 of the 100 need a pull request, a platform with strong patch tooling and no repository access leaves most of your queue untouched. The profiles state the outputs each vendor describes, and the none found labels show where a page was read and the capability was not on it.
## Related pages
- [Guides](/guides/)
- [How approval should work when an agent changes production](/guides/how-approval-should-work/)
- [How to measure a vulnerability backlog in hours, not findings](/guides/how-to-measure-a-backlog/)
- [Ownership mapping: finding who can fix a finding](/guides/ownership-mapping/)
## Sources
- Averlon blog on automating remediation: https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues (read 10 Nov 2026)
- Backline, product page: https://backline.ai/product/ (read 10 Nov 2026)
- Qualys, agentic AI page: https://www.qualys.com/apps/agentic-ai (read 10 Nov 2026)
- Tenable Patch Management: https://www.tenable.com/products/patch-management (read 10 Nov 2026)
- Seemplicity, Response Options, 2 Sep 2026: https://seemplicity.ai/news/response-options/ (read 10 Nov 2026)
- Onit Security, platform page: https://onit.security/platform/ (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/guides/what-an-agent-can-fix-without-a-human/
---
# Approval should be set by action type and confidence, and every approval should leave a record
Guide, 20 Oct 2026, read 10 Nov 2026
**The short answer.** 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. Cogent Security, Onit, Qualys and Tenable each describe such gates on pages read 10 Nov 2026. Ask for the setting, the log and the undo.
## Approve by action type, not by agent
A single switch labelled autonomous or manual is too coarse. An agent that reads a configuration, one that drafts a ticket, and one that deploys a patch carry different risks, and a team will want them at different settings.
The vendor pages read for the register show finer controls. Cogent says customers choose where agents act alone and where they pause for sign-off, configured by action type, severity or asset sensitivity, and that autonomy is staged from recommendations to wider action. Onit states a human approval gate on every agent action, with an audit trail and one-step reversal, and describes approved decisions becoming standing rules that cover matching exposures, logged and reversible.
## Gate by confidence and ring
Qualys describes patch reliability scoring that picks the deployment path: zero-touch for high confidence, ring-staged for medium, and a manual change advisory board for low. It also describes customer-set maintenance windows, a ServiceNow change integration that keeps changes under existing approval, and automatic rollback.
The pattern is useful beyond one vendor. High-confidence changes go out first to a small group, the group is watched, and the change widens only if health holds. Qualys names Dynatrace checks for that watching; if you use a different monitor, ask whether the platform can read it.
| Control | What to ask for | Example stated by a vendor (vendor's claim, read 10 Nov 2026) |
| --- | --- | --- |
| Per-action autonomy | A setting for each action type | Cogent Security: by action type, severity or asset sensitivity |
| Standing rules | Rules created from a reviewed decision, with an undo | Onit: approved decisions become logged, reversible rules |
| Staged rollout | Rings, with a pause on bad health | Qualys: confidence-gated waves, rollback |
| Pause and roll back | A control a person can use at any time | Tenable: schedule, pause or roll back deployments |
| Approval queue | A list of waiting changes with their evidence | Astelia: queue holds the drafted ticket and firewall rule |
## Keep the record that an auditor reads
Approval without a record helps nobody in the next review. For each approved action the platform should store who approved it, what the agent proposed, the evidence shown at the time, the time of change, and the re-check. Tenable states that Hexa AI logs every action for audit. Astelia lists role-based access control and execution logs among its controls.
NIST SP 800-40 Rev. 4 describes patch management as identifying, prioritizing, acquiring, installing and verifying patches. An approval record that covers each of those five steps answers most audit questions.
## Test the gate in the trial
- Ask the platform to propose a change you know you would reject. Confirm it waits.
- Remove an approver and confirm the change does not run.
- Roll back one change and time it.
- Export the log for one week and read it as an auditor would.
## Start narrow and widen on evidence
A sensible first 90 days moves through four settings. In the first weeks, agents run read-only and produce findings and drafts that people read. Then tickets and pull requests open automatically but a person merges or approves each one. Then low-risk, reversible changes, such as a patch to a non-production ring, run without approval. Only after a month of clean results do production rings widen.
Move to the next setting only when the log shows no change that a reviewer would have rejected. Cogent describes autonomy as staged in this way, starting with recommendations and review. Whatever the vendor offers, write your own widening criteria down before the trial starts.
## Separate who approves from who is notified
Approval and notification are different. An approver can stop a change; a person who is notified can only read about it afterward. Name both for each class of action.
A workable split: the owner of the asset approves changes to it, the security lead approves changes to controls such as firewall rules, and the change board is notified of reversible changes made inside an approved window. Where a platform writes into your ServiceNow change process, as Qualys describes, the approver is already named by the change type. Where it does not, the platform needs its own approver list, and that list needs the same review as any access list: removed when people move teams, and checked each quarter.
## Related pages
- [Guides](/guides/)
- [Ownership mapping: finding who can fix a finding](/guides/ownership-mapping/)
- [Automated vulnerability remediation: what an agent can fix without a human](/guides/what-an-agent-can-fix-without-a-human/)
- [Reading a vendor's vulnerability remediation claim](/guides/reading-a-vendors-remediation-claim/)
## Sources
- Cogent Security, autonomy levels: https://www.cogent.com/ai/autonomy-levels (read 10 Nov 2026)
- Onit Security, platform page: https://onit.security/platform/ (read 10 Nov 2026)
- Qualys, agentic AI page: https://www.qualys.com/apps/agentic-ai (read 10 Nov 2026)
- Tenable Patch Management: https://www.tenable.com/products/patch-management (read 10 Nov 2026)
- NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning: https://csrc.nist.gov/pubs/sp/800/40/r4/final (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/guides/how-approval-should-work/
---
# Ownership mapping decides how fast a finding moves, and it fails most often at the asset with no record
Guide, 14 Oct 2026, read 10 Nov 2026
**The short answer.** 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 on arrival, and Seemplicity reports unknown ownership at Hertz falling from 20% to 2% in six months. Both are vendor claims read 10 Nov 2026.
## What an owner means for a finding
An owner is the person or team that can approve and make a change to the asset. That is often not the person named in the configuration database. A host may be registered to the infrastructure team while an application team controls the software on it. A container image may belong to a platform team while the vulnerable package comes from a service team's dependency file.
Name the owner of the change, not the owner of the box. CISA BOD 22-01 makes the same point in federal terms: agency procedures must assign roles and responsibilities for executing remediation.
## Where platforms get ownership from
The vendor pages read describe several sources. Cogent shows an agent resolving an owner from a ServiceNow CMDB and checking Jira ticket history. Averlon traces a base image vulnerability to the Dockerfile and routes it to the team that owns that code. Maze states that agents infer the owner from commit history and code. Onit states that ownership is inferred from commit authorship, historical patterns and service maps, and re-resolved after reorganizations. Seemplicity states that it syncs owners and criticality from CMDBs.
| Source of ownership | Strength | Weak point |
| --- | --- | --- |
| CMDB record | Official, auditable | Stale after reorganizations; empty for new assets |
| Code owners and commit history | Close to who can change the code | Does not cover hosts and cloud resources |
| Cloud tags | Applied at creation | Missing on many resources; copied wrongly |
| Ticket history | Shows who actually closed similar work | Needs enough history |
| Service map | Links a service to a team | Needs upkeep |
## What happens after the owner is named
Naming is half the work. Backline states that it brings each remediation to the responsible people in Slack, Microsoft Teams and Jira, follows up, and escalates when nothing moves. Onit states that after assigning it nudges, escalates and tracks the work to closure. Seemplicity states that tickets are updated or expired as ephemeral resources change. Maze states a fix goes to a ticketing platform or coding agent, and the register records none found on 10 Nov 2026 for its follow-up after routing.
Ask each platform what it does at day 7 and day 14 of a ticket nobody has touched.
## Measure ownership with two numbers
Take both numbers from your ticket system before a trial and again at the end. If the platform cannot report them, you will not see whether ownership improved.
- Share of open findings with no owner. Seemplicity's Hertz example moved this from 20% to 2% (vendor-published case study).
- Bounce rate: tickets reassigned at least once, divided by tickets opened. Onit's figure of about half is its own field observation with no published method.
## Decide what happens to findings with no owner
Every mapping method leaves a residue: assets that no record claims. The residue is where findings age, because nobody is asked to act. Decide the rule before the platform meets the residue.
A workable rule has three steps. Assign a default owner by account, subscription or network segment, since someone pays for the account. Give the default owner a short window, such as seven days, to accept or pass the finding on. After the window, escalate to the manager of that group and record the escalation. Ask the platform whether it can run these three steps itself, and whether the log shows each one.
## Test the mapping on your own sample
Ownership accuracy is easy to measure and rarely measured. Take 30 findings from last month and write down the team that actually closed each. Run the same 30 through the platform's ownership step and compare.
Count three outcomes: right team, wrong team, and no answer. A platform that answers wrong creates a bounced ticket and a day of delay. A platform that says no answer sends the item to your default rule at no cost. Many buyers prefer the second behavior to the first, and the register records which platforms state that unknown is a possible answer. Onit states that an agent says unknown with the reason when evidence is missing.
## Related pages
- [Guides](/guides/)
- [Reading a vendor's vulnerability remediation claim](/guides/reading-a-vendors-remediation-claim/)
- [How approval should work when an agent changes production](/guides/how-approval-should-work/)
- [The remediation SLA that holds](/guides/the-remediation-sla-that-holds/)
## Sources
- Cogent Security, Discover: https://www.cogent.com/platform/discover (read 10 Nov 2026)
- Onit Security, platform page: https://onit.security/platform/ (read 10 Nov 2026)
- Seemplicity, Hertz case study: https://seemplicity.ai/resource/hertz-case-study/ (read 10 Nov 2026)
- Backline, owner post: https://backline.ai/blog/finding-and-chasing-the-owner-of-a-fix-in-jira-teams-or-slack/ (read 10 Nov 2026)
- CISA BOD 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities (archived copy): https://web.archive.org/web/2024/https://www.cisa.gov/news-events/directives/bod-22-01-reducing-significant-risk-known-exploited-vulnerabilities (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/guides/ownership-mapping/
---
# A remediation claim is worth what its method shows, so read the denominator, the clock and the customer first
Guide, 8 Oct 2026, read 10 Nov 2026
**The short answer.** 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. Backline states 5 weeks to 2 hours. Both are vendor claims read 10 Nov 2026. Check the denominator, the clock and the customer before using either.
## Ask three questions of every number
Remediation claims come as percentages, time reductions and ratios. Each hides three choices: what was counted, when the clock started and stopped, and who the customer was. A claim that states all three can be tested. A claim that states none is marketing copy, and the register labels it that way.
The denominator is the first thing to find. A 95% reduction of what: raw scanner output, critical findings, findings on internet-facing assets? The clock is second. Mean time to remediate can start at detection, at disclosure or at ticket creation, and end at deploy, at merge or at verified closure. The customer is third: size, stack and whether it is named.
## Four claims read for the register
The claims below are quoted as the vendors state them, and the third column notes what the page gives. All were read on 10 Nov 2026 and all are the vendor's claim unless marked.
| Vendor and claim | Customer | What the page gives |
| --- | --- | --- |
| Averlon: 110,000 critical and high issues, 3,400 tickets, 260 pull requests; mean time to remediate 45 days to 6 | Unnamed | Counts and a before and after; the register records no clock definition |
| Backline: average time to fix 5 weeks to 2 hours | Unnamed data-analytics company | A case study; the register records no clock definition |
| Cogent Security: 57.9% of 190 LiveCVEBench tasks, against 45.3% for two coding tools (third-party report) | Not a customer measure | Method notes: outbound network blocked, grading tests hidden, inference budgets differed |
| Seemplicity: unknown asset ownership 20% to 2% in six months | Hertz (named) | A named customer case study; the measure is ownership, not remediation time |
## Read the shape of the claim
- Named customers can be called. Unnamed ones cannot, and the register records that fact.
- A benchmark on a public task set can be repeated. A figure from a customer's private data cannot.
- An average over all customers includes the easy ones. Ask for the median and the range.
- A claim of time saved is not a claim of risk removed. Ask what happened to the findings that were not fixed.
- A homepage figure with no method on the page, such as a stated 90% faster remediation, is a headline. Ask for the method in writing.
## Turn the claim into a trial test
Every claim implies a test. If a vendor says mean time to remediate fell from 45 days to 6, ask for the definition, then measure the same quantity on a sample of your own findings before and during a trial. If it says a share of findings are not exploitable, take 20 of them and check the evidence shown. The guide on trial questions lists the tests by topic.
Where a page gives no method, the register says so. It does not fill the gap with an estimate.
## Know what a third-party label means
The register labels a fact third-party source when an outside party reported it. That label means the outside party published the statement, not that it measured the result. SiliconANGLE reports that Cogent's VR-1.1 passed 57.9% of 190 LiveCVEBench tasks, and notes the test was run by the vendor. SecurityWeek confirmed Astelia's $35 million seed and Series A, which is a funding fact, not a performance one.
Read the label with the content. A funding fact confirmed by an outside outlet is well supported. A performance figure reported by an outlet from a vendor's own test is the vendor's claim, carried by a second page.
## Keep a claims sheet
During evaluation, keep a sheet with one row per claim: the vendor, the figure, the page and date, the three answers (denominator, clock, customer), and the test you will run. Rows with no answers go to the bottom and stay out of the decision.
The sheet also gives you a record for procurement. When a contract names a figure, such as a reduction in findings, the row shows where it came from and what was agreed about its definition. Figures that appear only on a homepage should not appear in a contract without a written definition.
## Related pages
- [Guides](/guides/)
- [The remediation SLA that holds](/guides/the-remediation-sla-that-holds/)
- [Ownership mapping: finding who can fix a finding](/guides/ownership-mapping/)
- [Mean time to remediate, measured honestly](/guides/mean-time-to-remediate-measured-honestly/)
## Sources
- Averlon blog on automating remediation: https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues (read 10 Nov 2026)
- Backline case study: https://backline.ai/case-studies/five-weeks-to-under-a-day/ (read 10 Nov 2026)
- SiliconANGLE on Cogent VR-1.1, 3 Nov 2026: https://siliconangle.com/2026/11/03/exclusive-cogent-securitys-vr-1-1-model-outscores-claude-code-and-codex-on-vulnerability-repair/ (read 10 Nov 2026)
- Seemplicity, Hertz case study: https://seemplicity.ai/resource/hertz-case-study/ (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/guides/reading-a-vendors-remediation-claim/
---
# A remediation SLA holds when its clock starts at an event you can date and its tiers follow exploitation
Guide, 30 Oct 2026, read 10 Nov 2026
**The short answer.** 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 30-day SLA for every critical finding misses that. CISA BOD 22-01 sets two weeks for exploited CVEs assigned after 2021. Read 10 Nov 2026.
## Pick the start of the clock
Three clocks are in common use: from detection by your scanner, from public disclosure, and from ticket creation. They can differ by weeks. A finding disclosed on a Tuesday may reach your scanner the next week and your ticket queue the week after.
Use disclosure for exposure, since attackers use disclosure. Use ticket creation only for the team that receives the work. Report both, and label them.
## Tier by exploitation, not only by severity
Rapid7's Q3 2026 threat update reports 43 newly exploited high and critical vulnerabilities in the quarter, an average of three days from disclosure to exploitation, and exploitation inside 14 days for 80% and inside 30 days for 90% of the tracked set (vendor research, read 10 Nov 2026). A flat 30-day SLA covers 90% of that exploitation only after it has happened.
CISA BOD 22-01 shows a tiered model. Vulnerabilities in the Known Exploited Vulnerabilities catalog carry a default of two weeks if the CVE was assigned after 2021, and six months for older CVEs, with the default timelines open to adjustment in cases of grave risk. A private SLA can borrow the structure.
| Tier | Trigger | Example target |
| --- | --- | --- |
| Emergency | Listed as exploited, and the asset is reachable | Mitigate within days, fix within the next change window |
| Expedited | Public exploit or active scanning reported | Fix within 14 days |
| Standard | Severe but no exploitation reported | Fix within 30 to 60 days |
| Planned | Low exposure or compensating control in place | Fix in the normal release cycle, with the control recorded |
## Count the mitigation as a stop in the clock
Where a patch cannot ship in the window, a compensating control can stop the exposure while the fix waits. A SLA that counts only fixes will mark a mitigated finding as late. Write both into the policy: the finding is within SLA if exposure is blocked and the control is recorded with an expiry date.
Tenable states that patch policies can use different SLAs by criticality and exploitability. Zafran describes a workflow that opens a ServiceNow ticket, pushes a web application firewall rule and tracks the SLA. Rapid7 lists remediation projects and SLAs in its Essentials tier. These are vendor claims read on 10 Nov 2026.
## Report SLA as met, mitigated or breached
Three states are more honest than two. Met means fixed inside the window. Mitigated means exposure was blocked inside the window and the fix is scheduled. Breached means neither. Report the share in each state per tier, and the age of the oldest breached item. The weekly meeting should spend its time on that last list.
NIST SP 800-40 Rev. 4 treats patching as a planned preventive maintenance process rather than an emergency each time. An SLA with named tiers is how that plan appears in a policy.
## Write the exception path into the SLA
An SLA that has no exception path is broken on the first finding that cannot be fixed in time. Write the path in: who may accept the risk, for how long, on what evidence, and what ends the acceptance early.
BOD 22-01 itself requires agencies to establish internal validation and enforcement procedures. A private policy can do the same in one page: an approver by tier, a maximum acceptance period, an automatic review when a finding is added to the Known Exploited Vulnerabilities catalog, and a log the auditor can read. The exception then becomes a recorded state of the SLA, not a hole in it.
## Check the SLA against one real disclosure
Test the policy on a recent case. PHP2Shell was disclosed on 21 Oct 2026 and first exploitation was observed the same day, according to the CVE record read for this site, with the CISA catalog listing following on 26 Oct 2026. Under a flat 30-day SLA the finding would not have been late until late November, after exploitation and after the catalog listing.
Under the tiers above, the finding enters the emergency tier on the day the exploitation report appears, and the clock for mitigation starts then. Run your own policy against one real case each quarter. If the SLA would have judged you on time while an attacker was already inside the window, change the tier triggers.
## Related pages
- [Guides](/guides/)
- [Mean time to remediate, measured honestly](/guides/mean-time-to-remediate-measured-honestly/)
- [Reading a vendor's vulnerability remediation claim](/guides/reading-a-vendors-remediation-claim/)
- [Vulnerability ownership at scale: grouping, routing and expiry](/guides/vulnerability-ownership-at-scale/)
## Sources
- Rapid7, Q3 2026 Threat Update, 21 Oct 2026: https://www.rapid7.com/blog/post/tr-q3-2026-threat-update-attackers-exploiting-vulnerabilities-within-3-days/ (read 10 Nov 2026)
- CISA BOD 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities (archived copy): https://web.archive.org/web/2024/https://www.cisa.gov/news-events/directives/bod-22-01-reducing-significant-risk-known-exploited-vulnerabilities (read 10 Nov 2026)
- NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning: https://csrc.nist.gov/pubs/sp/800/40/r4/final (read 10 Nov 2026)
- Tenable Patch Management: https://www.tenable.com/products/patch-management (read 10 Nov 2026)
- Rapid7 Exposure Command: https://www.rapid7.com/products/command/exposure-management/ (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/guides/the-remediation-sla-that-holds/
---
# Mean time to remediate is honest when it reports a median, the open items and the clock it used
Guide, 12 Oct 2026, read 10 Nov 2026
**The short answer.** 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). All are unnamed or method-free claims read 10 Nov 2026. Report your own as a median, with open items counted at their age.
## Closed items alone flatter the number
The usual calculation averages the time to close items that were closed in a period. That leaves out every item still open. A team that closes ten easy findings in an hour and leaves one hard finding open for a year reports an average of one hour.
Add the open items at their current age, or report them separately as aged items. A good report has two lines: median time to remediate for items closed this quarter, and the count and age of items open beyond the SLA.
## Use a median and a percentile
Time to remediate has a long tail. Because of it, the mean is pulled up by a few very old items and can hide a typical week. The median shows the typical item. A 90th percentile shows the tail.
Report both by tier. A 4-day median for emergency items and a 40-day median for standard items says more than a 12-day mean across all of them.
| Measure | What it hides if used alone |
| --- | --- |
| Mean of closed items | Open items; the long tail |
| Median of closed items | The tail; the open items |
| 90th percentile of closed items | The typical case |
| Count and age of open items past SLA | How quickly easy items close |
## State the clock and the population
Say when the clock starts (disclosure, detection, ticket) and stops (merge, deploy, verified closure). Say which findings are in the population: all, critical and high only, or exploitable only. Moving from all findings to exploitable only can make mean time to remediate look worse, because the easy noise is gone, and that is a fair reading.
Vendor figures rarely say either. Averlon's example reports 45 days to 6 for an unnamed customer. Backline states more than two weeks to one hour for a Fortune 500 manufacturer it does not name, and 5 weeks to 2 hours for a data-analytics company. Vicarius states months to hours. Qualys cites a customer patching the most severe threats automatically in under 24 hours (Cintas). Only the last names its customer, and the register records a clock definition for none of them.
## A starting definition
Write the definition at the start of the report. When a platform is added, keep the definition the same so the before and after compare.
- Start: public disclosure date, or the date your scanner first saw the asset if later.
- Stop: verified closure, by rescan or version check, or recorded mitigation with an expiry date.
- Population: findings assigned to a tier above planned.
- Report: median, 90th percentile, and open items past SLA with their ages, per tier, per month.
## Read a before-and-after with care
A reduction from 45 days to 6 compares two periods, and many things differ between periods. Patch cycles, staffing, the mix of findings and the number of new disclosures all move the figure. A single quarter's change can come from a quiet quarter.
To trust a before-and-after, ask for at least two quarters on each side, the same population in both, and the same clock. Then measure your own baseline for the same length of time before the trial, so that the comparison is yours.
## Split the metric by who owns the delay
Mean time to remediate combines waiting and working. Waiting for an owner, waiting for approval, and waiting for a change window are different delays with different fixes. Working time is the engineering or operations effort.
Break the total into three segments: time to decide, time to assign and accept, and time to change and verify. Each has a different cure: evidence for the first, ownership mapping for the second, approval design and rollback for the third. A platform that shortens only one segment will move the total less than its demo suggests, and the segment view shows which one it moved.
Review the definition once a year. When tiers, scanners or the ticket system change, the clock can shift without anyone deciding it should, and a trend that looks like improvement may be a change in what is counted. A short note beside each chart, saying what was counted and when the definition last changed, prevents that.
## Related pages
- [Guides](/guides/)
- [Vulnerability ownership at scale: grouping, routing and expiry](/guides/vulnerability-ownership-at-scale/)
- [The remediation SLA that holds](/guides/the-remediation-sla-that-holds/)
- [What to ask in a vulnerability remediation platform trial](/guides/what-to-ask-in-a-remediation-platform-trial/)
## Sources
- Averlon blog on automating remediation: https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues (read 10 Nov 2026)
- Backline case study: https://backline.ai/case-studies/five-weeks-to-under-a-day/ (read 10 Nov 2026)
- Vicarius, patchless protection: https://www.vicarius.io/features/patchless-protection (read 10 Nov 2026)
- Qualys, Cintas case study: https://www.qualys.com/customers/success-stories/cintas-replaces-manual-patching-tasks-with-risk-based-from-qualys-enterprise-trurisk-platform (read 10 Nov 2026)
- CISA BOD 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities (archived copy): https://web.archive.org/web/2024/https://www.cisa.gov/news-events/directives/bod-22-01-reducing-significant-risk-known-exploited-vulnerabilities (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/guides/mean-time-to-remediate-measured-honestly/
---
# At scale, ownership work shifts from naming one owner to grouping findings so each owner gets few, complete tasks
Guide, 6 Nov 2026, read 10 Nov 2026
**The short answer.** 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 reports 110,000 issues becoming 3,400 tickets and then 260 pull requests. All are vendor claims read 10 Nov 2026, and grouping is the shared idea.
## Group by fix, not by finding
With thousands of owners and hundreds of thousands of findings, assigning findings one by one produces a ticket queue nobody can read. The reduction comes from grouping findings that one change closes. One base image upgrade closes every finding in that image. One library bump closes every CVE in that library.
Vendor pages describe the idea in their own terms. Zafran states that overlapping findings collapse into one fix routed to the right team, with an example of 700 findings in one OpenSSL ticket. Maze states that agents bundle proven-exploitable CVEs into single fixes. Averlon describes findings mapped to their source, a base image or dependency, and grouped rather than assigned individually.
## Route to the team that merges
Grouping only helps if the group reaches someone who can act. The route should end at a team with merge or change rights, in the tool that team already uses: a pull request in the repository, a ticket in the queue, a message in the channel.
Averlon states it creates a pull request plus a ticket for that pull request assigned to the code owner. Backline states it opens and maintains a ticket in the team's own Jira project. Zafran states it auto-assigns in Jira, Slack and ServiceNow.
## Expect reorganizations and short-lived assets
At scale, owners change every quarter and some assets live for hours. Two behaviors matter. The platform should re-resolve the owner when a reorganization changes the map; Onit states that it does. And it should close or expire tickets for assets that no longer exist; Seemplicity states that tickets are updated or expired as ephemeral resources change.
Ask both questions in a trial, and ask for the evidence: a ticket that moved owner after a change, and a ticket that expired.
| Scale problem | Control to look for | Vendor statement (vendor's claim, read 10 Nov 2026) |
| --- | --- | --- |
| Too many tickets | Grouping by fix | Averlon, Maze, Zafran |
| Wrong owner | Re-resolution after reorganization | Onit |
| Stale tickets | Expiry for ephemeral assets | Seemplicity |
| Silent tickets | Follow-up and escalation | Backline, Onit |
## Measure group size and group age
Track the median number of findings per task and the median age of open tasks. If the first number rises while the second falls, grouping is working. If the first rises and the second rises too, the groups are too large to approve, and reviewers are waiting on them.
## Check group size against review capacity
Grouping moves work from analysts to reviewers, so review capacity sets the limit. Averlon's example expects a developer to review each generated fix, at about 15 minutes per fix in its example. At that rate, 260 pull requests are 3,900 minutes, or 65 hours of review, across all owning teams.
That is a manageable load spread over many teams and a heavy one for a single team. Ask a platform to show the distribution: how many tasks per owner, and how many reviewers it expects. A grouped queue that lands on three people has only moved the bottleneck.
## Keep the owner's view short
An owner who receives a hundred items stops reading them. At scale, the owner's view should show a handful of tasks, each with its fix, its evidence and its deadline, and nothing else.
Ask each platform to show the screen or message an owner sees. Count the items, the clicks to act, and whether the fix is attached or has to be looked up. Cogent, Onit, Seemplicity and Zafran describe delivery into existing tools such as Jira, Slack, Teams and ServiceNow, so the owner does not need to log in elsewhere. The register records which tools each vendor names; match them to the tools your owners use.
Finally, plan for the platform being wrong. At scale some share of routed tasks will land with the wrong team. Count how often, make reassignment a single click for the receiving team, and feed each reassignment back into the ownership map. A platform that learns from reassignments, as Cogent and Onit describe for owner resolution, reduces the rate over time; ask to see the rate by month during a trial.
## Related pages
- [Guides](/guides/)
- [What to ask in a vulnerability remediation platform trial](/guides/what-to-ask-in-a-remediation-platform-trial/)
- [Mean time to remediate, measured honestly](/guides/mean-time-to-remediate-measured-honestly/)
- [Agentic vulnerability management, defined by what ships](/guides/agentic-vulnerability-management-defined-by-what-ships/)
## Sources
- Zafran, home page: https://www.zafran.io/ (read 10 Nov 2026)
- Maze, remediation: https://mazehq.com/solutions/remediation (read 10 Nov 2026)
- Averlon blog on automating remediation: https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues (read 10 Nov 2026)
- Backline, owner post: https://backline.ai/blog/finding-and-chasing-the-owner-of-a-fix-in-jira-teams-or-slack/ (read 10 Nov 2026)
- Onit Security, platform page: https://onit.security/platform/ (read 10 Nov 2026)
- Seemplicity, automated remediation: https://seemplicity.ai/automated-vulnerability-remediation/ (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/guides/vulnerability-ownership-at-scale/
---
# A trial answers seven questions, one per topic, and each needs a test on your own findings
Guide, 4 Oct 2026, read 10 Nov 2026
**The short answer.** 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. Qualys states a free trial for TruRisk Eliminate on pages read 10 Nov 2026.
## Set up the trial before the first call
Fix the data and the baseline first. Export a sample of 200 open findings that your team has already triaged, with the disposition each received. Record your current median time to decide, the share with no owner, and the number of tickets reassigned. The trial is a comparison against these, not against a demo.
Ask the vendor which integrations it needs and how long they take, since a trial that spends ten days on setup answers little about fixing.
## Seven tests, one per topic
The register groups its facts under seven topics. Each has a test.
| Topic | Test | Evidence that answers it |
| --- | --- | --- |
| Proves exploitability in your environment | Take 20 findings the platform dismissed and check each against your configuration | The evidence shown per dismissed finding, and whether you agree |
| Ships the fix | Ask for fixes on 10 findings of three types | Pull requests, patch jobs or rules you could apply, with test results |
| Finds the owner | Run 30 findings through ownership resolution | Share assigned to the right team on arrival |
| Speed on a new disclosure | Time a real disclosure during the trial | Minutes from disclosure to a list of your exposed assets |
| Agents you can shape | Change an approval rule and an agent behavior | The setting, the log entry and the undo |
| Works on the stack you have | Connect every scanner and ticketing tool you use | Named integrations working, not listed |
| Proof | Ask for a reference customer of your size and the method behind a headline figure | A call, and a written definition of the figure |
## Questions to put in writing
- Which of the findings in my sample would the platform close without a person, and under what approval setting?
- What does the platform do when it cannot determine exploitability or ownership, and where does that item go?
- Which actions does the agent take on my systems, with what permissions, and how are they revoked?
- Where is my data processed and stored, and is it used to train a model? Maze, for example, states it does not train or fine-tune models on customer code or findings and offers single-tenant hosting (vendor's claim, read 10 Nov 2026).
- What is the price basis? Maze states pricing by the size of cloud infrastructure and Vicarius by managed endpoint count; Rapid7 describes usage-based pricing by asset type. Most vendors in the register publish no price.
## Decide on the baseline, not the demo
At the end of the trial, repeat the baseline measures on the same sample. The useful results are numbers: minutes per finding, owner accuracy, findings removed with evidence you accepted, fixes you would merge. Write them down against the seven topics and compare with what the vendor's pages claimed.
Where the trial result and the vendor page disagree, the register is the place to send the source. Corrections are accepted at editor@automatedvulnerabilityremediation.com.
## Agree the exit before you start
Write the pass and fail thresholds before the trial begins. For example: at least 80% of dismissed findings have evidence you accept, at least 70% of tickets reach the correct owner on arrival, and every approved change appears in the log with a working undo. The numbers are yours; the point is that they exist before the demo.
Also agree what happens to your data at the end. Ask for deletion in writing, and for the list of systems the platform was given access to, so each credential can be revoked on the last day.
## Watch for what a trial cannot show
Two weeks will not show a quarterly patch cycle, a reorganization, or an audit. Ask for references that cover them, and ask what the vendor has seen go wrong in similar environments.
A trial also cannot show support quality after the contract. Read the documentation during the trial, since it shows what the product does when the sales team is not in the room. Where documentation is behind a login, as the register records for one vendor, ask for read access for the trial period.
## Related pages
- [Guides](/guides/)
- [Agentic vulnerability management, defined by what ships](/guides/agentic-vulnerability-management-defined-by-what-ships/)
- [Vulnerability ownership at scale: grouping, routing and expiry](/guides/vulnerability-ownership-at-scale/)
- [AI vulnerability management in the weekly remediation meeting](/guides/ai-vulnerability-management-in-the-weekly-meeting/)
## Sources
- Qualys, TruRisk Eliminate: https://www.qualys.com/apps/trurisk-eliminate/ (read 10 Nov 2026)
- Maze, cloud platform page: https://mazehq.com/platform/cloud (read 10 Nov 2026)
- Vicarius, pricing: https://www.vicarius.io/pricing (read 10 Nov 2026)
- Rapid7 Exposure Command pricing: https://www.rapid7.com/products/command/pricing/ (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/guides/what-to-ask-in-a-remediation-platform-trial/
---
# Agentic vulnerability management is defined by the artifact an agent delivers, since the word agent alone describes nothing
Guide, 8 Nov 2026, read 10 Nov 2026
**The short answer.** 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. Fourteen platforms were read on 10 Nov 2026, and the register lists the output each one states.
## The word agent covers three levels of work
Vendor pages use agent for very different things. At the first level an agent answers questions, as in a chat assistant over exposure data; Qualys describes ROCky and Seemplicity describes Seema in this way. At the second an agent investigates: it gathers evidence on one finding and returns a determination, as Onit's Reachability Agent and Seemplicity's AI Analysts are described. At the third an agent acts: it changes something in a repository, a patch tool or a firewall.
Only the third level shortens the time to remediate by itself. The first two shorten the time to decide. All three are useful, and a buyer should know which one a page is describing.
## Define by the artifact
A working definition: agentic vulnerability management is the use of software agents to carry a finding from scanner output to a closed, verified state, with a human setting limits and approving what crosses them. The measure of how far a platform goes is the last artifact it produces without a person writing it.
| Last artifact produced | Platforms stating it (vendor's claim, read 10 Nov 2026) |
| --- | --- |
| Determination with evidence | Astelia, Maze, Onit |
| Scoped ticket with plan | Onit, Rapid7, Seemplicity, Zafran |
| Rule or configuration change | Astelia, Seemplicity, Zafran |
| Patch job | Qualys, Tenable, Vicarius |
| Pull request | Averlon, Backline, Rival |
| Fix executed through existing tools, from assisted to autonomous | Cogent Security |
## What does not change the definition
A natural-language interface is not an agent that acts. A dashboard that summarizes a queue is not remediation. A mean time to remediate claim is not an artifact. The register keeps these apart by recording what each page says is produced, with the quotation.
Some platforms are placed in more than one row, because they produce several outputs. The table shows the last artifact stated on the pages read, and the profiles carry the full lists.
## Check it against the scanner
Agentic platforms in the register sit after the scanner. Astelia states it sits above the scanners the customer already runs. Backline states it ingests findings from existing production scanners. Qualys, Rapid7 and Tenable products appear among Seemplicity's named integrations. The scanner vendors in the register, Qualys, Rapid7 and Tenable, describe their own agents in the same terms: Qualys names Agent Insta, Val, Sara and Nyra, and Tenable names Hexa AI.
That placement is why the register treats ownership, approval and verification as first-order topics. The scanner has already done the finding. What remains is the work.
## Questions the definition raises for a buyer
Each question has a place in the register: the fix, the owner, the agent controls and the stack topics hold the sourced answers where a vendor has published them.
- Which artifact does the platform deliver for the findings that make up most of my backlog?
- How much of the path from finding to closed state is automated, and where does a person step in?
- What does the agent need to read, and what does it need to write, in my systems?
- How does the platform check that the fix worked?
- What happens to a finding the agent cannot handle?
## Why the label keeps moving
Vendors name the category differently: exposure management, remediation operations, autonomous exposure remediation, agentic exposure management. Backline says Gartner named autonomous exposure remediation in June 2026, and Zafran cites the same category as one it was named a Sample Vendor for in Gartner's report published 11 Sep 2026, as the vendors report it. Maze says it fits no existing category.
The labels follow marketing and analyst cycles. The artifacts do not. A pull request, a patch job and a rule are the same things under any heading. For a buyer the stable approach is to read the artifact column and ignore the heading.
One more test applies to any page. Look for the noun that follows the verb. A page that says the platform remediates, fixes or resolves, with no noun after it, is describing an aim. A page that says it opens a pull request, runs a patch job or pushes a rule is describing a product. The register keeps the noun and the quotation, and records none found where a page names neither.
## Related pages
- [Guides](/guides/)
- [AI vulnerability management in the weekly remediation meeting](/guides/ai-vulnerability-management-in-the-weekly-meeting/)
- [What to ask in a vulnerability remediation platform trial](/guides/what-to-ask-in-a-remediation-platform-trial/)
- [How to measure a vulnerability backlog in hours, not findings](/guides/how-to-measure-a-backlog/)
## Sources
- Qualys, agentic AI page: https://www.qualys.com/apps/agentic-ai (read 10 Nov 2026)
- Onit Security, AI agents in vulnerability management: https://onit.security/blog/ai-agents-vulnerability-management/ (read 10 Nov 2026)
- Astelia, AI information page: https://www.astelia.io/ai-info-page (read 10 Nov 2026)
- Seemplicity, integrations: https://seemplicity.ai/integrations/ (read 10 Nov 2026)
- Tenable Hexa AI: https://www.tenable.com/products/tenable-one/capabilities/hexa-ai (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/guides/agentic-vulnerability-management-defined-by-what-ships/
---
# With agents in the loop, the weekly remediation meeting should review decisions and exceptions, not the whole queue
Guide, 9 Nov 2026, read 10 Nov 2026
**The short answer.** 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. Rapid7's Q3 2026 report gives three days as the average disclosure-to-exploitation time.
## What the meeting used to be
The classic remediation meeting walks a list sorted by severity. Each item gets a name, a status and a promise. Most of the hour goes to items that will not move this week, and the items that will move are decided before the meeting by whoever has the time.
With agents doing the first pass, the list is shorter and the discussion can change. The meeting no longer needs to read findings. It needs to read decisions.
## A five-item agenda
The spot check is the one that keeps the arrangement honest. If the platform dismissed a finding as not exploitable, someone reads the evidence and agrees or disagrees. A disagreement is recorded and fed back to the vendor or to the policy.
- Newly exploited this week: items added to the Known Exploited Vulnerabilities catalog or reported exploited by a vendor, and whether each has an exposed asset. Rapid7's Q3 2026 report puts the average at three days from disclosure to exploitation, so this item cannot wait for the next cycle.
- Waiting for approval: changes the agents have proposed that need a person, oldest first, with the evidence the agent attached.
- Owner-less or bounced: findings with no owner or reassigned more than once, with the cause.
- Mitigations due to expire: controls recorded with an expiry date that falls before the next meeting.
- Spot check: five decisions the agents made alone, chosen at random, read in full.
## Bring four numbers
Bring the count of open items past SLA by tier, the median time to decide, the share removed before analysis with evidence, and the number of approvals waiting. The calculator on this site converts the first into hours, which tells the room whether the team can clear it by hand or needs the agents to take more. The guide on honest mean time to remediate lists the definitions.
## Keep the authority with people
Agents propose and people approve what crosses the limits. CISA BOD 22-01 requires agencies to assign roles and responsibilities and to set internal validation and enforcement procedures. The same structure applies in a private company: a named person approves each class of change, and the meeting is where that person is held to the date.
NIST SP 800-40 Rev. 4 frames patching as preventive maintenance with a plan. The meeting is where the plan is checked against what happened.
## Keep the minutes short and dated
Four lists are enough. The minutes become the evidence trail for the exceptions in an audit, and they show whether the agents are improving. A meeting that produces no disagreements for a quarter is either working very well or not reading the decisions.
- Decisions made: finding, decision, approver, date.
- Owners assigned: team and due date.
- Mitigations accepted: control, expiry date, review trigger.
- Disagreements with an agent's decision, and what was changed in the policy.
## Adjust the meeting as trust grows
In the first month of agent use, the spot check should cover many decisions, perhaps ten a week, and the meeting should run longer. If the spot checks agree with the agents, reduce to five, then to three. If a spot check finds a wrong dismissal, widen again and change the policy that allowed it.
Keep a running count of agreements and disagreements. It is a plain measure of trust that a CISO can read, and it gives the team a reason to widen approval settings that is based on its own results rather than on a vendor's page.
Finally, write down what the meeting decided not to do. A list of items deliberately left open, with the reason and the date to revisit, is the most useful page in an audit and the one most often missing. It also shows new attendees that the queue is managed rather than ignored.
## Related pages
- [Guides](/guides/)
- [How to measure a vulnerability backlog in hours, not findings](/guides/how-to-measure-a-backlog/)
- [Agentic vulnerability management, defined by what ships](/guides/agentic-vulnerability-management-defined-by-what-ships/)
- [Automated vulnerability remediation: what an agent can fix without a human](/guides/what-an-agent-can-fix-without-a-human/)
## Sources
- Rapid7, Q3 2026 Threat Update, 21 Oct 2026: https://www.rapid7.com/blog/post/tr-q3-2026-threat-update-attackers-exploiting-vulnerabilities-within-3-days/ (read 10 Nov 2026)
- CISA BOD 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities (archived copy): https://web.archive.org/web/2024/https://www.cisa.gov/news-events/directives/bod-22-01-reducing-significant-risk-known-exploited-vulnerabilities (read 10 Nov 2026)
- NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning: https://csrc.nist.gov/pubs/sp/800/40/r4/final (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/guides/ai-vulnerability-management-in-the-weekly-meeting/
---
# 32 terms a reader meets, each with a sourced example
Glossary, read 10 Nov 2026
**The short answer.** The glossary defines 32 terms used in vulnerability remediation, from backlog and compensating control to risk acceptance and mean time to remediate. Each entry gives a short definition, a dated example with its source, and the read date of 10 Nov 2026. Terms are listed alphabetically.
- [Approval gate](#approval-gate)
- [Attack path](#attack-path)
- [Autonomy level](#autonomy-level)
- [Backlog](#backlog)
- [Base image](#base-image)
- [Choke point](#choke-point)
- [CMDB](#cmdb)
- [CVE](#cve)
- [Deduplication](#deduplication)
- [Exception](#exception)
- [Exploitability](#exploitability)
- [Fix group](#fix-group)
- [Fix verification](#fix-verification)
- [Human in the loop](#human-in-the-loop)
- [Infrastructure as code](#infrastructure-as-code)
- [KEV](#kev)
- [MCP server](#mcp-server)
- [Mean time to remediate](#mean-time-to-remediate)
- [Ownership resolution](#ownership-resolution)
- [Pull request remediation](#pull-request-remediation)
- [Reachability](#reachability)
- [Regression test](#regression-test)
- [Remediation](#remediation)
- [Remediation agent](#remediation-agent)
- [Ring deployment](#ring-deployment)
- [Rollback](#rollback)
- [Runtime context](#runtime-context)
- [SBOM](#sbom)
- [SLA](#sla)
- [Ticket bounce](#ticket-bounce)
- [Time to exploit](#time-to-exploit)
- [Zero-day](#zero-day)
## Approval gate
An approval gate is a point where an agent stops and waits for a person to approve before it acts. Gates can be set per action type, severity or asset sensitivity. The record of who approved what, with the evidence shown, is what an auditor reads later.
Example: Onit states a human approval gate on every agent action, with an audit trail and one-step reversal, for both remediations and mitigations (vendor's claim, read 10 Nov 2026). ([source](https://onit.security/platform/), read 10 Nov 2026)
## Attack path
An attack path is a chain of steps an attacker could take from an entry point to a valuable asset, passing through vulnerabilities, misconfigurations and permissions. Paths help choose which fix breaks the most routes, instead of fixing findings one at a time.
Example: Astelia describes attack path visualization to critical assets through network controls and open ports (vendor's claim, read 10 Nov 2026). ([source](https://www.astelia.io/platform), read 10 Nov 2026)
## Autonomy level
An autonomy level is the amount of independence an agent is given, from recommending only, through acting with approval, to acting alone inside set limits. Teams usually move up the levels over weeks as logged results show the agent's decisions are ones they would have made.
Example: Cogent describes staged autonomy: start with recommendations and review, then expand, with high-impact changes requiring human approval and an audit trail (vendor's claim, read 10 Nov 2026). ([source](https://www.cogent.com/ai/autonomy-levels), read 10 Nov 2026)
## Backlog
A backlog is the set of open vulnerability findings that a team has detected and not yet fixed, mitigated, accepted or dismissed. Its size in findings matters less than its size in analyst hours, which depends on minutes per finding and how many findings are duplicates of one fix.
Example: Averlon describes a customer example with 110,000 critical and high issues, 3,400 tickets and 260 pull requests; the customer is unnamed and the figures are the vendor's claim, read 10 Nov 2026. ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
## Base image
A base image is the starting layer of a container image, such as an operating system layer. A vulnerability in it appears in every image built on it. Fixing the base image once can close hundreds of findings, which makes it a natural fix group.
Example: Averlon says it traces a base image vulnerability to the Dockerfile and routes it to the team that owns it (vendor's claim, read 10 Nov 2026). ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
## Choke point
A choke point is a place where many attack paths pass through, such as one gateway, one account or one shared service. Applying a control or fix at a choke point can break many paths with one change, which makes it a cheap place to spend effort when no patch exists yet.
Example: Zafran describes applying a compensating control at the choke point of an attack chain, with a web application firewall rule as the example (vendor's claim, read 10 Nov 2026). ([source](https://www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration-with-google-threat-intelligence), read 10 Nov 2026)
## CMDB
A CMDB, or configuration management database, records assets and their relationships, often with an owner and criticality. It is the usual source for ownership, and the usual source of errors when it falls out of date after reorganizations or when cloud assets appear without a record.
Example: Seemplicity states that it identifies owners and criticality by syncing with CMDBs (vendor's claim, read 10 Nov 2026). ([source](https://seemplicity.ai/automated-vulnerability-remediation/), read 10 Nov 2026)
## CVE
A CVE is a public identifier for a specific vulnerability, in the form CVE-YEAR-NUMBER, assigned by a CVE Numbering Authority. The identifier is the key that links scanner findings, advisories, exploitation reports and patches. Not every exposure has one when it first appears.
Example: The Linux kernel CNA published CVE-2026-98432, a TCP use-after-free rated CVSS 9.8, on 15 Oct 2026, and Averlon published a response write-up on 2 Nov 2026. ([source](https://www.averlon.ai/blog/cve-2026-98432-linux-kernel-tcp-use-after-free), read 10 Nov 2026)
## Deduplication
Deduplication merges findings that describe the same flaw on the same asset when several scanners report it. It reduces the count without changing risk. It is the cheapest reduction in a backlog and should be checked before any claim of findings removed by analysis.
Example: Maze states that it pulls and deduplicates findings from the scanners a customer already runs (vendor's claim, read 10 Nov 2026). ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
## Exception
An exception is a finding allowed to stay outside the normal SLA, with an approver, a reason and a review date. Exceptions should be few, written down and visible in the weekly meeting. A growing exception list shows a process problem that no scanner will fix.
Example: The PHP advisory for PHP2Shell lists an interim step, setting memory_limit to -1, and states it is not complete; an exception that relies on it should say so and carry a date to upgrade. ([source](https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w), read 10 Nov 2026)
## Exploitability
Exploitability is whether a vulnerability can be used against a specific system, given its version, configuration, exposure and controls. It differs from severity, which describes the flaw in general. A critical flaw on an unreachable service can be low in exploitability for that environment.
Example: Maze defines a vulnerability as exploitable relative to the customer's own configuration, controls and context, not by CVSS or exploit-in-the-wild status (vendor's claim, read 10 Nov 2026). ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
## Fix group
A fix group is a set of findings that one change closes, such as every CVE in a base image or a library version. Grouping by fix turns thousands of findings into a few hundred tasks, and it is how remediation platforms cut ticket volume.
Example: Zafran gives an example of 700 findings collapsing into a single OpenSSL upgrade ticket routed to the Platform team (vendor's claim, read 10 Nov 2026). ([source](https://www.zafran.io/), read 10 Nov 2026)
## Fix verification
Fix verification checks that a vulnerability is gone after a change, by rescan, version comparison or an exploit re-check. A closed ticket is not verification, because the ticket records intent and not the state of the system. NIST SP 800-40 Rev. 4 lists verifying installation among the steps of patch management.
Example: Qualys says it verifies that the vulnerability is fixed, rather than only the ticket closed, and rolls back automatically if a deployment causes issues (vendor's claim, read 10 Nov 2026). ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
## Human in the loop
Human in the loop means a person reviews or approves an agent's step before it takes effect. It is a design choice, not a fault. The useful questions are where in the path the person sits and how many items they must review in a week.
Example: Astelia's example workflow leaves a drafted ticket and firewall rule in an approval queue waiting for a human click (vendor's claim, read 10 Nov 2026). ([source](https://www.astelia.io/post/closing-the-exposure-loop), read 10 Nov 2026)
## Infrastructure as code
Infrastructure as code defines cloud resources in files, such as Terraform, Pulumi or Helm charts. A misconfiguration fixed in the file stays fixed on the next deployment, which is why remediation tools open pull requests against these files instead of editing the live resource.
Example: Averlon states its fix actions cover container images, Terraform and Pulumi infrastructure as code, and Kubernetes Helm charts (vendor's claim, read 10 Nov 2026). ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
## KEV
KEV is CISA's Known Exploited Vulnerabilities catalog: CVEs with reliable evidence of active exploitation. Under BOD 22-01, federal agencies must remediate listed items by the due date. Private teams often use it as the trigger for the emergency tier of an SLA.
Example: On 30 Oct 2026, CVE-2026-111357 and CVE-2026-118527, Ivanti Connect Secure flaws, were added to CISA's KEV catalog on evidence of active exploitation, as Rapid7 reported. ([source](https://www.rapid7.com/blog/post/etr-additional-ivanti-connect-secure-zero-days-exploited-in-the-wild-cve-2026-111357-cve-2026-118527/), read 10 Nov 2026)
## MCP server
An MCP server exposes a product's data and actions to AI assistants through the Model Context Protocol. For remediation tools it lets a customer connect its own language model and build workflows over the product's findings, subject to the permissions it grants.
Example: Tenable says its Hexa AI MCP server lets customers bring their own models and build custom workflows over Tenable tools (vendor's claim, read 10 Nov 2026). ([source](https://www.tenable.com/products/tenable-one/capabilities/hexa-ai), read 10 Nov 2026)
## Mean time to remediate
Mean time to remediate is the average time from a defined start, such as disclosure or detection, to a defined end, such as verified closure. It misleads when it counts only closed items, so a median, a 90th percentile and the age of open items should accompany it.
Example: Averlon states a customer's mean time to remediate fell from 45 days to 6 days; the customer is unnamed and the page gives no clock definition (vendor's claim, read 10 Nov 2026). ([source](https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues), read 10 Nov 2026)
## Ownership resolution
Ownership resolution is the step that decides which team can change the asset behind a finding. Sources include configuration databases, code owners, commit history, cloud tags and ticket history. A wrong answer produces a bounced ticket; an honest unknown can go to a default owner.
Example: Cogent's Discover page shows an agent resolving an asset owner from a ServiceNow CMDB and checking Jira ticket history (vendor's claim, read 10 Nov 2026). ([source](https://www.cogent.com/platform/discover), read 10 Nov 2026)
## Pull request remediation
Pull request remediation means an agent writes a code or configuration change and opens it as a pull request in the repository for review and merge. It fits dependency, container image and infrastructure-as-code findings, and keeps rollback inside the team's normal version control.
Example: Backline states that each remediation includes a plan and a ready-to-review pull request linked to the originating findings, and that existing unit tests run before delivery (vendor's claim, read 10 Nov 2026). ([source](https://backline.ai/product/), read 10 Nov 2026)
## Reachability
Reachability asks whether an attacker can get to the vulnerable code or service. Network reachability looks at routes and rules to the host. Code reachability looks at whether the application calls the vulnerable function. A finding can be present, and still not reachable.
Example: Onit describes a Reachability Agent that returns a determination per asset (reachable, restricted, internal, not reachable, unknown) with the path or the blocker as evidence (vendor's claim, read 10 Nov 2026). ([source](https://onit.security/blog/reachable-vulnerabilities/), read 10 Nov 2026)
## Regression test
A regression test checks that a fixed flaw stays fixed. When an agent writes a fix, a regression test written with it fails if a later change reopens the flaw. It is part of the evidence that a fix is more than a one-time edit.
Example: SiliconANGLE reports that Cogent's VR-1.1 model leaves regression tests that fail if a later code change reopens the flaw (third-party source, read 10 Nov 2026). ([source](https://siliconangle.com/2026/11/03/exclusive-cogent-securitys-vr-1-1-model-outscores-claude-code-and-codex-on-vulnerability-repair/), read 10 Nov 2026)
## Remediation
Remediation is the work that ends a vulnerability's exposure: applying a patch, changing a configuration, removing a component, or adding a control that blocks the path. It includes verifying that the change worked. Closing a ticket is not remediation unless the exposure is checked.
Example: Rapid7 reported on 2 Nov 2026 that Ivanti had released fixes for all three Ivanti Connect Secure vulnerabilities in an exploited chain, after the first fix on 13 Oct 2026 left the privilege escalation unpatched. ([source](https://www.rapid7.com/blog/post/etr-additional-ivanti-connect-secure-zero-days-exploited-in-the-wild-cve-2026-111357-cve-2026-118527/), read 10 Nov 2026)
## Remediation agent
A remediation agent is software, usually driven by a language model, that carries out one or more steps of fixing a finding, such as investigating, planning, writing a change or checking it. Vendors ship ready-made agents, and some let customers build their own.
Example: Backline names four vendor-built agents: Analyst, Planner, Coder and Verifier, with the Verifier validating every fix through testing (vendor's claim, read 10 Nov 2026). ([source](https://backline.ai/), read 10 Nov 2026)
## Ring deployment
Ring deployment rolls a change out in stages: a small test group first, then wider groups as health holds. It limits the damage of a bad patch. Platforms that deploy patches may pick the ring by a confidence rating for the patch.
Example: Qualys describes patch reliability scoring that sends high-confidence patches zero-touch, medium ones through staged rings and low ones to a manual change advisory board (vendor's claim, read 10 Nov 2026). ([source](https://www.qualys.com/apps/agentic-ai), read 10 Nov 2026)
## Rollback
Rollback returns a system to its state before a change. For an agent that deploys patches it is the safety net: a team should be able to trigger it, and the platform should trigger it on its own when health checks fail. Test it in a trial before relying on it.
Example: Tenable says Patch Management lets teams schedule, pause or roll back deployments under policy-based autonomous patching (vendor's claim, read 10 Nov 2026). ([source](https://www.tenable.com/products/patch-management), read 10 Nov 2026)
## Runtime context
Runtime context is information about what is running on an asset now: loaded libraries, open ports, active processes and effective configuration. It shows whether a vulnerable component is in use, which a static scan of installed packages cannot show. It is the main input for judging exploitability in a particular environment, and the least often shown to the customer.
Example: Maze states that it gathers runtime context without installing sensors (vendor's claim, read 10 Nov 2026). ([source](https://mazehq.com/platform/cloud), read 10 Nov 2026)
## SBOM
An SBOM, or software bill of materials, lists the components inside a piece of software. Matching a new advisory to SBOMs shows which products contain the flawed component before a scanner has a signature for it. The match depends on the SBOMs being current, so their upkeep is part of the cost.
Example: Astelia says its Hunter agent checks new and zero-day vulnerabilities against the SBOM before scanners detect them (vendor's claim, read 10 Nov 2026). ([source](https://www.astelia.io/use-cases/deploy-astelia-agents), read 10 Nov 2026)
## SLA
A remediation SLA is a time limit to fix or mitigate a finding, set by tier. It needs a stated clock start, such as disclosure or ticket creation, and a stated end, such as verified closure. Tiers by exploitation status hold up better than tiers by severity alone.
Example: CISA BOD 22-01 sets default remediation timelines for federal agencies of two weeks for known exploited vulnerabilities with CVEs assigned after 2021, and six months for older CVEs. ([source](https://web.archive.org/web/2024/https://www.cisa.gov/news-events/directives/bod-22-01-reducing-significant-risk-known-exploited-vulnerabilities), read 10 Nov 2026)
## Ticket bounce
A ticket bounce is a remediation ticket sent back or reassigned because it reached the wrong owner. The bounce rate, tickets reassigned divided by tickets opened, is a direct measure of ownership mapping and is worth tracking before and after any tool is added.
Example: Onit reports from its own field observation that roughly half of remediation tickets bounce because the owner is wrong on arrival; no method is published (vendor's claim, read 10 Nov 2026). ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
## Time to exploit
Time to exploit is the interval between public disclosure of a vulnerability and the first observed exploitation. Averages hide a spread: some flaws are exploited before disclosure and others never. Shorter windows push teams to tier SLAs by exploitation status.
Example: Rapid7's Q3 2026 report puts the average at three days, with 71% of tracked exploitation in the first seven days, 80% within 14 and 90% within 30. ([source](https://www.rapid7.com/blog/post/tr-q3-2026-threat-update-attackers-exploiting-vulnerabilities-within-3-days/), read 10 Nov 2026)
## Zero-day
A zero-day is a vulnerability exploited, or exposed to exploitation, before a fix is available. Defenders have no patch and must rely on detection and controls. How fast a team can list its exposed assets decides how long it works blind.
Example: PHP2Shell leaked on 20 Oct 2026, drew exploit attempts overnight and was patched about 18 hours after the leak, according to Onit's 23 Oct 2026 write-up. ([source](https://onit.security/blog/zero-day-response/), read 10 Nov 2026)
## Related pages
- [31 questions answered](/faq/)
- [News](/news/)
- [Remediation Register: the data, downloadable](/datasets/)
- [How the register works, and what it leaves out](/method/)
## Sources
- https://onit.security/platform/ (read 10 Nov 2026)
- https://www.astelia.io/platform (read 10 Nov 2026)
- https://www.cogent.com/ai/autonomy-levels (read 10 Nov 2026)
- https://www.averlon.ai/blog/automating-remediation-application-infrastructure-security-issues (read 10 Nov 2026)
- https://www.zafran.io/resources/zafran-launches-attack-chain-killswitch-in-collaboration-with-google-threat-intelligence (read 10 Nov 2026)
- https://seemplicity.ai/automated-vulnerability-remediation/ (read 10 Nov 2026)
- https://www.averlon.ai/blog/cve-2026-98432-linux-kernel-tcp-use-after-free (read 10 Nov 2026)
- https://mazehq.com/platform/cloud (read 10 Nov 2026)
- https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w (read 10 Nov 2026)
- https://www.zafran.io/ (read 10 Nov 2026)
- https://www.qualys.com/apps/agentic-ai (read 10 Nov 2026)
- https://www.astelia.io/post/closing-the-exposure-loop (read 10 Nov 2026)
- https://www.rapid7.com/blog/post/etr-additional-ivanti-connect-secure-zero-days-exploited-in-the-wild-cve-2026-111357-cve-2026-118527/ (read 10 Nov 2026)
- https://www.tenable.com/products/tenable-one/capabilities/hexa-ai (read 10 Nov 2026)
- https://www.cogent.com/platform/discover (read 10 Nov 2026)
- https://backline.ai/product/ (read 10 Nov 2026)
- https://onit.security/blog/reachable-vulnerabilities/ (read 10 Nov 2026)
- https://siliconangle.com/2026/11/03/exclusive-cogent-securitys-vr-1-1-model-outscores-claude-code-and-codex-on-vulnerability-repair/ (read 10 Nov 2026)
- https://backline.ai/ (read 10 Nov 2026)
- https://www.tenable.com/products/patch-management (read 10 Nov 2026)
- https://www.astelia.io/use-cases/deploy-astelia-agents (read 10 Nov 2026)
- https://web.archive.org/web/2024/https://www.cisa.gov/news-events/directives/bod-22-01-reducing-significant-risk-known-exploited-vulnerabilities (read 10 Nov 2026)
- https://onit.security/blog/zero-day-response/ (read 10 Nov 2026)
- https://www.rapid7.com/blog/post/tr-q3-2026-threat-update-attackers-exploiting-vulnerabilities-within-3-days/ (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/glossary/
---
# What changed in the last 90 days
News, read 10 Nov 2026
**The short answer.** 17 dated items from 2 Sep to 18 Nov 2026 cover launches, research and acquisitions among the profiled platforms, such as Cogent Security acquiring Specular on 10 Nov 2026. Each item links the original announcement, and items are listed newest first by date, not by importance.
## Maze releases a free read only checker for the Java4Shell JDK flaw
18 Nov 2026. Maze published java4shell-check on 18 Nov 2026, a free open source, read only tool that assesses whether CVE-2026-114938 is exploitable on the JVMs an organization runs. The flaw is a heap out of bounds write in OpenJDK's AVX-512 Base64 decoder, with fixes released 17 Nov 2026.
Maze's write-up says exposure needs three conditions together: an affected JDK (for example 17.0.6 through 17.0.21, 21 through 21.0.13, 25 through 25.0.5 and 27 through 27.0.1 and builds derived from them), an x86-64 CPU with AVX-512 VBMI, and the Base64 intrinsic enabled, which it is by default. Maze says ARM64, OpenJ9 and standard Java 8 and 11 builds do not run the vulnerable code.
The tool runs where the JVMs run, sends nothing to other services and changes nothing. Maze suggests handing the repository to a coding agent with read only credentials, and states that a patched JDK on disk does not fix a JVM that is already running, so each JVM must be restarted after patching.
Maze reports a CVSS 4.0 rating of 9.2, credits the finder as Calif, and says no exploitation in the wild had been reported as of 18 Nov 2026. The OpenJDK advisory of 17 Nov 2026 lists the flaw as CVE-2026-114938 in hotspot/compiler. Product claims about the checker are Maze's.
Source: [mazehq.com](https://mazehq.com/blog/java4shell), read 19 Nov 2026.
## Cognizant joins the Qualys mROC Alliance for managed remediation services
18 Nov 2026. Qualys announced on 18 Nov 2026 that Cognizant has joined its Global mROC Alliance and will pair Cyber Vulnerability Management services with Qualys ETM and TruRisk Eliminate. Qualys says Cognizant will package four mROC services built on ETM.
The release, datelined Foster City, describes a three step operating model: detection with Qualys InstaScan, prioritization with Qualys Agent Val, which validates which vulnerabilities are exploitable in a client environment, and autonomous remediation with TruRisk Eliminate with TruConfidence. Qualys says the remediation step accounts for existing security controls, selects a patch, mitigation or isolation, verifies the fix and rolls back if system health declines.
Qualys states that on November's Patch Tuesday InstaScan delivered 90 percent of detections within minutes of disclosure, and that of 48,172 vulnerabilities disclosed in 2025 its Threat Research Unit found 357 (0.74 percent) confirmed remotely exploitable and actively weaponized. These are vendor figures.
Cognizant will work within each client's existing tools, change windows and approval processes, agree scope with application owners, and phase in automation starting with low risk systems. The four services span cyber risk quantification and advisory, onboarding and integration, managed risk monitoring and managed risk remediation. Vishal Salvi of Cognizant is quoted in the release.
Source: [www.qualys.com](https://www.qualys.com/company/newsroom/news-releases/usa/cognizant-joins-qualys-global-mroc-alliance-deliver-managed-risk-operations-frontier-ai-era), read 19 Nov 2026.
## Zafran announces Offensive Validation for its exposure platform
18 Nov 2026. Zafran announced Offensive Validation on 18 Nov 2026 as a new part of its Autonomous Exposure Prevention platform. AI agents test an environment using the context in Zafran's Exposure Graph, to confirm which known findings an attacker can use and to look for unknown exposures.
Zafran says the feature completes a cycle of assess, validate, fix and verify. Each proven exposure is routed to the relevant owner with a fix that can be tested and verified in one click, and every result feeds back into the Exposure Graph.
The announcement says testing is narrowed by the graph, which maps assets, vulnerabilities, security controls and the paths between them, so agents test the short list an attacker could reach rather than the whole production environment. Beyond known findings, Zafran says the agents look for logic flaws and broken authorization in internet facing apps and APIs.
The post cites an FBI FLASH alert of 13 Nov 2026 about ARTEX, an open source AI agent penetration testing framework that it says attackers have used since at least August. That description is Zafran's account; the FBI alert itself was not read for this item. Claims about the platform are Zafran's own.
Source: [www.zafran.io](https://www.zafran.io/resources/zafran-announces-offensive-validation-to-prevent-exposure-ahead-of-ai-attackers), read 19 Nov 2026.
## Cogent introduces DefenseOS with Agent Policies and Agent Automations
17 Nov 2026. Cogent published on 17 Nov 2026 a description of DefenseOS, the context engine and agent runtime inside its platform, and introduced two capabilities: Agent Policies and Agent Automations. Cogent states DefenseOS ingests data through more than 100 integrations and that Agent Automations ships with 30 or more templates.
The post, by Josh Dreyfuss, says DefenseOS has two jobs. The context layer ingests scanner, business-system and security-tool data, normalizes and deduplicates findings, and links each vulnerability to the assets, owners and dependencies it touches. The execution layer is the harness the agents run inside, with approval gates, confidence thresholds and policy limits that decide what an agent may do alone. Cogent says every action is logged and traces back to its recommendation, and that low-confidence calls go to a person.
Agent Policies turns what DefenseOS learns into rules a team can read, edit and approve. Cogent lists three modes: rule discovery (agents propose, people accept, edit or reject), rule creation from uploaded documents or natural language, and drift detection that proposes updates when context changes.
Agent Automations runs recurring work on a schedule or on events, from a library of 30 or more templates or built in natural language, with results sent to Slack or email. These figures and the single unnamed customer example (nine reporting automations) are Cogent's own statements; the post gives no independent measurement. Cogent says most teams start with agents recommending fixes that people approve, then widen autonomy.
Source: [www.cogent.com](https://www.cogent.com/blog/introducing-defenseos-the-operating-system-that-runs-your-cyber-defense-factory), read 19 Nov 2026.
## Rival publishes a study of a model safety classifier that blocks security agents
12 Nov 2026. Rival Security published research on 12 Nov 2026 on how often a frontier model's cyber safety classifier blocks its vulnerability analysis agents. It reports blocked threads rising from about 5 percent to about 20 percent on some days in early November 2026.
Rival says its agents download vulnerable open source packages in a sandbox, read the code and decide when a flaw is exploitable, and that they run on gpt-6.1-sol. The study sampled 2,000 blocked threads from 14 days of production traces and replayed blocked requests against the real model and classifier, changing one thing at a time.
Rival reports that network facing packages were blocked 16.1 percent of the time against 6.2 percent for other packages, a ratio of 2.6, and that 33 of 78 blocked requests were never blocked again when resent unchanged. These are Rival's findings from its own traces.
The post notes that a block makes the run fail or fall back to a weaker model, which matters to anyone building security agents on these models. It does not publish exploit material.
Source: [rival.security](https://rival.security/blog/openai-cyber-classifier-security-agents?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=directory), read 19 Nov 2026.
## Cogent Security acquires Specular
10 Nov 2026. Cogent Security announced on 10 Nov 2026 that it had acquired Specular, a Google-backed AI security platform, and that Specular founder Peyton Smith and team members are joining Cogent. The company says the deal strengthens its ability to find, validate and fix vulnerabilities, and ties it to its PHP2Shell analysis.
Cogent's blog post, dated 10 Nov 2026, says Specular helps enterprises see their environments the way sophisticated attackers do.
The post cites Cogent's PHP2Shell analysis: when the flaw was disclosed on 21 Oct 2026, the average Fortune 500 company in its research had 2,266 affected assets, and Cogent says it narrowed that to 16 using runtime exposure, internet reachability and business criticality.
These figures are Cogent's own claims.
Source: [www.cogent.com](https://www.cogent.com/blog/cogent-expands-its-ai-cyber-defense-factory-with-specular-acquisition), read 10 Nov 2026.
## Cogent reports VR-1.1 repair results on LiveCVEBench
3 Nov 2026. SiliconANGLE reported on 3 Nov 2026 that Cogent Security's VR-1.1 model produced a working repair for 57.9% of the 190 tasks in LiveCVEBench, while Claude Code and Codex each scored 45.3%. Cogent ran the test. The report notes it blocked outbound network access during repairs.
The report says grading tests were hidden until each agent finished, and that inference budgets differed across the systems compared.
SiliconANGLE also reports that each patch goes to a separate review that starts from a fresh context and looks for a way around the fix, and that the model leaves regression tests.
The result is a vendor-run benchmark reported by a news outlet, and the register labels it that way.
Source: [siliconangle.com](https://siliconangle.com/2026/11/03/exclusive-cogent-securitys-vr-1-1-model-outscores-claude-code-and-codex-on-vulnerability-repair/), read 10 Nov 2026.
## Averlon publishes a response write-up on a Linux kernel TCP flaw
2 Nov 2026. Averlon published a write-up on 2 Nov 2026 on CVE-2026-98432, a Linux kernel TCP use-after-free rated CVSS 9.8, which the kernel CNA published on 15 Oct 2026. The post is dated 18 days after the CVE and covers which network paths expose a host.
Averlon's post describes the flaw as a race condition in the kernel's IPv4 TCP handshake code, reachable by a remote attacker with no credentials.
The write-up arrives 18 days after the CVE; Averlon states no time-to-answer figure for new CVEs on the pages read for the register, which records none found on 10 Nov 2026.
Source: [www.averlon.ai](https://www.averlon.ai/blog/cve-2026-98432-linux-kernel-tcp-use-after-free), read 10 Nov 2026.
## Rapid7 covers further exploited Ivanti Connect Secure flaws
2 Nov 2026. Rapid7 published on 2 Nov 2026 that Ivanti updated its advisory on 29 Oct 2026 to add CVE-2026-111357 and CVE-2026-118527 and released fixes. CISA added both to its KEV catalog on 30 Oct 2026. Rapid7 says authenticated checks have been available since the 30 Oct content release.
Ivanti says exploitation in the wild occurred before disclosure, affecting a limited number of customers when the flaws were chained with CVE-2026-104935.
Rapid7 notes a scoring difference: it rates CVE-2026-111357 at 7.0 while Ivanti assesses 8.8, based on different attack complexity and scope.
The blog covers mitigation guidance and how Rapid7 customers can check exposure.
Source: [www.rapid7.com](https://www.rapid7.com/blog/post/etr-additional-ivanti-connect-secure-zero-days-exploited-in-the-wild-cve-2026-111357-cve-2026-118527/), read 10 Nov 2026.
## Rival publishes its PHP2Shell triage write-up
2 Nov 2026. Rival Security published a write-up on 2 Nov 2026 on how its agents triaged PHP2Shell, CVE-2026-109618 and CVE-2026-109619. It reports scanning more than 80,000 repositories within hours, and one unnamed customer where an agent found 60 PHP repositories, 29 potentially vulnerable.
The post says its agents began triaging customer environments hours before vulnerability scanners could detect the CVEs.
The post also says agents can open pull requests, suggest web application firewall rules, apply configurations and message the relevant employees.
Customer results in the post are unnamed, and the figures are Rival's own claims.
Source: [rival.security](https://rival.security/blog/php2shell-black-october-2026?utm_source=automatedvulnerabilityremediation.com&utm_medium=referral&utm_campaign=directory), read 10 Nov 2026.
## Onit announces its Zero-Day Agent ahead of launch
23 Oct 2026. Onit Security published a post on 23 Oct 2026 announcing its Zero-Day Agent, which it says catches a zero-day as it breaks, finds every exposed asset and shows which are exploitable, in minutes. The post says PHP2Shell leaked on 20 Oct 2026 and was patched about 18 hours later.
The post states the agent runs no live exploits against production, needs no new endpoint agent and takes no disruptive action without approval.
It says full launch comes the following week. The minutes claim carries no published method, and the register labels it the vendor's claim.
Source: [onit.security](https://onit.security/blog/zero-day-response/), read 10 Nov 2026.
## Qualys offers free PHP2Shell detection for 15 days
23 Oct 2026. Qualys announced on 23 Oct 2026 that it was offering its solutions free to the community to detect, validate and mitigate exposure to PHP2Shell, CVE-2026-109618 and CVE-2026-109619. The service is free for 15 days for up to 1,000 assets from activation, and attack traffic had already been reported.
The announcement describes both flaws as unauthenticated remote code execution, each rated CVSS v4.0 9.2.
The offer is a time-limited response to a single disclosure. Qualys states no result figures for it in the announcement.
Qualys Threat Research Unit data in the release covers 167 million PHP package installations, 73% of them on internet-facing assets. Of 156 million with a known version, 110 million (71%) run end-of-life or end-of-support versions, 5.4 to 8.1, and most of these will not get a vendor patch. Another 44 million (28%) run supported branches, PHP 8.2 to 8.5, where a fix exists. Only 581,000 installations (0.37%) were patched in the first 24 hours after disclosure.
The trial covers Qualys VMDR, Enterprise TruRisk Management and TruRisk Eliminate. The release lists five steps: discover, prioritize and validate, patch supported versions and restart PHP services, mitigate unsupported versions with OS vendor backports or isolation, then rescan to verify. It also says leaked PHP worker memory can expose passwords, tokens and API keys.
Source: [www.qualys.com](https://www.qualys.com/company/newsroom/news-releases/usa/media-alert-qualys-offers-free-services-for-php2shell), read 10 Nov 2026.
## Maze publishes its PHP2Shell write-up one day after the patch
22 Oct 2026. Maze Security published a write-up on 22 Oct 2026, a day after the 21 Oct 2026 patch release for PHP2Shell, CVE-2026-109618 and CVE-2026-109619. It states how to tell whether a server is affected, including PHP behind Apache with mod_php, where an unauthenticated attacker may run code.
The post says both flaws are rated CVSS 9.2 on v4.0 and were patched a day earlier than planned.
Maze's pages also state that agents sweep every instance for a new zero-day in hours, before scanners have a signature; that is the vendor's claim.
Source: [mazehq.com](https://mazehq.com/blog/php2shell), read 10 Nov 2026.
## Rapid7 puts average time to exploitation at three days
21 Oct 2026. Rapid7's Q3 2026 threat update, dated 21 Oct 2026, reports three days as the average time from public disclosure to exploitation of high-severity vulnerabilities, with 71% of tracked exploitation inside seven days. It tracked 43 newly exploited high and critical vulnerabilities in the quarter.
The report says exploitation occurred within 14 days for 80% and within 30 days for 90% of the tracked set.
Rapid7 says the 43 newly exploited vulnerabilities were down 7% from Q2 and up 19% on the same period a year earlier.
Of the 43 newly exploited vulnerabilities, 34 (79%) required no authentication or user interaction. Rapid7 also says 8% of the threat reporting it tracked in Q3 cited AI as an operational component, with human operators still selecting targets and objectives.
Underground forum monitoring in the quarter found 41 posts advertising RDP or network access. The post dated 21 Oct 2026 says the full Quarterly Threat Landscape Report also covers ransomware activity and APT tracking, and recommends starting with externally accessible assets and the vulnerabilities that affect them.
Source: [www.rapid7.com](https://www.rapid7.com/blog/post/tr-q3-2026-threat-update-attackers-exploiting-vulnerabilities-within-3-days/), read 10 Nov 2026.
## Tenable adds an AI Inspector to the CyberAgents Exchange
8 Oct 2026. Tenable announced on 8 Oct 2026 the CyberAgents Exchange AI Inspector, built with OpenAI GPT cyber models, to evaluate AI agents, skills and MCP servers listed on the Exchange. The Exchange is an open-source, vendor-agnostic hub of agents and playbooks for security teams.
Tenable says the Inspector includes an enterprise-grade safety review designed to help organizations deploy listed components more securely in production.
OpenAI's head of global cyber partnerships is quoted in the release on the trust layer needed to scale agentic AI.
Tenable describes Exchange Inspector as a three-part vetting process. It starts with the skills inspection engine in Tenable One AI Exposure, which is designed to detect malicious content such as prompt injection and exposed hardcoded secrets or customer data. The component then gets an assessment using OpenAI GPT cyber models, followed by review from Tenable's security research team.
The release names three vetted skills available on the date of the announcement: SOC Hunter, Remediation Priority & Impact Agent, and Splunk Tenable Cloud Security Skill. Tenable says Exchange Inspector was developed as part of its participation in the OpenAI Daybreak Defense Network. The hunt-time figure for SOC Hunter is reported by the contributor, Tenable's enterprise security team.
Source: [www.tenable.com](https://www.tenable.com/press-releases/tenable-uses-openai-gpt-cyber-models-to-advance-agentic-security-review-in-the-cyberagents-exchange), read 10 Nov 2026.
## Zafran reports Gartner Emerging Tech mentions
22 Sep 2026. Zafran announced on 22 Sep 2026 that it was named a Sample Vendor for autonomous exposure remediation in Gartner's Emerging Tech Impact Radar: Preemptive Cybersecurity, published 11 Sep 2026. It also cites an April 2026 Gartner report on funded startups, covering 148 startups and about $4.19 billion.
The announcement repeats Zafran's own analysis that about 90% of vulnerabilities can be mitigated with controls already in place, such as firewalls, endpoint protection and web application firewalls.
The recognition is reported by Zafran; the register records it as the vendor's claim.
On the page, Zafran says it was named a Sample Vendor for Autonomous Exposure Remediation in the Gartner report. A Sample Vendor entry is an example named in a technology category; the page quotes Gartner's definition of the category as generative AI orchestrating closed-loop remediation that generates, validates and deploys fixes across code, supply chain and infrastructure.
Zafran also says it was identified among funded startups in the Unified Exposure Management Platform category in a Gartner report published 3 April 2026. The page quotes Gartner as saying that by 2028 at least half of the exposure management market will consist of unified exposure management platforms, up from less than 5% in 2025.
Source: [www.zafran.io](https://www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-reports-for-unified-exposure-management-platforms-and-autonomous-exposure-remediation-categories), read 10 Nov 2026.
## Seemplicity releases Response Options
2 Sep 2026. Seemplicity announced Response Options on 2 Sep 2026, available to all customers. They give alternatives to a full patch, such as compensating controls and targeted configuration changes, each with a Readiness Indicator showing whether it is ready to deploy now or needs review first.
AI Analysts pre-select a recommended option, and every alternative stays visible with its reasoning.
Options appear in the Analyst Results tab on a finding's detail page. The release states no customer results.
The release, datelined Las Vegas, describes the problem as follows: a complete fix such as a patch, an upgrade or a major configuration change is seen as the safest long-term answer, but it is also the slowest and most intrusive. It can demand heavy testing, coordination and sometimes a production reboot.
Seemplicity says Response Options is meant to give faster, lower-risk steps that reduce exposure now, without waiting on the full remediation cycle. Ravid Circus, Chief Product Officer and Co-Founder, is quoted in the release saying that patch or nothing is what slows organizations down. The capability applies to vulnerability management and exposure management workflows.
Source: [seemplicity.ai](https://seemplicity.ai/news/response-options/), read 10 Nov 2026.
## Related pages
- [Remediation Register: the data, downloadable](/datasets/)
- [How the register works, and what it leaves out](/method/)
- [The Backlog Calculator](/calculator/)
- [Guides](/guides/)
## Sources
- https://mazehq.com/blog/java4shell (read 19 Nov 2026)
- https://www.qualys.com/company/newsroom/news-releases/usa/cognizant-joins-qualys-global-mroc-alliance-deliver-managed-risk-operations-frontier-ai-era (read 19 Nov 2026)
- https://www.zafran.io/resources/zafran-announces-offensive-validation-to-prevent-exposure-ahead-of-ai-attackers (read 19 Nov 2026)
- https://www.cogent.com/blog/introducing-defenseos-the-operating-system-that-runs-your-cyber-defense-factory (read 19 Nov 2026)
- https://rival.security/blog/openai-cyber-classifier-security-agents (read 19 Nov 2026)
- https://www.cogent.com/blog/cogent-expands-its-ai-cyber-defense-factory-with-specular-acquisition (read 10 Nov 2026)
- https://siliconangle.com/2026/11/03/exclusive-cogent-securitys-vr-1-1-model-outscores-claude-code-and-codex-on-vulnerability-repair/ (read 10 Nov 2026)
- https://www.averlon.ai/blog/cve-2026-98432-linux-kernel-tcp-use-after-free (read 10 Nov 2026)
- https://www.rapid7.com/blog/post/etr-additional-ivanti-connect-secure-zero-days-exploited-in-the-wild-cve-2026-111357-cve-2026-118527/ (read 10 Nov 2026)
- https://rival.security/blog/php2shell-black-october-2026 (read 10 Nov 2026)
- https://onit.security/blog/zero-day-response/ (read 10 Nov 2026)
- https://www.qualys.com/company/newsroom/news-releases/usa/media-alert-qualys-offers-free-services-for-php2shell (read 10 Nov 2026)
- https://mazehq.com/blog/php2shell (read 10 Nov 2026)
- https://www.rapid7.com/blog/post/tr-q3-2026-threat-update-attackers-exploiting-vulnerabilities-within-3-days/ (read 10 Nov 2026)
- https://www.tenable.com/press-releases/tenable-uses-openai-gpt-cyber-models-to-advance-agentic-security-review-in-the-cyberagents-exchange (read 10 Nov 2026)
- https://www.zafran.io/resources/zafran-recognized-in-two-2026-gartner-r-emerging-tech-reports-for-unified-exposure-management-platforms-and-autonomous-exposure-remediation-categories (read 10 Nov 2026)
- https://seemplicity.ai/news/response-options/ (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/news/
---
# 31 questions, answered from the data
FAQ, read 10 Nov 2026
**The short answer.** Thirty questions with short answers cover the register, the Backlog Calculator and the remediation topics, such as how many platforms are listed (14), which date facts were read (10 Nov 2026) and what a none-found label means. Each answer points to the page that holds the evidence.
**How many platforms does the register list?**
Fourteen: Astelia, Averlon, Backline, Cogent Security, Dux, Maze, Onit, Qualys, Rapid7, Rival, Seemplicity, Tenable, Vicarius and Zafran, in alphabetical order. Each has a profile with the same seven topics. See /platforms/ for the list and /method/ for how a platform is added.
**Does the site order platforms by merit?**
No. Platforms are listed alphabetically, and no page carries a rating, a total or a pick. Facts sit side by side under seven topics, and the reader decides which rows matter. The rule is stated in plain words on /method/, and the guides at /guides/ name what to check, not what to buy.
**When were the facts read?**
10 Nov 2026 for the first edition. Every fact shows its own read date beside its source link. Vendors change their pages, so a fact describes the page on that day. Corrections are listed with their date on /corrections/, and the method is on /method/.
**What does none found mean in a profile?**
It means a page was read on the stated date and the thing was not on it, for example named ticketing integrations. It is a statement about the pages read, not about the product. Each entry names the pages. Examples are on /platforms/astelia/ and /platforms/dux/, and the labels are explained on /method/.
**What are the seven topics?**
Proves exploitability in your environment, ships the fix, finds the owner, speed on a new disclosure, agents you can shape, works on the stack you have, and proof. Every profile uses them in that order. The guide at /guides/what-to-ask-in-a-remediation-platform-trial/ gives one test for each.
**What is a vendor's claim label?**
It marks a statement taken from the vendor's own site or release, such as a customer result or a speed figure. The register quotes it and gives the page. A third-party source label marks a statement from an outside outlet. Read /guides/reading-a-vendors-remediation-claim/ for how to test the claim.
**What does the Backlog Calculator compute?**
Analyst hours and working days. With its defaults of 20,000 findings, 25 minutes each, 3 analysts and 30 queue hours a week, the result is 8,333 hours and 463 working days. Every input is editable, and the assumptions are listed on /calculator/. It counts analysis time only, not fix time.
**Does the calculator store what I enter?**
No. The calculator runs in your browser and the numbers are not sent anywhere or stored. The site sets no cookies and runs no analytics, as the privacy page at /privacy/ states. The only record of a visit is the request log kept by the content delivery network.
**How do I find a good minutes-per-finding number?**
Time a sample. Take 30 findings your team closed last month, measure the minutes from opening to a recorded decision, and use the median. The 25-minute default is an input to replace. The method is in /guides/how-to-measure-a-backlog/, with a table of results at 5,000, 20,000 and 50,000 findings.
**What is agentic vulnerability management?**
Software agents carry a finding through steps a person used to do, within limits the customer sets. The test is what ships: a pull request, a patch job, a rule or a scoped ticket. The definition and a table of the outputs vendors state are in /guides/agentic-vulnerability-management-defined-by-what-ships/.
**Which platforms say they open pull requests?**
Averlon, Backline and Rival state that they generate pull requests for human review, as read on 10 Nov 2026. Cogent Security describes executing fixes through existing tools. Each claim and its source are on the profiles, and /guides/what-an-agent-can-fix-without-a-human/ sorts them by output.
**Which platforms say they deploy patches?**
Qualys, Tenable and Vicarius state that they deploy patches through their own patch tooling. Astelia states that it drives patches through the customer's patch management tool where one exists. All are vendor claims read on 10 Nov 2026. See /platforms/qualys/, /platforms/tenable/ and /platforms/vicarius/.
**Which platforms let customers build their own agents?**
Astelia describes customers writing a workflow in natural language for a Planner agent to build, and Rival, Tenable and Zafran state a customer-built agent feature. Several others record none found on 10 Nov 2026. The agents topic on each profile at /platforms/ holds the quotations.
**Do remediation platforms replace the scanner?**
The agentic platforms in the register mostly sit after the scanner and read its findings; Astelia and Backline state this directly. Qualys, Rapid7 and Tenable are scanner vendors that also describe agents. See /guides/agentic-vulnerability-management-defined-by-what-ships/ for where each type sits.
**Which platforms publish prices?**
None publishes a price list on the pages read on 10 Nov 2026. Maze states pricing by cloud infrastructure size, Rapid7 by usage per asset type and Vicarius by managed endpoint count. Most others record none found. The profile pages at /platforms/ show the line, and /guides/what-to-ask-in-a-remediation-platform-trial/ covers asking.
**How fast do attackers exploit new vulnerabilities?**
Rapid7's Q3 2026 report puts the average at three days from public disclosure, with 71% of tracked exploitation inside seven days. That is Rapid7's research, read 10 Nov 2026. The consequences for policy are in /guides/the-remediation-sla-that-holds/.
**What deadline does CISA set for known exploited vulnerabilities?**
Two weeks for CVEs assigned after 2021 and six months for older ones, as the default under BOD 22-01 for federal agencies. The directive allows adjustment in cases of grave risk. Private companies are not bound by it, but /guides/the-remediation-sla-that-holds/ shows how to borrow the structure.
**How should mean time to remediate be reported?**
As a median and a 90th percentile per tier, with the count and age of open items past SLA, and with the clock start and stop stated. A mean of closed items alone hides the long tail. The full definition is in /guides/mean-time-to-remediate-measured-honestly/.
**How should approval work for agent changes?**
Set it per action type: read-only steps run alone, reversible changes run in staged rings, irreversible changes wait for a person, and every approval is logged with the evidence shown. Cogent Security, Onit and Qualys describe such gates. See /guides/how-approval-should-work/ for the table.
**How do I check whether ownership mapping works?**
Take 30 findings from last month, write down the team that actually closed each, and compare with the platform's answer. Count right team, wrong team and no answer. Onit claims about half of tickets bounce for wrong owners, which is its own observation. See /guides/ownership-mapping/.
**What should a lean team check first?**
How many findings the platform closes before a person reads them, and what evidence it shows. At 25 minutes a finding, 20,000 findings take about 8,333 analyst hours. The calculator at /calculator/ sizes your own queue.
**What should an enterprise with ServiceNow check?**
Whether each scanner you run and each ServiceNow module has a named integration, and how the platform resolves an owner for an asset with no CMDB entry. The guide /guides/the-remediation-sla-that-holds/ covers the clock choices.
**What should a regulated company ask for?**
An export of one exception and one fix with the full trail: evidence, approver, timestamps and the re-check after the change. NIST SP 800-40 Rev. 4 lists identifying, prioritizing, acquiring, installing and verifying as the steps an auditor expects. See /guides/how-approval-should-work/.
**What should a managed service provider check?**
Tenant separation, per-customer approval rules and per-customer reports, before any agent. Maze states that single-tenant hosting is available (vendor's claim, read 10 Nov 2026). The stack topic on each profile lists integrations.
**Are there side-by-side pages?**
Yes. Each page puts the sourced facts of two platforms in the same rows under the seven topics and ends without a conclusion. Pairs are named alphabetically. The index is at /compare/, and each page shows the read date, 10 Nov 2026, next to every fact.
**What is the difference between reachable and exploitable?**
Reachable means an attacker can get to the vulnerable code or service. Exploitable means they can use the flaw there, given version, configuration and controls. A flaw can be reachable and not exploitable. Definitions and sourced examples are at /glossary/#reachability and /glossary/exploitability/.
**What happens when no patch exists?**
Teams use controls such as a firewall rule, a web application firewall rule, a disabled feature or a virtual patch, record them as an exception with an expiry date, and plan the fix. PHP 8.1 and older had no upstream fix for PHP2Shell on 21 Oct 2026.
**Where can I see recent platform news?**
On /news/, which lists 17 dated items from 2 Sep to 18 Nov 2026, newest first, each linked to the original announcement. They include Cogent Security acquiring Specular on 10 Nov 2026 and Rapid7's Q3 2026 threat update on 21 Oct 2026. Order is by date, not importance.
**How do I report an error?**
Write to editor@automatedvulnerabilityremediation.com with the page URL and the line that no longer matches its source. Corrections are made on the page and logged with their date on /corrections/. Vendors may send a newer source for any fact about their own platform; the entry is updated with a new read date.
**Does the site use cookies or analytics?**
No cookies, no analytics and no third-party scripts, as of 10 Nov 2026. The only record of a visit is the content delivery network's request log, which holds the IP address, time and page requested. Details are on /privacy/, and the calculator runs entirely in the browser.
**Can I reuse the Remediation Register data?**
Yes, with the cite line shown on the register data page: Automated Vulnerability Remediation, Remediation Register, edition 10 Nov 2026. The file is available as CSV and JSON, sorted by vendor and topic, with no ratings. The terms are on /terms/, and the edition date matters because rows describe pages as read on that day.
## Related pages
- [News](/news/)
- [Remediation Register: the data, downloadable](/datasets/)
- [How the register works, and what it leaves out](/method/)
- [The Backlog Calculator](/calculator/)
## 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/faq/
---
# The Remediation Register, downloadable
Dataset edition 10 Nov 2026
**The short answer.** The Remediation Register holds every sourced fact read for the 14 platforms: topic, claim, quotation, source URL, read date and label. It is published as CSV and JSON with the edition date of 10 Nov 2026. Rows are sorted by vendor name, then topic, and carry no ratings.
Each row is one fact. The columns give the vendor, the topic (one of seven, or profile for company facts), the claim in the editor's words, the vendor's or outlet's own quotation, the page it came from, the date read, and the label: vendor's claim, third-party source, or none found. Rows marked none found record a page that was read and a thing that was not on it.
Use the file to build your own comparison. Filter to the topic you care about, drop the vendors that do not fit your stack, and read the quotations. Because the file carries no weights, any order you apply is yours.
Reuse is welcome with the cite line below. The edition date matters: a row read on 10 Nov 2026 describes a page on that day.
## Downloads
- [Remediation Register (CSV)](/datasets/register.csv): 531 rows, edition 10 Nov 2026
- [Remediation Register (JSON)](/datasets/register.json): One row per fact for 14 platforms, in alphabetical order of platform: the topic, the label (vendor's claim, third-party source or none found), the claim, the source and the date read.
- [Remediation Register, summary by platform (CSV)](/datasets/register-summary.csv): 14 rows, edition 10 Nov 2026
- [Remediation Register, summary by platform (JSON)](/datasets/register-summary.json): One row per platform with the count of facts read, split by label.
## What each file holds
| File | Rows | Columns |
| --- | --- | --- |
| register.csv / register.json | 531 | vendor, slug, topic, label, claim, source, read |
| register-summary.csv / register-summary.json | 14 | vendor, slug, category, facts_read, third_party_facts, vendor_claims, none_found_lines |
Remediation Register files as built on 19 Nov 2026; each JSON file adds the cite line.
## Cite this
**Cite this.** Automated Vulnerability Remediation, Remediation Register, edition 10 Nov 2026, https://automatedvulnerabilityremediation.com/platforms/.
## Changelog
- 10 Nov 2026: first edition. Facts read 10 Nov 2026.
- 19 Nov 2026: the register files take the new site title in their cite line, and the home table now shows what each platform fixes itself, who approves, owner resolution, scanners read and price, drawn from the same facts and their 10 Nov 2026 read dates.
## Related pages
- [How the register works, and what it leaves out](/method/)
- [The Backlog Calculator](/calculator/)
- [Guides](/guides/)
- [Glossary](/glossary/)
## 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)
- Cogent Security: www.cogent.com/platform/assess: https://www.cogent.com/platform/assess (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/datasets/
---
# About Automated Vulnerability Remediation
About, read 10 Nov 2026
**The short answer.** Automated Vulnerability Remediation is a reference on platforms that clear a vulnerability backlog with agents. The second edition, dated 19 Nov 2026, profiles 14 platforms under seven topics and adds 11 guides, 32 glossary terms, 17 news items and a backlog calculator. Platforms are listed alphabetically, and each fact has a source and a read date.
The reader in mind is the head of vulnerability management, the security engineering lead, or the CISO with more findings than people to fix them. The questions are practical ones. What does an agent fix without a person? Who approves a change? How does a platform find the team that owns a finding? Which scanners does it read?
Two original assets carry the work. The Remediation Register holds the sourced facts for each platform, and the [platforms page](/platforms/) shows them side by side. The Backlog Calculator turns a finding count and a minutes-per-finding estimate into analyst hours and working days, and it runs in your browser.
The guides cite public primary sources, among them CISA Binding Operational Directive 22-01 and NIST SP 800-40 Rev. 4, next to the vendor pages they discuss. Glossary terms and news items sit as anchored entries on the [glossary](/glossary/) and [news](/news/) pages, and each entry names the page it was read from.
The first edition was published on 10 Nov 2026. The second edition followed on 19 Nov 2026 with a new title, a reorganized glossary and news section, fewer guides and more news items. Each change is listed with its date on the [corrections page](/corrections/).
The method page explains how a fact enters the register: the editor opens the page, records the address, the date and a short quotation, and labels the claim by origin. The site lists platforms and does not rank them, and no number is put on any of them.
The site is static. Pages are plain HTML files, the calculator and tools run in the browser, and there is no login, no form and no mailing list. The privacy page lists what the server logs record and how long they are kept.
If a line is wrong or out of date, write to editor@automatedvulnerabilityremediation.com with the page address and the source line, and the entry will be changed and logged.
## Related pages
- [Editorial policy](/editorial-policy/)
- [Corrections](/corrections/)
- [Contact](/contact/)
- [Privacy](/privacy/)
- [Terms](/terms/)
## 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)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/about/
---
# How Automated Vulnerability Remediation is written
Editorial policy, read 10 Nov 2026
**The short answer.** Editorial policy: every fact on Automated Vulnerability Remediation comes from a page the editor opened and dated. The first edition was read on 10 Nov 2026 and the second on 19 Nov 2026. Platforms are listed alphabetically, claims are labeled by origin, and nothing is scored or placed in an order of merit.
A platform is added when it publicly describes agents that work a vulnerability backlog after a scanner has produced findings. Each platform is described under the same seven topics, in the same order, so a reader can compare one topic across vendors without hunting for it.
Every fact carries a label. A statement on the vendor's own site is labeled a vendor claim. A statement from an outlet or another outside party is labeled a third-party source. Where a page was read and the thing was not on it, the entry says none found on that date, with the date, which describes the pages read and not the product.
Customer numbers are quoted in the vendor's own wording and labeled the vendor's claim. When the page gives no method for a figure, the entry says so. The editor does not run vendor products, so no entry describes a test the editor performed.
Each entry shows its read date. A fact read on 10 Nov 2026 or 19 Nov 2026 describes the page on that day, and vendors change their pages. A vendor can send a newer source for any fact about its platform; the entry then moves to the new page with a new read date, and the older reading is kept in the correction note.
News items link the original announcement and are added only from primary sources the editor opened on the read date. They sit as anchored entries on the news page, newest first, ordered by date and not by importance.
The security content rule is fixed. The site publishes no exploit code, no proof-of-concept steps and no scanning instructions. Where a vulnerability is discussed, the text gives preconditions, detection, mitigation and fix, taken from vendor advisories, the National Vulnerability Database and the CISA Known Exploited Vulnerabilities catalog.
Wording stays plain. Text avoids claims of superiority and instructions to buy. A guide may describe what to check in a trial or a contract; it does not say which platform to choose.
## Related pages
- [About](/about/)
- [Corrections](/corrections/)
- [Contact](/contact/)
- [Privacy](/privacy/)
- [Terms](/terms/)
## Sources
- NVD CVE API: https://nvd.nist.gov/developers/vulnerabilities (read 10 Nov 2026)
- CISA Known Exploited Vulnerabilities catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/editorial-policy/
---
# Corrections and the correction rule
Corrections, read 10 Nov 2026
**The short answer.** Corrections policy: when a fact no longer matches its source, the entry is changed and the change is listed on this page with its date. Report an error to editor@automatedvulnerabilityremediation.com with the page address and the source line that shows the right fact. The log below starts with the second edition of 19 Nov 2026.
A vendor may send a newer source for any fact about its platform. The entry is updated to the new page with a new read date, and the older reading is kept in the correction note. A report that includes an address and a quotation is the quickest to check.
Corrections log, 19 Nov 2026. The site title changed from The Vuln Backlog to Automated Vulnerability Remediation, and titles and descriptions of the pages were updated to match.
Corrections log, 19 Nov 2026. Glossary terms and news items now sit as anchored entries on the glossary and news pages, instead of each having a separate page of its own.
Corrections log, 19 Nov 2026. One guide was removed, Vulnerability remediation tools for findings with no patch, because another reference already covers the subject. The remaining guides number 11.
Corrections log, 19 Nov 2026. News items were added from primary sources read on 19 Nov 2026, bringing the news page to 17 items.
Corrections log, 19 Nov 2026. The table on the home page now has these columns: what each platform fixes itself, who approves, how it resolves an owner, which scanners it reads, and price. Each cell keeps its source and read date.
Corrections log, 19 Nov 2026. Entries on this page are not deleted. A later correction to the same fact is added above the earlier one, so the order of changes can be read in order.
How to read an entry: it states the date, what changed and why. Where a figure or a quotation changed, the entry gives the old value, the new value and the source address for the new value, so a reader who cited the earlier text can see what to update.
Corrections log, 10 Nov 2026. First edition published. No corrections were made to it before the second edition.
## Related pages
- [About](/about/)
- [Editorial policy](/editorial-policy/)
- [Contact](/contact/)
- [Privacy](/privacy/)
- [Terms](/terms/)
## 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)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/corrections/
---
# Contact Automated Vulnerability Remediation
Contact, read 10 Nov 2026
**The short answer.** Contact Automated Vulnerability Remediation by email at [editor@automatedvulnerabilityremediation.com](mailto:editor@automatedvulnerabilityremediation.com). Send corrections with the page address and the source line, news tips with a link to the original announcement, and requests for the Remediation Register file. Corrections are logged on the corrections page with their date.
For a correction, name the page, copy the line you think is wrong, and give the address of the source that shows the right fact. A vendor page, a standards document or a dated announcement all work. The entry is changed to match the source and the change is logged.
For a news tip, send a link to the primary source, such as the vendor's own announcement, a filing, or a research post by the company that did the work. News items on this site link the original page, so a link to a secondary summary is less useful than one to the first source.
For the dataset, ask for the Remediation Register as CSV or JSON. It holds the claim, quotation, source address, read date and label for each fact, sorted by vendor and then topic. The file can be reused under CC BY 4.0 with the cite line shown on the platforms page.
Please do not send exploit code or proof-of-concept material. If you have found a flaw in a product, report it to the vendor named in that product's advisory.
For questions about method, ask how a fact was labeled or why a platform appears in the register. The answer points to the page that was read and the read date, which is the same information shown under the fact.
Vendors are welcome to send a newer source for any fact about their platform, with the address of the page that states it. The entry is updated with a new read date, and the earlier reading is kept in the correction note.
The site has no forms, no accounts and no mailing list. Email is the only way to reach the editor, and everything on the site is static pages with calculators that run in your browser.
## Related pages
- [About](/about/)
- [Editorial policy](/editorial-policy/)
- [Corrections](/corrections/)
- [Privacy](/privacy/)
- [Terms](/terms/)
## 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)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/contact/
---
# Privacy
Privacy, read 10 Nov 2026
**The short answer.** Privacy: Automated Vulnerability Remediation sets no cookies, runs no analytics and loads no third-party scripts. It has no forms, no accounts and no mailing list. The only record of a visit is the access log of the content delivery network that serves the pages, deleted after 400 days.
The pages are static HTML files stored on Amazon S3 and served by Amazon CloudFront. Fonts are self-hosted, so no font is fetched from another host. The Backlog Calculator runs in your browser, and the numbers you enter are not sent anywhere.
CloudFront standard access logs are written to a private S3 bucket in the US East (N. Virginia) region. Each line holds the date and time, the edge location, the client IP address, the requested path, the status code, the referrer and the user agent, as listed in the [AWS standard logging reference](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/standard-logs-reference.html) (read 2026-11-19).
The logs are used to count page views per page and visits by crawlers. A lifecycle rule on the bucket, set on 19 Nov 2026, deletes log files after 400 days.
Because the log holds the client IP address, a visit can be traced to an address by anyone with access to the bucket. The site does not combine the log with any other data about readers.
Email sent to editor@automatedvulnerabilityremediation.com is kept to answer it and to log any correction that follows. The correction log shows the date and the page changed, and does not show who wrote in.
A log line is not joined to an identity. The site has no accounts, so a line cannot be tied to a person except through the IP address it contains, and the site does not look addresses up.
The first edition of 10 Nov 2026 and the second edition of 19 Nov 2026 use the same hosting. The 400-day deletion rule was set on 19 Nov 2026, so log files written under the first edition fall under it as well once they pass 400 days.
Page-view counts come from the requested path in these lines. Crawler visits are counted from the user agent. The counts show which pages are read and which are fetched by automated programs.
To ask what the logs hold about an address, write to the same email address.
## Related pages
- [About](/about/)
- [Editorial policy](/editorial-policy/)
- [Corrections](/corrections/)
- [Contact](/contact/)
- [Terms](/terms/)
## Sources
- Amazon CloudFront standard log file fields: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/standard-logs-reference.html (read 19 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/privacy/
---
# Terms of use
Terms, read 10 Nov 2026
**The short answer.** Terms of use: Automated Vulnerability Remediation is a reference for general information, and the current edition is dated 19 Nov 2026. Each fact describes the page it was read from on the date shown. Check the source before relying on a fact for a purchase, a contract or a compliance decision.
The Remediation Register may be reused under CC BY 4.0. Cite it with the line shown on the platforms page: Automated Vulnerability Remediation, Remediation Register, edition 10 Nov 2026, https://automatedvulnerabilityremediation.com/platforms/. If you reuse the register, say which edition you took.
Quotations from vendor pages stay the property of their authors, and are included here as short extracts with a link to the page. Product and company names belong to their owners. They appear so a reader can tell which product a fact is about.
Facts are dated. Vendors change their pages, so a fact read on 10 Nov 2026 or 19 Nov 2026 may no longer match the page today. The source address under each fact lets you read the current page.
The Backlog Calculator gives an estimate from the numbers you enter. It does not know your tooling, your teams or your policy, so treat its output as arithmetic and not as a forecast.
Links to other sites are given so you can read the source. The text on those sites is theirs and can change without notice.
The text of the guides, the glossary and the news summaries may be quoted briefly with a link back to the page. Longer reuse, or reuse of the register in a product, should follow the CC BY 4.0 terms above.
Dates in the register use the form day, month, year, such as 19 Nov 2026. A read date is the day the editor opened the source. It is not the date the vendor published the page, which the entry gives separately when the page states it.
The register is a set of facts about public pages, and a platform you buy may differ from what its public page says. Ask the vendor for the current terms of any feature before you sign.
If you find a fact that does not match its source, write to editor@automatedvulnerabilityremediation.com and the entry will be corrected and logged.
## Related pages
- [About](/about/)
- [Editorial policy](/editorial-policy/)
- [Corrections](/corrections/)
- [Contact](/contact/)
- [Privacy](/privacy/)
## Sources
- Creative Commons Attribution 4.0 International: https://creativecommons.org/licenses/by/4.0/ (read 19 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/terms/
---
# A backlog of 20,000 findings takes 463 working days at these assumptions
Backlog Calculator, read 10 Nov 2026
**The short answer.** At 25 minutes of analyst time per finding, 20,000 open findings take 8,333 analyst hours. With 3 analysts giving 30 hours a week to the queue, that is 463 working days. Change any input below; every assumption is listed on this page.
Defaults: 20000 findings, 25 minutes each, 3 analysts, 30 hours a week each, 0 percent removed before analysis. Result: 8333 analyst hours, 463 working days.
## Worked examples
Four backlogs run through the same formula. The inputs are illustrations to compare against your own queue, not measurements of any team or platform.
| Open findings | Minutes each | Analysts | Queue hours a week each | Removed before analysis | Analyst hours | Working days |
| --- | --- | --- | --- | --- | --- | --- |
| 5,000 | 15 | 2 | 30 | 0% | 1,250 | 104 |
| 20,000 | 25 | 3 | 30 | 0% | 8,333 | 463 |
| 20,000 | 25 | 3 | 30 | 40% | 5,000 | 278 |
| 50,000 | 20 | 5 | 25 | 60% | 6,667 | 267 |
Computed with the formula under Assumptions; working days are rounded.
Removing findings before analysis moves the result more than any other input: at the default 20,000 findings, taking out 40 percent saves 3,333 analyst hours. A platform's stated reduction is a vendor claim until it is measured on your own findings; the [guide to measuring a backlog](/guides/how-to-measure-a-backlog/) shows how to count it.
## Assumptions
- Hours = findings left times minutes per finding, divided by 60.
- Working days = hours divided by (analysts times weekly queue hours divided by 5).
- Findings left = findings times (1 minus the percent removed before analysis, divided by 100).
- The percent removed is an input you set from a vendor result you trust; the calculator does not assume one.
- No fix time is included: the figure is analysis time only.
## Related pages
- [Guides](/guides/)
- [Glossary](/glossary/)
- [31 questions answered](/faq/)
- [News](/news/)
## Sources
- CISA Known Exploited Vulnerabilities catalog (the source for the finding counts readers compare against): https://www.cisa.gov/known-exploited-vulnerabilities-catalog (read 10 Nov 2026)
Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/calculator/