GitHub secret scanning now reads Actions workflow logs, with a catch
GitHub Actions has always had a known leak path: a step prints an API key to stdout, and that key sits readable in the run's log forever. On November 9, GitHub extended secret scanning to close part of that gap, but the feature only watches what happens after an admin flips it on.
What happened
Secret scanning can now detect secrets printed into GitHub Actions workflow logs, GitHub said, extending coverage that previously applied to issues, wikis, discussions, and pull requests since a 2024 GA announcement. The capability is in public preview for GitHub Enterprise Cloud customers on GitHub Secret Protection or GitHub Advanced Security, including those using data residency on GHE.com. When a workflow run completes, GitHub scans its logs for provider secret patterns and runs validity checks on supported secret types. Matches land in the repository's existing secret scanning alert list, each one linking back to the workflow file and the exact log line where the secret printed. Enterprise owners turn it on from Enterprise Settings, then Policies, then Advanced Security, where "Secret scanning for Actions workflow logs" is off by default and only applies to repositories that already have secret scanning enabled.
The scan only starts counting from the moment you enable it
GitHub does not backfill. Only workflow runs that complete after an admin enables the policy get scanned, so any secret already sitting in a year of old run logs stays invisible to this feature, per GitHub's documentation. The detection itself is narrower than code-level secret scanning too: it only catches known provider token patterns, not generic high-entropy strings, not custom regex patterns an org has configured, not AI-detected secrets, and not anything Actions already masks in the log. A hand-rolled internal credential that does not match a known provider format will not trigger an alert here even after the feature is on. Alerts also skip notifications during the preview, so a security team has to check the alert list directly rather than wait for a ping. For enterprises that print secrets to logs today, the practical move is to enable the policy now (it is off everywhere by default) and separately audit older workflow runs by hand, since those logs will never get scanned retroactively.
Context and reactions
The feature rounds out a coverage list GitHub has been filling in piece by piece since the original code-scanning secret detection: issues, wikis, discussions, and pull requests went GA in 2024, and Actions logs were the remaining major non-code surface. GitHub has not said when the preview might reach general availability or whether it plans to extend detection to self-hosted runner logs, which the November 9 announcement does not mention.
What to watch next
Worth watching is whether GitHub adds generic-pattern and custom-pattern detection to Actions logs during the preview, since that gap is the main thing separating this from code-level secret scanning. Also watch whether self-hosted runners get coverage, given they are common in regulated enterprises that would benefit most from the feature.
Sources
- Secret scanning detects secrets in GitHub Actions workflow logs: GitHub changelog, November 9, 2026
- About secret scanning: GitHub Docs
