Home / Glossary / Business continuity plan
Glossary, read 12 Nov 2026
Business continuity plan in a SOC 2 examination, defined with a sourced example
The definition of Business continuity plan
This plan matters most when you include the Availability category in scope, but auditors look at it whenever the system description promises uptime or recovery. They read the plan, then ask for the last test, the result, and the changes made afterward. A restore test that was never run is the usual exception.
CP-2 spells out the content: essential functions, recovery objectives and metrics, contingency roles with contact information, how the essentials continue through a failure, and how full restoration happens without losing the controls originally in place. It also requires coordinating with incident handling, so the two plans should refer to each other.
Teams mix up a backup with a plan. A nightly database backup is one input. The plan states how long you can be down, who decides to fail over, how customers are told and who restores what. Put recovery time and recovery point targets in numbers, and test against them.
A sourced example
NIST SP 800-53 control CP-2 requires a plan that "Provides recovery objectives, restoration priorities, and metrics" and that is updated to include "lessons learned from contingency plan testing, training, or actual contingency activities". A restore drill logged with its measured time, compared to the stated objective, satisfies both halves. NIST SP 800-53 Rev. 5 control catalog (OSCAL), read 12 Nov 2026.
Related terms
Sources
- NIST SP 800-53 Rev. 5 control catalog (OSCAL), read 12 Nov 2026
- NIST CSRC glossary, business continuity plan, read 12 Nov 2026
Last reviewed 12 Nov 2026.