You may be alerted to a security incident in the media, such as the discovery of the Heartbleed bug, or your computer could be stolen while you're signed in to your GitHub Enterprise instance. In such cases, changing your password prevents any unintended future access to your account and projects.
GitHub requires a password to perform sensitive actions, such as adding new SSH keys, authorizing applications, or modifying team members.
After changing your password, you should perform these actions to make sure that your account is secure:
- Enable two-factor authentication on your account so that access requires more than just a password.
Review your SSH keys, authorized applications, and OAuth tokens and revoke unauthorized or unfamiliar access in your SSH and Applications settings.
Review your account's Security History. This provides an overview on various configurations made to your repositories. For example, you can ensure that no private repositories were turned public, or that no repositories were transferred.
- Review the service hooks on your repositories. Service hooks could allow an attacker to intercept pushes made to your repository.
- Make sure that no new deploy keys were created. This could enable outside servers access to your projects.
- Review recent commits made to your repositories.
- Review the list of collaborators for each repository.
