> 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/manage-sboms/automate-risk-prioritization-and-management-1.md). # Automate risk prioritization and management Helm provides many ways to ensure you have a comprehensive and accurate view of your overall risk that is tailored to your product's particular security posture, enabling you to spend your limited time on the vulnerabilities that matter most: * Set rules to automatically update component **Level of support** and **EOS/EOL** information across all products, ensuring consistency * Reload components to automatically add missing licenses (only for components that do not have any associated licensing information), ensuring you're not missing valuable license risk that could even impact your IP. * Automatically rescore all vulnerabilities according to your product's security posture, ensuring you're focusing on the most exploitable vulnerabilities. Helm can also automatically update exploitability and fixability changes if you so choose. * If we identify inaccurate CPEs or PURLs in your SBOM, Helm will attempt to provide an enriched CPE or PURL that matches to the correct software * For components we're unable to match, you can create aliases to automatically match these to known software for future SBOMs. * Use our Helm API to automate many tasks, such as creating product versions, uploading SBOMs, returning all vulnerabilities and generating reports, as well as returning only unmatched components or only CISA KEV vulnerabilities. * Integrate our GitHub action your CI/CD process to automate product version creation and SBOM uploads * Export your FDA-ready SBOM to ensure you have everything you need for FDA submission --- # 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/manage-sboms/automate-risk-prioritization-and-management-1.md?ask=&goal= ``` `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.