Menu

Secrets in GitHub Actions logs: find and prevent leaks
📰

Secrets in GitHub Actions logs: find and prevent leaks

DEV Community: cicd·Sascha Mirow-Stanitzok·2 days ago
#3WAc96RK
#devtocicd#devto#dev#github#secret
Reading 0:00
15s threshold

Secrets in GitHub Actions logs are more common than most teams would like. Nobody deliberately writes echo $PASSWORD . What actually happens is that a Base64-encoded header, the JSON output of aws sts assume-role or a chatty debug log slips past automatic masking. Since November 9, 2026, GitHub scans these logs for secrets itself, but for now only for enterprise customers with Advanced Security.

This topic matters to me because workflow logs feel like they belong to nobody. They are created as a by-product, sit around for weeks, and anyone with read access to the repository can open them. In this article we look at what the new GitHub feature can and cannot do, how secrets end up in logs in the first place, and how to harden your workflows step by step. For everyone without an enterprise license, we also build a small log scanner in TypeScript that checks your recent workflow runs.

In short

GitHub only masks values in workflow logs that the runner knows to be secrets.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.