> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://docs.brainframe.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Dependency Tracking

# 🔗 **Dependency Tracking**  
> **"See how everything connects."**  
> *Link assets, risks, policies, suppliers, and more* *to each other and into a single connected system.*  

---

## 1️⃣ Why Dependencies Matter  
In Brainframe, **everything is a document**. That means you can create dependencies between anything that makes sense, such as:  
* Assets → Risks & Assessments  
* Risks → Vulnerabilities  
* Policies → Procedures  
* Contacts → Suppliers  

📌 *Dependencies give you a **360° view** of how items relate to each other.*  

---

## 2️⃣ Creating Dependencies  
Some document types already come with predefined **“linkable” types** (e.g., CIA risks expect assets to be linked).  

To link documents:  
1. Start typing an existing document’s name.  
2. Or create a new document in the current folder using that name.  

![](https://storage.crisp.chat/users/helpdesk/website/-/3/f/2/6/3f26ce462760bc00/screenshot-2026-07-08-at-11193_1tmjqgg.png)

Once created, you can always add or modify links using the **link icon** in the folder or document view.  

![](https://storage.crisp.chat/users/helpdesk/website/-/3/f/2/6/3f26ce462760bc00/screenshot-2026-07-08-at-11210_1d1p6m8.png =574xauto)

---

## 3️⃣ Viewing Linked Documents  
Dependencies appear under the **“Linked documents”** area of both documents.  

![](https://storage.crisp.chat/users/helpdesk/website/-/3/f/2/6/3f26ce462760bc00/screenshot-2026-07-08-at-11230_12lhdh2.png =471xauto)

*Example: A Corrective Action linked to the **InfoSec Policy**, which is also visible directly from the InfoSec document.*  

![](https://storage.crisp.chat/users/helpdesk/website/-/3/f/2/6/3f26ce462760bc00/screenshot-2026-07-08-at-11232_1pgqiw0.png =657xauto)


---

## 4️⃣ Visualizing Dependencies  

💡 To see dependencies as a **graph**, select **“Show dependencies in graph diagram.”**  

![](https://storage.crisp.chat/users/helpdesk/website/-/3/f/2/6/3f26ce462760bc00/screenshot-2026-07-08-at-11251_blv6ee.png =872xauto)

![](https://storage.crisp.chat/users/helpdesk/website/-/3/f/2/6/3f26ce462760bc00/2_1cadjx9.png =852xauto)


---

## 5️⃣ Graph Diagram Options  
When viewing dependencies in graph mode, you can configure:  

1. **Depth to auto load** – How many levels of dependencies to load (e.g., `2` loads first-level + their links).  
2. **Distance between nodes** – Adjust spacing in the visualization.  
3. **Export Image** – Save the graph as an image for reports.  
4. **Document type filter** – Only show specific document types (e.g., policies & procedures).  
5. **Selected node** – Current document and its dependencies (e.g., Okta with linked vulnerabilities).  
6. **Drill-down view** – Click a node to reveal its own dependencies (e.g., AWS Cloudfront links).  

| 📌 The graph view makes it easy to explain relationships to auditors or stakeholders.  

---

## 6️⃣ Best Practices  
* 📌 Always link related assets, risks, and suppliers for **full traceability**.  
* 💡 Use the **graph diagram** during audits to visualize dependencies.  
* 🔍 Keep dependencies updated when adding new risks or suppliers.  
* 📂 Use filters in graph view to simplify complex environments.  

---

### **🎯 Visual Checklist**  
* [x] Key assets linked to risks  
* [x] Policies linked to procedures  
* [ ] Suppliers linked to vulnerabilities  
* [ ] Graph diagram exported for audit  
* [ ] Dependencies reviewed yearly or during big changes