Map your critical systems — and know what's untested.
Most BC/DR plans describe systems in isolation. BastionIQ's infrastructure register captures what depends on what, RTO/RPO targets, and linked runbooks — so recovery sequencing is accurate and plan gaps are visible.
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 — 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 RTO targets allow.
BastionIQ's infrastructure register captures dependencies explicitly and uses them to sequence recovery correctly when generating plans — automatically.
Your infrastructure context — used across every module
Build your register
Add systems via the guided UI or import from a spreadsheet. Classify each system by type, criticality (Gold/Silver/Bronze), and data region.
Map dependencies
Define what each system depends on. BastionIQ builds the dependency graph and surfaces circular dependencies or sequencing risks automatically.
Set RTO/RPO targets
Assign recovery time and recovery point objectives per system. BastionIQ highlights where targets are unrealistic given upstream dependencies.
Use it everywhere
Your infrastructure register feeds into plan generation, exercise scenarios, and gap analysis — so every output is specific to your environment, not a generic template.
What the infrastructure register includes
Cloud, SaaS, and on-premises inventory
Catalogue every critical system — cloud accounts (AWS, Azure, GCP), on-premises servers, SaaS platforms, security tools, and network infrastructure — in one register.
Criticality ratings
Assign Gold, Silver, or Bronze criticality ratings to each system. These ratings feed directly into plan generation — Gold systems get first priority in recovery sequencing.
RTO and RPO targets
Set Recovery Time Objectives and Recovery Point Objectives per system. BastionIQ surfaces conflicts — where an RTO target is unrealistic given the dependencies — automatically.
Dependency mapping
Define what each system depends on and what depends on it. BastionIQ uses this map to sequence recovery correctly in your DR plans — so you're not restoring systems in the wrong order.
Linked runbooks
Link runbooks to specific systems in the register. During an incident, BastionIQ surfaces the relevant runbook automatically — no manual searching.
Gap visibility
BastionIQ highlights systems with no linked runbook, untested recovery procedures, or missing RTO/RPO targets — so you know exactly where your plan has gaps.
One register. Every module benefits.
Your infrastructure register is the backbone of BastionIQ. Every plan is generated from it. Every exercise scenario is built from it. Every gap analysis references it. Update it once — and everything else updates too.
Plans reference your actual systems, dependencies, and recovery priorities — not generic defaults.
Scenarios are built from your cloud accounts, EDR vendor, backup systems — making them realistic.
During an incident, the right runbooks and contacts for affected systems are surfaced automatically.
Know your estate. Know your gaps.
Free 30-day trial — infrastructure register included. Set up in under 30 minutes.