# Explore the dependency map

Connect activities and vendors to understand failure impacts.

> **Access:** member. **Beta** feature, subject to enabled modules and your plan.

## Prepare the data

The map uses activities and their vendor relationships. Create business activities and link supporting vendors first. Without relationships, the map can be empty even when vendors exist in the register.

## Explore the map

1. Open **Steering → Map of outbuildings**.
2. Find activities and the subjects they depend on.
3. Use the offered filters and presentation options.
4. Open accessible details to examine important relationships.
5. Consider this alongside criticality and identified risks.

![Dependency map connecting activities and vendors](https://docs.cisapp.eu/images/en/dependencies.webp)

*A relationship missing from the registers cannot be inferred by the map. · [Open full-size screenshot](https://docs.cisapp.eu/images/en/dependencies.webp)*

## Expected outcome

You can identify activities affected by vendor unavailability and prepare questions for review.

## Empty or incomplete map

Check relationships in activity records, filters and permissions. An isolated vendor may indicate a missing link; it is not proof that the vendor has no business impact.

To find shared dependencies, see [Concentration](https://docs.cisapp.eu/en/reporting/concentration).