Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 1 subscriber
  • Views 1268 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

HIPS detecting / alerting when disabled

chavez243

A large division of our business is software development, unfortunately a good sum of executables created by the dev team is detected by HIPS as suspicious behaviour - usually IP/Connect type. The onslaught of alerts to the IT team and the endless pop-ups have prompted us to disable HIPS for that division. Despite that and verifying that all Policies are in effect for that particular group, they still get the HIPS detections.

Any ideas why that might be?

:29581


This thread was automatically locked due to age.
Parents
  • 0

    Hello chavez234,

    when the state changes from Awaiting... To Same as policy you can be quite sure the policy is in effect. 

    As for the recurring alert - any chance that this particular client has "traveled back in time" (e.g. it's a VM which has been reset)?

    Christian

    :29589
Reply
  • 0

    Hello chavez234,

    when the state changes from Awaiting... To Same as policy you can be quite sure the policy is in effect. 

    As for the recurring alert - any chance that this particular client has "traveled back in time" (e.g. it's a VM which has been reset)?

    Christian

    :29589
Children
No Data