> For the complete documentation index, see [llms.txt](https://helm.docs.medcrypt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helm.docs.medcrypt.com/~/changes/KjixZskptrAaNWiTYnvj/ensure-fda-readiness/fda-ready-sbom-and-vulnerability-reports/meet-fda-requirements-with-your-fda-sbom-report.md).

# Meet FDA requirements with your FDA SBOM report

Get the Medcrypt advantage with the only FDA expert-crafted SBOM that ensures you meet FDA SBOM requirements. We also provide a suite of other reports to enable you to export exactly what you need to meet auditor requirements.

## Export FDA SBOM

You can export your SBOM from your dependency components page or from the **Reports** page.

1. From the components page, click **Manage SBOM > Export SBOM**. If you want to take advantage of our expert FDA SBOM, select the Export FDA SBOM option.  From the **Reports** page, click the **Export SBOM** button for the SBOM format you need.
2. In the export panel that displays, specify your file name. 
3. Select to export either your original or enriched SBOM. 
4. If you select **Enriched SBOM**, this will display the **Enriched SBOM details** section. Customize the details you want (as detailed in the fields below), then click **Export SBOM**. 

### Customize your export

Your FDA SBOM contains the data in your SBOM as well as your vulnerabilities, but can also be enriched with additional CPE/PURL, license, or vulnerability remediation data.

**Export as file format:**

Your FDA SBOM is only available as an Excel file.

**CPE/PURL source:**

Your FDA SBOM includes both CPE/PURL information from your SBOM and additional data identified by Helm to enrich your SBOM. This cannot be changed. 

**Vulnerabilities:**

Your FDA SBOM report includes all of your vulnerabilities, but you can now include CycloneDX and VEX remediation.

**Review information:**

You can further enrich your FDA SBOM with the review status and notes of each dependency component.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helm.docs.medcrypt.com/~/changes/KjixZskptrAaNWiTYnvj/ensure-fda-readiness/fda-ready-sbom-and-vulnerability-reports/meet-fda-requirements-with-your-fda-sbom-report.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.