Kaspersky Lab kaspersky anti-virus 5.5 for proxy server Mode D'Emploi
Operation algorithm and typical deployment scenarios
13
status defined according to the processing group parameters (please
refer to section 5.1 on p. 34 for details about groups).
refer to section 5.1 on p. 34 for details about groups).
5. If transfer is allowed, the proxy will transmit the object sent by the user.
If transfer is prohibited, Squid will not transmit the object. Instead, it will
send to the user a notification informing that the transfer has been
blocked.
send to the user a notification informing that the transfer has been
blocked.
2.2. Typical deployment scenarios
This section contains a description of two main methods available for application
deployment:
deployment:
• Application setup on the same server with Squid proxy
• Application setup on a dedicated server.
• Application setup on a dedicated server.
General guidelines described in the examples will allow you to configure the
application in accordance with your existing network structure.
application in accordance with your existing network structure.
2.2.1. Installing the application to the same
server with SQUID proxy
Further in this document we shall use this variant of Kaspersky Anti-
Virus setup (on the same server with SQUID proxy) to describe its
operation and configuration.
Virus setup (on the same server with SQUID proxy) to describe its
operation and configuration.
Application setup on the same server with Squid allows higher speed of
processing as data transfers between Squid and Kaspersky Anti-Virus occur
locally and do not involve the network. Such deployment scheme is efficient in
case of low load on the proxy server. If the proxy is used to serve a large number
of user requests, you are advised to install the application to a dedicated server
since anti-virus scanning and processing are most resource-intensive
procedures, which can therefore influence negatively the general proxy
performance. Please refer to section 2.2.2 on p. 14 for application setup on a
dedicated server. During application setup the installer automatically configures
the following aspects:
processing as data transfers between Squid and Kaspersky Anti-Virus occur
locally and do not involve the network. Such deployment scheme is efficient in
case of low load on the proxy server. If the proxy is used to serve a large number
of user requests, you are advised to install the application to a dedicated server
since anti-virus scanning and processing are most resource-intensive
procedures, which can therefore influence negatively the general proxy
performance. Please refer to section 2.2.2 on p. 14 for application setup on a
dedicated server. During application setup the installer automatically configures
the following aspects:
1. Kaspersky Anti-Virus will be set up to run automatically at the operating
system start and listen for requests from Squid proxy using port 1344 for
all network interfaces of the server.
all network interfaces of the server.
2. The following lines will be added to the ICAP OPTIONS section in the
Squid configuration file specified during application setup: