Goodbye Credential Leaks: Securing Code Together
summary
Describes how credential issuers and the developer community can reduce breaches caused by leaked secrets by coordinating on secret-scanning practices; focuses on GitHub’s secret scanning product and collaboration between issuers and researchers to detect and remediate exposed access credentials. Explains concrete roles and actions credential providers can take to prevent misuse of leaked secrets and how attendees can participate in the collective effort.
AI-written summary · about
related talks
33mGaining initial access by exploiting leaked credentials
30mWhoops! I Accidentally Leaked My Credentials (again)
24mHow to Find if Your Developers are Leaking Secrets?
26mSecret Hunting
26mHow To Keep A Secret
14mSecurity lifecycle management in a multicloud world
49mEnhancing CI/CD Secrets Security: The 3Rs Approach
48mHow Source Code is Revealing our Secrets