Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 28 subscribers
  • Views 3368 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

Started using Synchronized User ID. It works for my clients, but not servers?

JohnHilton

Hi all,

 

I Started using Synchronized User ID and all the client users are listed as "Heartbeat" awesome!

However, we also use server protection and it seems that the authentication of the users aren't working.

Its a domain account not a local account i'm testing, sam and upn match as per the documentation, and the account work fine on a "client" OS rather than a "Server" OS.

I've concluded that it's something to do with the endpoint heartbeats on the server platforms.

I've made sure that the "Heartbeat" is enabled in sophos central for the servers also.

The client Endpoint version is as follows:

Core:2.2.2

Endpoint Advanced:10.8.3

Sophos InterceptX:2.0.12

The server endpoint versions are as follow:

Server Core:2.1.3

Server Anti-Virus:10.8.2

Server InterceptX:2.0.4

 

I'm forced to use the client auth agent at the moment which i wasn't expecting to.

 

Is this all by design or have i done something wrong?

 

We've remove STAS and no longer want to use it.

 

Thanks all.



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

    STAS is kinda the Same like Heartbeat.

    So STAS works "Partly" for Servers. 

    The point is, we read all the user information from the workstation. And most of the time, on a server, there is no logged in user. 

     

    This is not implemented in Server right now. 

  • 0 in reply to LuCar Toni

    Thanks for your speedy reply.

    I will have to re enable to tuse of STAS for the time being then.

    Is there a ETA for this functionality to be added to servers?

  • 0 in reply to JohnHilton

    The Point is. What should be included in the Server Protection?

    As mentioned before, most of the time, synchronized User ID (Like STAS) is not the best use case for server.

    It is kinda in a concept phase, how to handle a server. 

  • 0 in reply to LuCar Toni

    What is Sophos' recommended option to authenticate the domain admin accounts and internet based services on the servers?

    STAS

    Heartbeat

    Client Auth

     

    Thanks again

  • 0 in reply to LuCar Toni

    Heartbeat on a server should track interactive user logins and the window stations + sessions associated with it.

    Then the Heartbeat can track users/processes on the server, and help allow multiple policies to be applied for Users on Remote Desktop servers.

  • 0 in reply to ChrisKnight

    So you want to have STAS / SATC combined into the Endpoint? 

    This is kinda more than a simple Hearteat User ID. 

  • 0 in reply to LuCar Toni

    Well if the goal is synchronised security, then the EndPoints (including mobile) need to increasingly send more granular information to Edge devices (on-premise or hosted/cloud), so appropriate policy can be applied.

    This means simplistic assumptions of one user per device need to be discarded and user tracking sent from the EndPoint to the Edge device.

    This then allows for per-user policy to be applied on Remote Desktop servers and handling of guest users on devices (e.g. Android mobile/tablet/Chromebooks).

    I'd be very surprised if this isn't already on a roadmap somewhere. If not it should be.

    But if you're talking about other features that should be present in a server, then I have a shopping list that would be best suited for another thread.

Reply
  • 0 in reply to LuCar Toni

    Well if the goal is synchronised security, then the EndPoints (including mobile) need to increasingly send more granular information to Edge devices (on-premise or hosted/cloud), so appropriate policy can be applied.

    This means simplistic assumptions of one user per device need to be discarded and user tracking sent from the EndPoint to the Edge device.

    This then allows for per-user policy to be applied on Remote Desktop servers and handling of guest users on devices (e.g. Android mobile/tablet/Chromebooks).

    I'd be very surprised if this isn't already on a roadmap somewhere. If not it should be.

    But if you're talking about other features that should be present in a server, then I have a shopping list that would be best suited for another thread.

Children
No Data