> For the complete documentation index, see [llms.txt](https://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://docs.medcrypt.com/medcrypt-documentation/helm/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. This will export your enriched FDA SBOM for all selected products in Excel format, including includes additional CPE/PURL, license, vulnerability remediation data, level of support and EOS/EOL data.

## Export FDA SBOM

You can export your FDA SBOM from the **Reports** page.

**From the reports page:**

1. In the **Reports** page, click the product version drop-down. You can select one or multiple product versions from this page.
2. Click the export button on the FDA SBOM card. This will export your enriched FDA SBOM for all selected products in Excel format. This includes additional CPE/PURL, license, vulnerability remediation data, level of support and EOS/EOL data. If you want to [customize your export](/medcrypt-documentation/helm/manage-sbom/export-your-sbom.md) for a single product version only, you can do so from the components page.


---

# 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.medcrypt.com/medcrypt-documentation/helm/ensure-fda-readiness/fda-ready-sbom-and-vulnerability-reports/meet-fda-requirements-with-your-fda-sbom-report.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.