Guest User!

You are not Sophos Staff.

Thread Info
  • Locked Locked
  • Replies 32 replies
  • Subscribers 23 subscribers
  • Views 70914 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

HitmanPro.Alert 3.6.9 Causes Exploit Detection Non Compliance

Shane Clark

After Sophos updated the version of HitmanProAlert  to version 3.6.9, All of my PC's are getting Exploit Detection Non Compliant alerts. After exactly two hours in this state they then go into compliance for 30 minutes and then repeat this process. Sophos Support says its an issue where the HitmanPro service is shutting down before the Management Communication System Service which is causing the trigger. They have yet to figure out how to fix this issue. Is anyone else seeing this issue? Does anyone have any suggestions of how to fix?



This thread was automatically locked due to age.
Parents

  • Thanks Dustin Garden! for the update.

    On Wednesday I noticed that an update come though updating the version of the The Core agent/Endpoint Advanced from 11.5.6 to 11.5.9 around 12:00PM.  We are still getting the error in the Event logs of all our systems but at least Alerts are not regenerating creating 100's and 100's of alerts in the console over and over for the same systems.

    -Graham

  • in reply to Graham Parenteau

    From the KB:

    "We are aware of the disruption this can cause for customers who have affected endpoints, we have now identified the cause of the issue for Central Customers and are testing the fix in our own environment before release. Sophos expects all Central customers to have the update by the 17th November 2017"

    So you at least have an ETA on the fix. Now I'm wondering what to tell my SEC customers:

    "The same issue exists for SEC managed endpoints but addressing that issue is more complicated. We are targeting a release to SEC managed endpoints in Q1 2018."

    I'm really not a happy camper right now. Sophos QA is leaving much to be desired lately...

    Regards,

    Giovani

Reply
  • in reply to Graham Parenteau

    From the KB:

    "We are aware of the disruption this can cause for customers who have affected endpoints, we have now identified the cause of the issue for Central Customers and are testing the fix in our own environment before release. Sophos expects all Central customers to have the update by the 17th November 2017"

    So you at least have an ETA on the fix. Now I'm wondering what to tell my SEC customers:

    "The same issue exists for SEC managed endpoints but addressing that issue is more complicated. We are targeting a release to SEC managed endpoints in Q1 2018."

    I'm really not a happy camper right now. Sophos QA is leaving much to be desired lately...

    Regards,

    Giovani

Children
No Data
Unfiltered HTML