> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/getting-started/use-cases/data-access-governance.md).

# Data access governance

## **Industry challenge**

Businesses with multiple SaaS apps have no centralized way to view the significant number of assets stored in each application, no insight into the exposure for each asset (for example, what is shared, and with whom), and no option to take bulk remediation actions when necessary (for example, remove sharing for a large number of files). 

Permissions are continuously added and changed as employees and collaborators go about their work, and the overall number of files continually grows as the business scales out. This creates challenges for security teams when establishing consistent data access governance across all SaaS applications.

## DoControl solution

The first step in reducing SaaS data exposure is to govern your data access.

DoControl discovers all your SaaS data, classifies assets by sensitivity and risk level, and remediates exposure by enforcing policies for data sharing, usage, and retention.

{% embed url="<https://youtu.be/Q69viWO50Z8>" %}

### **SaaS data discovery and categorization**

DoControl instantly builds an inventory of all SaaS assets, categorized by relevant metadata including location and recent events. In a single pane of glass, you have a unified view of all SaaS activity.

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FfoPSyjntg4G31DmLX83J%2Fassets%20remediate%20public%20sharing.gif?alt=media&amp;token=9ba87e6f-97a5-4920-a92b-874cfca7bd97" alt=""><figcaption><p>Discover and remediate all your publicly shared assets</p></figcaption></figure>

### **Exposure mapping**

Prioritize risk by evaluating the sensitivity and exposure level of each asset.

DoControl’s machine learning-based classification model sets a sensitivity score for each data asset, and maps the level of exposure for internal, public and external sharing.

### **Data access remediation**

Remove historical exposure at scale and use automation for future enforcement.

DoControl lets you remove permissions on-demand from hundreds of thousands of assets within minutes, and set up granular, pre-built workflows triggered by users' risky actions.

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FPWOa0GYM8unEUk7LU7wg%2Fplaybooks.gif?alt=media&amp;token=59d80765-84a9-46cd-859d-a66f2be5c542" alt=""><figcaption><p>Choose from dozens of DoControl playbooks to remediate data overexposure</p></figcaption></figure>

{% hint style="success" %}

* Learn more about discovering your [asset inventory](/docontrol-user-guide/saas-data-monitoring/inventory/inventory-assets.md).
* Learn more about setting up [playbooks](/docontrol-user-guide/workflows/create-a-workflow.md#playbooks) to automatically remediate overexposure.
* Learn more about [alerts](/docontrol-user-guide/risk-management/alerts.md) to identify high-risk activity.
  {% endhint %}

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FvPilzlM1zh7l98qyHpnf%2Fremediate%20alerts.gif?alt=media&amp;token=1d854e32-5a4a-4c22-81a0-8e757d1351e6" alt=""><figcaption><p>See all alerts, filter them, get details on the actor/target, and learn about the risks and remediate</p></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.docontrol.io/docontrol-user-guide/getting-started/use-cases/data-access-governance.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.