> For the complete documentation index, see [llms.txt](https://docs.veedna.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veedna.com/continuous-vulnerability-elimination-factory-cvef/sbom360/generate-an-sbom/existing-sbom-as-source.md).
# Existing SBOM As Source
Generate a project by uploading your existing SBOMs in either SPDX or CycloneDX format.
Follow the below steps:
1. Step 1: Project name and version
1. Enter a name and version for your project.
2. Step 2: Choose format and upload file
1. Choose the format of your SBOM.
1. SBOM360 supports both SPDX and CycloneDX files.
2. Please refer the [support matrix](/sca360-secure-deployment-for-restricted-environments/support-matrix.md) for supported versions and formats
2. Drag and drop or browse to find and enter your desired SBOM file.
3. CSV uploads are also supported. Please refer to the following sample file for the supported format.
{% file src="/files/Uhcd8iscswjLhh3Tu39U" %}
1. Step 3: Review
1. For every file uploaded, [EO 14028](/continuous-vulnerability-elimination-factory-cvef/sbom360/generate-an-sbom/existing-sbom-as-source/eo-14028-checks.md) check is performed and errors (if any) are displayed
2. Once the submit is clicked, the SBOM generation kicks off
3. Please note that the outcome of an SBOM generation with errors in the EO 14028 check will be incomplete.
---
# 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.veedna.com/continuous-vulnerability-elimination-factory-cvef/sbom360/generate-an-sbom/existing-sbom-as-source.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.
