GitHub secret scanning now checks Actions workflow logs, in preview and without backfill
GitHub has extended secret scanning to the logs of GitHub Actions workflow runs, the company said in its changelog on 9 November. Until now the scanner covered code and content such as issues, wikis, discussions and pull requests. The new coverage is in public preview.
When a run completes, GitHub checks its log for patterns from secret-scanning partner providers. Findings land in the repository's secret scanning alert list next to alerts from code, with a link back to the log. Validity checks run for the secret types that support them, and an alert stays available after the log itself has been deleted.
Access is limited. The preview is open to enterprises on GitHub Enterprise Cloud that hold GitHub Secret Protection or GitHub Advanced Security licences, including those using data residency on GHE.com. An enterprise owner switches it on in the enterprise settings under the Advanced Security policies; the policy is off by default and only applies to repositories that already have secret scanning enabled under those licences.
The changelog lists several limits for the preview. Logs are not scanned retroactively, so only runs that finish after the feature is enabled are covered. Generic patterns, custom patterns and AI-detected secrets are not checked, and neither are values that Actions has already masked. Alerts from workflow logs do not trigger notifications yet, so teams have to look at the alert list themselves.

Why it matters
Build logs are a common place for credentials to leak: a debug line, a verbose tool, a token printed by a failing script. Masking only protects values Actions knows are secrets, so a scanner that reads the finished log covers the ones it does not know about. Without notifications and without backfill, though, the preview helps only teams that enable it and then check the list.