Impact.
Translate risk into service impact over time: model how disruption escalates through real dependencies and where it reaches your customers.
Impact isn't a severity label.
It's a curve that grows with time.
Horizon turns business impact analysis into a continuously connected model, grounded in the operational topology from Blueprint, not a static spreadsheet. Impact escalates as disruption duration increases, and Horizon traces that escalation through dependencies to make the full blast radius visible.
When the model changes, risk exposure and impact analysis update automatically, and resilience gaps surface before an incident proves them.
Modeled forward,not reconstructed after.
Recovery Objectives Grounded in Reality
Recovery objectives should be grounded in modeled service impact, not maintained as static workshop outputs.
Horizon derives RTO, RPO, MTD, and Impact Tolerance from the impact timeline itself.
Defined by the thresholds that actually matter.
Customers, markets, and regulators: each with its own point where harm becomes intolerable.
Cascading Impact & Blast Radius
When an asset fails, the impact doesn't stop there.
It travels downstream through dependent services, applications, and customer journeys.
Horizon traces the cascade and quantifies the blast radius.
How deep it goes, what it touches, and what stays standing.
Time-Based Impact Modeling
Impact isn't a static severity label. It's a curve that grows with time.
Horizon models how disruption escalates hour by hour, so you can see the exact moment a manageable outage becomes intolerable.
Threat Modeling
A ransomware attack and a data center failure aren't the same incident.
Different assets, different durations, different regulatory obligations: each captured structurally in the threat model.
Every recovery strategy links to the assets it actually protects.
No more generic playbooks that assume uniform impact.
Resilience Gap Analysis
Surface the blind spots before they matter.
Assets with no recovery strategy, and strategies that fall short of their RTO.
Test against the threats most likely to hit, not just the ones already in the playbook.
ILLUSTRATIVE EXAMPLE
What one failurereaches.
23
APPLICATIONS HIT
70%
THROUGH ONE COMPONENT
8
NO VALIDATED RECOVERY
IMPACT ESCALATES WITH DURATION
- T+1hDegradedcascade reaches three customer services
- T+4hMaterial70% of customer impact flows through one middleware component
- T+9hIntolerableregulatory impact tolerance breached
- Paymentsdirect · hosted in the failed data center14 apps
- Client reportingcascaded · shared middleware dependency6 apps
- Onboardingperipheral · manual fallback keeps it standing3 apps
Every service in the radius traces back through the dependency path that carries the impact.
Query the impact.Research the threat.
Query impact before disruption hits.
Ask what-if questions about blast radius, recovery timelines, and cascading impact. Answers follow your topology and impact model, not a static risk register.
What's the blast radius if we lose the London DC?
Which services breach RTO after 4 hours?
If our primary payments vendor goes down, when do we breach Impact Tolerance?
Turn threat research into structured intelligence.
AIRA surfaces regulatory requirements, cross-references industry incident data, and enriches threat definitions with credibility-tiered intelligence. Prove resilience with scenarios grounded in your operations. Simulate disruption end to end and walk away with validated playbooks.
Surface regulatory requirements for critical infrastructure resilience
Cross-reference industry incident data for threat likelihood calibration
Draft threat definitions grounded in external intelligence
GROUNDED IN STRUCTURED DATA · TRACEABLE TO SOURCE · GOVERNED BY HUMAN APPROVAL
Walk into every reviewknowing exactlywhat's at stake.
Horizon gives your team risk-aware impact and resilience analysis that updates itself, grounded in your real dependencies, not last quarter’s assumptions.