DLP queries in Ediscovery-SharePoint Online

SSN/ Credit Card/ Drivers License

 

SensitiveType:"Credit Card Number" OR SensitiveType:"U.S. Social Security Number (SSN)" OR SensitiveType:"U.S. Driver's License Number"

Criteria you need to fulfill for the sensitive type documents to be shown in ediscovery queries.

SSN:

<Entity id="a44669fe-0d48-453d-a9b1-2cc83f2cba77" patternsProximity="300" recommendedConfidence="75">

      <Pattern confidenceLevel="85">

        <IdMatch idRef="Func_ssn" />

        <Any minMatches="1">

          <Match idRef="Keyword_ssn" />

          <Match idRef="Func_us_date" />

          <Match idRef="Func_us_address" />

        </Any>

      </Pattern>

      <Pattern confidenceLevel="75">

        <IdMatch idRef="Func_unformatted_ssn" />

        <Match idRef="Keyword_ssn" />

        <Any minMatches="1">

          <Match idRef="Func_us_date" />

          <Match idRef="Func_us_address" />

        </Any>

      </Pattern>

    </Entity>

 Eg1: Formatted SSN

685-20-1398

and then enter either one of the following below in document

a. Keyword SSN

b. Valid date in format month/year eg: 09/15

c. Valid US address: it should have street, apt no, city, State and zip code

For this one the query would look something like:

SensitiveType="U.S. Social Security Number (SSN) | * | 85.."

Eg2: Unformatted SSN

 561 20 1309 or 561201309

Put Keyword SSN

 and then enter either one of the following below in document

 a.      Valid date in format month/year eg: 09/15

b.      Valid US address: it should have street, apt no, city, State and zip code.

Credit Card:

<Entity id="50842eb7-edc8-4019-85dd-5a5c1f2bb085"
patternsProximity="300" recommendedConfidence="85">
<Pattern confidenceLevel="85">
<IdMatch idRef="Func_credit_card" />
<Any minMatches="1">
<Match idRef="Keyword_cc_verification" />
<Match idRef="Keyword_cc_name" />
<Match idRef="Func_expiration_date" />
</Any>
</Pattern>
</Entity>

 

Eg:1

Note: If you put a fake 16 digit number of credit card the this is not a valid test. We have an algorithm for verifying whether a number is a valid credit card number. This is why you cannot test with random or fake 16 digit numbers—you must use a properly formatted credit card number.

**** **** **** ****

CC verification number: 273

Expiration date: 04/30/16

Drivers License:

</Pattern>

      <Pattern confidenceLevel="75">

        <IdMatch idRef="Func_washington_drivers_license_number" />

        <Match idRef="Keyword_washington_drivers_license_name" />

        <Match idRef="Keyword_us_drivers_license" />

      </Pattern>

      <Pattern confidenceLevel="65">

        <IdMatch idRef="Func_washington_drivers_license_number" />

        <Match idRef="Keyword_washington_drivers_license_name" />

        <Match idRef="Keyword_us_drivers_license_abbreviations" />

        <Any minMatches="0" maxMatches="0">

          <Match idRef="Keyword_us_drivers_license" />

        </Any>

      </Pattern>

Eg:1 (* indicates the actual Driver License number)

************

Washington Drivers license number (Replace with your state name)

 

 Eg:2

 

************

State: WA (Replace with your state name or initials)