> 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/sbom-management.md). # SBOM management Import and analyze third-party Software Bills of Materials in Fortify SCA. Use Software Bills of Materials (SBOMs) to import, manage, and analyze third-party software. Third parties include vendors, partners, and suppliers. {% hint style="info" %} *This feature is only available for our* [*SCA Enterprise*](https://debricked.com/pricing/) *users. Already have an account?* [*Click here to upgrade.*](https://debricked.com/app/en/repositories?billingModal=enterprise,free) {% endhint %} Each organization can upload up to 15 SBOMs. The option to increase this quota will be available in a future release. ### About SBOMs An SBOM is a structured inventory of the components in a software project. It can include component names, versions, relationships, licenses, and vulnerability data. Use the available tabs to review specific data: * **All** tab: Lists all imported SBOMs. * **Dependencies** tab: Shows component details. * **Vulnerabilities** tab: Shows identified security issues. * **Malware** tab: Shows findings. * **Licenses** tab: Shows license information. Use **Search by name** to locate an SBOM. Select **Import** to add an SBOM. ### Compare SBOMs with repository scanning SBOM analysis examines supplied software inventory. Repository scanning analyzed source code and supported manifest files. Repository scanning discovers dependencies; SBOM analysis uses data in the uploaded file. Fortify SCA enriches imported components when identifiers are available, for example, Package URLs. ### Common use cases Use SBOMs to: * Review a supplier's SBOM before onboarding software. * Verify that components meet your license policies. * Track vulnerabilities in third-party software. * Identify supplied software affected by malware. ### Known limitations The quality of analysis depends on the uploaded SBOM. * Missing data can reduce dependency, vulnerability, and license visibility. * Fortify SCA does not analyze supplied source code. * Results rely on uploaded data and available component enrichment. --- # 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/sbom-management.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.