Dr.Web for UNIX File Servers is a software suite consisting of a set of components, where each component has its own set of functions. The components are separated into the following categories according to their objectives:
•Basic anti-virus components that form the Dr.Web for UNIX File Servers core. In the absence of the components under this category, the product cannot scan files (and other data) for viruses and other threats.
•Threat search components. These components are used to solve Dr.Web for UNIX File Servers basic tasks—detecting threats and potentially dangerous objects. In their operation the components falling under this category use basic anti-virus components.
•Service components that complete auxiliary tasks to maintain anti-virus protection (updating anti-virus databases, connecting to centralized protection servers, managing general Dr.Web for UNIX File Servers operation and so on).
•Interface components that provide (the user or third-party applications) with the Dr.Web for UNIX File Servers management interface.
Below is the list of Dr.Web for UNIX File Servers components.
1. Basic Anti-virus Components
Component |
Description |
|---|---|
Dr.Web Virus-Finding Engine |
An anti-virus engine. Implements algorithms to detect viruses and other malware (by using signature and heuristic analyses). Managed by the Dr.Web Scanning Engine component Library file: drweb32.dll. Logged internal name: CoreEngine |
Scanning engine. This component loads Dr.Web Virus-Finding Engine and virus databases. •Passes the contents of files and boot records to the anti-virus engine for scanning. •Manages a queue of the files to be scanned. •Cures threats to which this action is applicable. Operates under the control of the Dr.Web ConfigD daemon or in standalone mode. Used by the Dr.Web File Checker and Dr.Web Network Checker components. Also can be used by the Dr.Web MeshD component (in particular modes) and by external (in relation to Dr.Web for UNIX File Servers) applications using directly the Dr.Web Scanning Engine API Executable file: drweb-se. Logged internal name: ScanEngine |
|
Virus databases |
An automatically updated database of signatures of viruses and other threats, as well as of malware detection and neutralization algorithms. Used by Dr.Web Virus-Finding Engine and is bundled with it |
A component for scanning file system objects and a quarantine manager. •Receives tasks from the threat scanning component on scanning files in the local (relative to Dr.Web Scanning Engine) file system. •Surfs the file system directories according to the task, sends files for scanning to Dr.Web Scanning Engine and notifies the client components about the scanning progress. •Deletes infected files, puts them in and restores them from quarantine, manages quarantine directories. •Builds the cache and keeps it up-to-date. The cache contains information about previously scanned files to reduce the frequency of rescanning files. Used by components that scan file system objects, such as SpIDer Guard, SpIDer Guard for SMB and SpIDer Guard for NSS Executable file: drweb-filecheck. Logged internal name: FileCheck |
|
A network data scanning agent. •Used to send data to the scanning engine for actual scanning. The data is sent by components of the product via the network (such components as Dr.Web ClamD). •Allows Dr.Web for UNIX File Servers to manage distributed file scanning: to receive/transmit files for scanning from/to remote hosts. For that purpose, remote hosts must feature an installed and running Dr.Web for UNIX operating systems. In the distributed scanning mode, it allows automatic distribution of scanning load among available hosts by reducing load on hosts with a large number of scanning tasks (for example, on mail servers and internet gateways). If the network contains partner hosts that can receive data for scanning, the components that use Dr.Web Network Checker for scanning may operate without local Dr.Web Scanning Engine. Thus, local Dr.Web Scanning Engine, Dr.Web Virus-Finding Engine and virus databases may be absent. For security reasons, files are transmitted over the network using SSL Executable file: drweb-netcheck. Logged internal name: NetCheck |
|
A component that connects Dr.Web for UNIX File Servers to a local cloud, which allows Dr.Web for UNIX products to exchange updates, results of file scanning, transmit files to each other for scanning, as well as to provide scanning engine services directly. If this component is included in the product and the local cloud to which it is connected contains hosts providing scanning engine services, local Dr.Web Scanning Engine, Dr.Web Virus-Finding Engine and virus databases may be absent Executable file: drweb-meshd. Logged internal name: MeshD |
Component |
Description |
||
|---|---|---|---|
GNU/Linux File System Monitor. Operates in background mode and controls file operations (such as creation, opening, closing, running) in GNU/Linux file systems. It sends the Dr.Web File Checker component requests to scan new or modified files as well as executables of programs when they are run. Depending on OS features, uses the fanotify system mechanism or a custom kernel module developed by the Doctor Web company (LKM is supplied with SpIDer Guard as a separate package). When the fanotify system mechanism is used, the monitor can operate in enhanced mode, blocking access to files that have not been scanned yet (of all types or executables only) until the scan is complete. By default, the enhanced monitoring mode is disabled.
Executable file: drweb-spider. Logged internal name: LinuxSpider |
|||
Linux loadable kernel module for SpIDer Guard |
Linux loadable kernel module (LKM) used by SpIDer Guard to have access to file system events in some operating systems, where fanotify API is unavailable or implemented with limited functionality. The component is distributed both as a binary (for a set of operation systems where fanotify is not implemented or is unavailable) and as source code allowing to build and install the operating system kernel module manually (for the instruction, refer to the Building kernel module for SpIDer Guard section).
Executable file: drweb.ko |
||
Samba shared directory monitor. Operates in a background mode and monitors file system operations (such as creating, opening, closing, read and write operations) in directories selected as the Samba SMB server file storages. Sends requests for scanning of new and modified files to the Dr.Web File Checker component. For integration with the file server uses VFS SMB modules that operate on the Samba server side Executable file: drweb-smbspider-daemon. Logged internal name: SMBSpider |
|||
NSS (Novell Storage Services) volume monitor. Operates in a background mode and monitors file system operations (such as creation, opening, closing and write operations) on NSS volumes mounted on the file system. Sends requests for scanning new and modified files to the Dr.Web File Checker component.
Executable file: drweb-nss. Logged internal name: NSS |
Component |
Description |
|---|---|
The Dr.Web Cloud interaction component. Sends URLs visited by the user and information about the scanned files to Dr.Web Cloud to scan them for threats not yet covered by virus databases Executable file: drweb-cloudd. Logged internal name: CloudD |
|
Dr.Web for UNIX File Servers configuration daemon. •Starts and stops other product components depending on the settings. •Restarts components if a failure in their operation occurs. Starts components at the request of other components. Informs active components when another component starts or shuts down. •Stores information about current license keys and settings and provides this information to all components. Receives adjusted settings and license keys from the designated components of Dr.Web for UNIX File Servers. Notifies other components of changes in license keys and settings Executable file: drweb-configd. Logged internal name: ConfigD |
|
The centralized protection agent. Ensures product operation in the centralized protection and mobile modes. •Provides connection between the product and the centralized protection server, receives a license key file, updates of the virus databases and anti-virus engine. •Sends the information about the Dr.Web for UNIX File Servers components, their status and statistics on threat events to the server Executable file: drweb-esagent. Logged internal name: ESAgent |
|
A component for storing Dr.Web for UNIX File Servers component operation events. Receives and stores product component events, such as unexpected shutdown, threat detection and so on. Executable file: drweb-statd. Logged internal name: StatD |
|
An updating component. Downloads updates of virus databases, the anti-virus engine from Doctor Web servers. The updates can be downloaded automatically, on schedule, and on user demand (via the Dr.Web Ctl utility or management web interface) Executable file: drweb-update. Logged internal name: Update |
Component |
Description |
|---|---|
Dr.Web for UNIX File Servers component management web server. Provides a custom HTTP API for managing Dr.Web for UNIX File Servers components. This API is used by the management web interface. For security reasons, the component uses HTTPS to connect to the management web interface. Uses Dr.Web Network Checker to send data for scanning to Dr.Web Scanning Engine Executable file: drweb-httpd. Logged internal name: HTTPD |
|
Management Web Interface. Can be accessed using any browser on a local or remote host. The management web interface enables the product not to use third-party web servers, such as Apache HTTP Server, or remote administration tools, such as Webmin. The functionality is ensured by the Dr.Web HTTPD web server |
|
A tool designed to manage Dr.Web for UNIX File Servers from the command line. Allows the user to start file scanning, view and manage quarantined objects, start a virus database update procedure, connect Dr.Web for UNIX File Servers to or disconnect it from a centralized protection server, view and change product parameters Executable file: drweb-ctl. Logged internal name: Ctl |
|
An SNMP agent. Designed for integration of Dr.Web for UNIX File Servers into external monitoring systems over SNMP. Such integration allows you to monitor the state of the product components and to collect statistics on threat detection and neutralization. Supports SNMP v2c and v3 protocols Executable file: drweb-snmpd. Logged internal name: SNMPD |
|
A component emulating the interface of the clamd anti-virus daemon (the component of the ClamAV® anti-virus). Allows all applications supporting ClamAV® to use Dr.Web for UNIX File Servers transparently for anti-virus scanning. Depending on the mode, uses Dr.Web File Checker or Dr.Web Network Checker to pass data for scanning to Dr.Web Scanning Engine Executable file: drweb-clamd. Logged internal name: ClamD |
The figure below shows the structure of Dr.Web for UNIX File Servers and its interaction with external applications.
Figure 1. The structure of Dr.Web for UNIX File Servers
In this scheme, the following notations are used:
|
—Dr.Web for UNIX File Servers as a whole and external Dr.Web applications not distributed with it |
||
|
—programs external to Dr.Web for UNIX File Servers and products that integrate with it |
||
|
—the service components that perform particular anti-virus protection tasks (updating anti-virus databases, connecting to centralized protection servers, overall coordination of operation and so on) |
||
|
—interface components that provide (the user or third party applications) with the Dr.Web for UNIX File Servers management interface |
||
|
—components used for anti-virus scanning |
||
|
—basic anti-virus components that form the Dr.Web for UNIX File Servers core. Used by the components that perform data and file scans |
Components marked with a dotted line can be absent depending on the Dr.Web for UNIX File Servers distribution or usage.
For details on Dr.Web for UNIX File Servers components, refer to Dr.Web for UNIX File Servers Components.