GitHub updates secret scanning audit log events and fixes bugs
GitHub published a changelog entry on 2026-10-20 describing improvements and bug fixes for its secret scanning feature. The entry includes a change to audit log events, where the business field in secret_scanning_alert.* and secret_scanning_push_protection.bypass events is affected starting November 12, 2026.
Why it matters
Teams that parse GitHub audit logs for secret scanning alerts or push protection bypasses may need to update log parsers or dashboards before the November 12, 2026 change takes effect.
Who should care
DevOps engineers, security teams, and developers who run GitHub audit log exports or SIEM integrations for GitHub organizations.
What you can do
Review any scripts or SIEM rules that read the business field in secret_scanning_alert and secret_scanning_push_protection.bypass audit log events, and update them before November 12, 2026.