Since Version: 9.0
The crypto engines of PIPEFORCE allow to encrypt and decrypt data very effectively so workflows can be implemented in an very secure way.
If you're using PIPEFORCE as a cloud service, a random secure keystore is automatically provided to your instance. This keystore is generated in an encrypted wallet oustide the PIPEFORCE cloud and is never persisted somewhere else. The keystore will also take part on key rotations which will take place in order to change the keys from time to time. So all setup for you by default in a most secure way.
In order to store property values only in encrypted format in the property store, you have to set the parameter
true when you create the property schema using the command
property.schema.put. For example:
When storing value to this property later using the command
property.put this value is automatically encrypted using AES-256 with CBC mode before it gets stored to the database using the default access key of the platform. So you can be sure that the data is encrypted at rest.
Encrypting the value of a property this way increases security but also has some drawbacks you have to be aware of:
- You can no longer apply in-database JSON queries on encrypted property values.
- Events with the properties as payload (for example
property.updated) will send the payload in messages also encrypted. So listeners to these events do have limited access to this property.
- In lists where a set of properties is returned, the encrypted property stays encrypted. So you could have a mixture of plain text and encrypted properties for example. You have to make sure to handle this in your application accordingly.
- Once a property was set to
encrypted:trueit cannot be switched back to plain text.
Once a property has been stored encrypted in the property store you can load and decrypt its value using the command
property.value.get with parameter
decrypt set to
true. For example:
In this case the property will be automatically decrypted using the default access key of the platform and then returned.
This is the only way to decrypt the value of the property. For performance and security reasons it is not possible to "mass-decrypt" properties returned in a list. For example by using the command
property.get with a path pattern.
Custom encryption and decryption
You can also encrypt and decrypt data in PIPEFORCE using AES-256 in CBC mode by providing your own encryption key. For this see the command
data.decrypt where you can set your custom key.
When using custom encryption and decryption you have to make sure by your own to manage the encryption keys securely.
Report an Issue
In case you're missing something on this page, you found an error or you have an idea for improvement, please click here to create a new issue. Another way to contribute is, to click Edit this page below and directly add your changes in GitHub. Many thanks for your contribution in order to improve PIPEFORCE!