LOADING…
Platform  /  Business Resilience  ·  Module
BIA · continuity · recovery

When a supplier goes down,you don't.

Business impact analysis, dependency mapping and tested recovery - with supplier risk linked directly to the services that keep you running.

BIA drivenRTO · RPO trackedTested recovery
Why it's different

Supplier risk is business continuity.

When the supplier goes down, you go down. Map the dependency before the incident - and make the link visible to your board.

Business impact analysis

Score services by impact over time - RTO, RPO and maximum tolerable disruption.

Dependency mapping

An interactive dependency graph links each service to the suppliers, systems and assets it relies on - and auto-derives a per-service dependency-risk score from the map.

Continuity plans

Owned continuity plans per critical service - activation criteria, recovery steps, comms plan and an approval workflow, exportable to PDF.

Exercises & failover tests

Run and record exercises from tabletop to full failover - capturing achieved RTO against target, with findings tracked to closure.

Supplier-linked continuity

Supplier compromise maps straight to service impact - exposure known before the event.

Continuous review

Plans re-validated on change; gaps tracked to closure.

See it work

One screen. Every critical service. Live recovery.

FCA, PRA, DORA and the NCSC CAF all expect proven recovery of important business services within impact tolerance. Here it is - live, not a binder on a shelf.

 E2ERisk · Business Resilience postureLive
42
CRITICAL SVCS
7
OVER TOLERANCE
18
PLANS APPROVED
61%
TESTED 12M
DEPENDENCY RISK
Critical · 6High · 14Medium · 12Low · 10
SERVICES AT RISK
Citizen Portal · RTO 4h, no tested continuity planno planPayments · recovery time outside impact toleranceover toleranceCasework · single point of failuredep risk 82
Resilience posture

Prevent. Absorb. Recover.

A live resilience score across the whole lifecycle - not a binder on a shelf, a posture that moves as your controls, dependencies and tested plans change.

 resilience lifecycle · live postureLive
81
Resilience readinessBlended across Prevent, Absorb and Recover · recalculated as evidence changes
Prevent
84
Controls upstream of disruption
Supplier assurance88
Patching cadence76
Absorb
72
Redundancy & dependency risk
Dependency risk68
Concentration74
Recover
90
Tested, owned continuity
Plans approved12/14
Exercised (12mo)86%
The problem

An untested recovery plan is a plan that fails.

Without E2E Risk
BIA in a spreadsheet, last updated two years ago
RTO and RPO guessed, never tested against reality
Supplier and system dependencies undocumented
Recovery plans untested until a real incident hits
No link between resilience and supplier risk
With E2E Risk
A live BIA with RTO, RPO and MTPD per service
Recovery targets set, owned and tested on a schedule
Supplier and asset dependencies mapped end to end
Scenario and tabletop tests with actions tracked to closure
Resilience tied directly to the supplier risk register
How it works

From impact analysis to tested recovery.

01
Identify
Critical services
Owners assigned
02
BIA
RTO / RPO / MTPD
Impact over time
03
Map
Supplier dependencies
System dependencies
04
Plan
Recovery strategy
Roles & runbooks
05
Test
Tabletop to failover
Achieved RTO logged
06
Review
Post-test learning
Re-baseline
Why it's better

Four ways to do resilience. Three capture a fragment.

CapabilityBIA spreadsheetBCP documentsCMDBBusiness Resilience
BIA with RTO / RPOFrozen snapshotNot reallyAsset data onlyLive, criticality-scored
Dependency graphNoneFree textWiring, not impactInteractive, FK-linked
Cascade / blast radiusNoneNonePartialMapped before the incident
Tested continuity + logNoneFiled, never testedNoneTabletop to full failover
Recovery-readiness scoreNoneNoneNonePrevent / Absorb / Recover
Connected to your platformRe-keyedRe-keyedSeparate toolReuses services, assets, risk & CAF
Framework depth

One critical service, resilience evidenced.

Critical service
Recovery of a citizen-facing payments service within its agreed recovery-time objective.
This maps to
ISO 22301Business continuity management
NCSC CAF D1 / D2Response & recovery planning
Operational resilienceImportant business services
NIST CSF 2.0RC - recover
Outcomes

Recovery you can actually evidence.

3-phase
Prevent, Absorb, Recover score
Full failover
to tabletop exercises
Achieved RTO
logged against target
ISO 22301
+ NCSC CAF Objective D
What you get

Proof you can recover, not just hope to.

BIA & recovery targets

RTO, RPO and MTPD per critical service, with impact modelled over time.

Dependency map

Every supplier and system a service relies on - concentration risk made visible.

Tested recovery plans

Tabletop and scenario exercises with findings tracked through to closure.

Native to your frameworks

Map once. Report against everything.

ISO 22301NCSCNIS RegulationsNIST SP 800-34DORABCI Good Practice
Business Resilience

Know the blast radius before the breach.

Pre-map supplier dependencies to critical services, so ‘are we exposed?’ is answered in minutes.

See Supplier Assurance