How do we make sure we don't have any developers who have checked in passwords or secrets into code accidentally?
You can use credentials scanning solutions comb through git repositories and flag anything sensitive that was committed in error.
For Bitbucket, you can use our app Security for Bitbucket. Security for Bitbucket streamline this process. Scans can be performed, reviewed, and dispositioned without scripting or setting up an external service. Security for Bitbucket also integrates with Bitbucket’s hook architecture to block any dangerous incoming commits. Without such an integration, committed secrets can only be caught after the fact, and must be considered compromised and rotated out.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.