Answer yes if your organisation can demonstrate the composition and provenance of the software it develops, including any third-party or open-source components. Upload supporting evidence such as, but not limited to: a software inventory, dependency lists, or a software bill of materials (SBOM).
Supply chain attacks increasingly take advantage of vulnerabilities in commonly-used software packages (both third-party and open-source components). Without a clear inventory, your organisation cannot quickly identify if it is affected by a new 0-day vulnerability in a common library. By tracking software provenance, you ensure that the code you are deploying is legitimate and hasn't been compromised by a malicious actor. Maintaining this visibility increases the overall transparency and trustworthiness of your software delivery pipeline.
If you have not already done so, you may wish to consider solutions that can help create a centralised register for all external libraries and packages that you use for your development. This list should be updated every time new dependencies are added to your codebase. You can use tools to generate a Software Bill of Materials (SBOM) in formats such as Cyclone DX or SPDX to have a machine-readable view of your software components. For more information, please visit the following sites:
System Package Data Exchange (SPDX)
CycloneDX
If you would like to contribute to this article or provide feedback, please email knowledge@riskledger.com. Contributors will be recognised on our contributors page.