Data Loss Prevention

 View Only
  • 1.  DLP policy exception/exclusion

    Posted Jan 09, 2017 03:22 PM

    I am trying to figure out how to reduce false positives and am hoping that someone could give me some advice.

    I want to add a "NOT" operator to a rule (x AND y AND NOT z)

    I.e. Rule: content matches "foo" AND content matches "bilbo" w/5 "gandalf" AND NOT content matches "foo.com"

     

    The rule and exceptions as they read are not paired together, so the logic can't be as granular.

    RULES (content matches "foo" AND content matches "bilbo" w/5 "gandalf")

    EXCEPTIONS ( content matches "foo.com")

     

    If I could use an AND NOT operator within a rule I could get around this limitation. Am I wrong? Is there anyway to be more selective?

     

    As an explanation, I'm trying to find out when client data (confidential) is emailed to an external domain that is not in the client's domain list. That means that I have to use client name terms matched with confidential terms with a group recipient exception for the client's domain names. The excessive false positives occur where some of the terms are included in valid communications that fall outside of the client's domain. This happens because the confidential or client name terms are too common, but without classification metadata fields the content tends to be pretty nebulous.

     

     

     



  • 2.  RE: DLP policy exception/exclusion

    Posted Jan 10, 2017 02:14 AM
    You can use a regular expression rule utilising negative lookahead/lookbehind statements to allow "AND NOT". For example look for "confidential" only of its not in a paragraph (looking for confidential in header/footer) could be something like; (?i)confidential(?!\s\w+) Match only if confidential isnt followed by a whitespace then words.


  • 3.  RE: DLP policy exception/exclusion

    Posted Jan 10, 2017 12:47 PM

    Thanks for the reply. I'll see if this will cover what I need.