status-im
/
status-security
mirror of https://github.com/status-im/status-security.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

authenticatio and authorization

This commit is contained in:
Corey 2020-04-21 11:29:45 -04:00
parent d24a019a53
commit f241744610
No known key found for this signature in database
GPG Key ID: 724684AF1BAAC90F
1 changed files with 39 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
drafts/authentication-and-authorization.md Normal file
View File

@ -0,0 +1,39 @@
# Authentication and Authorization in Status (Draft WIP)
## Authorization vs Authentication
This is me vs I can have access to this. Often time these two steps happen at the same time, but they do not have to.
It is important to map out the various places in Status that can potentially hold value, and what mechanisms we have in place to access them. From that we can reason about what options are useful/make sense for the user to implement.
## Possible Methods
- password
- yubikey (TOTP/FIDO/HID)
- pin
- keycard tap
- fingerprint / facial recognition
## Possible places within Status to check (or define)
- login
- sign txn (per wallet)
- add new wallet
- add new chat (when feature available)
- backup seed phrase
- change sensitive settings
- export data
- access private chat (new feature, but easily possible)
## What is valuable in Status
- private chats
- wallet assets
- data (account) encryption
## Mappings
- account: login
- **description:** Initial access to an account within the application. It gives read access to everything (currently) but does not allow for anything that changes within the wallet, as well as changing preferences.
- risk: variable
- **appropriate security measures:** Depends on associated risk and held value. We should default with password, and hint to change it as value increases.
- Wallet: sign txn
- **description:** Signing a transaction in the Status app approves a change to the assets within a specific a wallet account or the user's profile. The associated risk is dependent upon the assets the wallet account holds, or the control it may have in a given smart contract.
- **appropriate security measures:** any and all options should be available to secure the wallet account, but default to whatever the account login security measures are. Depending on the use of the account, a user should be able to remove or add whatever measures they want to desecure or ultra secure the account.