Data Loss Prevention

 View Only
  • 1.  How can i view Incidents on DLP ?

    Posted Oct 31, 2013 08:25 AM

    Hello All,

    Please i need help, my problem is :

    I create a policy and rule intervention for Endpoint, and i test it, it's OK

    But i don't see anything on Incident Endpoint.

    Please how can i put a configuration to view incident on Enforce Server.

    Thank's.



  • 2.  RE: How can i view Incidents on DLP ?

    Broadcom Employee
    Posted Oct 31, 2013 08:56 AM

    Did you log into Enforce as Administrator or other user that have the rights to review incident?

    You can review the incidents from DLP Enforce's Incidents tab.



  • 3.  RE: How can i view Incidents on DLP ?

    Posted Oct 31, 2013 08:59 AM

    Hello Mavericks SYS

     

    From a troubleshooting perspective i would check the following :

    • The endpoint is connected to the network hosting the Endpoint Server, it may be the endpoint could not send incident information over
    • The role you are logged into Enforce as has access to view Endpoint Incidents
    • You are looking at the "Endpoint" section of reports (not Network or Discover)
    • Ensure the incidents are not being filtered out by the report you are using. 

    How do you know your testing is working on the endpoint - do you get a notification / block message?

     

    Steve



  • 4.  RE: How can i view Incidents on DLP ?

    Broadcom Employee
    Posted Oct 31, 2013 09:29 AM

    can yopu see incident tab on the enforcer console?

     



  • 5.  RE: How can i view Incidents on DLP ?

    Posted Oct 31, 2013 11:39 PM

    In addition to the suggestions above, check endpoint - incidents all and see if you see the data there.  



  • 6.  RE: How can i view Incidents on DLP ?

    Posted Nov 06, 2013 01:24 PM

    You Login on Enforce with Administrator account? 

    Check the comunication between enforcer and the Endpoint client.



  • 7.  RE: How can i view Incidents on DLP ?

    Posted Nov 19, 2013 11:26 AM

    When I have problems like this, it is typically because I am changing the status on the incidents and the default status is new...