> For the complete documentation index, see [llms.txt](https://docs.threatdefence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.threatdefence.com/attack-surface-management/dark-web-monitoring.md). # Dark Web Monitoring ## Overview ThreatDefence Dark Web Monitoring continuously searches underground forums, marketplaces, data dumps, and criminal infrastructure for compromised credentials, sensitive data, and mentions of your organization. Findings are ingested into the platform and correlated with SOC workflows to enable rapid detection and response to external exposures. *** ## How It Works * ThreatDefence monitors a wide range of dark web sources, including credential dumps, marketplaces, forums, and paste sites. * Custom watchlists are configured for your organisation (e.g., domains, email addresses, keywords). * When matches are detected, they are collected, normalised, and ingested into the ThreatDefence platform. * Results appear in dashboards and reports, and are reviewed by the SOC team. * Alerts are prioritised based on severity, e.g., valid credentials with recent breach data are treated as higher risk. * Correlation with internal telemetry highlights if exposed credentials or data are already being used in active attacks. *** ## How to Activate Dark Web Monitoring To enable Dark Web Monitoring for your organization, contact your ThreatDefence representative.\ Provide a list of your email-enabled domains. Our team will configure your custom watchlist and begin monitoring immediately. *** ## Dark Web Reports All vulnerability findings are available in the **Analyst Console**, while summary reports can be exported from our **Customer Portal**. Reports include: * Discovered compromised credentials or data. * Contextual details such as breach source, date, and content type. * Severity ratings and recommendations for response. * Historical trend of exposures over time. * Export options (PDF) for offline analysis and compliance reporting. --- # 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.threatdefence.com/attack-surface-management/dark-web-monitoring.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.