Thread Info
  • State Verified Answer
  • +2 person also asked this people also asked this
  • Locked Locked
  • Replies 1 reply
  • Subscribers 28 subscribers
  • Views 1054 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

Action required for Sophos Authentication for Thin Clients (SATC)

M8ey

So got this today:

 

You are receiving this email as you have been identified as utilizing Sophos Authentication for Thin Clients (SATC). If you use Mozilla Firefox as your default browser, there is no action required.

Version 84 of Google Chrome and other Chromium-based browsers are expected to be released on July 14, 2020 which removes a feature required to ensure compatibility with SATC. This will prevent SATC and XG Firewall authentication from correctly identifying the user associated with web browsing traffic from Chrome, resulting in incorrect policies and web traffic reporting.

 

Seriously - Firefox is the work around?

How about fix SATC so it works irrespective of browser. I have enough trouble with STAS with out SATC as well... :-(



This thread was automatically locked due to age.
Parents
  • +2

    Hi M8ey,

    SATC works by intercepting outbound connections as they are about to start on the network, and sending information to the firewall so that it can recognise the connection on its way out, and assign it to the correct user.

    To provide a similar functionality to SATC that is compatible with Chrome, as well as Chromium Edge, we need to fundamentally change the way that we intercept network traffic within the Windows operating system stack. As you might imagine, this is not something we can do lightly - it's not a simple bug fix.

    Sophos Central Server protection products (e.g. Intercept-X) already do network interception at the right point, for malicious traffic detection. We have therefore taken the decision to integrate the SATC identification functionality into this product. When configured appropriately, every time it intercepts a connection for MTD, it will also send an identification message to the Firewall just like SATC did.

    Work is already well advanced in doing this and we hope to include it in Server Protection early in 2021.

Reply
  • +2

    Hi M8ey,

    SATC works by intercepting outbound connections as they are about to start on the network, and sending information to the firewall so that it can recognise the connection on its way out, and assign it to the correct user.

    To provide a similar functionality to SATC that is compatible with Chrome, as well as Chromium Edge, we need to fundamentally change the way that we intercept network traffic within the Windows operating system stack. As you might imagine, this is not something we can do lightly - it's not a simple bug fix.

    Sophos Central Server protection products (e.g. Intercept-X) already do network interception at the right point, for malicious traffic detection. We have therefore taken the decision to integrate the SATC identification functionality into this product. When configured appropriately, every time it intercepts a connection for MTD, it will also send an identification message to the Firewall just like SATC did.

    Work is already well advanced in doing this and we hope to include it in Server Protection early in 2021.

Children
No Data