> For the complete documentation index, see [llms.txt](https://docs.inopli.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inopli.com/drp/surface-web-monitoring/enrichment-strategies.md).

# Enrichment Strategies

Each piece of <mark style="color:green;">collected evidence</mark> undergoes normalization and classification. Language is detected and content is cleaned to eliminate false positives from formatting issues or irrelevant matches. When credentials, keys, or tokens are identified in code or web pages, the enrichment process cross-checks them against known brand domains, employee emails, or infrastructure patterns to confirm the likelihood of real exposure.

In cases involving <mark style="color:green;">domains or subdomains</mark>, WHOIS metadata, certificate transparency records, and DNS responses are added to determine whether the asset is newly registered, active, and potentially malicious. **Additionally,&#x20;**<mark style="color:green;">**all suspicious domains are validated against the Inopli internal threat feed**</mark>**&#x20;and public phishing repositories to confirm known malicious infrastructure and reduce false positives.** This step enhances the ability to quickly identify phishing threats and supports prioritization based on confirmed reputation signals.

When findings involve <mark style="color:green;">**cloud storage**</mark>, enrichment confirms whether the exposed content is publicly accessible, identifies the cloud provider, and examines the filenames and content types to highlight sensitive data such as internal documentation, logs, or customer information.

For <mark style="color:green;">**public code repositories**</mark>, commit metadata and author information are included to support traceability. Findings are enriched with indicators such as repository visibility, timestamps, and file paths to help prioritize which exposures require immediate attention.


---

# 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.inopli.com/drp/surface-web-monitoring/enrichment-strategies.md?ask=<question>&goal=<endgoal>
```

`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.