The component is designed to check both content of files in the local file system and streams of data transmitted by a client application via socket. Such checks are performed by the component at a client application request. Moreover, the component can check content of files for which an open descriptor was transmitted via the socket. If a client application transmitted only a file path, the component sends the scanning task to the component of file checking Dr.Web File Checker; otherwise, the component transmits data, received via the socket, to network scanning agent Dr.Web Network Checker, as shown in the picture below.
Picture 46. Component operation scheme
By default, the component is not automatically run upon Dr.Web for UNIX File Servers startup. To enable starting of the component, it is necessary to set Yes value for the Start parameter and define at least one connection point for client applications. After that, the component starts waiting for external application requests to scan files or data streams. In the component settings, you can configure several connection points for client applications and adjust different scan settings for each of the points, if required.
|
Detected threats cannot be neutralized by Dr.Web for UNIX File Servers; the client application receives only scan results. Thus, a detected threat should be neutralized by a client application. |
