Anonymizer
Most recent version: v0.0.1
Last updated
Was this helpful?
Most recent version: v0.0.1
Last updated
Was this helpful?
See the changelog of this Action type .
The Anonymizer Action modifies sensitive data to remove or mask personally identifiable information, ensuring privacy.
In order to configure this action, you must first link it to a Listener or another Action. Go to Building a Pipeline to learn how this works.
These are the input and output ports of this Action:
To open the configuration, click the Action in the canvas and select Configuration.
Enter the required parameters:
Field to anonymize*
Select an input event field to anonymize.
Anonymize Operation*
Hash Anonymizer - Choose this operation to hash any type of data and make it anonymous.
IP Anonymizer - Choose this operation if you want to encrypt IP addresses. Note that the input IP addresses must be in IPv4 format.
Salt*
Click Save to complete.
Let's say we have a list of IPs we wish to anonymize in one of our events fields. To do it:
Add the Anonymizer Action to your Pipeline and link it to your required Listener.
Now, double-click the Anonymizer Action to configure it. You need to set the following config:
Field to anonymize*
We choose the required field with the IPs to be anoymized.
Anonymize Operation*
We need the IP Anonymizer operation.
Salt*
We're adding the following salt value to make decryption more difficult: D;%yL9TS:5PalS/du874jsb3@o09'?j5
Now link the Default output port of the Action to the input port of your Data sink.
Finally, click Publish and choose which clusters you want to publish the Pipeline in.
Click Test pipeline at the top of the area and choose a specific number of events to test if your data is transformed properly. Click Debug to proceed.
This is how your data will be transformed:
A random value added to the data before it is hashed, typically used to enhance security. Note that the salt length must be 32 characters. Learn more about salt in cryptography .
