* initial commit
* adding quotes for the array error
* Create Gemfile
* Create Gemfile.lock
* add .nvmrc and .node-version
* removed /article from URL
* update links to work with netlify
* more fixed links
* link fixes
* update bad links
* Update netlify.toml
toml test for redirects
* article redirect
* link fixes
* Update index.html
* Update netlify.toml
* Update _config.yml
* Update netlify.toml
* Update netlify.toml
* Update netlify.toml
* Update netlify.toml
* Update netlify.toml
* add article back into URL for launch
* Update netlify.toml
* Update netlify.toml
* add order to categories front matter
* Update netlify.toml
* update
* sidemenu update
* Revert "sidemenu update"
This reverts commit 5441c3d35c.
* update order prop
* Navbar updates per Gary and compiler warnings
* font/style tweaks
* Update sidebar.html
* Stage Release Documentation (#739)
* initial drafts
* rewrite Custom Fields article to prioritize new context-menu option & better organize ancillary information
* edit
* edit
* Custom Field Context Menu & CAPTCHA item in release notes
* SSO relink event
* update rn
* small edits
* improve release notes titles
* fix side menu
* Edits courtest of mportune!
* update order
* link fixes
* link cleanup
* image updates and a link
* fix trailing slash
Co-authored-by: DanHillesheim <79476558+DanHillesheim@users.noreply.github.com>
2.8 KiB
layout, title, categories, featured, popular, tags, order, redirect_from
| layout | title | categories | featured | popular | tags | order | redirect_from | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| article | Account Encryption Key |
|
false | false |
|
04 |
|
Each unique Bitwarden account has an encryption key derived from your Master Password, according to the methods defined in Encryption. This encryption key is used to encrypt all Vault data.
Rotate your Encryption Key
{% callout warning %} Rotating your encryption key is a potentially dangerous operation. Please read this section thoroughly to understand the full ramifications of doing so. {% endcallout %}
Rotating your account’s encryption key generates a new encryption key that is used to re-encrypt all Vault data. You should consider rotating your encryption key if your account has been compromised such in a way that someone has obtained your encryption key.
After rotating, you should quickly take the following actions to prevent data loss or corruption:
Log out of Client Applications
When you rotate an encryption key, you must immediately log out of any logged-in sessions on Bitwarden client applications (Desktop App, Browser Extension, Mobile App, etc). Logging out of client applications in this way will shut down sessions using the "stale" (prior-to-rotation) encryption key. After doing so, logging back in as normal will use the new encryption key.
Making changes in a session with a "stale" encryption key will cause data corruption that will make your data unrecoverable.
Re-create any Encrypted Exports
If you're using Encrypted Exports to store long-term secure backups, you should immediately re-create the encrypted export of your Vault data using the new encryption key.
Encrypted Exports use your encryption key to encrypt and decrypt your Vault data, meaning that a rotated encryption key will not be able to decrypt an export created with the "stale" (prior-to-rotation) key.
How to Rotate your Encryption Key
Complete the following steps to rotate your account encryption key:
-
Log in to your Web Vault{:target="_blank"}.
-
Select Settings from the top navigation bar.
-
On the My Account page, locate the Change Master Password section.
-
Enter your Current Master Password and create/confirm a New Master Password.
{% callout success %}If you don't want to change your Master Password and only rotate your account encryption key, you can enter your current master password in the New fields to prevent it from changing.{% endcallout %}
-
Check the Also rotate my account's encryption key checkbox and accept the dialog.
-
Select the Change Master Password button.