# rollback plan

GLOSSARY, read 10 Nov 2026

**Definition.** A rollback plan states how to return to the old platform if the new one fails its checks after cutover, and who decides. It needs the old contract to still be live, the final export, and a rule for data created in the meantime. ArmorCode advertises a risk-free switch guarantee.

The plan is only as good as the contract that sits under it. If the old term ends at cutover, there is nothing to roll back to, so the term end and the rollback window must be set together.

ArmorCode's Kenna program page lists the guarantee with guided migration, training and onboarding. The page read on 2026-11-10 does not state the guarantee's terms, so get them in writing.

## A sourced example

ArmorCode's Kenna replacement page, published 2026-08-19 by its page data, lists a risk-free switch guarantee as part of its three years for the price of two offer.

## Related terms

- [cutover](/glossary/cutover/)
- [parallel run](/glossary/parallel-run/)
- [contract notice period](/glossary/contract-notice-period/)
- [proof of value](/glossary/proof-of-value/)

## Sources

- Source for the example: rollback plan: https://www.armorcode.com/request-a-kenna-replacement-demo (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/rollback-plan/
