Index Data for an EDM
The DLP indexer creates irreversible fingerprints of critical data structured in records with a consistent format and uploads them to Secure Access to establish a custom EDM Identifier. EDM Identifiers enable Secure Access to protect sensitive data by using data fingerprinting techniques as opposed to pattern matching techniques.
EDM Identifiers can be added to a Data Classification (see Manage Data Classifications) as custom identifiers; DLP rules that use these identifiers can monitor and/or block files that match the data you have indexed.
You need to run the DLP indexer in two different circumstances:
- When you initially create an EDM Identifier, you run the indexer on the data set you want to detect. This topic provides basic information for running the indexer, but for a description of the process to use the indexer within the context of creating an EDM Identifier, see Create an Exact Data Match Identifier. You cannot use the indexer to create an EDM Identifier without also performing the steps described in that topic.
- When the data set to be detected changes, you run the indexer to produce an updated version of the EDM Identifier. This process is described in Update the Indexed Data Set Periodically.
NOTE: To see a summary of the indexer options available, invoke the indexer with the -h option. (java -jar <directory-path>\dlp-indexer.jar -h.)