CAST SBOM Manager vs OWASP Dependency-Track

CAST SBOM Manager analyzes source code and creates Software Bills of Materials for software product owners, release managers, and compliance specialists. SBOM creation can start from application code, existing files, Git repositories, or CAST Highlight results. A dashboard presents components, vulnerabilities, licenses, obsolescence, languages, topics, and file extensions. Users can define proprietary components with custom descriptions, licenses, vulnerabilities, copyrights, and programming languages, then place components in catalogs for reuse. License tools support custom definitions and management of open-source risks, requirements, obsolescence, and copyrights. Vulnerability information includes CVEs from NIST’s NVD and advisories from GitHub and GitLab, with custom vulnerabilities also supported. SBOMs can be imported from multiple formats and exported as Excel, Word, or CycloneDX. Multiple versions can be managed, and exported contents can be tailored for different audiences. The product runs on Linux and Windows with cloud or on-premises deployment. A free download is listed at free.

OWASP Dependency-Track is a free, self-hosted platform for managing software-component risk across a supply chain. It builds inventories from software bills of materials and identifies vulnerable components, supporting CycloneDX SBOM, HBOM, VEX, and VDR documents for ingestion, analysis, and production. Components can be matched against NVD, GitHub Advisories, OSV, OSS Index, Snyk, Trivy, and VulnDB, while integrated EPSS support helps prioritize mitigation. Integrity checks flag components when published hashes differ from those served by an upstream registry. A Common Expression Language policy engine evaluates component rules and can break a build when a policy fails. Alerts can be filtered by event fields and sent to Slack, Teams, Mattermost, email, or webhooks. API and web interfaces are available, with least-privilege portfolio access and single sign-on through OpenID Connect, Active Directory, and LDAP. Version 5.1 uses separate API and frontend container images, supports Kubernetes, and requires PostgreSQL.