Data Loss Prevention

 View Only
  • 1.  Symantec DLP Standard Edition 11 - Creating Custom Data Identifier

    Posted Jan 16, 2014 12:00 PM

    I'm trying to create a custom data identifier in Symantec DLP 11.1 - Standard Edition.  Does this version of Symantec DLP support custom data identifiers?  

     

    Even a very simple pattern (like '\d\d\d\d') is not working.



  • 2.  RE: Symantec DLP Standard Edition 11 - Creating Custom Data Identifier

    Broadcom Employee
    Posted Jan 16, 2014 01:33 PM

    check the logs on the agents , as i understand support for custom DIs on the agent is not there.



  • 3.  RE: Symantec DLP Standard Edition 11 - Creating Custom Data Identifier

    Posted Jan 16, 2014 01:41 PM

    Where/How would I validate this? (Sorry new to DLP)



  • 4.  RE: Symantec DLP Standard Edition 11 - Creating Custom Data Identifier

    Broadcom Employee
    Posted Jan 16, 2014 01:50 PM

    from the console,pull the agent logs . check for entries if the custom DI has been applied.



  • 5.  RE: Symantec DLP Standard Edition 11 - Creating Custom Data Identifier

    Trusted Advisor
    Posted Jan 17, 2014 03:08 PM
      |   view attached

    Hello,

    I do not believe that the DLP Standard version supports custom DI's. The Standard version is a stripped down version of the DLP platform, if you do not see the option of a "Custom Data Identifier" under the Manage section it may not be there.

    The option of the Custom Data Identifier is available in the Full Version of 11.1

    Also when doing a DI use /d{3} not /d/d/d

    Your best bet is to look at othe DI examples and try to find similar expressions.

    Attached is athe Admin guide, look to pages 460 and it will outline how to create them.

    Hope this makes sense.

    If this solves your questions please marked as solved.

    Ronak

    Attachment(s)



  • 6.  RE: Symantec DLP Standard Edition 11 - Creating Custom Data Identifier

    Posted Jan 17, 2014 03:13 PM

    Thanks for the replies.

     

    Our server just needed to be restarted for the DI to work.