> 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-loss-prevention.md).

# Data loss prevention

## **Industry challenge**

Taking active measures to prevent the loss of sensitive data stored in SaaS applications is critical for your business longevity. 

Employees routinely share Personally Identifiable Information (PII), Payment Card Industry (PCI) and Personal Health Information (PHI). This sharing takes place in overexposed locations such as public Slack channels and Microsoft Teams chats. Leveraging the security controls that are native to each SaaS application does not prevent sharing this data or targeting it for removal. 

File-scanning offered by traditional Data Loss Prevention (DLP) solutions also creates too many false positives and overloads security teams with detections to review.

## **DoControl solution**

DoControl’s SaaS Data Loss Prevention utilizes natural-language processing (NLP) for real-time discovery, classification and protection of sensitive data types, including PII, PHI, PCI, secrets, and credentials.

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

### Context-based data classification

Avoid false positives with a context-based DLP to detect sensitive information.

DoControl’s DLP leverages a combination of custom keywords, RegEx, and business context from IdP, EDR and HRIS to distinguish between normal business activity and actual data loss.

### Automated, real-time remediation

Prevent data loss with pre-defined, automated remediation workflows.

DoControl immediately quarantines or removes sensitive data shared in SaaS applications according to your SaaS security policies.

### End-user empowerment and education

Increase security awareness with proactive engagement.

DoControl empowers your employees to independently remediate sensitive data exposure where possible via automated workflows, ensuring data loss risk reduction through increased awareness.

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2F7tI9ktwoXivoPxbtuTB3%2FPII%20playbook.gif?alt=media&amp;token=9a5ee635-25d1-44e7-816c-b6fc902ddc3d" alt=""><figcaption><p>Playbook for scanning and deleting a file in Slack containing PII </p></figcaption></figure>

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2Fql1w8vzbhuIak8XqQvY9%2Fisolate%20asset.gif?alt=media&amp;token=80f6d4ee-18e1-4a03-9918-d5884a2f75d2" alt=""><figcaption><p>Playbook for removing sharing of a file from a specific folder</p></figcaption></figure>

{% hint style="success" %}
For more information on PII scanning, see:

* [PII scanning](/docontrol-user-guide/system-management/settings/legal-consent-for-pii.md)
* [Query action](/docontrol-user-guide/workflows/define-workflow-settings/action-settings/query/pii-scan.md)
  {% endhint %}


---

# 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-loss-prevention.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.