Preventing Accidental Secret Commits with Gitleaks
summary
Gitleaks plus Harness Open Source actually stop accidental secret commits by applying pattern-based scanning at pre-commit/CICD time; demo shows a pushed commit failing with an explicit file, commit id and detected secret and the push is refused. Setup uses Gitleaks rules (predefined and customizable) and a lightweight Harness instance; it prevents new leaks but doesn't remove existing secrets in history and blocks commits containing secrets until fixed.
AI-written summary · about
chapters (8)
- 0:00Introduction and Speaker Introduction
- 0:39Understanding Git Repository Vulnerabilities
- 1:45The Concept of Secrets in Code
- 2:49Shifting Left on Security
- 3:16Introducing GitLeaks: An Open Source Secret Scanner
- 5:29Harness Open Source: Features and Setup
- 7:02Demo: Preventing Accidental Secret Commits
- 13:44Summary and Conclusion
related talks
15mStop Committing Your Secrets - Git Hooks To The Rescue!
14mStop Committing Your Secrets - Git Hooks To The Rescue!
48mHow Source Code is Revealing our Secrets
31mExploiting Leaked Credentials - How python code is leaking millions of secrets
35mGit those secrets out your repos!
49mProtect Your Code with GitHub Security Features
27mCan you keep a secret?
24mHow to Find if Your Developers are Leaking Secrets?