Component |
Description |
|---|---|
Dr.Web Server Security Suite component management web server. Provides a custom HTTP API for managing Dr.Web Server Security Suite 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 |
|
Tool designed to manage Dr.Web Server Security Suite 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 Server Security Suite to or disconnect it from a centralized protection server, view and change product parameters Executable file: drweb-ctl. Logged internal name: Ctl |
|
SNMP agent. Designed for integration of Dr.Web Server Security Suite 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 |
|
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 Server Security Suite 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 Server Security Suite and its interaction with external applications.
Figure 1. The structure of Dr.Web Server Security Suite
In this scheme, the following notations are used:
|
Dr.Web Server Security Suite as a whole and external Dr.Web applications not distributed with it |
||
|
Programs external to Dr.Web Server Security Suite and products that integrate with it |
||
|
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 Server Security Suite management interface |
||
|
Components used for anti-virus scanning |
||
|
Basic anti-virus components that form the Dr.Web Server Security Suite 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 Server Security Suite distribution or usage.
For details on Dr.Web Server Security Suite components, refer to Dr.Web Server Security Suite Components.