GitHub 公开监控功能升级：新增告警分流、有效性验证、API 与 Webhooks 支持

公开监控（Public monitoring）现已包含告警管理功能（例如自动有效性检查），以帮助你大规模分流并修复泄漏的机密凭据。

• 告警管理：支持忽略操作、时间线追踪与过滤筛选
• 全天候有效性检查：覆盖受支持的机密类型
• REST API 与 Webhook 支持：无缝对接公开监控告警

拥有公开监控权限的企业现在可以直接在企业安全仪表板中对发现的泄漏项进行分流：

• 忽略和重新打开告警：可将告警关闭为 已忽略（Dismissed） 或 已修复（Fixed），并填写说明决策的可选备注；若后续情况发生变化，也可以重新打开已关闭的告警。
• 活动时间线：查看针对告警所执行的所有操作及状态变更的完整审计记录。
• 筛选与排序：支持按代码仓库、提交者、机密类型、归属方式（成员身份或已验证域名）以及状态（即 open 或 closed）筛选告警列表，从而优先聚焦影响最大的暴露风险。

关闭告警仅会更新其在贵企业内部的状态，并不会撤销已暴露的凭据，也不会将其从公开代码仓库中删除。

公开监控现已支持针对指定提供商持续自动检测令牌有效性。告警会明确展示该凭据的状态为 Active、Inactive 还是 Unknown，使安全团队能够迅速针对仍处于活跃状态的有效凭据制定高优先级的响应措施。

你还可以将公开监控的发现项引入自定义的安全事件响应流水线中：

• REST API：企业管理员与企业安全经理可通过调用 GET /enterprises/{enterprise}/secret-scanning/public-monitoring-alerts 以编程方式查询已归属的泄漏凭据。该接口会返回告警元数据、机密类型、归属关系以及暴露的具体位置。
• 企业 Webhooks：在企业层级订阅 secret_scanning_public_monitoring_alert Webhook 事件，每当检测到归属于贵组织的新机密泄漏时，即可接收实时通知。

公开监控功能目前面向 GitHub Enterprise Cloud 客户（包括支持数据驻留的数据驻留版 GitHub Enterprise Cloud）提供公开预览。企业管理员和企业安全经理可直接在企业安全仪表板中启用该功能并管理告警设置。

公开监控已包含在你的 GitHub Advanced Security 或 GitHub Secret Protection 许可证中，无需支付额外费用。

欢迎了解关于 公开监控（public monitoring） 的更多信息，并加入 GitHub Community 参与讨论。

Public monitoring now includes alert management capabilities like automatic validity checks to help you triage and remediate leaked secrets at scale.

• Alert management with dismissals, timelines, and filtering
• Always-on validity checks for supported secret types
• REST API and webhook support for public monitoring alerts

Enterprises with public monitoring can now triage findings directly from the enterprise security dashboard:

• Dismiss and reopen alerts: Close alerts as Dismissed or Fixed , provide an optional comment explaining the decision, or reopen closed alerts if circumstances change.
• Activity timeline: Review an audit trail of all actions and state changes taken on an alert.
• Filter and sort: Filter the alert list by repository, committer, secret type, attribution method (membership or verified domain), and state (i.e., open or closed) to focus on the exposures that matter most.

Closing an alert updates its state for your enterprise. It does not revoke the exposed credential or remove it from the public repository.

Public monitoring now automatically checks token validity on an ongoing basis for supported providers. Alerts display whether a credential is Active, Inactive, or Unknown, allowing security teams to quickly prioritize response for live tokens.

Bring public monitoring findings into your custom incident response pipelines:

• REST API: Enterprise admins and enterprise security managers can query attributed findings programmatically using GET /enterprises/{enterprise}/secret-scanning/public-monitoring-alerts. This returns alert metadata, secret type, attribution, and exposed locations.
• Enterprise webhooks: Subscribe to the secret_scanning_public_monitoring_alert webhook event at the enterprise level to receive real-time notifications whenever a newly detected leak is attributed to your organization.

Public monitoring remains available in public preview for GitHub Enterprise Cloud customers, including GitHub Enterprise Cloud with data residency. Enterprise admins and enterprise security managers can enable the feature and manage alert settings from the enterprise security dashboard.

Public monitoring is included with your GitHub Advanced Security or GitHub Secret Protection license at no additional cost.

Learn more about public monitoring and join the discussion in the GitHub Community.