icon-zia.svg
Secure Internet and SaaS Access (ZIA)

Creating an Exact Data Match Template

Watch a video on Exact Data Match.

Using the Index Tool you can create, modify, or delete an Exact Data Match (EDM) index template.

Creating an EDM Template

To create a new EDM template:

  1. Go to https://<IP Address of the Index Tool VM> to access the Index Tool. Log in to the Index Tool with your ZIA Admin Portal login credentials.
  2. In the Exact Data Match Templates dashboard, click Create New Template.
  3. In the New Exact Data Match Template window:
    1. Type in a Template Name. After the template is saved, this name appears in Administration > Index Templates within the ZIA Admin Portal.
    2. Drag and drop a comma-separated values (.csv) file into the window or click Browse to select a file.
    3. Click Next.
  4. Define the fields you want to include in the template:
    1. From the drop-down menu, select a DATA TYPE for the field.

Be sure to select the type that best matches your data. For example, a field named SSN with sample data from the United States in the format of 123-45-6789 might need the Social Security Number (US) type applied, not Numeric. Also, for all data types, the Index Tool removes leading and trailing spaces in the data after you submit.

The following data types and formats are supported:

  • Supported FormatExamples
    An India-issued 12-digit unique identification (UID) number, where the number can include spaces or hyphens.
    • 1234-5678-9012
    • 123456789012
    • 1234 5678 9012
    Close
  • Supported FormatExamples
    A 9 digit ABA Bank routing number.
    • 211274450
    Close
  • Supported FormatExamples
    Any combination of letters (a-z, A-Z). Including hyphens and underscores as character delimiters is supported. You must make sure that the data includes at least 3 characters. If you select this data type as a PRIMARY FIELD, the data cannot be longer than 24 characters.
    • abcdZSa
    • abcd-ZSa
    • abcd_ZS_a
    Close
  • Supported FormatExamples
    Any combination of digits (0-9) or letters (a-z, A-Z). Including hyphens and underscores as character delimiters is supported. You must make sure that the data includes at least 3 characters. If you select this data type as a PRIMARY FIELD, the data can include up to 8 separate variable lengths and cannot be longer than 24 characters.
    • Z8675309
    • a8675309-ZS
    • a_8675309_ZS
    Close
  • Supported FormatExamples
    A Netherlands-issued 9-digit citizen service number (BSN), where the number can include spaces or hyphens.
    • 111222333
    • 111 222 333
    • 111-222-333
    Close
  • Supported FormatExamples
    A Japan-issued 13-digit Corporate Number, where the first digit is a checksum number.
    • 7288275758478
    • 6854046373053
    • 3952116402622
    Close
  • Supported FormatExamples
    Without popular format check: A 13 to 19-digit credit, debit, or payment card number, where the number can include spaces or hyphens. The Index Tool performs a Luhn check on the data after you submit.
    • 4929597154872802715
    • 4539 0864 8005 0690
    • 4539-0864-8005-0690
    • 378413854542304
    With popular format check: The popular format for a credit card number is a range from 12-19 numeric digits separated periodically by a delimiter (slash, period, hyphen, or space). If the number is not in the popular format, it will not be supported.
    • AMEX (15 digits)
      • NNNN<delimiter>NNNNNN<delimiter>NNNNN
    • Diner's Club (14 digits)
      • NNNN<delimiter>NNNNNN<delimiter>NNNN
    • China UnionPay (16 digits beginning with 62 or 60)
      • 62NNNNNNNNNNNNN
      • 62NNNNNNNNNNNNNNNNN
    • Maestro Debit Card (16–19 digits starting with 50, 56, 57, 58, 6013, 62, 63, or 67)
      • 50NN-NNNN-NNNN
      • 6013 NNNN NNNN
    • Other Credit Cards (16 digits)
      • NNNN<delimiter>NNNN<delimiter>NNNN<delimiter>NNNN
      • NNNN NNNN NNNN NNNN
    Close
  • Supported FormatExamples

    Any date using the format of MMDDYYYY or DDMMYYYY where:

    • MM: Is the 2-digit month (01-12)
    • DD: Is the 2-digit day (01-31)
    • YYYY: Is the 4-digit year (0000-3000)

    Including spaces, hyphens, and forward slashes as character delimiters is supported.

    • 02231999
    • 23021999
    • 02-23-1999
    • 02 23 1999
    • 02/23/1999
    Close
  • Supported FormatExamples
    Any email address using the RFC 5321 Simple Mail Transfer Protocol syntax definition. However, international email addresses (i.e., characters using UTF-8 encoding) are not supported.
    • jane.doe@zscaler.com
    • jdoe47@corp.zscaler.com
    • a.b.c@x.y.ru
    • a_b_c@x.y.z.de
    Close
  • Supported FormatExamples

    A China-issued 17 or 18-digit Resident Identity Card number using the format of ######YYYYMMDD000@, where:

    • ######: Is a 6-digit number
    • YYYY: Is the 4-digit year
    • MM: Is the 2-digit month (01-12)
    • DD: Is the 2digit day (01-31)
    • 000: Is a 3-digit number
    • @: Is a checksum number or the letter X
    • 110108197008056644
    • 11010819700805880X
    Close
  • Supported FormatExamples

    A Malaysia-issued 12-digit national identity card (MyKad) number using the format of YYMMDD-##-000@, where:

    • YY: Is the 2-digit year
    • MM: Is the 2-digit month (01-12)
    • DD: Is the 2-digit day (01-31)
    • ##: Is a 2-digit number (0-99, excluding 17-20, 69-70, 73, 80-81, 94-97)
    • 000: Is a 3-digit number
    • @: Is a 1-digit number (0-9)

    Including spaces and hyphens as character delimiters is supported.

    • 991111113456
    • 991111-11-3456
    • 991111 11 3456
    Close
  • Supported FormatExamples

    A Poland-issued 11-digit national identification number (PESEL) using the format of YYMMDD####@, where:

    • YY: Is the 2-digit year
    • MM: Is the 2-digit month.
      • For people born between 1900 and 1999 (01-12)
      • For people born between 2000 and 2099 (21-32)
    • DD: Is the 2-digit day (01-31)
    • ####: Is a 4-digit number
    • @: Is a checksum number
    • 84011201654
    • 42251488383
    Close
  • Supported FormatExamples
    A Thailand-issued national identity card number using a 12-digit number and the 13th digit is a checksum. Including hyphens and underscores as character delimiters is supported.
    • 3-7377-29920-32-6
    • 3_7377_29920_32_6
    Close
  • Supported FormatExamples
    A Brazil-issued 11 digit Individual Taxpayer Registry ID number (CPF). The popular format for CPF numbers is "ddd.ddd.ddd-dd". Since '.' (dot) is an EDM numeric delimiter a CPF number in the format "401.757.431-93" does not match.
    • 40175743193
    Close
  • Supported FormatExamples
    An Australia-issued 10-digit Medicare number, where the first digit is from 2 to 6 and the ninth digit is a checksum. Including spaces and hyphens as character delimiters is supported.
    • 2123 45670 1
    • 2123-45670-1
    Close
  • Supported FormatExamples

    Any combination of a maximum of 4 alphanumeric character groupings. The character groupings can include any combination of digits (0-9), letters (a-z, A-Z), and special characters, and each character grouping must include at least three alphanumeric characters.

    When you upload data, strings are normalized and a match occurs only if all of the data appears in the same order as the normalized character grouping. For example, if the following strings are sent:

    • "123 Bob Anne Smith aaas" will match.
    • "Bob 123 Anne Smith aaaa" will not match.
    • "123 Anne Bob Smith aaaa" will not match.
    • "Bob 12 Anne Smith aaaa" will match because "12" is too short and is ignored.
    • "Bob + Anne Smith" will match.

    A field with this data type can be selected as a primary field for a template.

    • Bob Anne Smith
    • 1234 Smith Street, San Jose
    Close
  • Supported FormatExamples

    Any combination of a maximum of 4 alphanumeric character groupings. The character groupings can include any combination of digits (0-9), letters (a-z, A-Z), and special characters, and each character grouping must include at least three alphanumeric characters.

    A field with this data type cannot be selected as a primary field for a template.

    Zscaler recommends the use of the Multi-alphanumeric Identity data type instead of this data type. This data type does not follow the order of the indexed string. A match can happen even if the data does not appear in the same order.

    • Bob Anne Smith
    • 1234 Smith Street, San Jose
    • 123 Gary-Carter Street, Quebec
    Close
  • Supported FormatExamples

    Any combination of a maximum of 4 words and three spaces (e.g., personal names, city names, entity names).

    A field with this data type cannot be selected as a primary field for a template.

    • San Francisco
    • General Motors Company
    • Bob Smith
    • Mary Joe Fernandez James
    Close
  • Supported FormatExamples
    A Japan-issued 12-digit My Number (also known as Individual Number), where the last digit is a checksum number. Including hyphens, spaces, and ‘.’ (dot) as delimiters is supported.
    • 675616148173
    • 6756-1614-8173
    • 6756 1614 8173
    • 6756.1614.8173
    Close
  • Supported FormatExamples

    A Uruguay-issued Document ID number using the format, 7-digit number followed by a validation number where:

    • The validation number is calculated by multiplying the 7-digit number, digit by digit, by 8123476. For example if the 7-digit number is 1.234.567, <1,2,3,4,5,6,7>.<8,1,2,3,4,7,6>=1∗8+2∗1+3∗2+4∗3+5∗4+6∗7+7∗6=132132mod10=2
    • 1.234.567-2
    Close
  • Supported FormatExamples
    A 10 digit United Kingdom-issued National Health Service (NHS).
    • 3256728308
    Close
  • Supported FormatExamples
    A Taiwan-issued national identification card number using one prefix letter (A-Z, excluding L, R, S, Y), one digit (1 or 2), an 8-digit number, and the ninth digit is a checksum.
    • M140051654
    Close
  • Supported FormatExamples
    A Chile-issued national identity card number (RUN) using the format of an 8-digit number followed by a verification digit where the digit is either a number or the letter K.
    • 76086428-5
    • 22060449-K
    Close
  • Supported FormatExamples

    A France-issued national identification number (INSEE code) using the format of 0YYMM######## @@, where:

    • 0: Is a 1-digit number (1 or 2)
    • YY: Is the 2-digit year
    • MM: Is the 2-digit month (01-12)
    • ########: Is a 8-digit number
    • @@: Is a 2-digit checksum

    Including spaces and hyphens as character delimiters is supported.

    • 1801269552223 80
    • 1801269552223-80
    Close
  • Supported FormatExamples
    A Peru-issued national identity card number (CUI) using an 8-digit number followed by a verification digit.
    • 25465832-5
    Close
  • Supported FormatExamples
    A Spain-issued national identity card number (DNI) using an 8-digit number and one letter representing the checksum (a-z, A-Z, excluding i, o, u, I, O, U).
    • 45592283G
    • 25621992s
    Close
  • Supported FormatExamples
    A United Kingdom-issued insurance number using two prefix letters (a-z, A-Z), six digits (0-9), and one suffix letter. Including hyphens and underscores as character delimiters is supported.
    • AB-123456-C
    • AB_123456_C
    • AB123456C
    Close
  • Supported FormatExamples

    A Singapore-issued NRIC number/FIN using the format of #0000000@, where:

    • #: Is a letter that can be S, T, F, or G
    • 0000000: - Is a 7-digit number
    • @: Is a checksum letter calculated with respect to # and 0000000

    Including hyphens and underscores as character delimiters is supported.

    • S-1234567-A
    • T-1234567-B
    Close
  • Supported FormatExamples
    Any combination of digits (0-9). Including spaces and hyphens as character delimiters is supported. You must make sure that the data includes at least 3 characters. If you select this data type as a PRIMARY FIELD, the data can include up to 8 separate variable lengths and cannot be longer than 24 characters.
    • 212-867-5309
    • 86 7 530 9
    Close
  • Supported FormatExamples

    A South Korea-issued resident registration number using the format of YYMMDD-######@, where:

    • YY: Is the 2-digit year
    • MM: Is the 2-digit month (01-12)
    • DD: Is the 2-digit day (01-31)
    • ######: Is a 6-digit number
    • @: Is a checksum

    Including spaces and hyphens as character delimiters is supported.

    • 800821-6490697
    • 800821 6490697
    Close
  • Supported FormatExamples
    Without popular format check: A Canada-issued 9-digit social security number, where the number can include spaces or hyphens.
    • 123-456-789
    • 123456789
    With popular format check: A 9-digit number separated at the 3rd and 6th digit by a delimiter (period, hyphen, or space) or not separated at all. If the number is not in the popular format, it will not be supported.
    • 123-456-789
    • 123 456 789
    • 123.456.789
    • 123456789
    Close
  • Supported FormatExamples

    A Spain-issued 12-digit social security number using the format of ##00000000@@, where:

    • ##: Is a 2-digit number (01-50, 53, 66)
    • 00000000: Is a 8-digit number
    • @@: Is a 2-digit checksum

    Including hyphens, spaces, and ‘.’ (dot) as character delimiters is supported.

    • 281234567840
    • 28-12345678-40
    • 28 12345678 40
    • 28.12345678.40
    Close
  • Supported FormatExamples
    A Switzerland-issued 13-digit social security number (AHV), where the first three digits are 756 and the 13th digit is a checksum. The popular format for the AHV number is “756.dddd.dddd.dd”. Including ‘.’ (dot) as character delimiters is supported.
    • 756.2022.6001.16
    • 7562022600116
    Close
  • Supported FormatExamples
    A United States-issued 9-digit social security number, where the number can include spaces or hyphens.
    • 123-45-6789
    • 123 45 6789
    • 123456789
    With popular format check: A 9-digit number separated in parts by a delimiter (hyphen or space) or not separated at all. If the number is not in the popular format, it will not be supported.
    • 123 45 6789
    • 123-45-6789
    • 123456789
    Close
  • Supported FormatExamples
    A Mexico-issued 18 digit Standardized Bank Code (CLABE) number.
    • 102211123456789015
    Close
  • Supported FormatExamples
    An Australia-issued 8 or 9-digit tax file number, where the number can include spaces or hyphens.
    • 123-456-789
    • 123 456 789
    • 1234567-8
    Close
  • Supported FormatExamples
    An Indonesian-issued 15-digit tax identification number (NPWP), where the 9th digit is a checksum. The popular format for the tax identification number is “dd.ddd.ddd.d-ddd.ddd”. Including ‘.’ (dot) and hyphens as character delimiters is supported.
    • 021832415123456
    • 02.183.241.5-123.456
    Close
  1. Select the INCLUDE FIELD IN TEMPLATE checkbox.
  2. Select the PRIMARY FIELD checkbox for the field that you want to designate as the primary criteria for data matching.

You must select at least one primary field, and no more than two. Also, the primary field must be unique for the selected data type.

You can configure EDM to function without primary or secondary fields. To learn more, see Configuring DLP Advanced Settings.

  1. Click Submit.

You are redirected back to the Exact Data Match Templates dashboard, and the tool processes the template. If the template was created properly, Completed is shown in the Status column. If the template was not created properly, then Error is shown.

Click on the template row to view the Template Details page. If an error occurred, details about the error are displayed. Be sure to read the Error Detail, which includes a Recommended Action, while troubleshooting the issue.

When an EDM template is created, it appears on the Index Templates page of the ZIA Admin Portal, where you can view the template's details or delete it. You cannot change the template name after creation. Also, after creation, you cannot update the included fields or the selected primary fields within the template. In order to make these modifications, you must create a new template.

Submitting New EDM Template Data

To submit new data for an EDM template:

  1. Log in to the Index Tool.
  2. In the Exact Data Match Templates dashboard, locate the template you want to modify.
  3. In the Actions column:
    • If you need to resubmit data for a template that was processed successfully (i.e., has a Completed status), click the Submit New Data icon. The data types, included fields, and primary fields you originally selected for the template are not updated. You must create a new template to modify the data types and selected fields.
    • If you need to resubmit data for a template that did not process successfully (i.e., has an Error status), click the Submit New Data icon or click the Edit Template icon. The ability to edit a template only becomes available if there was an error when you originally submitted the data. If you edit a template, you are able to modify the data types and selected fields to resolve the issue.

You can also click on the template row and, in the Template Details page that appears, click Submit New Data or Edit Template (if available).

The selected included fields and primary fields you originally selected for the template are not updated. You must create a new template to modify fields.

  1. In the Upload File window that appears, drag and drop the .csv file into the window or click Browse to select the file.
  2. Click Submit.

Scheduling Updates for an EDM

After you have successfully uploaded your template, you can schedule regular updates. You can also choose to receive an Alert if there are any missed updates.

To schedule regular updates for your EDM Template:

  1. Log in to the Index Tool.
  2. In the Exact Data Match Templates dashboard, locate the template you want to schedule updates for.
  3. Perform one of the following actions:
  • In the Actions column, click the Schedule icon.
  • Click on the template row. The Template Details page appears. In this window, click Create Schedule.
  1. In the Schedule Template Update window, select the following:
    1. File Path: The file path is automatically populated with the location that you uploaded your file to. Ensure that the file is still at this location.
    2. Status: Select whether to Enable or Disable your schedule
    3. Repeat: Choose if the update repeats Monthly, Weekly, or Daily.
    4. Every: If you selected Monthly or Weekly, choose when in the selected period the update repeats. For example, if you selected Weekly, you can choose to have the update happen every Friday.

If you select Monthly, index updates are converted to, and trigger in UTC. It is possible that after being converted, your update may occur between the 29th and 31st UTC. If a month doesn't contain the converted date, that update is skipped.

For example, if you schedule your update to occur on the 28th of every month at 5:00 PM PST, it does not trigger in February since the UTC time is already 1:00 AM February 29 and that date does not exist (excluding leap years). If you schedule your update to occur on the first of every month at 8:00 AM IST, it also does not happen every month. As the UTC time is 3:00 AM on the 31st, it does not occur in February, April, June, September, or November.

Zscaler recommends you schedule your monthly updates to occur between the 2nd and the 27th.

  1. At: Choose what time the scheduled update happens on.
  2. Time Zone: Select the time zone your update happens in.
  3. Update Now: Select to immediately update the template.
  4. Click Save.

To edit your schedule:

  1. Log in to the Index Tool.
  2. In the Exact Data Match Templates dashboard, locate the template whose schedule you want to edit.
  3. Perform one of the following actions:
  • In the Actions column, click the Schedule icon. The Schedule Index Update window appears.
  • Click on the template row. The Template Details page appears. Click Edit Schedule. The Schedule Index Update window appears.
  1. Make your desired changes and click Save.

To delete your schedule:

  1. Log in to the Index Tool.
  2. In the Exact Data Match Templates dashboard, locate the template whose schedule you want to delete.
  3. Perform one of the following actions:
  • In the Actions column, click the Schedule icon. The Schedule Index Update window appears.
  • Click on the template row. The Template Details page appears. Click Edit Schedule. The Schedule Index Update window appears.
  1. In the Schedule Index Update window, click Delete in the lower right-hand corner.

To temporarily disable your schedule, set the status to Disable.

Deleting an EDM Template

To delete an EDM template, do one of the following sets of steps:

  • Delete from the Exact Data Match Templates Dashboard
  1. Log in to the Index Tool.
  2. In the Exact Data Match Templates dashboard, locate the template you want to remove.
  3. In the Actions column, click the Delete icon.

You can also click on the template row and, in the Template Details page, click Delete Template.

  1. In the confirmation window that appears, click Delete.
  • Delete from the Index Templates
  1. Go to Administration > Index Templates.
  2. Locate the template you want to remove and click the View icon.
  3. In the View Template window, click Delete.
  4. In the confirmation window that appears, click Confirm.
Related Articles
About Exact Data MatchUnderstanding Exact Data Match Index TemplatesCreating an Exact Data Match TemplateDefining Exact Data Match Fields for Custom DLP Dictionaries