GitHub secret scanning audit logs swap enterprise names for slugs
From 12 November, the business field on secret_scanning_alert and secret_scanning_push_protection.bypass audit log events reports the enterprise slug instead of its display name. Filters keyed on the old name stop matching.
GitHub changed how its secret scanning audit log events identify your enterprise, effective 12 November. The business field on secret_scanning_alert.* and secret_scanning_push_protection.bypass events now carries the enterprise slug instead of the display name.
business: "Acme Corp" // before
business: "acme-corp" // from 12 November
The field stays a string, so nothing obviously errors, it just stops matching whatever display name your filters expect. Event names and the numeric business_id value are unchanged. GitHub’s own advice is to update any integration that filters by display name to accept both formats, or switch to matching on business_id instead.
Why it matters: if you pipe GitHub Enterprise audit logs into a SIEM, a webhook, or your own alerting, and your rules filter on that business field by name, they go quiet today rather than throwing an error. Check your filters before you notice the silence.