Skip to content
After Kenna

FAQ, read 10 Nov 2026

30 questions, answered with the numbers

MethodGlossary

When does Cisco stop selling Kenna?
Cisco's End-of-Sale Date for Cisco Vulnerability Management, formerly Kenna.VM, Kenna.VI and AppSec, is March 10, 2026, the last day to order the affected products. The End of New Service Attachment Date for the subscription is the same day. The source is Cisco bulletin EOL15812, whose End-of-Life Announcement Date is December 10, 2025.
What is the last date I can renew Kenna?
Table 1 of Cisco bulletin EOL15812 lists June 11, 2026 as both the End of Service Contract Renewal Date and the End of Change/Renewal Date for the subscription. That date has passed as of 2026-11-10, so a term already in place runs to its own end date and cannot be extended by renewal.
When does Kenna support end?
Cisco's Last Date of Support for the Kenna subscription is June 30, 2028, defined in the bulletin as the last date to receive subscription entitlements, service and support. Between the March 10, 2026 end-of-sale and that date the subscription is supported but not sold, which is the window available for an overlap with a new platform.
Does Cisco name a replacement for Kenna?
No. Bulletin EOL15812 states that no replacement is available for Cisco Vulnerability Management. Tenable states on its Kenna page that Tenable One is the replacement Cisco endorses through SolutionsPlus, and that is Tenable's statement; the bulletin as read on 2026-11-10 does not say it. Nucleus, ArmorCode and Phoenix Security each publish their own Kenna pages.
What is bulletin EOL15812 and which version should I cite?
EOL15812 is Cisco's End-of-Sale and End-of-Life bulletin for Cisco Vulnerability Management, Vulnerability Intelligence and the Application Security Module. It is marked Amended and shows an updated date of May 6, 2026, while its announcement date is December 10, 2025. Cite the bulletin number, both dates and the read date in your migration file.
Is Cisco still developing Kenna?
Cisco's bulletin as read on 2026-11-10 does not say either way. ArmorCode states on its Kenna page, modified September 3, 2026, that Cisco confirmed it stopped developing new features, connector updates and algorithm improvements, with no support for CVSS 4.0 or EPSS v4. That is ArmorCode's claim, so ask Cisco for a written roadmap statement.
How do I get my data out of Kenna?
Use the Request Data Export API. It runs asynchronously for the models asset, fix, vulnerability and finding, in json, jsonl or xml, and returns a search ID valid for 30 days. Downloads are gzip, and fields can be chosen with export_settings. A daily full export can also be arranged through Cisco tech support.
How long do Kenna export results stay available?
Search IDs for Kenna data exports are valid for 30 days after the request is made, according to the Request Data Export reference page. Download and store the files yourself within that window, and run the export again before cutover so the final state is captured. Note the date and the record counts for reconciliation.
Why not just page through the vulnerability list?
Kenna's List Vulnerabilities endpoint fixes the page size at 500 and allows at most 20 pages, so one listing reaches 10,000 records. It returns open vulnerabilities by default and closed ones with the filter value closed. A program larger than that, or one that needs closed history, should use the export API instead.
Can I export closed findings and their dates?
Yes. Kenna's export filter accepts the status values open, closed, risk accepted and false positive, and vulnerability records carry closed_at, status_changed_at, last_seen_time and first_found_on. Export closed history separately from open items, because it feeds mean time to remediate and the audit trail, and it is the part most teams forget.
What happens to my Kenna scores in another tool?
They do not convert directly. The Cisco Security Risk Score is an integer from 0 to 100. Brinqa's SLA bands run on a 0 to 10 scale, Tenable's Vulnerability Priority Rating is 0 to 10, and Nucleus describes its Threat Rating as running from low to existential with no numeric scale found. Map by band and test on a parallel run.
Who leads the alternatives list for teams leaving Kenna?
On the Cisco Vulnerability Management alternatives list, Brinqa leads with 7.20 and Nucleus is second with 7.05, a margin of 0.15 over 11 platforms on the Method page. The margin is narrow: one point on Nucleus's unify or automation score would reverse it. The scoring method and each criterion are on the Method page.
Who leads the list for teams leaving Vulcan Cyber?
Brinqa leads the Vulcan Cyber alternatives list with 7.20, ahead of Nucleus at 7.05. The list covers 10 platforms and leaves out Tenable, because Tenable owns Vulcan Cyber. The margin is 0.15, so the order could change with one point on a single criterion. Ownership details are in the Tenable press releases of January 29 and February 7, 2025.
Who leads the list for teams leaving a spreadsheet?
Brinqa leads the spreadsheet alternatives list at 7.20, with Nucleus second at 7.05 across 11 platforms. Both read CSV files: Brinqa documents a CSV connector that builds its schema from the header row, and Tenable One's Open Connector ingests spreadsheets or files. Clean the sheet first: one row per finding and one identifier per asset.
Who leads the list for teams leaving Brinqa?
Nucleus leads the Brinqa alternatives list at 7.05, ahead of Tenable at 6.40, a margin of 0.65 across 10 platforms. A move to Nucleus is a migration, not a switch: connectors and ticket workflows have to be set up again, and scoring rules have to be rebuilt because Kenna's 0 to 100 risk score has no published counterpart in Nucleus, whose rating runs from low to existential.
What happened to Vulcan Cyber?
Tenable announced a definitive agreement to acquire Vulcan Cyber Ltd. On January 29, 2025, for about $147 million in cash plus $3 million in RSUs, and announced the close on February 7, 2025. Fetching vulcan.io on 2026-11-10 returned a 301 redirect to tenable.com. Tenable states Vulcan's capabilities are being folded into Tenable One.
Is Vulcan ExposureOS still sold on its own?
None found on 2026-11-10. The Vulcan site redirects to tenable.com, and Tenable describes the capabilities as folded into Tenable One, with integration ongoing. A Vulcan customer should ask the Tenable account team in writing which product the contract maps to, when it ends, and how data leaves, because no Vulcan end-of-sale bulletin was found.
Did anything change at Brinqa recently?
On August 19, 2026 Brinqa announced it acquired PlexTrac, an offensive security validation and reporting platform. By Brinqa's own count it serves over 3,000 customers in 57 countries and is the largest standalone unified exposure management vendor. Brinqa also shipped platform 11.34.24 on August 25, 2026, which needs a one-time data migration and an 8 to 10 hour window.
How long does a Kenna migration take?
No vendor publishes a figure that applies to every program. Nucleus states smaller customers can move in under 30 days and publishes a sample healthcare timeline; ArmorCode states most organizations see value within a few weeks. Both are vendor claims. Build your own estimate from the connector count, the export size, the ticket flows and the reporting calendar.
Should I run Kenna and the new platform side by side?
Yes, where the contract allows it. Nucleus states it runs in parallel with Kenna so results can be validated before cutover. Kenna is supported to June 30, 2028 under the bulletin, so an overlap is possible. Set exit criteria first: asset counts, open finding counts, and a tolerance on band changes. Check the term end and notice period in your order.
Can a vendor buy out my remaining Kenna term?
Three vendors publish offers, all theirs to decide. Nucleus states it may be able to buy out the remaining Kenna term for a limited time. Phoenix Security states it offers a Kenna buyout covering the remaining contract term. ArmorCode offers three years for the price of two, with guided migration and a risk-free switch guarantee. Eligibility and prices are not published.
What if my Kenna term ends before June 2028?
Cisco's last renewal date was June 11, 2026, so a term that ends before the June 30, 2028 last date of support is a decision date on your own order. Find the term end and the notice period in the contract, and set the cutover to land before them. The bulletin as read on 2026-11-10 states no notice period.
How do I carry over SLAs?
Export the first-found date and due date of every open finding, then check whether the target recomputes dates from the load date. Brinqa's default finding SLA sets due dates from the risk score band: 7 days for 9 to 10.1, 30 days for 7 to 9, 90 days for 4 to 7 and 365 days for 0 to 4. Kenna reports past-due counts by risk level to reconcile against.
How do I carry over risk acceptances and false positives?
Kenna holds them as statuses, risk accepted and false positive, which its export filter can select. Export each with the owner, reason and expiry fields the source holds, and review any that lapse in the next 90 days. Kenna also logs manual risk score overrides for audit, and its audit log search returns a gzip JSON lines file for a date range.
What happens to my tickets?
Open findings need to be re-linked to the tickets already raised, or the new platform will open duplicates. Brinqa documents a Jira ticket sync automation that you run and then check by source under Remediation, Tickets. Kenna's API has ServiceNow-format endpoints for fixes and vulnerabilities. Test in a sandbox project and compare ticket counts before and after.
How do I move users and roles?
Map roles first, then users. Kenna's roles carry asset group scope, updating a role's asset groups overwrites the current list, and a role cannot be deleted while a user is connected to it. Because roles depend on groups, finish tag and asset group mapping before roles. Remove unused accounts at cutover and test with real users.
What about tags and Risk Meters?
Tags drive routing, groups and reports, so map each Kenna tag to a target tag or attribute and compare group counts after load. A Kenna Risk Meter is an asset-group score with a history, which the API returns by asset group ID. Export the trend before cutover, because the new platform starts its own trend from its first day.
Will the connectors I use carry over?
Check source by source. Nucleus states Kenna has fewer than 40 integrations and Nucleus more than 200, while its catalog lists 183. ArmorCode's pages give 400+, 375+ and 325+ in different places. Treat counts as vendor claims and list your scanners, cloud feeds and ticketing systems against each candidate's connector pages, marking each covered, partial or none found.
Which vendors publish a Kenna migration page?
On 2026-11-10 the pages read were Nucleus (modified August 25, 2026), ArmorCode (modified September 3, 2026, plus a replacement demo page published August 19, 2026), Phoenix Security (December 22, 2025) and Tenable, whose Kenna page redirects to tenable.com/cisco. Each carries that vendor's own claims. The Cisco bulletin is the record of the dates.
How do I judge a trial before I sign?
Write pass-fail tests with a date: all scanners connected, asset count within an agreed tolerance, score bands compared on a sample, one report rebuilt and one ticket flow working. No Kenna migration page read on 2026-11-10 uses the phrase proof of value. Nucleus's offer to run both products in parallel is the closest, so agree the criteria yourself.

Where Nucleus is behind

A move to Nucleus is a migration, not a switch: connectors and ticket workflows have to be set up again, and scoring rules have to be rebuilt because the old platform's risk score (Kenna's runs 0 to 100) has no published counterpart in Nucleus, whose rating runs from low to existential. Nucleus states smaller customers move in under 30 days, a vendor claim, and it publishes no public technical documentation to plan the move from.

Last reviewed 10 Nov 2026.