SATC replacement - Server Endpoint

Hi,

no, we're not using AD SSO on any Zone.

Most firewall rules match known AD Users.

I can see the user is authenticated on XG from that server. But when I try hit some firewall rule by communicating with other machines in other subnets, it's not working because the user is not bound to the traffic as can bee seen in the live logging.

Currently, I cannot access any internal targets that require user authentication from that SATC Sercer.

Web rules are working though. Nothing else... What's that?

I'm not aware of a feature "Match unknown users" - can you explain this?

I wonder how Ryan Partington got this all working at the customer? Or do they need the TS only for surfing? Or don't they have user-based rules on the XG for internal servers?

I'm not sure I follow all of the above, but essentially:

Customer just connects to RDC from the internet using published apps, and then we use SATC to filter OUTBOUND HTTP(s) web requests and apply the appropriate filtering.

The RDC server has a number of applications on the session host that all work fine (outlook, etc.) and when they come to use the published browser, it just makes sure they can't get on stuff they shouldn't be able to.

OK, that explains, why they probably did'nt notice issues as long as they have Webfiltering in Intercept-X disabled.

Would be nice to know if they could access some other internal destination from that Server that have user authentication required on the firewall rule.

As far as i know, all traffic should be covered by Server Protection, and not only Web based. But you need to difference between traffic generated by the server itself and by a session. If you RDP to a session, can you do a SSH and it gets filtered by the firewall rule accordingly? 

So: 

This is rule 6. 

RDP Session to the server.

proto=tcp proto-no=6 timeout=102 state=SYN_SENT orig-src=192.168.1.5 orig-dst=172.17.1.2 orig-sport=7484 orig-dport=3390 packets=3 bytes=152 [UNREPLIED] reply-src=172.17.1.2 reply-dst=192.168.1.5 reply-sport=3390 reply-dport=7484 packets=0 bytes=0 mark=0x0 use=1 id=1974529064 masterid=0 devin=PortA devout=xfrm1 nseid=50334781 ips=1 sslvpnid=0 webfltid=1 appfltid=1 icapid=0 policytype=2 fwid=6 natid=0 fw_action=1 bwid=0 appid=0 appcatid=0 hbappid=10097 hbappcatid=0 dpioffload=0 sigoffload=0 inzone=1 outzone=5 devinindex=6 devoutindex=34 hb_src=0 hb_dst=0 flags0=0x100008000a20000a flags1=0xb1020a00800 flagvalues=1,3,21,25,27,43,60,75,85,87,93,100,104,105,107 catid=0 user=12 luserid=5 usergp=32 hotspotuserid=0 hotspotid=0 dst_mac=00:0d:3a:22:81:b5 src_mac=fc:bd:67:7b:9d:51 startstamp=1637165173 microflow[0]=INVALID microflow[1]=INVALID hostrev[0]=0 hostrev[1]=0 ipspid=0 diffserv=0 loindex=34 tlsruleid=0 ips_nfqueue=1 sess_verdict=0 gwoff=0 cluster_node=0 current_state[0]=17498 current_state[1]=0 vlan_id=0 inmark=0x0 brinindex=0 sessionid=9248 sessionidrev=9721 session_update_rev=4 dnat_done=0 upclass=0:0 dnclass=0:0 pbrid[0]=0 pbrid[1]=0 profileid[0]=0 profileid[1]=0 nhop_id[0]=65535 nhop_id[1]=65535 nhop_rev[0]=0 nhop_rev[1]=0 conn_fp_id=NOT_OFFLOADED

Just a random connection is mapped to fwid=6

But what you have to do: You should create a HTTPs Connection in the first place and get the user authenticated. 

BTW: 

SATC Replacement does not work with Clientless user. If you have the TS as a clientless server, you need to delete the clientless user on SFOS. 

LuCar Toni said:

SATC Replacement does not work with Clientless user. If you have the TS as a clientless server, you need to delete the clientless user on SFOS. 

can you please explain this? According to the KBs I've read, we need to enable SATC via Registry parameters on the Terminalserver

And on the XG

system auth thin-client add citrix-ip xxx.xxx.xxx.xxx (TS IP Address)

.

I performed an other test with Windows Server 2019 as TS:

Whenever I log on to the Terminalserver, Port 80 and 443 Packets appear with Userauthentication on the XG.

For this test I put the Terminalserver 2019 into the Client LAN where we have User authentication working against XG from Windows 10 clients.

All other packets: CIFS, DNS, LDAP, are without user.

I have also checked this from an other 2019 server which is not configured as Terminalserver and does'nt have the EAP Client installed. It is acting the same - so no user autentication is arriving at the FW.

tested also SSH (putty): different:  I can see the Source IP, and the User.

You can have a look at this Log File. Here you can see the Connection to User/SessionID relation which the Endpoint sends to the Firewall.

"C:\ProgramData\Sophos\Sophos Network Threat Protection\Logs\SntpService.log"

In my setup I have skipped the local Users like SYSTEM and NETWORK SERVICE etc... via registry key (SatcExcludedUsers) and saw that after skipping these users will not longer be logged in that Sntp.Service.log file.

But when I scroll up in this log in the time while this local users where not skipped, I can see:

- SYSTEM user had a lot of smb/445 entries

- NETWORK SERVICE user had a lot of dns/53 entries

I am not an expert in SATC, I dont know even how it works 100%. But I assme that some traffic you want to authenticate against a specific AD-User is "generated" by one of the system users and thats your problem.

Other applications like your SSH test is binded to your AD-User Session ID and thats the reason why you can see that information in XG Log.

thank you! I#m just in the process of writing all this together and saw your post - will add the SntpService.log - one less question from support I hope. Currently I have not excluded the system users and see them on the XG logs.

to add some more information here:

found this in the XG access server log

XG430_WP02_SFOS 18.0.6 MR-6-Build655# cat access_server.log | grep terminalserver_IP
ERROR     Nov 25 12:37:25.138360 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-1
ERROR     Nov 25 12:37:29.327584 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-2
ERROR     Nov 25 12:37:31.582105 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-2
ERROR     Nov 25 12:44:01.917202 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-4
ERROR     Nov 25 12:45:06.811953 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-1
ERROR     Nov 25 12:48:05.351970 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-1
ERROR     Nov 25 12:53:07.561911 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-1
ERROR     Nov 25 12:55:08.716986 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-5
ERROR     Nov 25 12:55:09.000721 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-3
ERROR     Nov 25 12:55:14.879696 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-3
ERROR     Nov 25 12:55:14.881768 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-3
ERROR     Nov 25 13:05:03.447016 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-1
ERROR     Nov 25 13:07:08.460984 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-2
ERROR     Nov 25 13:07:08.641793 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-2
ERROR     Nov 25 13:07:08.914866 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-1
ERROR     Nov 25 13:09:04.314358 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-2
ERROR     Nov 25 13:12:14.403464 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-2
ERROR     Nov 25 13:18:08.124805 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-2
ERROR     Nov 25 13:18:09.364701 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-4
ERROR     Nov 25 13:19:13.509368 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-2
ERROR     Nov 25 13:41:37.547174 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-2
ERROR     Nov 25 13:41:38.926125 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-2
ERROR     Nov 25 14:12:14.932129 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-2
ERROR     Nov 25 14:16:09.756777 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-1
ERROR     Nov 25 14:22:18.354221 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-1
ERROR     Nov 25 14:31:29.488805 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-1
ERROR     Nov 25 14:34:26.402013 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-4
ERROR     Nov 25 14:34:27.945061 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-2
ERROR     Nov 25 14:34:27.947143 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-2
ERROR     Nov 25 14:37:50.705532 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-2
ERROR     Nov 25 14:51:16.886054 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-1
ERROR     Nov 25 14:51:16.893019 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-1
ERROR     Nov 25 14:51:48.939470 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-1
ERROR     Nov 25 14:51:48.942277 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-1
ERROR     Nov 25 14:51:48.948203 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-1
ERROR     Nov 25 14:51:48.975657 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-1
ERROR     Nov 25 14:51:48.984067 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-1
ERROR     Nov 25 14:53:40.980600 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-1
ERROR     Nov 25 14:54:46.488496 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-1
ERROR     Nov 25 15:00:33.272375 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-1
ERROR     Nov 25 15:12:21.256203 [access_server]: (process_citrix_login_request): An identical SATC request is being processed at the moment, canceling the current request from terminalserver_IP-1