Back to updates

Secret Scanning - 1

2026 (7)

March (5)

github: GitHub secret scanning — coverage update

GitHub

2026-03-31

GitHub secret scanning added nine new secret detectors from seven providers as part of a coverage update. The update includes detectors for providers such as Langchain, Salesforce, and Figma, along with additional secret types from Figma, Google, and OpenVSX.

github: Push protection exemptions from repository settings

GitHub

2026-03-23

GitHub now lets repository admins manage secret scanning push protection exemptions from a repository’s settings. Before this change, exemptions were only configurable through organization- and enterprise-level security configurations.

github: Configure Copilot coding agent’s validation tools

GitHub

2026-03-18

GitHub says Copilot coding agent now automatically runs project tests and linting, plus GitHub validation tools such as CodeQL, advisory database checks, and secret scanning. The new update lets you configure which validation tools the agent uses.

github: Secret scanning in AI coding agents via the GitHub MCP Server

GitHub

2026-03-17

GitHub MCP Server can now scan code changes for exposed secrets before commit or pull request creation. The feature is intended to catch credential leaks early in AI coding agent workflows.

github: Push protection exemptions for roles, teams, and apps

GitHub

2026-03-17

GitHub added push protection exemptions for secret scanning at the organization level. Specific roles, teams, and GitHub Apps can now be exempted, with exemption status checked on each push.

February (1)

github: Secret scanning improvements to extended metadata checks

GitHub

2026-02-18

GitHub Secret Scanning now supports configuring extended metadata checks via security configurations, making it easier to enable these checks across many repositories.

January (1)

github: Secret scanning extended metadata to be automatically enabled for certain repositories

GitHub

2026-01-15

GitHub secret scanning will add support for extended metadata checks in repository security configurations, with the change taking effect on February 18, 2026. Extended metadata is implemented as a nested feature under existing validity checks and will be automatically enabled for certain repositories.

2025 (5)

December (2)

github: Enterprise governance and policy improvements for secret scanning

GitHub

2025-12-16

GitHub announced the general availability of enterprise governance and policy improvements for secret scanning, including enterprise-level delegated bypass controls for push protection and support for the new Enterprise Security Manager to provide stronger, more centralized controls and delegation for secret scanning across enterprises.

github: Secret scanning updates — November 2025

GitHub

2025-12-02

GitHub Secret Scanning received updates in November 2025 that added support for 24 new secret types via new provider patterns; details were published in the GitHub Blog changelog.

November (3)

github: Secret scanning alert assignees, security campaigns are generally available

GitHub

2025-11-25

GitHub announced that secret scanning alert assignees and security campaigns are now generally available. Alert assignees will receive email notifications to help teams track and remediate secret scanning alerts more effectively.

github: Secrets in unlisted GitHub gists are reported to secret scanning partners

GitHub

2025-11-25

As of 2025-11-25, GitHub will report publicly leaked secrets found in unlisted gists to the appropriate secret scanning partners, extending secret-scanning reporting beyond only listed/public gists.

github: Secret scanning improves private key detection, updates Sentry pattern names

GitHub

2025-11-12

GitHub secret scanning now recognizes additional private key formats and has upgraded its existing private key detectors to better catch exposed cryptographic credentials. The release also updates Sentry-related pattern names used in scanning.