> For the complete documentation index, see [llms.txt](https://docs.cipp.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cipp.app/user-documentation/security/defender/list-defender-tvm.md). # Vulnerabilities Software vulnerabilities found by Microsoft Defender across the selected tenant's onboarded devices, grouped so that each CVE appears once with a count of the devices it affects rather than once per device. Use it to see which vulnerabilities are worth chasing in a tenant and how far each one has spread. ## Table Details | Column | Description | | ---------------------------- | ----------------------------------------------------------------------------------------------------- | | Affected Devices Count | How many device findings were rolled up into this CVE. Counted by CIPP when the findings are grouped. | | Affected Devices | The devices the CVE was found on. Expand the cell to see the full list. | | Os Platform | The operating system platform the finding was reported against. | | Software Vendor | The vendor of the vulnerable software. | | Software Name | The vulnerable software. | | Vulnerability Severity Level | Microsoft's severity rating for the vulnerability. | | Cvss Score | The CVSS score for the vulnerability. | | Security Update Available | Whether a security update that addresses the vulnerability is available. | | Exploitability Level | Microsoft's assessment of how exploitable the vulnerability is. | | Cve Id | The CVE identifier, and the value the findings are grouped on. | {% hint style="warning" %} Only **Affected Devices Count** and **Affected Devices** reflect every device behind a row. The remaining columns are taken from a single one of the grouped findings, so where a CVE spans more than one platform, vendor or software version, this table shows one of them rather than all of them. Treat those columns as an example of what the CVE was found on, not a complete picture. {% endhint %} *** ## Feature Requests / Ideas We value your feedback and ideas. Please raise any [feature requests](https://github.com/CyberDrain/CIPP/issues/new?template=feature.yml) on GitHub. --- # 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.cipp.app/user-documentation/security/defender/list-defender-tvm.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.