885da5b3d3
* New Crowdin translations by Github Action * Reset broken translated files to English * Ran script/i18n/homogenize-frontmatter.js * Ran script/fix-translation-errors.js * Reverted translated files with parsing and rendering errors * fix malformed liquid * add next directory to exclude list * currentversion -> currentVersion * fix liquid errors * fix liquid errors * Reset broken translated files to English * Ran script/i18n/homogenize-frontmatter.js * Revert /ja/github/authenticating-to-github/about-authentication-with-saml-single-sign-on * Reset known broken translation files LAST * Run script/i18n/homogenize-frontmatter.js Co-authored-by: Crowdin Bot <support+bot@crowdin.com> Co-authored-by: Rachael Sewell <rachmari@github.com> Co-authored-by: Kevin Heis <heiskr@users.noreply.github.com>
2.2 KiB
2.2 KiB
title, intro, redirect_from, versions, topics
| title | intro | redirect_from | versions | topics | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Preventing unauthorized access | You may be alerted to a security incident in the media, such as the discovery of the [Heartbleed bug](http://heartbleed.com/), or your computer could be stolen while you're signed in to {% data variables.product.product_location %}. In such cases, changing your password prevents any unintended future access to your account and projects. |
|
|
|
{% data variables.product.product_name %} 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, deploy keys, and authorized integrations and revoke unauthorized or unfamiliar access in your SSH and Applications settings. {% if currentVersion == "free-pro-team@latest" %}
- Verify all your email addresses. If an attacker added their email address to your account, it could allow them to force an unintended password reset. {% endif %}
- Review your account's security log. 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 webhooks on your repositories. Webhooks 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.