PREPARE / CMDB
Know the blast radius before the bridge call asks for it
Every incident opens with the same four questions: which services are down, which business processes and customers feel it, which vendors are in the path, and whose rules now apply. When the answers live in a spreadsheet, a BCP binder, a vendor register and one senior engineer's head, the opening stretch of the incident goes to assembling them. Incident Lake ships with a CMDB built in, so infrastructure, business processes, sites and suppliers sit in one graph your responders can query mid-incident.
The answers you need are spread across four systems
Impact assessment tends to depend on whoever knows the estate best. The real test is whether the on-call engineer gets the same answer when that person is asleep or on leave.
Which customer-facing services sit downstream?
A failed host or switch is easy to spot. What it feeds, from the checkout flow to the partner API to branch operations, is not in the asset list.
Is this vendor breach our problem?
When a supplier discloses a compromise, someone has to work backwards from the contract register to find where you actually depend on them.
Which regulator, in which country?
Operate in several jurisdictions and the notification duties, and the clocks attached to them, change from site to site.
What did the topology look like when we decided?
In the review, you need to show why scope was drawn where it was. That means the configuration as it stood at the time, not as it stands today.
One graph: infrastructure, business processes, sites, suppliers
The CMDB lives in the same workspace as your incidents. The agent and your responders reason over the same data, with no context switch to another tool.
01 Graph
CIs and business services, connected
Configuration items and a BCP business layer share one graph, so you can walk from a low-level dependency all the way up to the business process it supports.
02 History
Point-in-time topology
Changes to the graph are kept as history, so you can reconstruct what the estate looked like when the incident began.
03 Search
Find things by what they do
With vector search, a query like “the database behind checkout” gets you to the likely CIs, even when nobody remembers the hostname.
04 Sites and regulation
Obligations mapped to locations
Register sites by country and region, tag them, and see which regulations may apply to each combination, along with the concrete to-dos.
05 Suppliers
A breach impact map for your vendors
Supplier management is wired into the graph. When a vendor is breached, the impact map shows which of your services and business processes depend on them.
06 Scale
Built for real estates, not demos
List views and bulk operations handle CMDBs in the thousands of items. Sync from NetBox or ServiceNow rather than maintaining a second source of truth by hand.
During an incident: propose the scope, then commit to it
The agent proposes a blast radius from the graph; the incident commander reviews and confirms it. Nothing gets scoped without a human decision.
01
Propose
Link the affected service and the agent walks the graph, listing the business processes, services and sites that may be hit.
02
Check vendors and obligations
Review the suppliers in the path and the regulations flagged for each site. If a notification may be due, move straight into deadline tracking.
03
Record the rationale
The confirmed scope, and how you got there, stays on the incident record for the postmortem.
Illustrative mock. Demo video coming soon.
Deadline calculation and report drafting are covered on the regulatory reporting page.
In drills: find the gaps before production does
Drill scenarios can be generated from the services in your CMDB. Pulling the blast radius during a tabletop is a practical way to surface missing CIs and stale dependencies while nothing is on fire. Findings flow into problem management and the knowledge review queue.
Regulations and to-dos shown for a site and tag combination are prompts for review, not a legal determination. Confirm applicability with your legal or compliance team. This is general information, not legal advice.
Model one critical service and see what it touches
Sign up with a work email and company name. Already running NetBox or ServiceNow? Talk to us about syncing.