Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
cloudencryption [2018_12_10 18:09] – steven | cloudencryption [2020_11_13 14:51] – [Encryption Overview] jim | ||
---|---|---|---|
Line 3: | Line 3: | ||
===== Encryption Overview ===== | ===== Encryption Overview ===== | ||
- | One of the issues | + | One of the issues with increasing compliance regimes such as GDPR, CCPA, and increasing breaches of data is the issue of security. |
- | The secondary security concern can be with Cloud the Providers themselves. Users often want to protect certain files on the actual Cloud where they reside, and to that end they can want to use encryption | + | Most data services use an encryption 'at rest' data strategy. This encrypts all data that resides |
- | This particular use case can be solved by using the Cloud encryption service that SME provides. Encryption works when users upload files from SME web or desktop access clients, to any of the 40+ Cloud Storage and Saas Providers that SME supports. Users connect over SSL and assign files a private key phrase to file that are uploaded. | + | From a compliance perspective, |
- | This key phrase | + | Companies therefore should take additional precautions with data ie. ensuring it is encrypted independent of the storage provider. File based encryption is one such mechanism that can be used to achieve this. |
+ | |||
+ | The File Fabric' | ||
+ | |||
+ | You can consider file based encryption | ||
+ | |||
+ | The File Fabric can be used to encrypt either | ||
===== Encryption Algorithm ===== | ===== Encryption Algorithm ===== | ||
- | SME uses AES-256 encryption using the Rijndael cipher, with Cipher Block Chaining (CBC) where the block size is 16 bytes. The cipher Rijndael consists of: | + | The File Fabric |
* an initial Round Key addition | * an initial Round Key addition | ||
Line 27: | Line 33: | ||
===== Encryption Scope ===== | ===== Encryption Scope ===== | ||
- | Encryption can be set at an Org (Team) or on a Personal level. | + | Encryption can be set for the whole team by the File Fabric Administrator by setting |
+ | If global team encryption is not turned on, the File Fabric Administrator can set the scope to be on a per user level, in which the end user is responsible for setting and remembering the encryption key. | ||
+ | |||
+ | |||
+ | |||
===== Team Encryption ===== | ===== Team Encryption ===== | ||
- | The Cloud Admin of the Team Account can set by logging | + | The File Fabric Administrator |
- | Once this password is set then Cloud Files for all users of the Primary Cloud are ' | + | Once this password is set then Files for all users of the Primary Cloud are ' |
**Note:** Existing files are not encrypted only new file uploads are encrypted. | **Note:** Existing files are not encrypted only new file uploads are encrypted. | ||
Line 40: | Line 50: | ||
---- | ---- | ||
- | The password is stored, in an encrypted fashion, in the SME appliance | + | The password is stored, in an encrypted fashion, in the File Fabric |
Line 49: | Line 59: | ||
* All shared team folders | * All shared team folders | ||
* All Shared team folders plus user files | * All Shared team folders plus user files | ||
+ | * Nominated Folders | ||
//Share Team Folders:// Only team folders are encrypted the users personal files are not encrypted | //Share Team Folders:// Only team folders are encrypted the users personal files are not encrypted | ||
Line 54: | Line 65: | ||
//All Shared Team folders plus user files:// Shared Team folders and users personal files in the personal cloud are encrypted at rest | //All Shared Team folders plus user files:// Shared Team folders and users personal files in the personal cloud are encrypted at rest | ||
+ | Nominated folders: Only files in nominated are encrypted. | ||
---- | ---- | ||
- | For team folders, the encryption **is transparent** to end users. Team users **do not need to know** the encryption password and files are simply encrypted and decrypted as accessed via SME Apps. | + | For team folders, the encryption **is transparent** to end users. |
Team encrypted files that are shared without passwords also **do not** require the recipient to know the encryption password. | Team encrypted files that are shared without passwords also **do not** require the recipient to know the encryption password. | ||
Line 67: | Line 78: | ||
Standalone desktop decryption tools are provided in the event users want to download encrypted files direct from remote clouds or data stores. | Standalone desktop decryption tools are provided in the event users want to download encrypted files direct from remote clouds or data stores. | ||
- | |||
===== Personal Encryption ===== | ===== Personal Encryption ===== | ||
==== Uploading ==== | ==== Uploading ==== | ||
- | A user can set his own password to encrypt files uploaded in the web browser (entered when uploading), in the desktop tools, and also using the SME Android App. | + | A user can set his own password to encrypt files uploaded in the web browser (entered when uploading), in the desktop tools, and also using the File Fabric |
- | + | ||
- | + | ||
- | ---- | + | |
In the browser when uploading the user has the option to encrypt the files and enter the encryption phrase. | In the browser when uploading the user has the option to encrypt the files and enter the encryption phrase. | ||
- | + | For Windows | |
- | ---- | + | |
- | + | ||
- | For windows | + | |
- | + | ||
- | + | ||
- | ---- | + | |
On the SME Android App files uploaded can also be encrypted on upload from the device | On the SME Android App files uploaded can also be encrypted on upload from the device | ||
- | |||
- | |||
- | ---- | ||
Unlike the account level encryption the encryption phrase set by personal users is **not stored on the server** ie. the user has to remember the phrase otherwise they will not be able to gain access to the file and if they forget it there is no way for the SME service to recover it. | Unlike the account level encryption the encryption phrase set by personal users is **not stored on the server** ie. the user has to remember the phrase otherwise they will not be able to gain access to the file and if they forget it there is no way for the SME service to recover it. | ||
**Note:** also that different phrases can be used for different files. | **Note:** also that different phrases can be used for different files. | ||
- | |||
- | |||
- | ---- | ||
As an optimization the SME desktop tools provide an option to save a single encryption phrase for ease of use when dealing with files from the desktop. | As an optimization the SME desktop tools provide an option to save a single encryption phrase for ease of use when dealing with files from the desktop. |