# SLA carry-over

GLOSSARY, read 10 Nov 2026

**Definition.** SLA carry-over is keeping the due dates and remediation deadlines on open findings across the move, so a finding found in March is still due on its March clock. Brinqa's default finding SLA calculates due dates from the risk score band: 7, 30, 90 or 365 days.

Export the due date and the first-found date for every open finding, then check whether the target recomputes dates from the load date. If it does, every open item restarts its clock and past-due counts reset to zero, which is not a result to report.

Kenna's API also reports past-due vulnerabilities by risk level and vulnerabilities by due date, which give you totals to reconcile against.

## A sourced example

Brinqa's SLA documentation states its default finding SLA defines service levels from risk scores and calculates due dates, with L1 due in 7 days and L4 due in 365 days.

## Related terms

- [risk score mapping](/glossary/risk-score-mapping/)
- [closed-finding history](/glossary/closed-finding-history/)
- [exception carry-over](/glossary/exception-carry-over/)
- [ticket re-linking](/glossary/ticket-re-linking/)

## Sources

- Source for the example: SLA carry-over: https://docs.brinqa.com/docs/sla (read 10 Nov 2026)

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