User Community Service Desk Downloads
If you can't find the product or version you're looking for, visit support.ataccama.com/downloads

Protegrity Integration

Protegrity is a robust data security platform that enhances data protection via tokenization and encryption techniques. Protegrity Application Protector for Java lets you use the Protegrity protection and unprotection functions to secure your sensitive data and ensure compliance with regulations like GDPR and PCI-DSS.

This guide explains how to integrate Protegrity Application Protector for Java with ONE Runtime for secure data handling. This way, Protegrity Application Protector can be applied in ONE Desktop, MDM, or the Runtime Server.

Overview

The integration of Protegrity with ONE workflows allows you to:

  • Easily protect sensitive data elements.

  • Meet regulatory requirements for data privacy and security, helping you comply with relevant regulations.

  • Reduce exposure to sensitive data through tokenization, hashing, encryption, and masking.

Tokenization is the process of substituting sensitive data with non-sensitive placeholders called tokens. These tokens can be reverted back to their original values using the right permissions and tools, to ensure that sensitive data is not exposed during regular operations.

Prerequisites

To be able to use Protegrity in ONE Desktop, MDM, or the Runtime Server:

  1. Install and configure Protegrity Application Protector for Java if you don’t have it already. For instructions, refer to the official Protegrity resources: Protegrity Training.

  2. In the Protegrity Application Protector installation folder, make sure you have access to the following files:

    • ApplicationProtectorJava.jar

    • ApplicationProtectorJava.properties

      On Linux, the default installation location is /opt/protegrity/applicationprotector/java/lib.

  3. Copy the ApplicationProtectorJava.jar and ApplicationProtectorJava.properties`files to the `runtime/lib directory in your ONE Desktop or Runtime Server installation folder, depending on where you intend to use Protegrity.

  4. In addition, ensure the files copied to the runtime/lib directory have the correct permissions so your runtime engine can access them.

How to use Protegrity with ONE

You can now use Protegrity’s tokenization functions to protect and unprotect your sensitive data. Add the following functions to your expressions:

  • coding.protect(user, dataElementName, input)

  • coding.unprotect(user, dataElementName, input)

The parameters you need to provide are as follows:

  • user: The username defined in the Protegrity policy.

  • dataElementName: The data element defined in the Protegrity policy, corresponding to the specific data type (for example, SSN or Credit Card Number).

    Choose a data element appropriate for the type of data that will be protected (for example, for SSN, this could be de_TokSSN, for a credit card number, de_TokCCN).

    The element must already be configured in Protegrity. Once a data element is used for protection, the same one must be used for unprotection.
  • input: The value to protect or unprotect.

Test the integration

You can check whether your runtime server can access the Protegrity libraries by running a test job that uses the coding.protect() function.

Query example

+

coding.protect('user1', 'de_TokCCN', '1111-1111-1111-1111');

If an issue occurs, look for possible solutions in Troubleshooting.

Troubleshooting

Some common issues during integration can typically be resolved using the following solutions.

Missing libraries error

If you get a Protegrity Application Protector JAR not present error, check whether both ApplicationProtectorJava.jar and ApplicationProtectorJava.properties are correctly placed in the relevant runtime/lib directory, as described in Prerequisites.

Initialization error

In case of a Protegrity Application Protector initialization error error, verify that the configuration in the ApplicationProtectorJava.properties file is correct (for example, check whether you have correctly provided parameters such as hostnames and data elements).

For further details about advanced configuration or debugging issues, refer to the Protegrity official resources: Protegrity Training.

Was this page useful?