CBCLA flashcards
CBCLA · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Recovery Time Objective
- The maximum time a business function can be unavailable before the impact becomes unacceptable. It sets the target speed for restoring processes, systems, and resources.
- Recovery Point Objective
- The maximum acceptable amount of data loss measured in time before an incident. It determines backup or replication frequency needed for each system.
- Maximum Tolerable Downtime
- The total elapsed time a function can be unavailable before unacceptable consequences occur. It must be greater than or equal to the RTO plus recovery time.
- Time-based impact curve
- A plot of impact severity against elapsed downtime at defined intervals. The point where impact becomes unacceptable establishes the maximum tolerable downtime for that function.
- Function prioritization tiers
- Grouping business functions by criticality, typically critical, essential, and deferrable. Tiering determines which functions receive recovery resources first.
- Dependency mapping
- Documenting the internal and external resources a function needs to operate, including people, systems, suppliers, facilities, and records. It reveals single points of failure.
- BIA owner validation
- The business function owner reviews and formally approves impact ratings, MTD, RTO, and RPO. Without owner sign-off, BIA results lack authority for strategy decisions.
- Hot site
- A fully equipped alternate facility with hardware, connectivity, and data ready for immediate operation. It supports near-zero RTO at the highest recurring cost.
- Warm site
- An alternate facility with partial infrastructure and connectivity that requires hours to days to become operational. It balances cost against a moderate recovery time objective.
- Cold site
- An alternate space with power and basic environmental controls but no pre-installed technology. Activation typically takes days to weeks, suitable only for long tolerable downtimes.
- Reciprocal agreement
- An arrangement where another organization provides space or capacity during a disruption. It is inexpensive but depends on partner capacity and must be documented and tested.
- Synchronous replication
- Data is written to the primary and secondary location before the transaction completes. It yields near-zero data loss but adds latency and requires adequate network bandwidth.
- Manual workaround
- A documented interim procedure using paper or alternate tools when systems are unavailable. It is time-bounded and must be exercised because it cannot sustain operations indefinitely.
- Annualized loss expectancy
- Single loss expectancy multiplied by annualized rate of occurrence. It estimates expected yearly loss and supports cost-benefit comparison of continuity strategies.
- Strategy gap acceptance
- When no affordable strategy meets the RTO, the business owner formally accepts the residual risk or funds the gap. Acceptance must be documented at the right authority level.
- Plan activation criteria
- Objective thresholds such as outage duration, casualties, or facility loss that trigger plan invocation. Clear criteria prevent delay caused by debate over whether to activate.
- Emergency operations center
- The designated coordination location for incident management, with an identified alternate site, communications equipment, and predefined roles for responders.
- Call tree
- A structured notification sequence where each person contacts designated others. It requires current contact data and periodic testing to confirm reachability.
- Plan hierarchy
- The layered structure of enterprise, business unit, and function-level plans plus incident-specific annexes. Each layer addresses decisions appropriate to its scope.
- Role succession depth
- Each critical plan role has named backups, typically at least two, with documented authority. This prevents paralysis when primary responders are unavailable.
- Crisis communications plan
- Predefined audiences, owners, channels, message templates, and approval paths for communicating during an incident. It covers employees, customers, regulators, media, and suppliers.
- Plan assumptions
- Conditions the plan presumes to be true, such as staff availability or supplier response. Each assumption must be documented and validated through exercises.
- Tabletop exercise
- A discussion-based session where participants talk through a scenario and their responses. It validates roles, decisions, and communications but not technical recovery capability.
- Functional drill
- An exercise that actually executes a specific recovery procedure, such as restoring a system or activating a notification tool. It verifies capability rather than discussion.
- Full-scale exercise
- A live exercise involving actual relocation or recovery operations, often with external responders. It is the most realistic and most costly validation method.
- After-action report
- A document recording exercise objectives, what occurred, observed gaps and root causes, and corrective actions with owners and due dates. It drives program improvement.
- Exercise objective
- A measurable statement of what the exercise must demonstrate, such as restoring a function within four hours. Unmeasurable objectives cannot be evaluated afterward.
- Corrective action program
- A tracked process assigning findings from exercises, audits, and incidents to owners with due dates, including verification that the fix was effective.
- Maintenance triggers
- Events requiring plan review, such as reorganization, new technology, new critical supplier, audit finding, or scheduled annual review. They keep plans aligned with reality.
- Continuity maturity assessment
- A structured evaluation of program capability areas such as governance, BIA, strategy, plans, exercises, and maintenance. Scores indicate progression from ad hoc to optimized practice.
- Program performance metrics
- Quantitative measures such as exercise completion rate, corrective actions closed on time, plan currency, and training completion. They demonstrate program effectiveness to management.
- Supplier continuity evidence
- Documentation obtained from critical vendors, including certifications, test results, and contractual recovery commitments. It is reviewed at renewal or after material change.