Map your critical systems and know what's untested.
Most business continuity and disaster recovery (BC/DR) plans describe systems in isolation. BastionIQ's infrastructure register captures what depends on what, recovery targets, owners and test history. It also flags where a recovery target can't be met because of something further down the chain.
Most DR plans describe systems in isolation, and get recovery sequencing wrong as a result.
A DR plan that says "restore the application server" without noting that the application server depends on the database, which depends on the storage array, which depends on the AD domain controller. That plan will fail in an actual recovery scenario. The sequencing will be wrong, systems will come up in the wrong order, and recovery will take longer than your recovery time objectives allow.
BastionIQ's infrastructure register captures dependencies explicitly, follows them through RTO chain analysis, and feeds them into the plans you generate. The problem shows up on your screen, not in the middle of a recovery.
Your infrastructure context, used across every module
Build your register
Add systems in the register. Give each one a Gold, Silver or Bronze criticality rating, an owner, and its linked runbooks and backup tools.
Map dependencies
Define what each system depends on. See the dependency chain for any system, and its blast radius if it fails.
Set RTO and RPO targets
Assign a recovery time objective (RTO) and recovery point objective (RPO) per system. RTO chain analysis flags any target your dependencies can’t support.
Use it everywhere
Your register feeds plan generation, exercise scenarios and incidents, so every output is specific to your environment, not a generic template.
What the infrastructure register includes
Criticality ratings
Assign Gold, Silver or Bronze criticality to each system, so everyone agrees what matters most when it comes to recovery.
Recovery targets and owners
RTO and RPO targets, owners, linked runbooks and backup tools for every critical system, in one register.
RTO chain analysis
Follows dependencies up to 10 levels deep and flags where a system’s RTO can’t be met because something it depends on has a longer or missing RTO.
Dependency chain and blast radius
See the full dependency chain for any system, and the blast radius of a failure: what else goes down with it.
Change classification
Classify changes to your systems. Plans show which linked infrastructure has changed since they were generated, so you know when a plan needs another look.
Test history
Keep a test history for each system, so you can see what’s been tested and what hasn’t.
One register. Every module benefits.
Your infrastructure register is the backbone of BastionIQ. Keep it current, and every plan, exercise and incident starts from your real environment. For the business side of recovery, pair it with the business impact analysis in Bastion Control.
Plan wizards pre-fill from your register, and the runbook wizard flags dependency and RTO issues before it generates.
Learn more →Exercise injects are tailored to your register, so scenarios reference your real systems.
Learn more →Link affected infrastructure to an incident, alongside the plans, runbooks and contacts your team needs.
Learn more →Your business impact analysis sets recovery targets for business functions and flags where DR plans can’t meet them.
Learn more →Know your estate. Know your gaps.
Free 30-day trial with the infrastructure register included. Set up in under 30 minutes.