docs(security): add gitea attestation response intake [skip ci]

This commit is contained in:
Your Name
2026-05-17 21:26:33 +08:00
parent 872f34fbbd
commit 444229a2c3
28 changed files with 805 additions and 45 deletions

View File

@@ -33,7 +33,7 @@
|----------|------|----------|
| Redacted finding ingestion | MEDIUM | 只準備 ingestion adapter 的 redaction / audit 前置條件 |
| Safe web crawl scope | MEDIUM | 只準備 TLS/header/basic crawl 的低噪音 scope |
| Gitea owner attestation + read-only inventory | MEDIUM | 先準備 S4.7 owner scope decision,再準備 read-only token 或 redacted export inventory |
| Gitea owner attestation + read-only inventory | MEDIUM | 先依 S4.9 驗收 S4.7 owner response,再準備 read-only token 或 redacted export inventory |
| GitHub target decision | HIGH | 只準備 owner / visibility / canonical / workflow parity 決策 |
| Ref truth review | HIGH | 只準備 refs truth / deprecated / release tag 人工判定 |
| Credentialed scan exception | HIGH | 只準備人工 exception、credential lifecycle 與停用方式 |
@@ -63,3 +63,5 @@ S3.4 是「批准後仍不能直接做事」的保險絲。
它讓未來真正進 runtime 前的資料門檻先被定義清楚,但仍維持初期低摩擦:目前只顯示、只準備、只留痕,不執行。
2026-05-17 S4.8 追加Gitea follow-up runtime gate 已要求 S4.7 owner coverage attestation 先完成。即使未來 read-only inventory 被批准,仍要先看 public-only / local remote gap、org/user endpoint、110 adjacent source、canonical owner 與 legacy/inaccessible disposition 的 owner decision未完成前不得執行 inventory。
2026-05-17 S4.9 追加Gitea follow-up runtime gate 已要求 S4.9 owner response 通過基本驗收後,才可把 S4.7 owner scope decision 當成 read-only inventory 的前置 evidence。未收到或未驗收 owner response 前,不得執行 inventory也不得標記 inventory complete。