# Vulcan Cyber was acquired by Tenable on 7 Feb 2025 and no standalone product was found on sale

PROGRAM GUIDE, read 10 Nov 2026

**The short answer.** Tenable announced the Vulcan Cyber deal on 29 Jan 2025 for about $147 million in cash plus $3 million in stock units, and closed it on 7 Feb 2025. By 2026-11-10, vulcan.io redirected to tenable.com and no standalone Vulcan product page was found. Vulcan customers should ask Tenable what their contract maps to.

## The sequence of events

On 29 Jan 2025 Tenable announced a definitive agreement to acquire Vulcan Cyber Ltd. for approximately $147 million in cash and $3 million of restricted stock units, according to [Tenable's announcement](https://www.tenable.com/press-releases/tenable-plans-to-acquire-vulcan-cyber-accelerate-leadership-in-exposure-management). On 7 Feb 2025 Tenable [announced the close](https://www.tenable.com/press-releases/tenable-completes-acquisition-of-vulcan-cyber). That is nine days from signing to close.

Tenable states that Vulcan's capabilities are to be folded into the Tenable One Exposure Management Platform. Its press release describes the integration as planned. Vulcan's former CEO, Yaniv Bar-Dayan, is described on a Tenable webinar page as Vice President, Engineering at Tenable.

## What a reader can verify today

Fetching vulcan.io on 2026-11-10 returned HTTP 301 to the Tenable home page. A standalone sale after the acquisition: none found on 2026-11-10, after searching tenable.com product pages and the Tenable One pages, none of which name Vulcan as a product. The page tenable.com/products/vulcan-cyber returned 404. Vulcan documentation: none found on 2026-11-10, since docs.vulcan.io did not resolve.

The Vulcan feature descriptions that survive are in Internet Archive snapshots of vulcan.io from 1 Jan 2025 and in Tenable's own posts. Treat both as vendor statements. This site did not test any Vulcan feature.

## What Vulcan customers carried

According to Vulcan's archived platform page, the product deduplicated findings across sources, let customers configure the weight of each criterion in the risk score, tag business context and mark accepted risk, and auto-opened tickets while tracking SLA compliance. Its integration catalog listed scanners, application security tools, cloud tools, bug bounty platforms, CMDB and ticketing systems such as ServiceNow and Jira.

The archived pages do not name the score or give its scale. A risk score name and scale: none found on 2026-11-10. Whoever holds the tenant must read the score definition from the product itself and record it before the tenant changes.

## What to ask Tenable

The practical questions are contractual. Ask in writing which Tenable product your Vulcan entitlement maps to, until what date the existing Vulcan tenant is supported, whether the Vulcan API stays available and for how long, and how your tickets and accepted-risk records can be exported. Tenable's current catalog page says the Tenable One Open Connector ingests data from tools, internal systems, spreadsheets or files, which is a route for bringing data in. No page found describes a route for bringing Vulcan data out.

If the answers are slow, treat that as the schedule risk it is. Export what the tenant allows now, using the pattern in the export guide: raw files first, hashes, row counts compared with the console.

## Choosing between Tenable and others

Staying inside Tenable is one option, and the product has changed shape since the close. In the Migration Ledger, Tenable's Vulnerability Priority Rating runs 0 to 10. If your Vulcan rules were weighted on a different scale, the scoring guide covers translating them. Any shortlist for a Vulcan replacement should leave out Tenable, since Tenable owns Vulcan; ask Tenable separately for its migration path.

- Keep a dated copy of both Tenable press releases.
- Request the contract mapping in writing.
- Export tickets, exceptions and score settings first.
- Record the Vulcan score definition from the live tenant.

## Reading acquisition language

Acquisition announcements use future tense. Tenable's announcement says it plans to expand Tenable One with Vulcan's capabilities. A team that bought a standalone product should read these as statements of intent about a roadmap, not a date for a feature or an assurance for a contract.

The facts that can be checked are the dates and the redirect: signing on 29 Jan 2025, close on 7 Feb 2025, and a vulcan.io address that sent a request to the Tenable home page on 2026-11-10. The facts that cannot be checked from public pages are what happens to a particular tenant and to its data. That is a question for your contract and your account team.

If you are the person who inherited a Vulcan tenant after a staff change, start with an inventory of what it does: which sources feed it, which tickets it creates, which accepted-risk records it holds and which reports leave it. The archived catalog lists scanner, application security, cloud, bug bounty and ticketing connectors, so it is a reasonable template for the questions to ask of your own tenant. Then decide whether the next home for the program is inside Tenable or elsewhere, using the same steps that a Cisco customer would follow.

## Sources

- Tenable: plans to acquire Vulcan Cyber (29 Jan 2025): https://www.tenable.com/press-releases/tenable-plans-to-acquire-vulcan-cyber-accelerate-leadership-in-exposure-management (read 10 Nov 2026)
- Tenable: completes acquisition of Vulcan Cyber (7 Feb 2025): https://www.tenable.com/press-releases/tenable-completes-acquisition-of-vulcan-cyber (read 10 Nov 2026)
- Tenable One connectors: https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026)
- Vulcan platform page, Internet Archive 1 Jan 2025: https://web.archive.org/web/20250101093214/https://vulcan.io/platform/ (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/guides/after-vulcan-cyber-and-tenable/
