From dfa2f074e57c81666c44da828e4fb4530768c58f Mon Sep 17 00:00:00 2001 From: fred_the_tech_writer <69817454+fschillingeriv@users.noreply.github.com> Date: Tue, 7 Dec 2021 09:32:19 -0500 Subject: [PATCH] change format of Emergency Access article (#816) --- _articles/security/emergency-access.md | 149 +++++++++++++++++-------- 1 file changed, 102 insertions(+), 47 deletions(-) diff --git a/_articles/security/emergency-access.md b/_articles/security/emergency-access.md index 84d682d9..5016caa3 100644 --- a/_articles/security/emergency-access.md +++ b/_articles/security/emergency-access.md @@ -13,55 +13,69 @@ description: "The emergency access feature of the Bitwarden password manager ena Emergency Access enables users to designate and manage trusted emergency contacts, who may request access to their Vault with a configurable level of permissions. {% callout info %} -Establishing Emergency Access to a Vault is available for Premium users, including members of Paid Organizations (Families, Teams, or Enterprise), but anyone with a Bitwarden account can be designated *as* a trusted emergency contact (i.e. your trusted emergency contacts do not need to have Premium). +Only Premium users, including members of paid Organizations (Families, Teams, or Enterprise) can designate trusted emergency contacts, however anyone with a Bitwarden account *can be designated as* a trusted emergency contact. -**If your premium features are cancelled or lapses due to failed payment method,** your trusted emergency contacts will still be able to request and obtain access to your Vault. As a grantor, however, you will not be able to add new or edit existing trusted emergency contacts. +**If your premium features are cancelled or lapses due to failed payment method**, your trusted emergency contacts will still be able to request and obtain access to your Vault. You will, however, not be able to add new or edit existing trusted emergency contacts. {% endcallout %} ## How it Works Emergency Access uses public key exchange and encryption/decryption to allow users to give a [trusted emergency contact](#trusted-emergency-contacts) permission to [access Vault data](#user-access) in a zero knowledge environment: -1. A Bitwarden user (the *grantor*) [invites another Bitwarden user](#invite-a-trusted-emergency-contact) to become a trusted emergency contact (the *grantee*). The invitation (valid for only 5 days) specifies a [user access level](#user-access) and includes a request for the grantee's public key. -2. Grantee is notified of invitation via email and [accepts the invitation](#accept-an-invitation) to become a trusted emergency contact. On acceptance, the grantee's public key is stored with the invite. -3. Grantor is notified of acceptance via email and [confirms the grantee](#confirm-an-accepted-invitation) as their trusted emergency contact. On confirmation, the grantor's Master Key is encrypted using the grantee's public key and stored once encrypted. Grantee is notified of confirmation. -4. An emergency occurs, resulting in grantee requiring access to grantor's Vault. Grantee [submits a request for emergency access](#initiate-emergency-access). -5. Grantor is notified of request via email. The grantor may [manually approve the request](#approve-or-reject-emergency-access) at any time, otherwise the request is bound by a grantor-specified wait time. When the request is approved or the wait time lapses, the public-key-encrypted Master Key is delivered to grantee for decryption with grantee's private key. +1. A Bitwarden user (the *grantor*) [invites another Bitwarden user](#setup-emergency-access) to become a trusted emergency contact (the *grantee*). The invitation (valid for only 5 days) specifies a [user access level](#user-access) and includes a request for the grantee's public key. +2. Grantee is notified of invitation via email and [accepts the invitation](#setup-emergency-access) to become a trusted emergency contact. On acceptance, the grantee's public key is stored with the invite. +3. Grantor is notified of acceptance via email and [confirms the grantee](#setup-emergency-access) as their trusted emergency contact. On confirmation, the grantor's Master Key is encrypted using the grantee's public key and stored once encrypted. Grantee is notified of confirmation. +4. An emergency occurs, resulting in grantee requiring access to grantor's Vault. Grantee [submits a request for emergency access](#use-emergency-access). +5. Grantor is notified of request via email. The grantor may [manually approve the request](#use-emergency-access) at any time, otherwise the request is bound by a grantor-specified wait time. When the request is approved or the wait time lapses, the public-key-encrypted Master Key is delivered to grantee for decryption with grantee's private key. 4. Depending on the specified [user access level](#user-access), the grantee will either: + - Obtain view/read access to items in the grantor's Vault (**View**). - Be prompted to create a new Master Password for the grantor's Vault (**Takeover**). ### Trusted Emergency Contacts -Emergency Access relies on public key exchange within Bitwarden, therefore trusted emergency contacts must be existing Bitwarden users, or will be prompted to create a Bitwarden account before they can accept an invitation. Trusted emergency contacts do not need to have Premium to be designated as such. +Trusted emergency contacts must be existing Bitwarden users, or will be prompted to create a Bitwarden account before they can accept an invitation. Trusted emergency contacts do not need to have Premium to be designated as such. -A user's status as a trusted emergency contact is tied to a unique Bitwarden account ID, meaning that if a grantee [changes their email address]({{site.baseurl}}/article/product-faqs/) there is no reconfiguration required to maintain their emergency access. If a grantee creates a **new Bitwarden account** and [deletes]({{site.baseurl}}/article/delete-your-account/) the old account which had been specified as a trusted emergency contact, they will automatically be removed from the grantor's list and must be [re-invited](#invite-a-trusted-emergency-contact). +A user's status as a trusted emergency contact is tied to a unique Bitwarden account ID, meaning that if a trusted emergency contact [changes their email address]({{site.baseurl}}/article/product-faqs/) there is no reconfiguration required to maintain their emergency access. If a trusted emergency contact creates a **new Bitwarden account** and [deletes]({{site.baseurl}}/article/delete-your-account/) the old account, they will automatically be removed as a trusted emergency contact and must be [re-invited](#setup-emergency-access). There is no limit to the number of trusted emergency contacts a user can have. {% callout success %} -As a grantor, you can [reject](#approve-or-reject-emergency-access) an emergency access request at any time before the configured wait time lapses. +You can [reject](#use-emergency-access) an emergency access request by your trusted emergency contact at any time before the configured wait time lapses. {% endcallout %} ### User Access Trusted emergency contacts can be granted one of the following user access levels: + - **View**: When an emergency access request is granted, this user is granted view/read access to all items in your personal Vault, including passwords of Login items. - {% callout success %}As the grantor, you may [revoke access](#revoking-access) to a grantee with **View** access at any time.{% endcallout %} + {% callout success %}You may [revoke access](#use-emergency-access) to a trusted emergency contact with **View** access at any time.{% endcallout %} - **Takeover**: When an emergency access request is granted, this user can create a Master Password for permanent read/write access to your Vault (this will **replace** your previous Master Password). Takeover disables any [Two-step Login Methods]({{site.baseurl}}/article/setup-two-step-login/) enabled for the account. -**When the grantor is a member of an Organization**, they will be automatically removed from any Organization(s) for which they are not an [Owner]({{site.baseurl}}/article/user-types-access-control/). Owners will not be removed from or lose permissions to their Organization(s), however a [Master Password Policy]({{site.baseurl}}/article/policies/#master-password) will be enforced on takeover if enabled. Policies that are not usually enforced on Owners (e.g. [Two-step Login]({{site.baseurl}}/article/policies/#two-step-login)) will not be enforced on takeover. +**If you are a member of an Organization**, you will be automatically removed from any Organization(s) for which they are not an [Owner]({{site.baseurl}}/article/user-types-access-control/) on takeover. Owners will not be removed from or lose permissions to their Organization(s), however a [Master Password Policy]({{site.baseurl}}/article/policies/#master-password) will be enforced on takeover if enabled. Policies that are not usually enforced on Owners (e.g. [Two-step Login]({{site.baseurl}}/article/policies/#two-step-login)) will not be enforced on takeover. -## Using Emergency Access +## Setup Emergency Access -The following sections will walk you through establishing a trusted emergency contact, and executing on emergency access: +The following sections will walk you setting up Emergency Access, separated by whether you want to **Give Access** to your Vault or **Receive Access** to another user's Vault: +
+ +