> For the complete documentation index, see [llms.txt](https://docs.trustlogix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trustlogix.io/trust-dspm/data-sprawl.md).

# Data Sprawl

TrustLogix generates the Data Sprawl report to showcase the following things

* All the outbound nodes to which your data source data is being sent to
* All the inbound nodes from which data is coming into your data source
* Security risk alerts that are tied to the inbound and outbound nodes
* Different types of data movements like Share activity, Large data being exported out etc.

The primary purpose of this report is to highlight various security issues like the ones below

* Is your sensitive data being moved to compromised data sources like a public AWS S3 bucket or Azure ADLS container
* Are unsanctioned User Applications connecting to your data source and performing risky activity 
* Cost impact of moving data to various downstream data sources
* Lack of data access controls on different objects within your data sources.

<figure><img src="https://815455107-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0SWnT1NcjBiPxnUvPcqE%2Fuploads%2F5yZtjZ1Rwfmch0Bh7Q4y%2Fimage.png?alt=media&amp;token=b854a34f-93ed-4731-b4de-da808e1d2860" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.trustlogix.io/trust-dspm/data-sprawl.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.