Office365 Sensitive Information Types

ChrisHoardMVP
MVP
Jan 28, 2019
Hi Sean,

Thanks - I read it as is it as opposed to it is!

I have raised a uservoice for you on the GUI.

https://office365.uservoice.com/forums/289138-office-365-security-compliance/suggestions/36648940-custom-sensitive-information-type-allow-minimum

I am going to raise this to the Sec and Compliance Microsoft Team to see if we can get an answer -

Ryan Heffernan - see above string from Sean. With regards custom sensitive information types how do we specify a minimum count for a regex defined in the xml? It would be great to get an answer on this.

Best, Chris
- Adam Jung
  Former Employee
  Jan 30, 2019
  Posting this on behalf of the DLP product team:
  
  In custom sensitive type is defined by patterns with 2 elements – idMatch and Match. Both these elements could take Regex, Keyword or Dictionary or built-in functions.
  
  There are key differences between idMatch and Match.
  
  idMatch –enables detecting the sensitive content in document (like a credit card number)
  
  match – enables detection of supporting evidence in the proximity of idMatch (like words like “CVV”, “Credit Card”, “VISA” etc..,)
  
  Min Matches
  
  For a match element, min match count allows setting requirement to minimum number of supporting evidence to found to match pattern. As mentioned match could be a keyword list or a Regex.
  
  Single match of idMatch along with required matches will identify a sensitive content found in document. In DLP Policy, the customer could configure the min and max number of sensitive type (like Credit cards) required to be found.
- Ryan Heffernan
  Microsoft
  Jan 28, 2019
  Adding Caroline Shin and Anthony Smith (A.J.). Can either of you speak to this question?

Forum Discussion

Resources