# exception carry-over

GLOSSARY, read 10 Nov 2026

**Definition.** Exception carry-over is moving accepted risks and false-positive decisions, with their owner, reason and expiry, into the new platform. Kenna keeps these as statuses: its export filter lists risk accepted and false positive alongside open and closed, and its API counts risk-accepted vulnerabilities over time.

An exception without its approver and expiry is just a hidden finding. Export the status together with whatever note and date fields the source holds, and check the expiry dates for anything that lapses in the next 90 days.

Vulcan's archived platform page describes marking accepted risk as a customer control, so Vulcan teams should check the same fields.

## A sourced example

Kenna's Request Data Export schema lists the filter values active, inactive, open, closed, risk accepted and false positive, and its Risk Accepted by Risk Level Over Time page counts risk-accepted vulnerabilities by level.

## Related terms

- [SLA carry-over](/glossary/sla-carry-over/)
- [Kenna risk score](/glossary/kenna-risk-score/)
- [closed-finding history](/glossary/closed-finding-history/)
- [ticket re-linking](/glossary/ticket-re-linking/)

## Sources

- Source for the example: exception carry-over: https://apidocs.kennasecurity.com/reference/request-data-export.md (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/exception-carry-over/
