DB FPX 8650 Assessment 2

Specific Business Problem

HarborTrust relies on several heritage core banking systems, third-party platforms (payments, document imaging), and a growing remote pool. There’s no consolidated BC DR program that maps critical processes to recovery time objects (RTOs) and recovery point objects (RPOs), performs regular provisory confirmation, or executes cross-functional recovery playbooks. Recent near-miss seller outages caused multi-hour service interruptions with homemade workarounds that created data conciliation issues and client escalations. 

Gap in Practice

The gap in practice is the lack of an integrated, governance-backed business durability & disaster recovery program that (a) supplies critical means processes and their RTO/RPO conditions; (b) maintains current, tested recovery playbooks and runbooks; (c) conducts regular, cross-functional tabletop and live recovery exercises; (d) validates backups and alternate point readiness; and (e) embeds BC/DR into change operation for major system upgrades and seller contracts. Liabilities are disintegrated across IT, threats, and operations with no single program proprietor or regular administrative reporting. 

The reason for selecting this specific gap in practice is that functional outages of banking services (such as payments, online banking, and teller systems) quickly erode client trust, lead to regulatory scrutiny, and can result in direct financial loss.

Functional outages of banking services (payments, online banking, teller systems) fleetly erode client trust, induce nonsupervisory scrutiny, and can beget direct fiscal loss. The gap explains habitual homemade workarounds, slow recovery after incidents, and inconsistent seller readiness. It’s measurable (MTTR, RTO/RPO compliance, exercise pass rates, number of untested backups), practicable (force, playbooks, exercises, seller SLAs), and aligned with strategic and nonsupervisory precedences (durability of service, third-party threat operation). 

The research and effectiveness of the chosen gap in practice standards and guidance are crucial.

Standards and guidance (ISO 22301, NIST SP 800-34, FFIEC Business Continuity Management pamphlets) emphasize the value of a formal BC/DR lifecycle business impact analysis (BIA), threat assessment, strategy selection, plan development, testing/exercises, and nonstop enhancement. Organizations that institutionalize BC/DR with clear RTO/RPOs, tested recovery procedures, and seller adaptability clauses recover briskly, reduce data-loss threat, and demonstrate stronger nonsupervisory compliance. Regular exercises and validated backups are constantly shown to be the most effective ways to turn plans into dependable issues. 

DB FPX 8650 Assessment 2: Project of Interest

“RecoveryReady Pilot”—a ”5-month program to establish a foundational BC DR capability for three critical services. Core Banking, Online Banking/Payments, and Document Imaging. Core factors 

1. Governance & power—appoint a BC/DR Program Lead reporting to Threat/Susurrus and form a cross-functional BC/DR working group with an administrative guarantor. 
2. Business Impact Analysis (BIA)—chart critical processes, their dependencies (systems, merchandisers, people), and set RTOs, RPOs, and precedence recovery categories. 
3. Force & runbooks—produce an authoritative force of critical means and produce terse recovery runbooks (proprietor, way, alternate connections, communication scripts) for each service. 
4. Provisional confirmation & alternate point readiness—perform backup restore tests for critical datasets and validate failover capability to an alternate point or pall recovery case. 
5. Tabletop & live exercises—run a tabletop for each service and one live failover drill (simulated cutover to alternate terrain) for the highest-precedence service. Capture assignments and update plans. 
6. seller adaptability alignment—review top merchandisers for contractual SLAs, recovery commitments, and bear remediation plans where seller readiness is inadequate. 
7. Reporting & nonstop enhancement—establish BC/DR KPI dashboard (RTO/RPO compliance, exercise pass rate, backup restore time) and a daily superintendent briefing. 
8. Anticipated issues  proved RTO/RPOs for airman services, tested and validated recovery runbooks, successful tabletop exercises, at least one validated restore/failover, reduced estimated MTTR for airman services, and formal seller remediation plans where demanded. 

Observations within My Workplace

• No single, current register of which upstream merchandisers support which client-facing services; brigades maintain coinciding lists. 
• Some backups are live, but restoration has not been validated end-to-end; provisory windows and retention vary by system. 
• Incident response has been politic; dispatches during outages are inconsistent and escalate client dissatisfaction. 
• Change  operation doesn’t  constantly spark BC/DR revalidation (e.g., after a major seller upgrade). 
• These functional issues lead to a fragile recovery posture and repeated homemade rapprochements after outages. 

Personal Biases

I favor structured, test-driven programs (BIAs, runbooks, exercises), which may underemphasize the need for cultural change (awareness, drills, leadership engagement). I must ensure the program balances practical testing with change-management and communication efforts so it becomes part of day-to-day operations.

Reflection

Developing this assessment emphasized that BC/DR isn’t simply an IT roster but an organizational capability taking governance, clear objects, and regular testing. Beforehand triumphs (a validated restore and a clear runbook) make credibility and reduce anxiety during factual incidents. Embedding BC DR into the seller’s operation and change control prevents decay of adaptability over time.