Create a useful component record

A software bill of materials (SBOM) describes software components in a product or application. Record package names, versions and relationships in a format your team can maintain.

Generate the list from the build process where possible. Add details that help an operator find the product owner and determine whether an affected component is present.

Use it when an advisory arrives

Search the SBOM for an affected component and version. Confirm whether the code is present in the released product and whether the affected function is used. Assign an owner to investigate and report the result.

The list does not prove that a product is secure. It helps your team answer an inventory question faster and find the system that needs review.

Keep the record tied to each release

Generate an SBOM for each release or build where practical. Store it with release records and protect it from unauthorised changes. Define who can share it with a customer or regulator.

Review the process when package sources or build tools change. An accurate inventory supports vulnerability management, but the team still needs to validate impact and apply fixes.