Forum Discussion
@pavan Once encrypted, do I need to pass all the information onward? Is it a security risk to do so?
ENC {
"transformation":"AES/CBC/PKCS5Padding",
"iv":"[MYIV]",
"type":"STRING",
"ciphertext":"[MYCIPHERTEXT==]",
"key_params": {
"passphrase": {
"key_gen_iterations":10000,
"key_gen_algorithm":"[ALGORITHM]",
"key_algorithm":"AES",
"key_salt":"[SALTKEY]",
"key_size":128
}
}
}:ENC
Yes, the information is needed to correctly decrypt the ciphertext.
No, it’s okay to send the IV in the clear and the rest of the information is used to configure the decryption process.
- Deepak7 years agoNew Contributor II
@tstack I have a similar scenario. Please read through the steps.
- We are using Encryption & Decryption in 2 seperate ultra pipelines, where first pipeline would encrypt the password field and send this data to second pipeline & the second pipeline would decrypt the data and use it.
- The problem is we are giving away key information like Type Of Algorithm, IV, Key_SALT over the internet along with the Ciphertext which is a security concern.
- Our design has to have 2 seperate ultra pipelines & not pipeline execute as its an architectural decision.
How can we achieve decrypting the field, without giving away these key attributes?
- tstack7 years agoFormer Employee
These values are not secrets, so I don’t think there should be a problem.
Can I ask what is driving the decision to not use PipeExec?
- Deepak7 years agoNew Contributor II
Those give away key information on what stratergy is used by an organization for encryption. Also, the attributes I mentioned are key attributes required for encryption.
These are sensitive data.Pipeline exec vs Iltra ppipeline decision would take this chain in a different direction. Let’s consider the fact that we need to utilize this Ultra pipelines.