> For the complete documentation index, see [llms.txt](https://docs.debricked.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.debricked.com/product/exporting-sbom/vulnerability-export.md).

# Vulnerability export

Learn how to create a Vulnerability Export.

{% hint style="info" %}
*This feature is only available for* [*SCA Premium & Enterprise*](https://debricked.com/pricing/) *users. Already have an account?* [*Click here to upgrade.*](https://debricked.com/app/en/repositories?billingModal=enterprise,free)
{% endhint %}

The Vulnerability Export summarizes data across all projects in your organization. It shows the total number of vulnerabilities, their critical or high classification, and their review status.

### Generate a vulnerability export

1. Click **Generate Export** on the top right corner of the page.
2. Select the **Global** scope. Vulnerability exports are not available for individual repositories or groups.
3. Under **Export Type**, select **Vulnerability Export**.
4. Click **Generate**.
5. Check your email for the exported data, sent in `.xlsx` format. Check your spam folder if needed.

The exported data is divided into four columns:

* Repository - A list of all your projects.
* Total vulnerabilities - The total number of vulnerabilities found per repository.
* Vulnerability priority - The number of vulnerabilities found with a CVSS rating of high or critical.
* Review status - The current status set for each vulnerability. It can be either vulnerable, unexamined, paused snoozed or unaffected.


---

# 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.debricked.com/product/exporting-sbom/vulnerability-export.md?ask=<question>&goal=<user_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.