Encrypt and decrypt sensitive data in a source

[pavan]

Created by @pavan

---

This pipeline pattern will encrypt fields passed as JSON docs using a defined transform type (AES), and decrypts and gives back the original message. This pattern is useful for encrypting sensitive messages (credit card info, SSN, patients name, DOB etc).

Configuration

Within the JSON Generator, replace “Enter certificate here” with your own certificate.

Sources: JSON
Targets: JSON
Snaps used: JSON Generator, Encrypt Field, Mapper, Decrypt Field

Downloads

Encrypt & Decrypt Fields.slp (9.1 KB)

[Deepak]

@tstack

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.

[tstack]

Deepak:

Those give away key information on what stratergy is used by an organization for encryption.

The encryption algorithm in use is not a secret. You can hardcode the algorithm if you want, but it won’t increase security. In some use cases, it can make things less secure since the interface will be stuck with a single algorithm. Then, if that algorithm becomes vulnerable, it will be difficult to change while remaining backwards compatible during the transition period.

Deepak:

Also, the attributes I mentioned are key attributes required for encryption.
These are sensitive data.

No, they are not sensitive. If you don’t want to believe me, please do some of your own research.

Here is a section on IVs in Wikipedia to start:

An initialization vector has different security requirements than a key, so the IV usually does not need to be secret.