Operation Modes

Dr.Web for Linux can operate both in the standalone mode and as a part of an anti-virus network managed by a centralized protection server. Operation in the centralized protection mode does not require installation of additional software or Dr.Web for Linux re-installation or uninstallation.

In the standalone mode, the protected computer is not connected to an anti-virus network and its operation is managed locally. In this mode, configuration and license key files are located on local disks and Dr.Web for Linux is fully controlled from the protected computer. Updates to virus databases are received from Doctor Web update servers.

In the centralized protection mode, protection of the computer is managed by the centralized protection server. In this mode, some functions and settings of Dr.Web for Linux can be adjusted in accordance with the general (corporate) anti-virus protection policy implemented on the anti-virus network. The license key file used for operating in the centralized protection mode is received from the centralized protection server. The demo key file stored on the local computer, if any, is not used. Statistics on virus events together with information on Dr.Web for Linux operation are sent to the centralized protection server. Updates to virus databases are also received from the centralized protection server.

In the mobile mode, Dr.Web for Linux receives updates from Doctor Web update servers, but operation of the product is managed with the local settings. The license key file is received from the centralized protection server.

When Dr.Web for Linux is operating in the centralized protection mode or the mobile mode, the following options are blocked:

1.Deletion of a license key file in License Manager.

2.Manual start of an update process and adjustment of update settings.

3.Configuration of file system scanning parameters.

Configuration of SpIDer Guard settings as well as an option to enable or disable SpIDer Guard when Dr.Web for Linux is running under control of the centralized protection center is dependent on permissions specified on the server.

In the centralized protection mode, scanning of files according to a set schedule is not available.

 

Note that if launch of scanning on demand is prohibited on the centralized protection server, the page for starting scanning and Scanner button of the Dr.Web for Linux window will be disabled.

Centralized Protection Concept

Doctor Web solutions for centralized protection use client-server model (see the figure below).

Workstations and servers are protected by local anti-virus components (herein, Dr.Web for Linux) installed on them, which provides for anti-virus protection of remote computers and allows connection between the workstations and the centralized protection server.

Centralized protection server

Network based on TCP, NetBIOS

Anti-virus network administrator

Management via HTTP/HTTPS

Protected local computer

Transmitting updates via HTTP

Doctor Web update server

 

 

Figure 1. Logical structure of the Anti-virus Network

Local computers are updated and configured from the centralized protection server. The stream of instructions, data and statistics in the anti-virus network goes also through the centralized protection server. The volume of traffic between protected computers and the central server can be quite sizeable, therefore solutions provide options for traffic compression. To prevent leak of sensitive data or substitution of software downloaded onto protected computers, encryption is also supported.

All necessary updates are downloaded to the centralized protection server from Doctor Web update servers.

Local anti-virus components are configured and managed from the centralized protection server according to commands received from anti-virus network administrators. Administrators manage centralized protection servers and topology of anti-virus networks (for example, validate connections to the centralized protection server from remote computers) and configure operation of local anti-virus components when necessary.

Local anti-virus components are not compatible with anti-virus products of other companies or anti-virus solutions of Dr.Web if the latter do not support operation in the centralized protection mode (for example, Dr.Web for Linux version 5.0). Installation of two anti-virus programs on the same computer can cause a system crash and loss of important data.

Centralized protection mode allows exporting and saving Dr.Web for Linux operation reports using the centralized protection center. Reports can be exported and saved in the following formats: HTML, CSV, PDF, and XML.

Connecting to Anti-Virus Network

Dr.Web for Linux can be connected to an anti-virus network in one of the following ways:

On the Mode tab of the settings window in the Dr.Web for Linux graphical interface.

Using the esconnect command of the command-line management tool (drweb-ctl).

Disconnecting from Anti-Virus Network

Dr.Web for Linux can be disconnected to an anti-virus network in one of the following ways:

On the Mode tab of the settings window in the Dr.Web for Linux graphical interface.

Using the esdisconnect command of the command-line management tool (drweb-ctl).