Skip to content

Instantly share code, notes, and snippets.

@iAnonymous3000
Created February 20, 2025 05:28
Show Gist options
  • Save iAnonymous3000/27c5c7f30b0a8b82ca492f1664e41567 to your computer and use it in GitHub Desktop.
Save iAnonymous3000/27c5c7f30b0a8b82ca492f1664e41567 to your computer and use it in GitHub Desktop.
A comprehensive hardening guide for Bitwarden password manager, covering encryption best practices, 2FA with hardware keys, self-hosting considerations, and offline backup strategies. Includes practical configuration steps and security-focused workflows.

How to Secure Your Bitwarden Account: A Comprehensive Guide

A breach in your password manager could be catastrophic, so securing it is non-negotiable. This guide covers the essentials and some pro-level tricks to make your account a fortress. Let’s dive in!

1. Use a Strong, Unique Master Password

Your master password is the linchpin of your Bitwarden security. If it falls, everything does—so let's make it unbreakable.

What Makes a Password Strong?

  • Length: Aim for 20+ characters. The longer, the better—each character ramps up the cracking difficulty.
  • Complexity: Blend uppercase, lowercase, numbers, and special characters (e.g., @, #, &).
  • Uniqueness: This password is for Bitwarden only. No recycling allowed.
  • No Personal Info: Skip birthdays, pet names, or favorite quotes—hackers can guess these using social media or phishing.

How to Create One

  • Passphrase Approach: String together random words with a twist. Example: "ThunderHub$22GreenForest!" Easy to recall, tough to guess.
  • Steer Clear of Obvious: "Password123," "letmein," or your birthday? Nope. Hackers love those.
  • Bitwarden's Generator: Stuck? Go to Tools > Generator in Bitwarden for a random, bulletproof option.

Storage Tip

Jot it down on paper and stash it in a locked drawer or safe. Digital copies are a risk—keep it analog and offline.

2. Enable Two-Factor Authentication (2FA)

2FA is your second line of defense. Even if your master password leaks, this extra step keeps intruders out.

How to Set It Up

  1. Log into Bitwarden.
  2. Head to Settings > Security > Two-step Login.
  3. Choose your method:
    • Authenticator App: Ente Auth or similar. Codes stay on your device—top-tier choice.
    • Email: A code lands in your inbox. Handy, but less secure if your email's compromised.
    • Hardware Key: YubiKey or similar. Physical, phishing-resistant, and elite-level (more on this later).
  4. Follow the setup prompts.

Why an Authenticator Beats Email

Email 2FA hinges on your inbox's security—a weak link if hacked. An authenticator app keeps codes offline and out of reach.

3. Secure Your Recovery Code

Your recovery code is your lifeline if you lose your master password or 2FA access. Protect it like it's gold.

How to Handle It

  1. Navigate to Settings > Security > Two-step Login.
  2. Click Generate under Recovery Code.
  3. Write it down manually and store it offline—think safe, locked box, or hidden nook.

Critical Warning

Lose this code and your password, and your vault's gone forever. No recovery code, no second chances.

4. Be Cautious with Vault Sharing

Sharing passwords or vault items is useful, but one misstep can expose your data. Let's keep it tight.

Best Practices

  • Trust First: Share only with people you'd hand your house keys to.
  • Use Organizations: For teams or families, set up an Organization in Bitwarden to manage access precisely.
  • No Public Links: Avoid sharing via open URLs—anyone with the link could snoop.
  • Audit Access: Check Settings > Organizations regularly and boot out ex-members.

Pro Tip

For sensitive stuff, use Secure Notes instead of sharing passwords outright. It's like handing over a locked box, not the key.

5. Keep Bitwarden Updated

Updates patch vulnerabilities. Skipping them is like leaving your windows open during a storm.

How to Stay Current

  • Desktop App: Check Help > Check for Updates or let auto-updates roll.
  • Browser Extension: Your browser usually manages this—peek at extension settings to confirm.
  • Mobile App: Visit your app store and grab the latest version.

Why It Matters

Hackers exploit old software. Stay updated, stay safe.

6. Monitor Security Reports

Bitwarden's built-in reports are your security radar, spotting risks before they blow up.

How to Use Them

  1. Go to Tools > Reports.
  2. Check these:
    • Exposed Passwords: Flags credentials leaked in breaches.
    • Reused Passwords: Highlights duplicates you've used elsewhere.
    • Weak Passwords: Calls out flimsy ones needing a boost.
    • Unsecured Websites: Warns if saved sites lack HTTPS.
  3. Fix issues with Bitwarden's password generator.

Stay Ahead

Run these monthly. It's your vault's health check—catch problems early.

7. Adjust Your Vault Timeout Settings

An unlocked vault on a shared or stolen device is a goldmine for snoopers. Tighten the leash.

Why It Matters

Vault Timeout dictates how long your vault stays open. Too long, and it's an open invitation.

Action Steps

  • Go to Settings > Options.
  • Set Vault Timeout to 1–5 minutes of inactivity.
  • Enable Lock on Browser Refresh for extra protection when closing tabs.

8. Explore Emergency Access (Paid Plans)

For Premium or Family users, Emergency Access ensures your vault isn't lost forever in a crisis.

How It Works

  • Designate a trusted contact in Settings > Emergency Access.
  • Set a Wait Time (e.g., 7 days). If they request access and you don't block it, they're in.

Why It's Useful

Illness or accident? Your loved ones or colleagues can still access critical logins.

9. Consider Self-Hosting for Total Control

Tech-savvy? Self-hosting Bitwarden puts your data in your hands.

Pros & Cons

  • Pros: You control the server, updates, and backups.
  • Cons: You're on the hook for security and maintenance. Self-hosting takes tech skills and ongoing effort—it's powerful but not beginner-friendly.

How to Start

  • See Bitwarden's self-hosting guide.
  • Secure your server with backups and regular patches.

10. Watch Out for Phishing & Social Engineering

Even the best setup crumbles if you're tricked into handing over the keys.

Red Flags

  • Fake Emails/DMs: Bitwarden won't ask for your password or 2FA code—ever.
  • URL Trickery: Check for typos (e.g., bitwarden[dot]co vs. bitwarden[dot]com).
  • Panic Plays: Urgent "act now" messages? Pause and verify.

Stay Sharp

Double-check login pages and never rush into entering credentials.

11. Keep Tabs on Login Sessions

Suspicious activity? Check who's logged in.

How to Check

  • Log into the Web Vault.
  • Go to Settings > My Account > Sessions.
  • Revoke unknown or old sessions.

12. Back Up Your Encrypted Vault Exports (Offline)

A backup ensures you're never fully locked out.

How to Do It

  • In the Web Vault, go to Tools > Export Vault.
  • Choose encrypted format (e.g., .json with a password).
  • Store it offline (USB in a safe) and encrypt it further with VeraCrypt or GPG.

Why It Helps

Server issues or emergencies won't leave you stranded.

13. Level Up with a Hardware Security Key for 2FA

Authenticator apps are great, but a hardware key (YubiKey) is next-level.

Benefits

  • Phishing Proof: Keys verify the real Bitwarden site before unlocking—no fake login page can trick them.
  • Ease: Tap and go—no codes to type.

Setup

  • In Two-step Login, select YubiKey and follow the prompts.

Wrap-Up

You’ve got the blueprint—now lock down your Bitwarden account! Start with the basics (password, 2FA), then layer on advanced tips as you go. Security’s a habit, not a one-off. Share this guide with friends, drop your own tips in the Gist comments, or hit up Bitwarden support if you’re stuck. Stay secure!


Questions? Check out Bitwarden’s official documentation for more details.

@pamperer562580892423
Copy link

pamperer562580892423 commented Mar 4, 2025

Nice!

I would consider adding

  • changing the KDF to Argon2 (as long as it's not the default)
  • setting up "login-with-passkey"-passkeys as a potentially more secure login method (hopefully, it get's out of Beta some day and is possible with more apps than just the web vault...)
  • probably not a "hardening topic" per se, but it could be mentioned that 1. without 2FA, one becomes subjected to the new device verification / login protection, and 2. a basic measure to prevent a lockout, if the device verification would ever get activated unexpectedly (e.g. after using the 2FA recover code), would be to at least store your BW email login credentials also outside of the Bitwarden vault (ideally on your emergency sheet)

PS:

  • changing the "clear clipboard" setting to e.g. 20 seconds (instead of the default "never") --> PS: If you have a kind of "clipboard history" activated on your system, make sure, if "clear clipboard" indeed deletes Bitwarden data from your clipboard.
  • and not a "hardening measure" for Bitwarden itself, but for it's usage: use auto-fill and/or "drag & drop" wherever you can (and avoid "copy & paste" as much as you can)

@pamperer562580892423
Copy link

pamperer562580892423 commented Mar 20, 2025

@iAnonymous3000 Because I like your idea, I wanted to give some more feedback and thoughts (additionally to my previous comment, see above). Some points may be important and I would like it, if you incorporated them. (and to keep it shorter, I won't repeat the points of my previous comment)

  1. Master Password:
  • please add "randomness" as a main criterion what makes a password strong!
  • the Bitwarden community regularly recommends an (at least) 4-random-words passphrase
  • and one could argue, that your example with "...GreenForest" are not two random words, but two associated words, which is not a good example for a random (!) passphrase of words...
  1. 2FA
  • you could mention, that you have to login to the web vault here (as you did at other places)
  • you could mention, that with email 2FA, you can actually use another email than you use with your Bitwarden account
  • don’t use the „30-day remember me“ for 2FA-usage (at least on critical devices, that may be more likely to be stolen or compromised)
  • also, it should be mentioned now, that everyone who doesn't use 2FA for the Bitwarden account/vault, would now have automatically activated the "new device verification / login protection" (see here: https://bitwarden.com/help/new-device-verification/)
  1. Recovery Code
  • in your first sentence here, please change this: "Your recovery code is your lifeline if you lose your master password or 2FA access." - No!!! That sentence is highly misleading. The recovery code can't help you at all if you loose your master password!!! It is "only" a 2FA recovery code! You still need the master password to even be able to use the 2FA recovery code. (I think in your last sentence in this section you expressed that also... but please, change this first sentence, before it misleads people)
  • also, you should mention that you have to login to the web vault for that (this info is missing here)
  • and there is no "Generate" you can click, but "View recovery code"
  1. Sharing
  • I don't know if I got your "Pro Tip" wrong, but Secure Notes can't be shared at all... I guess you meant using "Sends", to share something with others?!?
  1. Vault Health Reports
  • again, you should mention you're talking about logging in to the web vault, as reports currently can only be used there
  • and then, it's not in "Tools", but "Reports" have their own menu item...
  1. Vault Timeout
  • I think, here it should be mentioned, that every (!) Bitwarden app has to get their own set up of vault timeout settings, as there is no "sync" for the settings of all apps
  1. Phishing
  • I think you're mainly talking about a "fake Bitwarden web vault" or "fake Bitwarden (phishing) emails" ?!? I think you should make more clear that you mainly mean this here
  1. Active Sessions
  • the path is wrong... the correct path is: web vault --> Settings --> Security --> Devices
  • and, more importantly, currently you CAN'T revoke "unknown or old sessions" !!! (at the moment, you just can see the "known devices", but can't do anything... possibly this will change in the future, as this "Devices" overview is overall fairly new)
  1. Backup
  • at the latest, you should mention at this point here that users should make an emergency sheet, with at least their master password, email, 2FA recovery code, URL, server region and their login credentials for the used email address on it
  • ... and then, if you use password-protected encrypted exports, the used password for that should be also on your emergency sheet! (you can't use the password-encrypted export, if you don't have access to the used password, e.g. if you only have it in your Bitwarden vault! That would be the famous problem of "circular dependency" and you would need access to your Bitwarden vault, to get access to your Bitwarden vault...
  1. Hardware Security Key as 2FA
  • if you set it up in "Two-Step Login" --> and then choose "YubiKey", then that's the path to Yubico OTP (!) and that's not phishing-resistant
  • if you want to set up a security key in the best way (FIDO2 - phishing-resistant, and I guess that was what you indeed meant), then you would have to set it up this way: web vault --> Security --> Two-Step Login --> Passkey !!! (yeah, technically, it may not be a "passkey" in the strict sense, but Bitwarden calls the FIDO2 WebAuthn 2FA now "passkey"-2FA)
  • and again, as just written, you should mention that setting is only to be done in the web vault!

PS:

  1. Vault Timeout (additions)
  • there is no "Lock on Browser Refresh" --> I think you meant "Lock on Browser restart" ?!
  • and, if using a PIN for unlocking, check the option "Require master password on browser restart"
  • with mobile devices and using them in public, using biometrics might be preferrable, as it prevents e.g. shoulder-surfing (if/when typing in a PIN or the master password)
  • and, consider very short timeout settings of 1-2 minutes or even "immediately" on "mobile" devices (phone, tablet, laptop...), as they might get stolen "out of your hand"...

And to the "auto-fill feature":

  • better avoid "autofill on page load"
  • URI matching settings:
  • -- try to avoid "base domain"
  • -- best, to use "exact", if possible
  • -- if the exact domain varies, then use either "host" or (with caution) "start with"

PPS:

Another addition:

  • choose your email for your Bitwarden account/vault wisely (private, "not leaked", maybe an alias-address, ...)
  • if you want to log in to the web vault, always type in vault.bitwarden.com or vault.bitwarden.eu - or use "favorites" of your browser (if you search for it, you might fall for fake/phishing sites, mimicking the Bitwarden web vault)
  • always download the Bitwarden apps via the official Bitwarden website: https://bitwarden.com/download/
  • and some (cybersecurity) basics should also be mentioned: only use Bitwarden on devices with the "latest" security updates, general malware and phishing prevention (be cautious with links in emails, download software only from secure sources etc.), consider encrypting the devices/systems/disks you use Bitwarden on, don't connect "foreign" cables and devices, don't use public charging ports, be cautious with "insecure" Wi-Fi connections etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment