Security Model
A key feature of the scrambls system is to provide security of user-to-user communications and to provide the ability for the user to control content owned/generated by that user (by controlling who can descrambl content, when it can be descrambld, etc.). The first version of the security pieces of the system includes non-standard security algorithms that “play well” with the constraints imposed by applications loosely defined as “social networking” (e.g., Facebook, Twitter, Gmail, etc.). These constraints include user interface, user interaction, simplicity, and ease-of-use.
The components of the scrambls system are not meant to be limited to these non-standard algorithms. While not explicitly mentioned in the System Model section above, the components have been designed to support replacement of the following functionality:
- key generation (e.g., cryptographically secure keys could be generated by, say, MS-CAPI)
- ciphering algorithm (e.g., AES could be used)
- key storage/management (e.g., a different, or external, key management system could be used)
Details on the current security algorithms can be found in a separate Scrambls Security document.
next Component Interaction | |
