WH Theme: SBOMS /  Notifications

• Look at OpenSSF SLSA/SBOM work (SLSA).  See also mail from GOSST
• Look at https://github.com/ossf/wg-security-tooling
• https://github.com/spdx/spdx-maven-plugin
• See security-discuss mailing list discussion 

Other background:

• SBOM section at https://openssf.org/oss-security-mobilization-plan/ based on WH and other meetings
  • https://thenewstack.io/sbom-everywhere-the-openssf-plan-for-sboms/
• CSRB report on Log4j mentions some current issues, limitations, and recommendations https://www.cisa.gov/sites/default/files/publications/CSRB-Report-on-Log4-July-11-2022_508.pdf

Draft ASF Position:

• SBOMs needs to be automatically generated for builds at build time
• SBOMs need to be signed with the same keys used for releases, in the same way (detached signature, detached hash)
• SBOMs are expected to be static to the given release, must never be changed after release
• SBOMs need to be useful (i.e. can be parsed, machine readable by current/future tools)

Questions

• What type of projects/builds should include SBOMs?
• What format should be used (e.g., SPDX, CycloneDX)
• What projects are interested in working on this? 
  • Commons? https://github.com/apache/commons-parent/pull/122 (CycloneDX)
  • ORC-1342: Publish SBOM artifacts (CycloneDX)
  • AVRO-3700: Publish SBOM artifacts (CycloneDX)
  • PARQUET-2224: Publish SBOM artifacts (CycloneDX)
  • SPARK-41893: Publish SBOM artifacts (CycloneDX)
  • FLINK-30578: Publish SBOM artifacts (CycloneDX)