You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we transfer our datasets outbound from z/OS, our information security policies require that the datasets first be PGP encrypted prior to transfer.
When the datasets arrive in our large data platform, we first decrypt them and then run our Spark job. It would be a more secure solution if Cobrix were able to decrypt the data in the byte stream as opposed to decrypting the file in-situ and then running the Spark job against decrypted data
Feature
Add support to enable Cobrix to read a PGP encyrpted dataset when provided with a valid encryption key.
Ideally this feature should not allow the key to be read from a filesystem, or contained in code and only support key storage in a secure key vault.
As for the key vaults that should be supported, I would suggest the following support list which would cover all of the most commonly used commercial solutions
Amazon Web Services Key Manager
Azure Key Vault
Google Cloud Platform Secret. Manager (my own needs)
Hashicorp Vault
The text was updated successfully, but these errors were encountered:
Background
When we transfer our datasets outbound from z/OS, our information security policies require that the datasets first be PGP encrypted prior to transfer.
When the datasets arrive in our large data platform, we first decrypt them and then run our Spark job. It would be a more secure solution if Cobrix were able to decrypt the data in the byte stream as opposed to decrypting the file in-situ and then running the Spark job against decrypted data
Feature
Add support to enable Cobrix to read a PGP encyrpted dataset when provided with a valid encryption key.
Ideally this feature should not allow the key to be read from a filesystem, or contained in code and only support key storage in a secure key vault.
As for the key vaults that should be supported, I would suggest the following support list which would cover all of the most commonly used commercial solutions
The text was updated successfully, but these errors were encountered: