--- title: Updates to GitHub secret scanning | daily.dev description: GitHub is changing an audit log field and shipping several secret scanning fixes. On November 12, 2026, the business field in secret_scanning_alert.* and... canonical: https://daily.dev/posts/updates-to-github-secret-scanning-ddx1nfjzs copyright: © 2026 Daily Dev Ltd. terms: https://daily.dev/tos/ twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Updates to GitHub secret scanning | daily.dev og:description: GitHub is changing an audit log field and shipping several secret scanning fixes. On November 12, 2026, the business field in secret_scanning_alert.* and... og:url: https://daily.dev/posts/updates-to-github-secret-scanning-ddx1nfjzs og:image: https://api.daily.dev/og/posts/Ddx1NfJZS.png og:image:alt: Updates to GitHub secret scanning og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Updates to GitHub secret scanning **[GitHub Changelog](https://daily.dev/sources/github_updates)** · 2 min read · 0 upvotes · 0 comments ## Summary GitHub is changing an audit log field and shipping several secret scanning fixes. On November 12, 2026, the business field in secret_scanning_alert.* and secret_scanning_push_protection.bypass events switches from the enterprise display name to the enterprise slug, so integrations filtering by display name should accept both formats or switch to business_id. Other updates: custom pattern alerts no longer close and reopen on matching rescans, the revocation action (public preview) now supports base64-encoded tokens, including encoded classic PATs, fine-grained PATs and OAuth tokens, dismissal-request webhooks add exemption_request.number, and invalid custom pattern API requests now return 422 instead of 500. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why is the business field in my GitHub secret_scanning_alert audit log events about to change? Starting November 12, 2026, the business field in secret_scanning_alert.* and secret_scanning_push_protection.bypass audit log events changes from the enterprise display name to the enterprise slug. The field stays a string, event names are unchanged, and the numeric business_id value is unaffected. Integrations filtering by display name should accept both formats or switch to business_id before that date. _Teams maintaining audit log integrations can track GitHub changelog updates like this on daily.dev._ ### Does GitHub's secret scanning revocation support base64-encoded tokens? Yes, in private and internal github.com repositories with secret scanning enabled, the revocation action (public preview) now handles base64-encoded personal access tokens (classic), fine-grained personal access tokens, OAuth access tokens, and GitHub App user access tokens, automatically decoding the value before revoking it. _Developers hardening secret scanning workflows can follow updates like this on daily.dev._ ### What HTTP status code does GitHub's custom pattern secret scanning API return for invalid arguments? Requests rejected by the scanning service for invalid arguments now return 422 instead of 500, letting integrations distinguish input validation errors from actual server failures. _Developers building against GitHub's API can keep up with error-handling changes like this on daily.dev._ ## Similar posts on daily.dev - [Secret scanning improvements to alert APIs, webhooks, and delegated workflows](https://daily.dev/posts/secret-scanning-improvements-to-alert-apis-webhooks-and-delegated-workflows-n6rf0j1vg) · GitHub Changelog · 0 upvotes · 0 comments - [Secret scanning pattern updates and product improvements](https://daily.dev/posts/secret-scanning-pattern-updates-and-product-improvements-bc0vka53d) · GitHub Changelog · 0 upvotes · 0 comments - [Enterprise governance and policy improvements for secret scanning](https://daily.dev/posts/enterprise-governance-and-policy-improvements-for-secret-scanning-ayi0mz2mi) · GitHub Changelog · 0 upvotes · 0 comments - [GitHub Secret Scanning Public Monitoring for Enterprises: Coverage and Gaps](https://daily.dev/posts/github-secret-scanning-public-monitoring-for-enterprises-coverage-and-gaps-txomrmpk3) · StepSecurity · 3 upvotes · 0 comments --- Tags: [#github](https://daily.dev/tags/github), [#architecture](https://daily.dev/tags/architecture), [#appsec](https://daily.dev/tags/appsec) [View this post on daily.dev](https://daily.dev/posts/updates-to-github-secret-scanning-ddx1nfjzs) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Updates to GitHub secret scanning","url":"https://daily.dev/posts/updates-to-github-secret-scanning-ddx1nfjzs","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/updates-to-github-secret-scanning-ddx1nfjzs"},"datePublished":"2026-10-20T18:33:12.878Z","dateModified":"2026-10-20T19:10:49.054Z","description":"GitHub is changing an audit log field and shipping several secret scanning fixes. On November 12, 2026, the business field in secret_scanning_alert.* and...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7ff43f0eed8f3f445aaaa7b5b819760f?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7ff43f0eed8f3f445aaaa7b5b819760f?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"GitHub Changelog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"GitHub Changelog","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/15004b7835da4d89b02b115871f0f6dc","url":"https://daily.dev/sources/github_updates"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/updates-to-github-secret-scanning-ddx1nfjzs","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"github,architecture,appsec","timeRequired":"PT2M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"GitHub Changelog","item":"https://daily.dev/sources/github_updates"},{"@type":"ListItem","position":3,"name":"Updates to GitHub secret scanning"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/updates-to-github-secret-scanning-ddx1nfjzs#faq","mainEntity":[{"@type":"Question","name":"Why is the business field in my GitHub secret_scanning_alert audit log events about to change?","acceptedAnswer":{"@type":"Answer","text":"Starting November 12, 2026, the business field in secret_scanning_alert.* and secret_scanning_push_protection.bypass audit log events changes from the enterprise display name to the enterprise slug. The field stays a string, event names are unchanged, and the numeric business_id value is unaffected. Integrations filtering by display name should accept both formats or switch to business_id before that date. Teams maintaining audit log integrations can track GitHub changelog updates like this on daily.dev."}},{"@type":"Question","name":"Does GitHub's secret scanning revocation support base64-encoded tokens?","acceptedAnswer":{"@type":"Answer","text":"Yes, in private and internal github.com repositories with secret scanning enabled, the revocation action (public preview) now handles base64-encoded personal access tokens (classic), fine-grained personal access tokens, OAuth access tokens, and GitHub App user access tokens, automatically decoding the value before revoking it. Developers hardening secret scanning workflows can follow updates like this on daily.dev."}},{"@type":"Question","name":"What HTTP status code does GitHub's custom pattern secret scanning API return for invalid arguments?","acceptedAnswer":{"@type":"Answer","text":"Requests rejected by the scanning service for invalid arguments now return 422 instead of 500, letting integrations distinguish input validation errors from actual server failures. Developers building against GitHub's API can keep up with error-handling changes like this on daily.dev."}}]} ```