Platform · Dependency Mapping
Upstream and downstream dependencies on every asset, classified by service or data, scored by criticality, and built into the same record that holds the asset's vulnerabilities, continuity plan, and data governance.
Why it matters
Most security teams have an asset inventory. Some have a CMDB. Almost none have an accurate, current, criticality-scored dependency map of which assets rely on which, and how data flows between them. So when an incident hits, the blast radius is estimated in a meeting rather than read off a screen.
Alvor models dependencies as part of the asset record. Open any asset and you see its upstream services and data sources, its downstream consumers, and a criticality score on every link. The same register is where risks name the assets they affect and where continuity processes declare the assets they depend on, so each asset shows the strictest RTO and RPO those processes need.
Open an asset to see its blast radius and the continuity posture it inherits from the processes that depend on it.
On every asset
Five upstream services, three downstream consumers, every link criticality-scored. No tab-switching, no separate CMDB.
web-frontend:latest
vm-p-bastion-amd
Riyadh DR Data Center
orders-db-primary
EU Customer Portal
app.example.com
alvor-github-actions
main.manage.suite
exec-analytics
web-frontend:latest
vm-p-bastion-amd
Riyadh DR Data Center
orders-db-primary
EU Customer Portal
app.example.com
alvor-github-actions
main.manage.suite
exec-analytics
Capabilities
Built into the asset record, classified by type, scored by criticality, cross-linked across the platform.
Pan, zoom, and explore upstream and downstream dependencies as a node graph, with a synchronised list view alongside.
Each link has a type, such as service dependency, data dependency, network dependency or authentication, and you can add your own. A type's flags decide whether it passes criticality along and whether it marks a trust edge.
Each link carries a Critical, High, Medium or Low rating. A business service's criticality flows down its dependencies into each asset's effective criticality, and blast radius is read from the same edges.
Every asset shows its dependency counts at a glance. Five upstream, three downstream: how many things does this asset hold up.
Risks name the assets they affect, and continuity processes declare the assets they depend on. Each asset then shows the strictest RTO and RPO set by those processes' impact analyses.
Dependencies live on the asset record, alongside components, vulnerabilities, continuity, and data governance.
Where it fits
Questions
Every asset in Alvor carries its own dependency map. Open any asset and you see its upstream dependencies (what it depends on) and downstream dependencies (what depends on it) as an interactive graph, plus a flat list view. Each dependency has a relationship type, such as service dependency or data dependency, and a criticality rating (Critical, High, Medium, Low), so blast radius is visible at a glance.
Get started
Whether you lead security, run IT, manage compliance, or sit in the C-suite - we'll show you your view.