Encryption is primarily used to safeguard the contents of a message so that only the intended recipient can read it. This is done by replacing the contents with unrecognizable data, which can be understood only by the intended recipient. This is how encryption became a method to protect data from those who may want to steal it.
Encryption can be used in two situations:
- Encryption in Transit
- Encryption at Rest (EAR)
Encryption in Transit
This refers to data that is encrypted when it is in transit — including from your browser to the web server and other third parties via integrations. Encrypting data in transit protects your data from man-in-the-middle-attacks.
Encryption at Rest
This refers to data that is encrypted when it is stored (not moving) — either on a disc, in a database, or some other form of media. In addition to encryption of data during transit, encryption of data when it is stored in the servers provides an even higher level of security. EAR protects against any possible data leak due to server compromise or unauthorized access.
Encryption is done at the application layer using two layers of security: the Data Encryption Key (DEK) and the KEK (Key Encryption Key). These keys are generated and maintained by our in-house Key Management Service(KMS). You can learn more about EAR
here.
What Data do we encrypt in Zoho Solo?
The following data is encrypted in Zoho Solo.
Business Information
| Includes business name and other details collected during onboarding.
|
Customer data
| Contact data such as first name, last name, company, email, phone, website, contact address, and contact profile image.
|
Work data
| Users can add tasks and track their work duration using timers. The names or titles of tasks and timers may contain ePHI. Project name, task name, subtask name, auto scan data, and calendar entries are encrypted.
|
Financial data
| Solopreneurs can create invoices and expenses for customers and receive payments. Invoices, expenses, and payment account information is encrypted.
|
Notes
| Users can create notes in Solo, which may contain ePHI, including customer details. Therefore, notes are classified as ePHI and encrypted at rest. Additionally, any resources added to notes, such as images or other file attachments, are also encrypted.
|
Attachments
| Resources such as files, note attachments, and profile images are encrypted, including their names.
|
Customer Mail History
| Sender and receiver email addresses are encrypted.
|
OAuth Tokens
| Refresh tokens and access tokens are encrypted in the database.
|