python / python/cpython

Update SBOM generation to meet new guidance from CISA

未關閉
#123,038 4 則留言 1 個 reaction 已指派 1 人 在 GitHub 檢視

@sethmlarson 已經在處理了。

開始於 2024年8月15日。

triaged type-security
主要語言
Python
星號
77.2k
分支
36k
PR 合併指標
PR 指標待擷取

描述

Proposal:

CISA has published the third revision of SBOM guidance, which at the moment isn't approved but is headed towards final rounds of review. Currently our SBOMs met the old revision which is "Minimum Elements of an SBOM" published by NTIA.

The new guidance uses a "maturity level", ranging from minimum required to aspirational. Below I've used the "aspirational" maturity level for all the criteria.

I checked our SBOM documents against the document to see how much would be needed to follow this new set of guidance. It turns out, not too much! Here's the breakdown:

Elements that need more work:
  • Author Name: We need to add an email address
  • SBOM Type: We need to upgrade to SPDX 3 for this field
  • Supplier Name: Need to double-check that these names conform. Also need to update where we add Heritage information.
  • Unique Identifier: We're almost there, there's at least one project we should request a CPE for.
  • Heritage: We don't encode this information today. Some of our components are slightly modified from upstream dependency, should be automatable.
  • Relationship Completeness
  • License
  • Copyright Notice
Elements we already conform with:
  • Timestamp
  • Primary Component
  • Component Name
  • Component Version
  • Cryptographic Hashes
  • Relationships
  • Redacted and Unknown Components and Attributes
Has this already been discussed elsewhere?

This is a minor feature, which does not need previous discussion elsewhere

Links to previous discussion of this feature:

No response

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。