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

Security Heartbeat

I have 2 servers that are continually showing up as being at Risk, the not at Risk. When I check on Sophos Central is shows nothing at Risk.

The router that reports them as being at Risk is an XG135 (SFOS 17.5.5 MR-5). A scan is run on the servers weekly. I have run additional scans on them as well.

Has anyone else had this happen ? I'm looking for some direction please

 



This thread was automatically locked due to age.
Parents
  • Hi Keith,

    What is the health status of the servers if you log into them and open up Sophos UI?  A snippet of the below two logs may help us determine why these servers are reporting themselves as at risk to the XG:

    C:\ProgramData\Sophos\Heartbeat\Logs\Heartbeat.log

    C:\ProgramData\Sophos\Health\Log\Health.log

  • Thank you for replying. The UI does not show any alerts. The 24 Malware & PUA were from a month ago. I have attached screen shots from the logs you suggested

     

     

     

     

  • Hi Keith,

    Thanks for the logs.  The heartbeat log shows the server indeed reporting its health status as bad (3) and good (1) constantly.  This looks to be a known issue development is actively working on.  I would advise raising a support case to increase visibility on this issue, to be notified of when the issue will be fixed, as well as have Sophos support's suggested workarounds.  Please include the screenshots you collected here, a set of SDU logs from the server and reference development ticket "WINEP-19248" in the case.

Reply
  • Hi Keith,

    Thanks for the logs.  The heartbeat log shows the server indeed reporting its health status as bad (3) and good (1) constantly.  This looks to be a known issue development is actively working on.  I would advise raising a support case to increase visibility on this issue, to be notified of when the issue will be fixed, as well as have Sophos support's suggested workarounds.  Please include the screenshots you collected here, a set of SDU logs from the server and reference development ticket "WINEP-19248" in the case.

Children