# Sensitive Strings

<mark style="color:green;">Sensitive Strings</mark> are <mark style="color:green;">user-defined keywords, patterns, or identifiers</mark> that represent critical data elements for the organization. These may include API keys, internal project codes, client tokens, legal references, employee identifiers, or any proprietary string whose exposure could lead to risk scenarios such as data leakage, impersonation, or regulatory violations.

The <mark style="color:green;">Inopli DRP module</mark> allows companies to configure these strings directly from the platform’s settings panel under the `Sensitive Strings` tab. Once registered and activated, each string becomes a monitored entity. The DRP engine will continuously inspect indexed content (surface, dark web, and other channels) for signs of exposure, correlation, or misuse involving these terms.

Findings are enriched with metadata, including context of exposure, severity, and source, and may trigger incident creation through the Response module if confirmed as valid by the analyst or an automated policy.

***

#### String Configuration Fields

Each entry includes the following fields:

* `type` – Category of the string to be monitored. Accepted types are: `API Key`, `Password`, `Token`, `Secret`, `Other`
* `value` – The actual keyword or string to be monitored
* `regex_pattern` – Optional field to define a custom regular expression pattern
* `case_sensitive` – Boolean that defines if the match is case-sensitive
* `exact_match` – Boolean to specify if only exact string matches are accepted
* `category` – Optional logical grouping (e.g., Legal, DevOps, HR)
* `severity` – Risk impact associated with string exposure (e.g., Low, Medium, High)

***

#### User Interface Example

Below is the platform screen used to manage and edit sensitive strings for monitoring

<figure><img src="/files/PwHVAsIFaKT2gM8kZgqF" alt=""><figcaption></figcaption></figure>

Each Sensitive String can be toggled on/off, and actions include edit or remove. Only active Sensitive Strings are monitored in real time.


---

# Agent Instructions: 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:

```
GET https://docs.inopli.com/drp/client-onboarding-and-configuration/monitoring-profiles/sensitive-strings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.