> 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/vulnerability-scanning.md). # Vulnerability Scannning ## Overview ThreatDefence Vulnerability Scanning continuously assesses external systems for known vulnerabilities, misconfigurations, and outdated software. Results are ingested into the platform and correlated with SOC workflows for monitoring, prioritization, and remediation tracking. *** ## How It Works * External assets (IP ranges) are scanned periodically (by default, weekly). * Scans can also be run on-demand as required. * The scanning engine checks against vulnerability databases (e.g., CVE, CPE mappings) to identify issues. * Detects exposed services, weak configurations, and outdated versions. * Findings are normalized and ingested into the ThreatDefence platform. * Results are available in dashboards and reports, and can be escalated through SOC workflows. * Vulnerabilities are mapped to CVSS scoring and assigned a priority level. * If a vulnerable system generates security alerts, correlation rules automatically highlight it for immediate action. *** ## How to Activate Vulnerability Scanning To enable vulnerability scanning for your organization, contact your ThreatDefence representative.\ Provide your public IP ranges and advise on your preferred scan schedule, including day & time preference as well as frequency of the scanning. (e.g., weekly, monthly). *** ## Vulnerability Reports All vulnerability findings are available in the **Analyst Console**, while summary reports can be exported from our **Customer Portal**. Reports include: * Detected vulnerabilities (with CVSS scores and severity). * Affected IPs and services. * Historical trend of vulnerabilities over time. * Export options (PDF) for offline analysis and 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/vulnerability-scanning.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.