Manage Translate Tables

A translate table is a table of replacement values for the data that you want to disguise. First a translate table is defined. Later, when the translation technique is selected, the user chooses from a list of predefined translate tables and access paths. The Manage Translate Tables view lists the currently defined translate tables.

Each translate table must be assigned a unique name. Unique value tables are required when the access to the translate table is based on saving unique access values.

For translate to be repeatable, the rows of the translate table must be able to be read in the same order each time the translate table is processed. Therefore, when the translate table is stored in a DBMS table, a primary key is required.

The Translate Table Name is the name that appears in the list of translate tables that can be chosen for a particular rule. This name is used within the disguise rule action to request the use of a specific translate table. The disguise rule does not see the actual database table name or location, only the Translate Table Name.

All fields available from the translate table must be mapped to a label. Fields that are not mapped cannot be used by translate actions. Mapping to a label is required so that translate tables can be shared and the source of the translate table can be changed without impacting the rules that use the translate table. Before removing a label mapped to a field, be sure that no rule uses that label.

Access paths must be created for each translate table. Often translate tables contain data that will be used as replacement data for many different fields. No matter which field is being replaced, access to the table will probably be done in the same way (for example, by search or unique value). Defining the access paths as part of the translate table definition provides better control over how translate tables are accessed and eliminates the need to define the access details more than once. When the disguise rule is created, the user will select from the predefined list of access paths rather than defining all of the access details for each new rule.

Access path failed options are specified for the translate table, and all access paths created for that table use the same options. Depending on which access path is used, it is possible that no row will be returned from the translate table. For example, if the access path specifies search for a source value and the source value is not in the table, no replacement row can be returned. Access path failed options determine what to do when no replacement row is identified (not found condition) or the source value is longer than expected.

The options for source not found are to return the specified values for each field, retain the source, and apply format-preserving encryption. The default is return the value specified. If format-preserving encryption is requested, an encryption key must be selected from the list of predefined encryption keys. You can specify whether this condition is written to the execution log and whether it is counted toward the warning threshold.

A status indicator is associated with each translate rule action that denotes whether the access was successful. The status indicator can be checked by the selection conditions defined within the rule logic to execute alternative actions if the access path fails.