Skip to content

docs(sbom): document the Asset-page export and the version it produces #15671

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Maffooch merged 1 commit into from
Aug 14, 2026
+14 −0
Merged

docs(sbom): document the Asset-page export and the version it produces #15671

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions docs/content/asset_modelling/locations/PRO__exporting_sboms_and_vex.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,20 @@ DefectDojo Pro can serialize an Asset's current dependency inventory back out as

Both endpoints require **V3 Locations** to be enabled, and respect Asset-level permissions: an Asset the requesting user cannot view returns a 404.

## Exporting from the Asset page

The Asset page carries an **Export** panel offering the same data without going through the API, in one of three shapes:

| Export type | What the document contains |
| --- | --- |
| **SBOM** | The component inventory only. |
| **VEX** | The vulnerability analysis only — a standalone document describing the exploitability of this Asset's findings. |
| **SBOM with vulnerabilities (VDR)** | Both — the inventory with an embedded `vulnerabilities` block carrying the VEX analysis. |

Each choice names the format and specification version it produces, for example *SBOM — component inventory only (CycloneDX 1.6)*. Those labels are read from the server as the panel renders rather than written into the page, so they describe the document you will actually receive: when the exporters adopt a newer specification, the labels follow rather than going stale.

The Asset page and the API endpoints below emit the same specification version, so a document exported from either path is interchangeable with the other.

## Exporting an SBOM

```
Expand Down
Loading