Skip to content
After Kenna

PROGRAM GUIDE, read 10 Nov 2026

Move SLAs and exceptions as records with owners and expiry dates, not as counts

All guidesGlossary

What counts as a record

An SLA in a vulnerability program is a due date per finding, derived from a policy: for example 15 days for items in the CISA KEV catalog and 30, 60 or 90 days by severity for the rest. The clock starts when the finding is first seen, not when it is loaded into the new platform. If you let the new platform restart the clock, every overdue item looks new and your overdue count falls to zero for the wrong reason.

An exception is an accepted risk. Each one needs the finding or rule it covers, the reason, the approver, the date approved, the expiry date and any compensating control. A yes or no flag is not an exception record. An auditor will ask for the approver and the date.

Find them in the old platform

In Cisco Vulnerability Management, the API exposes fix and finding models in the data export, in json, jsonl or xml. Look for status fields and due dates in a first full export before you decide the mapping. We did not find a documented exception model in the API pages read; check your own tenant for how accepted risk was recorded, and ask Cisco support if it is stored somewhere other than the export.

If the exceptions live in a ticket, a spreadsheet or a GRC tool, they are outside the platform, and the move is easier. If they live only as a status inside the platform, export them and verify that the approver and expiry are in the file. Vulcan Cyber's archived platform page said customers could mark accepted risk and that the product tracked SLA compliance; the export route for either: none found on 2026-11-10.

Map the fields

Brinqa documents an SLA data model and risk factors, and supports ticket sync with Jira and ServiceNow. Other platforms describe SLAs and approved exceptions on their pages; Nucleus states that it supports automatic ownership, SLAs and approved exceptions, which is a vendor claim from marketing pages. Ask each candidate for a field list, not a feature statement.

Use a mapping table and send it to the vendor in your proof of concept. Ask the vendor to load three exceptions, one active, one expired and one expiring in 7 days, and show what each looks like in the console.

Old fieldNeeded in new platformTest
Finding first seen dateStart of SLA clockOverdue count matches the old count on the cutover date
Policy tierSLA lengthSame finding gets the same due date
Exception approverApprover name or IDVisible in the record
Exception expiryExpiry date and reopen behaviorExpired item returns to the queue
Compensating controlFree text or linked recordPresent in an audit export

Test the awkward cases

Run four tests in the proof of concept. An exception that expires during the migration should return to the open queue on its date. An exception covering a rule, not a single finding, should still apply to new findings that match it. A finding that closes and reopens should keep its first seen date. A finding that moves from one scanner to another should keep its SLA clock.

Keep the old platform's records for the audit period. The exceptions you carried are copies; the originals are the evidence of what was decided and when.

  • Export all exceptions with approver, date and expiry.
  • Preserve first seen dates for SLA clocks.
  • Load one active, one expired and one expiring exception in the trial.
  • Archive the originals with a hash.

Who signs the exceptions again

Some programs ask exception approvers to sign again on the new platform. That is a sound practice when the approver has changed or when the exception was written against a score that no longer exists. An exception that said accepted because the Kenna score was 40 means little when the new platform scores the same item 3 out of 10.

Prefer to carry the original approval with its original date and add a review date. Do not backdate anything. If the approver has left, record who now owns the decision. Where the exception depended on a compensating control, check that the control is still in place before you carry the record forward.

Report the carried exceptions once, as a count by approver and expiry month, to the director or the audit committee. It shows that nothing was dropped, and it gives the first expiry dates a chance to be seen in advance. Exceptions that expire during the migration window deserve a calendar entry of their own, since the team is busy and an expiry nobody sees becomes an overdue finding.

Sources

  1. Request Data Export, Kenna Platform API, read 10 Nov 2026
  2. Brinqa service-level agreements, read 10 Nov 2026
  3. Brinqa: sync tickets with Jira, read 10 Nov 2026
  4. Vulcan platform page, Internet Archive 1 Jan 2025, read 10 Nov 2026

Last reviewed 10 Nov 2026.