> For the complete documentation index, see [llms.txt](https://docs.sola.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sola.security/resources/prompt-library/data-security.md).
# Sola for Data Security
Files and data are shared across cloud storage, collaboration tools, and email, often without visibility into who has access.
Sola helps you detect externally shared files, exposed cloud storage, and risky sharing patterns across Google Drive, S3, Slack, and other connected systems.
This page explains the key concepts behind **data loss prevention** and **file exposure**, what it is, why it matters, and how Sola helps you monitor it.
Get started with these below **ready-made Ask and Build prompts**, or the **Prompt Library**, both available directly in the Sola chat interface.
Ask: Check for exposed files
Copy this prompt into [Sola AI](https://app.sola.security/) to get started:
{% code overflow="wrap" %}
```
I want to discover which files and documents are exposed externally or shared too broadly. Guide me to identify which data source I should connect first - such as Google Workspace or AWS S3 - or if I already have one connected, ask me which to use. Then help me find issues like overshared documents, externally shared files, public links, or S3 bucket exposure that could lead to data leaks. Guide me to the best next step to quickly experience Sola's value. Do this as an interactive conversation, guide me one step at a time, avoid long explanations upfront, and pause for my response.
```
{% endcode %}
Build: Data exposure monitoring
Copy this prompt into [Sola AI](https://app.sola.security/) to get started:
{% code overflow="wrap" %}
```
I want to build an app that continuously monitors file exposure and sharing risks. Guide me to identify which data sources I should connect first - such as Google Workspace or AWS S3 - or if I already have one connected, ask me which to use. Then help me build queries to detect issues like overshared documents, externally shared files, public links, and unusual sharing patterns, create canvases visualizing exposure trends over time, and set up alerts for external data sharing. Guide me to the best next step to quickly experience Sola's value. Do this as an interactive conversation, guide me one step at a time, avoid long explanations upfront, and pause for my response.
```
{% endcode %}
## What is DLP and File Exposure?
Data loss prevention (DLP) is the practice of detecting and preventing sensitive data from being shared, accessed, or exposed beyond its intended audience. File exposure refers to documents, cloud storage buckets, or data accessible to external users, the public, or individuals who should no longer have access.
In simple terms, DLP and file exposure monitoring helps answer the question:\
\&#xNAN;***"Who can see my data, and should they be able to?"***
Risks addressed include:
* Google Drive files shared publicly or with external users or domains.
* Cloud storage buckets with public or cross-account access.
* Files shared with former employees or expired contractors.
* Unusual spikes in external sharing activity.
* Sensitive content shared through Slack channels accessible to guests.
## Why is DLP and File Exposure important
Unmonitored file exposure is one of the most common and underreported sources of data leakage.
Public links, misconfigured storage, and files shared with the wrong people create persistent risk that goes undetected without active monitoring. A single improperly shared document can expose sensitive data, and files containing API keys or access tokens can give attackers direct access to internal systems.
Most organizations lack a unified view of where their data is going across Drive, Slack, email, and cloud storage.
## DLP and File Exposure with Sola
Sola unifies file exposure signals across Drive, Slack, email, and cloud storage into a single view.
With Sola, you can:
* **Identify** files shared externally across Google Drive and other collaboration tools.
* **Audit** cloud storage exposure across S3 and other services, including bucket policies and ACLs.
* **Surface** unusual or anomalous sharing behavior and flag statistical outliers.
* **Detect** sensitive content shared with external users, contractors, or the public.
* **Identify** gaps in existing DLP policies, including platforms and data types not covered.
## Prompt library examples
Browse and run these prompts directly from the Prompt library in the Sola chat interface.
External File Sharing Overview
{% code title="PROMPT" overflow="wrap" %}
```
List all Google Drive files shared externally. Group by exposure type: shared with specific external users, shared with external domains, and ‘anyone with the link.’ Include the file owner, last accessed date, and the sensitivity classification if available.
```
{% endcode %}
High-Risk Document Exposure
{% code title="PROMPT" overflow="wrap" %}
```
Identify Drive files with the broadest exposure - ‘anyone with the link’ or shared with 5+ external collaborators. Highlight files owned by Finance, Legal, HR, or Engineering, where data sensitivity is highest.
```
{% endcode %}
Cloud Storage Exposure Audit
{% code title="PROMPT" overflow="wrap" %}
```
List S3 buckets and objects with public or cross-account access. Include bucket policies, ACLs, and which identities have read or write permissions. Flag any bucket that has had external access in the last 30 days.
```
{% endcode %}
Anomalous External Sharing Trends
{% code title="PROMPT" overflow="wrap" %}
```
Which users or teams have had the largest increase in external file sharing over the last 30 days? Flag anyone whose sharing activity is a statistical outlier compared to their historical baseline or peer group.
```
{% endcode %}
DLP Coverage Gap Analysis
{% code title="PROMPT" overflow="wrap" %}
```
Where are the blind spots in my current data loss prevention posture? Identify data types, platforms, or sharing patterns that fall outside existing DLP policies and suggest which gaps present the greatest immediate risk.
```
{% endcode %}
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.sola.security/resources/prompt-library/data-security.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.