Skip to main content

User Guide

Creating SecureLink Jobs

In addition to the SecureLink Environments, two Jobs are required, corresponding to the contributor and recipient parts of the SecureLink process.

The process is summarized as follows:

  1. Contributor: This Job uses the SecureLink Encryption Rule to encrypt direct identifiers in input data. These Jobs can be run through Batch, Data Flow or Privitar On Demand. The Job references the appropriate SecureLink destination environment in its configuration.

  2. Recipient: This Job uses the SecureLink Tokenization Rule to convert the encrypted direct identifiers produced by the contributor into tokenized identifiers. These Jobs can only be run through Privitar On Demand (not Batch or Data Flow).

Together, these steps implement the SecureLink process.

UUID-39afd9e3-f17d-85fc-46cc-24d1a20f5550.png

The following sections describe how to configure Jobs for the two steps.

Contributor Jobs

Contributor Jobs produce encrypted ciphertext from raw direct identifiers. This is performed by a SecureLink Encryption Rule. The Policy for this Job must include this Rule.

  1. Create a SecureLink Encryption Rule. For more information, see Using the Rules Library.

  2. Create a Policy. For more information, see Creating a Policy.

    In the Policy, ensure that the SecureLink Encryption Rule is applied to the direct identifier field. For more information, see Setting a Masking Rule.

  3. Create a Batch, Data Flow or Privitar On Demand Job, referencing the Policy created earlier. For more information, see What is a Job?.

    Note

    Ensure that the SecureLink destination Environment is set correctly on the contributor's Job.

  4. Running this Job will produce output containing encrypted identifiers suitable for use with a recipient Job.

Recipient Jobs

Recipient Jobs consume encrypted output from a Contributor Job, and produce tokenized linkable identifiers. This is performed by a SecureLink Tokenization Rule. The Policy for this Job must include this Rule.

  1. Create a SecureLink Tokenization Rule. For more information, see Using the Rules Library.

    The Rule includes a regular expression option that determines the format of the linkable identifier. As with other tokenization rules, output from this Rule will be random, but consistent within a PDD.

  2. Create a Policy. For more information, see Creating a Policy.

    In the Policy, ensure that the SecureLink Tokenization Rule is applied to the field containing the encrypted value.

  3. Create a Data Flow Job, referencing the Policy created above. For more information, see What is a Job?.

Running this Job will produce output containing linkable tokenized identifiers.

In this section: