eScan Blog
eScan Website
eScan Forum
eScan Feeds From eScan Wiki
Roaming Clients
Roaming Clients submodule provides protection for the remote endpoints when not connected to the organization network, adding another layer of security. According to the needs of the business, admins might want to continue the protection of roaming client on the organization network. Using this feature admin can provide protection for such clients connected to both organization network and also to internet via cloud.
This feature is quite helpful for the remote clients. Apart from it, it does not require any additional machine set up apart from the (on-premise) EPS Server in the network. All the communication is handled by the EPS Server via Cloud to the client having stable internet connection.
Here, the remote clients will update their status, download the latest configuration from the EPS Server via Cloud.
This service allows admin to apply policies to the client from EPS Server. All events from the clients such as Application Control Scan, Vulnerability Scan, Virus Scan, etc. are collected and managed on EPS server via Cloud Platform.
Adding Roaming Client
To add roaming client, it is mandatory to connect to the Cloud Platform. Follow the below steps, to do the same:
- Go to Settings > Roaming Clients.
- Enter the company name and email address.
- Click on Generate Secret Code.
A secret security code will be generated and sent to given email address. - Enter the secret code received via email, click on Connect to cloud platform.
- A confirmation window appears. Click on OK, this will authenticate and allows to connect to Cloud Platform.
An information window appears. - After connecting to the cloud platform successfully, you can manually enable and disable the roaming service.
- Click on Download Roaming Client Setup to download the setup file. Install the set up file in the client system to make it as roaming client and it should be connected to the internet.
|
NOTE |
eScan Server should be able to communicate to eScan Cloud Server. To allow communication, make sure the following URL and port is allowed under Gateway Security device. |
