empayre/fleet
14
0
Fork 0
mirror of https://github.com/empayre/fleet.git synced 2024-11-06 08:55:24 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Adding account recovery procedure (#5388)

Browse Source
This commit is contained in:
Guillaume Ross 2022-04-26 18:15:50 -04:00 committed by GitHub
parent a2d3b91de2
commit e740dea70f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 28 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
handbook/README.md
View File

@ -21,6 +21,8 @@ The Fleet handbook is the central guide for how we run the company. As part of o
### ⛑ Security
[Account recovery process](./security.md#account-recovery-process)
[How we protect end-user devices](./security.md#how-we-protect-end-user-devices)
[Hardware security keys](./security.md#hardware-security-keys)

26
handbook/security.md
View File

@ -1,5 +1,31 @@
# Security
## Account recovery process
As an all-remote company, we do not have the luxury of seeing each other or are able to ask for help in person. Instead, we require live video confirmation of someone's identity before performing recovery and this applies to all Fleet company accounts, from internal systems to SaaS accounts.
| Participant | Role |
| ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| Requester | Requests recovery for their own account |
| Recoverer | Person with access to perform the recovery who monitors *#help-login* |
| Identifier | Person that visually identifies the requester in a video call. The identifier can be the recoverer or a person the recoverer can recognize visually |
Here are the steps we take for the recovery process:
1. If the requester still has access to Slack, they ask for help in *#help-login*. If they do not have access to Slack, they can contact their manager or a teammate over the phone via voice or texting, and they will post in *#help-login* for the requester.
2. A recoverer acknowledges the request in #help-login using the "eyes" emoji 👀.
3. The recoverer identifies the requester through a live video call.
* If the recoverer does not know the requester well enough to positively identify them visually, the
recoverer can ask a colleague whom they recognize to act as the identifier. **All three must be
live on a video call at the same time.**
* For example, if the recoverer does not recognize Guillaume but can recognize Zach, they should ask Zach to identify Guillaume. Using the requester's manager or a direct teammate is recommended, as it increases the chances they see each other on video frequently.
4. If the recoverer recognizes the requester, or has the identity confirmed by the person acting as
the identifier, they can perform the recovery and update the thread in *#help-login*.
* If the recoverer is not 100% satisfied with identification, they do **NOT** proceed, and post to #g-security to engage the security team immediately.
## How we protect end-user devices
At Fleet, we believe that a good user experience empowers contributors.