Keeping your account and data secure

You can securely access your account's resources by authenticating to GitHub Enterprise Server, using different credentials depending on where you authenticate.

Secure your account on GitHub with a strong and unique password using a password manager.

GitHub Enterprise Server credentials include not only your password, but also the access tokens, SSH keys, and application API tokens you use to communicate with GitHub Enterprise Server. Should you have the need, you can reset all of these access credentials yourself.

You can use a personal access token in place of a password when authenticating to GitHub in the command line or with the API.

To keep your credentials secure, you should regularly audit your SSH keys, deploy keys, and review authorized applications that access your account.

You should review deploy keys to ensure that there aren't any unauthorized (or possibly compromised) keys. You can also approve existing deploy keys that are valid.

Your tokens can expire and can also be revoked by you, applications you have authorized, and GitHub Enterprise Server itself.

You can review the security log for your personal account to better understand actions you've performed and actions others have performed that involve you.

Learn about security log events recorded for your personal account.

Sensitive data can be removed from the history of a repository if you can carefully coordinate with everyone who has cloned it and you are willing to manage the side effects.

To confirm access to your account before you perform a potentially sensitive action, your GitHub Enterprise Server instance prompts for authentication.

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 GitHub. In such cases, changing your password prevents any unintended future access to your account and projects.

You can view and revoke your active sessions in your settings.