## Summary CBOMs provide the transparency necessary to identify crypto algorithms that should be deprecated or end-of-lifed, which prevents the introduction of weak algorithms. CBOMs help with identifying cryptographic assets (e.g., certificates) that are expiring. Identifying these reduces the likelihood of service downtime due to expired certs. Additionally, the usage of CBOMs can outline cryptographic assets that have long-term validity and are not expiring for several years or longer. In `CycloneDX v1.6` the concept of CBOMs were introduced. Users can understand the dependency information (as provided in a standard SBOM) but also see the protocol (e.g., TLS 1.2) provided by a given dependency. ### Problem to solve Currently our SBOM support handles ingestion and generation of SBOMs. We can output SBOMs as an artifact or consume an SBOM to pull in dependency information. As Crypto Bill of Materials become more common we need to support: 1. Consuming Crypto information 2. Detecting Crypto information to add to our SBOMs This epic is currently focused on both of these aspects, however we can break this work into smaller pieces if there is a high degree of technical work that will be required to support both of these initiatives.