With Debricked’s tool, we help you create an SBOM and keep track of license and security risks in all included open source components. Soon, you will also be able to download the SBOM in the CycloneDX format.
Change is underway
Our society is facing an increased number of cyber attacks. In the light of these attacks, Biden’s executive order on cybersecurity is a welcomed step towards an increased focus on security.
To secure Federal Government computer systems, significant security measures are to be put in place. This includes both cloud-based systems and those that operate on-premise. It also includes both IT and OT systems.
The SolarWinds attack compromised data confidentiality at a number of organizations, including the Department of Homeland Security and Treasury Department. As such, it highlighted the need for higher security in the supply chain. Maybe most importantly, it emphasized this need to the U.S. Government, a government with the capacity to mandate real change.
The executive order from president Biden identifies a wide range of measures, and anyone selling products to the U.S. Government must implement these measures. In effect, any private sector company that has (or wants to have) the government as a customer, must follow the requirements.
One category of requirements is focused on improving software supply chain security. While sophisticated attacks such as the SolarWinds compromise are difficult to protect against, a wide range of security measures will at least raise the bar for the attackers.
The Software Bill Of Materials (SBOM)
Commercial software often lacks transparency, and the manufacturers often have insufficient focus on the software’s ability to resist attacks. One defined measure mandates providing a Software Bill Of Materials (SBOM) for each product.
The SBOM is a record of the supply chain relationships between components used when building software. The record lists all components in a product, including all open source software, similar to the list of ingredients given on food packaging.
This is valuable both to those that develop and those that purchase the product. It allows the developers to proactively manage and remediate license risks and security vulnerabilities, and it allows the buyers to verify such risks throughout the product’s life cycle.
Handling security and license risks
The complexity of managing license and security risks should not be underestimated. Software dependencies very often include their own dependencies, so-called transitive (or indirect) dependencies. These can in turn include further dependencies. For this reason, the SBOM can have hundreds, or thousands, of listed components. Each of these components have its own license and its own security risk from vulnerabilities.
It is clear that the SBOM and the related risks can not be managed manually for any reasonably sized software. It requires automation, which is also explicitly mentioned in the executive order.
The Debricked tool automatically creates the SBOM for you. We also identify all licenses and assess your risk level, which is automatically calculated based on how your software is used. What this solution means in the context of SBOM, we recommend you to dive deeper into software composition analysis and ecosystem.
In addition to this, the SBOM information is matched with our vulnerability database in order to identify security vulnerabilities in the software components. With the click of a button, these vulnerabilities can be remediated through an automatically created pull request.
SBOM export to be released shortly
Very soon we will take this one step further by releasing the possibility to export the SBOM to the widely used CycloneDX format. CycloneDX is an open standard for communicating SBOM information. This format has e.g., recently been adopted by OWASP as a flagship project.
Create a free Debricked account today and try it out!