-
Notifications
You must be signed in to change notification settings - Fork 9.8k
Email 2FA changelog #26135
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.
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
Merged
+29
−0
Merged
Email 2FA changelog #26135
Changes from 2 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
2697769
Create 2025-10-30-email-2FA.mdx
jhutchings1 b347ec2
Update 2025-10-30-email-2FA.mdx
jhutchings1 df472d4
Update src/content/changelog/fundamentals/2025-10-30-email-2FA.mdx
jhutchings1 ab83dab
Update src/content/changelog/fundamentals/2025-10-30-email-2FA.mdx
jhutchings1 afbec50
Update src/content/changelog/fundamentals/2025-10-30-email-2FA.mdx
jhutchings1 423f561
Update src/content/changelog/fundamentals/2025-10-30-email-2FA.mdx
jhutchings1 3817882
Update src/content/changelog/fundamentals/2025-10-30-email-2FA.mdx
jhutchings1 e8fb3f6
Update src/content/changelog/fundamentals/2025-10-30-email-2FA.mdx
jhutchings1 e1d31ec
Update src/content/changelog/fundamentals/2025-10-30-email-2FA.mdx
jhutchings1 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
23 changes: 23 additions & 0 deletions
23
src/content/changelog/fundamentals/2025-10-30-email-2FA.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,23 @@ | ||
| --- | ||
| title: Introducing email two-factor authentication | ||
| description: Cloudflare now offers email two-factor authentication to protect your account | ||
| date: 2025-10-30 | ||
| --- | ||
|
|
||
| Two-factor authentication (2FA) is one of the best ways to protect your account from the risk of account takeover. Cloudflare has offered phishing resistant 2FA options including hardware based keys (eg Yubikey) and app based TOTP (time-based one-time password) options which use apps like Google or Microsoft's Authenticator app. Unfortunately, while these solutions are very secure, they can be lost if you misplace the hardware based key, or lose the phone which includes that app. The result is that users sometimes get locked out of their accounts and need to contact support. | ||
|
|
||
| Today, we are announcing the addition of email as a 2FA factor for all Cloudflare accounts. Email 2FA is in wide use across the industry as a least common denominator for 2FA because it is low friction, loss resistant, and still improves security over username/password login only. We also know that most commercial email providers already require 2FA, so your email address is usually well protected already. You can now enable email 2FA by going to your user profile (the person icon in the top corner of the Dashboard), then **Authentication**, and then under Two-Factor Authentication click **Set up**. | ||
jhutchings1 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| ## Sign-in security best practices | ||
|
|
||
| Cloudflare is critical infrastructure, and you should protect it as such. Please review the following best practices and make sure you are doing your part to secure your account. | ||
jhutchings1 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| - Use a unique password for every website, including Cloudflare, and store it in a password manager like 1Password or Keeper. These services are cross-platform and simplify the process of managing secure passwords. | ||
| - Use 2FA to make it harder for an attacker to get into your account in the event your password is leaked | ||
jhutchings1 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - Store your backup codes securely. A password manager is the best place since it keeps the backup codes encrypted, but you can also print them and put them somewhere safe in your home. | ||
| - If you use an app to manage your 2FA keys, enable cloud backup, so that you don't lose your keys in the event you lose your phone. | ||
| - If you use a custom email domain to sign in, [configure SSO](https://developers.cloudflare.com/fundamentals/manage-members/dashboard-sso/). | ||
jhutchings1 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - If you use a public email domain like Gmail or Hotmail, you can also use social login with Apple, GitHub, or Google to sign in. | ||
| - If you manage a Cloudflare account for work: | ||
| - Have at least two administrators in case one of them unexpectedly leaves your company | ||
jhutchings1 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - Use SCIM to automate permissions management for members in your Cloudflare account | ||
jhutchings1 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.