OSPS-QA-02 Publish Software Dependencies (maturity level 3). Requirement: When the project has made a release, all compiled released software assets MUST be delivered with a software bill of materials. Objective of the control: Provide transparency and accountability for the project's dependencies while enabling users and contributors to understand the software's direct dependencies. Recommendation: It is recommended to auto-generate SBOMs at build time using a tool that has been vetted for accuracy. This enables users to ingest this data in a standardized approach alongside other projects in their environment.
This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.