An SBOM should be used as part of any comprehensive software and application security strategy, as you seek to safeguard your code. It should also be used as part of any response to RFPs to demonstrate robust compliance and security. In increasing cases and contexts, potential purchasers make it a prerequisite for vendors to supply an SBOM. Typical use cases for SBOMS are: Vulnerability remediation. SBOMs enable you to check for and identify vulnerabilities in your applications and software. When notified about a vulnerability, you can use the SBOM to find all instances of the affected software and patch the problem. Regulatory compliance. Governmental, public sector organizations and heavily regulated industries like healthcare and finance may require vendors to demonstrate that they deliver secure products. Often they require an SBOM as a part of the purchasing process. Merger and acquisition due diligence. An SBOM helps demonstrate that a potential acquisition is sound both in terms of its capabilities and its compliance.