Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modernize 2FA policy #338

Merged
merged 1 commit into from
Jan 2, 2024
Merged

Modernize 2FA policy #338

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions 2_Operations/security.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,9 +28,9 @@ The passwords stored in a password manager should be much longer randomly genera

### Two-Factor Authentication (2FA)

Whenever possible enable 2FA (two-factor authentication) for logging into services.
Whenever possible, enable 2FA (two-factor authentication) for logging into services.

* OTP (one-time-password) authentication application, e.g. Google Authenticator, is a really secure option.
* Using 1Password to [store OTP](https://support.1password.com/one-time-passwords/) (one-time-password) tokens is convenient and safe.
* SMS authentication should be avoided, unless the only 2FA option, as it is vulnerable to attacks.
* [U2F](https://en.wikipedia.org/wiki/Universal_2nd_Factor) hardware token is the most secure, requiring a physical device e.g. Yubikey. Further details in [U2F explained](https://www.howtogeek.com/232314/u2f-explained-how-google-microsoft-and-others-are-creating-universal-two-factor-authentication-tokens/).

Expand Down
Loading