Data Masking
Add an extra layer of security to your application data by masking action input and output data.
Add an extra layer of security to your application data by masking action input and output data.
Your workflows contain critical information such as web service account access tokens and resource IDs. It is imperative to secure this data, especially when you are working on a shared workflow. IBM webMethods Integration enables you to do this with the help of Data Masking.
Using Data Masking, you can mask the entire action input and output data as per your requirements. This masked data is then stored in the IBM webMethods Integration DB in the encrypted format and can be unmasked when required.
Let us understand how data masking and unmasking works with the help of an example.
Let’s say you have a workflow that gets the details of a card in your Trello account and sends you the file details through email.
You can mask the critical input/output data of this workflow. To do this, follow the steps given below:
This will mask the entire input object.
You can now view the action output data.
This will mask the output object of the action.
If you submit this workflow to IBM webMethods Integration recipes, the values of the masked keys will remain masked when a user imports it to an account. Similarly, if you share this workflow with other users, the values of the masked keys will remain masked.
You can unmask the masked data by following the steps given below:
This will unmask the entire input data.
Similarly, you can unmask the action output data using the Unmask All option.