Stop Committing Your Secrets - Git Hooks To The Rescue!
summary
Repository scans find over 6 million exposed keys in 2021 and roughly three in a thousand commits contain a secret, so the proposed fix is automation: install pre-commit hooks that grep or run detectors, or enforce checks on the server with pre-receive hooks, using tools like AWS Labs git-secrets, truffleHog or GG Shield (GitGuardian) which checks ~350 patterns and can stop commits or reject pushes and thus prevent most accidental secret leaks before they land.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:39Exposed secrets threat
- 4:29Why secrets leak
- 6:35Git hooks for security
- 8:22Stopping secret commits
- 11:09Secret detection tools
- 13:59Demo: Git hooks in action
- 14:41Conclusion and key takeaways
related talks
14mStop Committing Your Secrets - Git Hooks To The Rescue!
15mPreventing Accidental Secret Commits with Gitleaks
48mHow Source Code is Revealing our Secrets
31mExploiting Leaked Credentials - How python code is leaking millions of secrets
35mGit those secrets out your repos!
30mOops! I Committed My Password To GitHub!
26mSecret Hunting
27mLarge-Scale Exposure Of Orphaned Commits On Major Git Platforms