STAS Manual en
STAS Manual en
STAS Manual en
Authentication Suite
Quick Start Guide
Limited Warranty
No guarantee is given for the correctness of the information contained in this document.
Please send any comments or corrections to [email protected].
Contents
1 Features Overview 5
1. The user logs on to the Active Directory domain controller from any workstation in
the LAN. The domain controller authenticates the user credentials.
Note – Access is only granted for users logged onto the domain. Users who are
logged into a workstation directly (or locally) but not logged in as a domain user
will not be authenticated and are considered as “unauthenticated” users.
4. Sophos UTM queries the Active Directory domain controller to determine the
user’s group membership and registers the user in the Sophos UTM database.
5. The STAS Collector regularly polls all workstations available in its user map to
check if the same user is still logged in.
Note – For more information, see the Sophos UTM online help.
2 Prerequisites
6. Fill in the remaining fields as described in the online help of the WebAdmin console
(for help, click the "?" button).
3. Follow the on-screen instructions to install STAS on the Active Directory domain
controller.
Administrative right is required to install STAS.
Note – For installation, at least 4.1 MB of free disk space is required. The client
will not be installed, if there is not enough disk space.
Type of Setup
l Select STA Agent if you want to monitor user authentication requests on the
domain controller and send information to the Collector for authorization on
Sophos UTM.
l Select STA Collector if you just want to collect user authentication requests
from multiple agents, process the requests and send them to Sophos UTM for
authorization.
l Select SSO Suite to install both of the above components.
By default, the entire SSO Suite is installed.
7. Click Next to proceed.
8. Specify the administrators' user account.
l Specify the User Name and the Password for the user for which you want to
launch the service.
This user must have administrative rights for the machine on which you are
installing STAS.
l Click Next to proceed.
Once the installation is completed successfully, the following screen is displayed.
Installation Complete
EVENTLOG is recommended.
Note – In case of Eventlog, the agent has to be installed on the domain con
troller, in case of Netapi, the domain controller can be selected.
l WMI
l Registry Read Access
l In the section Logoff Detection Settings, enable Logoff Detection if you want
to monitor user log-offs.
If enabled, specify the Detection Method (either pinging the workstation or
polling through WMI or Registry Read Access).
If you enable Logoff Detection Settings, ensure that the firewalls on all work
stations are configured to allow traffic to and from the domain controller.
l If ping is selected as log off detection method, ensure that the work
station firewall allows ping packets.
l If WMI polling method is selected, ensure that the workstation firewall
allows traffic over UDP port 135.
l Dead Entry Timeout: Specify if you want a user to be logged off from the
Sophos UTM after the mentioned time, even when the Logoff Detection for
the users is disabled.
l In the section Application Port, specify the UDP port on which the STAS Col
lector is to listen for requests from Sophos UTM.
The default port is 6677.
l Specify the TCP port on which the STAS Collector is to listen for requests
from remote STAS Agents.
The default port is 5566.
Make sure that the AD server has TCP port 5566 open to communicate with
the STAS Collector. If the STAS Collector also runs on the AD domain con
troller, UDP port 6677 must be open to communicate with Sophos UTM.
3. Click Apply.
This list is identical with the one shown on the Global tab in the Client Authentic
ation section of Sophos UTM.
Start STAS Service
After configuring STAS on the AD server, you need to make some settings on the AD
server.
Test Connectivity
WMI Verification
To perform a successful WMI verification, access to UDP port 135 must be allowed by
the workstation firewall.
To perform a successful Registry Read verification, the remote registry service should
be started on the workstation.
To check the service:
1. Launch Run and open services.msc.
2. Select Remote Registry and make sure that the service is started.