Payments data corruption — restore and replay
Data corruption · Severe but plausible · 3 affected service(s)
A defective vendor patch applied to the ACH engine corrupts posting records for four hours of morning traffic before detection. Processing halts; the recovery strategy is point-in-time restore followed by controlled replay and reconciliation of ~180,000 entries. Every hour of replay must be balanced before the next is released. Core posting integrity is protected but end-of-day cannot start until replay completes.
The Examiner persona is read-only — switch to any operating role to launch a live run. The Monte Carlo executes in a Web Worker: the interface stays fully responsive while 10,000 iterations run.
Firms must test their ability to remain within impact tolerances under severe but plausible disruption scenarios, increasing sophistication over time.
Institutions test critical operations against severe but plausible scenarios, using results to assess whether tolerances would be breached and to remediate weaknesses.
A proportionate testing programme (including advanced threat-led testing for significant entities) validates the entity's ability to withstand ICT disruption.
Banks maintain and test business continuity plans under severe but plausible scenarios to continue delivering critical operations through disruption.
Expectations are paraphrased for demonstration; consult the source instruments for authoritative text.