All the sensitive data is encrypted and stored in the Qntrl database.
Sensitive data:
Task payload, response
Credentials
Tokens used to connect with the Bridge
AES algorithm is used to encrypt the data at rest.
Encryption keys are different for each org and kept confidential. To know more about our encryption policy refer to this link.
All the sensitive data is encrypted and stored, as required, in either the file system or the Bridge database.
Sensitive data:
Bridge credentials - to login Bridge in UI
OAuth credentials - to connect with the Qntrl
Registration Token
All the Credentials are created in the Bridge.
AES algorithm is used to encrypt the data.
A unique encryption key is generated while installing the Bridge. So, even if the encrypted data is exposed, it will be difficult to view the original data.
Task payload may contain sensitive information. So, in addition to protocol encryption, the payload will be encrypted to avoid exposure of original data.
AES/SHA256 algorithm is used to encrypt the payload.
Sensitive data in logs are masked on both the Qntrl and Bridge sides.
Users can create Credentials either in Qntrl or in Bridge. In both cases, data will be encrypted and stored in respective databases.
Credentials created in the Qntrl are encrypted as per our EAR policy. Profile-level permissions can be configured for Credentials. Also, it can be viewed only by the created user.
The credentials created in the Bridge will be encrypted using the AES algorithm with AES/CBC/PKCS5P mode.
Learn how to use the best tools for sales force automation and better customer engagement from Zoho's implementation specialists.
If you'd like a personalized walk-through of our data preparation tool, please request a demo and we'll be happy to show you how to get the best out of Zoho DataPrep.
You are currently viewing the help pages of Qntrl’s earlier version. Click here to view our latest version—Qntrl 3.0's help articles.