Data Masking

You can use data masking to clear or replace sensitive data like locations, service providers, and contacts with fictitious data. Data masking is available when exporting planning data via the Export Planning Data page.

On the Export Planning Data page, the Apply Data Masking check box points to a Data Masking Definition ID of BASIC which uses the data masking options of CLEAR and HASH. These options do the following:

• CLEAR: Set to null. For example, clear the name of a location
• HASH: Uses SHA-224 hash algorithm to provide one-way data compression. The result can't be decrypted or associated with the original data.

During export, data masking mode masks and subsets the data in near real-time while extracting the data from a database. The extracted masked and subsetted data is written to the CSV files created during the export process.

During import, the masked data is imported into OTM. So you will see masked values when using contacts, locations, etc. in OTM. See the full list of masked data below.

The PUBLIC data masking definition of BASIC does the following:

Sets the following fields to NULL via the CLEAR masking format:

Data in the following fields is removed or nulled out.

• CONTACT
  • ALTERNATE_NAME
  • CELL_PHONE
  • COMPANY_NAME
  • DESCRIPTION
  • EMAIL_ADDRESS
  • FAX
  • FIRST_NAME
  • JOB_TITLE
  • LAST_NAME
  • NOTES
  • PHONE1
  • PHONE2
  • TELEX
• LOCATION
  • DESCRIPTION
  • LOCATION_NAME

Sets the following to HASH masking format

The following GIDs and XIDs are encrypted:

• CONTACT_GID and CONTACT_XID
• SERVPROV_GID and SERVPROV_XID
• LOCATION_GID and LOCATION_XID

All foreign key (FK) references, such as SOURCE_LOCATION_GID and DEST_LOCATION_GID, are also encrypted.

Note: If you choose to apply data masking, you should try to avoid those masked columns in saved queries. For example, location "ABC" could be masked as "DEF".  If your saved query searches locations by "ABC", it would return nothing.