Dependency Atlas
Map business and technology dependencies, simulate outage or breach blast radius, and turn tabletop findings into a living resilience model—all in your browser.
Opening your local workspace…
From asset inventory to decision-grade resilience
Asset lists answer what an organization owns. A dependency model answers what happens next. Dependency Atlas connects business capabilities to the applications, identity systems, infrastructure, data, vendors, and manual procedures that keep them operating.
Start with exported evidence such as cloud tags, CMDB relationships, Nagios parents, or application inventories. Then enrich that technical evidence with ownership, criticality, recovery tolerances, fallback capacity, and confidence gathered from stakeholders.
Model
Record directed relationships in plain language and retain the evidence behind every imported or manually confirmed claim.
Simulate
Run separate outage and breach traversals to expose affected capabilities, likely data exposure, and low-confidence assumptions.
Validate
Use multidisciplinary tabletop exercises to discover missing systems, human constraints, policy gaps, and unrealistic recovery plans.
Interpreting the results responsibly
A graph makes hidden relationships easier to see, but it does not automatically prove operational failure or exploitability. Review low-confidence paths with system owners, distinguish observed communication from hard dependency, and validate fallback assumptions under realistic capacity and staffing conditions.
Frequently Asked Questions
Common questions about the Dependency Atlas
A dependency graph represents systems, capabilities, data, vendors, people, and controls as entities connected by directed relationships. It makes multi-hop dependencies visible, such as a business capability relying on an application that relies on a shared identity provider.
No. The tool processes imports and stores the active workspace locally in your browser. Download an Atlas workspace backup before clearing browser data or moving to another device.
You can import a flat CSV dependency list, an array of dependency records in JSON, or a complete .atlas.json workspace backup. A downloadable CSV template shows the supported source, relationship, target, type, criticality, and owner fields.
The tool traverses operational dependency relationships in the direction that failure propagates. It carries dependency strength, time tolerance, and the lowest confidence along each path so the result remains explainable.
Breach analysis follows storage, access, data-flow, and identity-trust paths rather than assuming that every operational dependency is an attack path. Connectivity indicates potential exposure, not proof of exploitability.
Yes. Entities and relationships use stable IDs and property-graph semantics. The CSV export produces separate node and relationship files suitable for mapping into Neo4j as the data set grows.
Capture observations and findings during the exercise, then verify proposed graph changes before treating them as authoritative. This keeps assumptions and incomplete information distinct from confirmed dependencies.
Explore More Tools
Continue with these related tools
⚠️ Security Notice
This tool is provided for educational and authorized security testing purposes only. Always ensure you have proper authorization before testing any systems or networks you do not own. Unauthorized access or security testing may be illegal in your jurisdiction. All processing happens client-side in your browser - no data is sent to our servers.