Skip to content
After Kenna

PROGRAM GUIDE, read 10 Nov 2026

Keep the old tickets open and link the new findings to them, instead of closing and reopening

All guidesGlossary

Why tickets are the hardest part

Tickets are the one part of the program that engineers see every day. A migration that closes thousands of tickets and opens new ones tells every team that the program is unstable. It also breaks the history: the ticket that was opened on a given date and closed on another is the proof that the work happened.

The old platform holds a link between each finding and its ticket. That link is what you need to preserve. Without it you can still match by CVE and asset, but the match takes longer and produces more mistakes.

Start with the old platform. The Cisco export API covers asset, fix, vulnerability and finding models; its API reference also lists ServiceNow-format endpoints, including ServiceNow List Fixes and ServiceNow Search Vulnerabilities. Check whether the ticket identifier is a field in your export. If it is not, pull the identifiers from the ticketing system instead: list the tickets created by the integration account and read the CVE and asset from the description.

Whichever way you export, the key you want is three columns: ticket ID, CVE or finding ID, and asset identifier. Add the ticket status and the created and closed dates as extras.

Match in the new platform

Brinqa documents ticket sync with Jira and with ServiceNow, plus ad hoc ticket creation and ticket generation through automation. Read the sync page before the trial for which fields flow in which direction. Other platforms describe bidirectional ticketing on their marketing pages; ask for the documentation page, not the marketing claim.

Your test should cover four checks. The new platform should be able to attach to an existing ticket without editing it. Record whether a finding closes, reopens or stays open when its Jira ticket is closed. Record how it handles one ticket that covers many findings, and a finding whose ticket the old platform closed before cutover.

Run it team by team

Choose one engineering team with a moderate ticket volume. Switch its tickets over, and watch for a week. Check that nobody receives a duplicate ticket and that due dates have not moved. Then add the next team. A phased switch means a mistake affects one team, and the fix applies to all that follow.

On the day each team switches, turn off the old platform's ticket creation for that team's projects. Leave the old integration account in place but disabled, not deleted, until the audit period for those tickets ends.

  • Export ticket ID, CVE and asset identifier from the old side.
  • Test attach, close, reopen and one-to-many behavior in the trial.
  • Switch one team at a time.
  • Disable, do not delete, the old integration account.

Edge cases to test

Four patterns cause most of the trouble. The first is a ticket that groups many findings, for example one ticket per host, which the new platform may want to represent as many links. The second is a ticket that was split by an engineer into several, where the old link now points at a closed parent. The third is a ticket that was closed as not reproducible while the finding is still open. The fourth is a ticket in a project that has since been renamed or archived in Jira or ServiceNow.

For each pattern, pull ten examples from the old data and walk them through the trial by hand. Write what happened to each. If the new platform reopens a closed ticket, find out whether it comments on it, creates a new one, or changes the due date, and tell the engineering leads before they find out from their queue.

Finally, check the permissions of the integration account. The new platform needs rights to read and comment on existing tickets, and rights to create new ones in the right projects. In many companies the ticketing administrator approves these on a schedule, so ask early.

A last check concerns reporting. Many programs report mean time to remediate from ticket dates. When you re-link, keep the original ticket creation dates in the report source. If the new platform records its own link date, do not use that field for the metric. Compare the metric for the quarter before and the quarter after the switch, and if it moved, find the cause before you present the number.

Keep the mapping file you built. It is the only record of which old finding corresponds to which new one, and it is useful when a team asks in six months why a ticket exists.

Sources

  1. Kenna API: ServiceNow List Fixes, read 10 Nov 2026
  2. Request Data Export, Kenna Platform API, read 10 Nov 2026
  3. Brinqa: sync tickets with Jira, read 10 Nov 2026
  4. Brinqa service-level agreements, read 10 Nov 2026

Last reviewed 10 Nov 2026.