Public Monitoring For Enterprises [General Availability]
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 25/100
- Issue 類型
- 功能
- 描述清晰度
- 需要釐清
- 活躍度
- 冷清
- 技術堆疊
- github
- 領域
- security
研究方向
此路線圖 issue 描述了 GitHub Secret Protection 的公開監控，但沒有指定實作檔案、測試或進入點。首先確定涉及的 repository 和現有的 secret-scanning 元件；當公開的 GitHub 內容能夠即時掃描，且暴露的 secret 被歸屬至正確的 enterprise 時，這項工作就完成了。
由索引模型根據 Issue 內容生成。
描述
Value Prop
Secrets don’t respect boundaries; scanning for them shouldn’t either.
GitHub monitors the entire public surface of github.com for leaked secrets in real time. Public monitoring attributes those secrets back to your enterprise, based on where your people commit.
Expected Outcome
Secret scanning has always protected the repositories you own. But secrets leak beyond that boundary. For example, a developer commits to a personal fork or an open source project, or they paste a token into a public issue or pull request, and this often happens from an account your security team isn’t tracking. Exposures like these were nearly impossible to find and often only surfaced after they’d been abused by bad actors.
Public monitoring closes that gap. It finds these vulnerabilities and attributes them to your enterprise so you can respond quickly. The feature scans for secrets exposed anywhere in public content across github.com—including git content, pull request comments, and GitHub issues—and natively attributes each one back to your enterprise, through GitHub’s identity layer and verified domains.
Because the activity happens on GitHub, so does the attribution: in real time (not a nightly async crawl), definitively with native platform metadata (not on a guess from a commit email), and across arbitrary public repositories (not just surfaces where you tell us to look).
Public monitoring will never scan private repositories; it surfaces only secrets that are already exposed publicly, so you can revoke leaked secrets before they’re abused by bad actors. The feature is available at no additional cost for enterprises with GitHub Secret Protection.
- 主要語言
- 沒有語言資料
- 星號
- 9k
- 分支
- 1.8k
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
github/roadmap 的其他 Issue
-
Enterprise Free GA GHES 3.24 GitHub Advanced Security (GHAS) Shipped Team
難度 5/5 一週以上 新手友好度 25/100
-
Enterprise Free GA GHES 3.24 Team
難度 4/5 3-5 天 新手友好度 25/100
-
Enterprise Free GA GHES 3.24 Team
難度 5/5 一週以上 新手友好度 18/100
-
Closing Down cloud Enterprise Free Shipped - Dotcom Team
難度 5/5 一週以上 新手友好度 25/100
-
cloud Copilot Enterprise Copilot for Business Copilot for Individuals Public Preview Shipped - Dotcom
難度 5/5 一週以上 新手友好度 10/100
相似的 Issue
-
UX
難度 2/5 1-3 小時 新手友好度 78/100
mediajunkie/piper-morgan-product#2286 ·
-
seabeectl verify exits 0 when verification fails可能已有人在做 @theyottaboy 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 82/100
NationalSecurityAgency/seabee#73 ·
維護者通常 4 天內回覆
-
false-positive help wanted
難度 1/5 1 小時以內 新手友好度 72/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 67/100
OffchainLabs/nitro#4784 ·
維護者通常 1 天內回覆
-
bot:ai-assisted documentation status:untriaged
難度 2/5 1-3 小時 新手友好度 67/100
midnightntwrk/midnight-zk#624 ·
維護者通常 1 天內回覆