> 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/risk-management/alerts/configure-alerts/configure-global-settings/sensitive-keywords.md). # Sensitive keywords You can configure keywords to [trigger](#triggering-keywords) or [suppress](#suppressing-keywords) alerts based on the file name. Keywords help to optimize your security monitoring, reduce noise, and improve the precision of your alerts. DoControl alerts are triggered when potentially sensitive files are shared. A file is considered sensitive if: * DoControl's sensitivity model assigns a high score to the file name, or * A customized keyword from the Alert triggers list is detected in the file name. ## Triggering keywords You can customize keywords that generate alerts for sensitive content. If the file name contains any of the triggering keywords, the file is considered sensitive and an alert is triggered. **For example**: Keywords such as "confidential," "payroll," or "medical" most probably indicate sensitive information, even if the file's contents are encrypted or not scannable.
**To add sensitive keywords to trigger alerts:** 1. In the **Alerts** page, click **Configure alerts.**
2. Under **Triggering keywords**, click **Add** 3. Enter up to 1000 keywords. {% hint style="success" %} * You can add multiple-word keywords with spaces, such as "date of birth" or "credit card." * Keywords are **case-sensitive** and can **contain spaces**. DoControl detects the keyword exactly as it is entered. For example, if the file name includes "Salary" and the lexical list item is "salary" then a match will **not** be found. * After entering each keyword, click **Enter** or the **Add** button to add it to the list. Click **X** to remove a keyword. * You can also customize alert triggers in [lexical lists](/docontrol-user-guide/system-management/settings/lexical-lists.md). {% endhint %} ## Suppressing keywords If the file name contains suppressing keywords in the excluded list, the file is considered less sensitive and an alert is **not** triggered. Configuring exclusion criteria helps to reduce alert fatigue, since files that are non-sensitive or low-risk can be ignored. You can customize keywords that do **not** generate alerts. If the file name contains any of the suppressing keywords, the file is **not** considered sensitive and an alert is **not** triggered. **For example**: You can ignore files that match exclusion criteria, such as if they contain any of these words: test, announcement, newsletter, schedule, presentation, training. {% hint style="info" %} If keywords from both the **Triggering keyword** and **Suppressing keyword** lists are detected in a file name, an alert is still generated. {% endhint %}
**To add keywords to suppress alerts:** 1. In the **Alerts** page, click **Configure alerts.**
2. Under **Suppressing keywords,** click **Add** 3. Enter up to 1000 keywords. {% hint style="success" %} * You can add multiple-word keywords with spaces, such as "date of birth" or "credit card." * Keywords are **case-sensitive** and can **contain spaces**. DoControl detects the keyword exactly as it is entered. For example, if the file name includes "Salary" and the lexical list item is "salary" then a match will **not** be found. * After entering each keyword, click **Enter** or the **Add** button to add it to the list. Click **X** to remove a keyword. * You can also customize alert suppressors in [lexical lists](/docontrol-user-guide/system-management/settings/lexical-lists.md). {% endhint %} ## Alert types with sensitive keywords All these DoControl alert types leverage sensitive keywords when generating an alert. An alert will be triggered If: * A keyword from the Alert triggers list is detected in the file name. * DoControl's sensitivity model assigns a high score to the file name.
Alert IDDoControl alert type
DC3External sharing of sensitive files
DC6Public sharing of sensitive files
DC7Shared sensitive file with private email
DC8Shared sensitive file with personal email
DC105Unprotected sensitive cloud recording is public
--- # 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/risk-management/alerts/configure-alerts/configure-global-settings/sensitive-keywords.md?ask=&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.