← All AI news
GitHubSafety

GitHub adds workflow-log secret scanning—with no preview notifications

An enterprise preview scans future completed Actions runs, but teams must inspect its alert list themselves.

THE UPDATE

What changed

GitHub’s November 9 public preview extends secret scanning to Actions workflow logs. After a run finishes, supported provider-pattern matches appear in the repository’s secret-scanning alerts with a log link. Alerts remain available after the logs are deleted. The feature is disabled by default.

One useful next step

Ask the security owner to check eligibility and the current policy read-only. Before any approved enablement, assign an alert-review owner and response process. Never paste a real secret into a workflow to test detection; use only an organization-approved non-secret fixture.

Record a safe evaluation plan ↗

Before you dive in

The preview requires GitHub Enterprise Cloud with Secret Protection or Advanced Security and applies to eligible repositories with secret scanning enabled. Only runs completed after enablement are scanned; old logs are not backfilled. Generic, custom, AI-detected and already-masked secrets are excluded. Preview alerts do not send notifications, so direct review of the alert list is essential.

GO TO THE ORIGINAL

Source & announcement date

GitHub ·

GitHub Changelog: Secret scanning detects secrets in GitHub Actions workflow logs ↗ (opens in a new tab)

This brief summarizes the linked announcement. “The AI Superpower take” and the next step are our editorial interpretation, not claims from the source.

KEEP YOUR CURIOSITY GOING

A few more worth knowing.

All AI news ↗