Help for Kaspersky Web Traffic Security
- Kaspersky Web Traffic Security
- Licensing the application
- Scaling Kaspersky Web Traffic Security
- Installation and initial configuration of the application from an RPM or DEB package
- Installation and initial configuration of the application deployed from an ISO image
- Deploying a virtual machine in the VMware ESXi Hypervisor Management Console
- Deploying a virtual machine in the VMware vSphere web interface
- Deploying a virtual machine in the Management Console of Microsoft Hyper-V Manager
- Deploying a virtual machine using Microsoft SCVMM
- Application installation and initial configuration
- Removing an application deployed from an ISO image
- Preparing to remove the application
- Removing the application from a physical server
- Removing a virtual machine in the VMware ESXi Hypervisor Management Console
- Removing a virtual machine in the VMware vSphere web interface
- Removing a virtual machine in the Microsoft Hyper-V Hypervisor Management Console
- Removing a virtual machine using Microsoft SCVMM
- Getting started with the application
- Monitoring application operation
- Reports
- Kaspersky Web Traffic Security event log
- Using traffic processing rules
- Scenario for configuring access to web resources
- Adding a bypass rule
- Adding an access rule
- Adding a protection rule
- Configuring a rule triggering initiator
- Configuring traffic filtering
- Adding an exclusion for a traffic processing rule
- Configuring the schedule of a traffic processing rule
- Modifying a traffic processing rule
- Deleting a traffic processing rule
- Creating a copy of a traffic processing rule
- Enabling and disabling a traffic processing rule
- Changing the order of applied rules
- Working with traffic processing rule groups
- Configuring a default protection policy
- Monitoring traffic processing rules
- Managing workspaces
- Working with roles and user accounts
- Managing the cluster
- Creating a new cluster
- Configuring the display of the cluster node table
- Viewing information about a cluster node
- Adding a node to a cluster
- Modifying node settings
- Removing a node from a cluster
- Changing the role of a node in a cluster
- Deleting the cluster
- Checking data integrity
- Connecting to cluster nodes over the SSH protocol
- Restarting a cluster node
- Application operation in emergency mode
- Protecting network traffic
- ICAP server settings
- Block page
- Exporting and importing settings
- Upgrading the application from version 6.0 to version 6.1
- Installing update packages
- Installing the kwts_upgrade_6.1.0.4762_os_security_november_2024 update package
- Configuring the server time
- Configuring proxy server connection settings
- Updating Kaspersky Web Traffic Security databases
- Participating in Kaspersky Security Network and using Kaspersky Private Security Network
- Connecting to a LDAP server
- Configuring integration with Kaspersky Anti Targeted Attack Platform
- Syslog event log
- Application management over the SNMP protocol
- Single Sign-On authentication
- Managing the settings of a built-in proxy server in the application web interface
- Decrypting TLS/SSL connections
- Processing CONNECT requests
- About TLS connections
- Managing certificates for intercepting SSL connections
- Enabling and disabling decryption of SSL connections
- Selecting the default action for SSL connections
- Managing SSL rules
- Managing trusted certificates
- Sources of information about the application
- Publishing application events to a SIEM system
- Contacting the Technical Support
- Appendix 1. Installing and configuring the Squid service
- Appendix 2. Configuring integration of the Squid service with Active Directory
- Configuring Kerberos authentication
- Configuring NTLM authentication
- Installing the Samba service
- Configuring time synchronization
- Configuring DNS
- Configuring Samba on the server hosting the Squid service
- Checking Samba settings on the server hosting the Squid service
- Configuring the Squid service
- Configuring the client side of NTLM authentication
- Configuring NTLM authentication of a host that is not in a domain
- Configuring Basic authentication
- Appendix 3. Configuring ICAP balancing using HAProxy
- Appendix 4. MIME types of objects
- Appendix 5. URL normalization
- Appendix 6. Website categories
- Appendix 7. Physical processor core bandwidth values depending on the type of proxy server and the required protection level
- Appendix 8. Virtual processor bandwidth values depending on the type of proxy server and the required protection level
- Glossary
- Access rule
- Basic authentication
- Bypass rule
- Certificate fingerprint
- Cluster
- Directory service
- Heuristic analysis
- ICAP server
- Kaspersky Private Security Network
- Kaspersky Security Network (KSN)
- Kerberos authentication
- Keytab file
- Layout
- LDAP
- License serial number
- Malicious links
- MIB (Management Information Base)
- nginx service
- Node with role Control
- Node with role Secondary
- Normalization
- NTLM authentication
- Phishing
- Protection rule
- PTR record
- Replay cache
- Reputation filtering
- SELinux (Security-Enhanced Linux)
- Service principal name (SPN)
- SIEM system
- SNI (Server Name Indication)
- SNMP agent
- SNMP trap
- Squid
- SRV record
- SSL Bumping
- Syslog
- TLS encryption
- Tracing
- Traffic processing rule
- Update source
- Virus
- Workspace
- AO Kaspersky Lab
- Information about third-party code
- Trademark notices
Requirements for RAM and hard drive capacity on a server hosting Kaspersky Web Traffic Security
The server requirements for RAM and hard drive capacity are determined based on the node performance value derived from the estimated hardware requirements (see the table below).
Server RAM and hard drive capacity
Node performance, Mbps |
RAM, GB |
Hard drive capacity, GB |
RAID type |
Minimum spin rate of the disk subsystem of the hypervisor or physical server, revolutions/min |
Maximum cache size, GB (only for a Standalone installation) |
Maximum size of Syslog event log files, GB (only for a Standalone installation) |
0–90 |
16 |
200 |
— |
7200 |
3 |
15 |
90–180 |
22 |
250 |
— |
7200 |
6 |
35 |
180–270 |
28 |
300 |
— |
10,000 |
9 |
60 |
270–360 |
34 |
350 |
— |
10,000 |
12 |
90 |
360–450 |
40 |
400 |
— |
10,000 |
15 |
120 |
450–540 |
46 |
450 |
10 |
10,000 |
18 |
150 |
540–630 |
52 |
500 |
10 |
10,000 |
21 |
180 |
630–720 |
58 |
550 |
10 |
10,000 |
24 |
210 |
720–810 |
64 |
600 |
10 |
10,000 |
27 |
230 |
The hard drive capacity indicated in the table is applicable if the drive is partitioned into a root partition and a swap partition corresponding to the amount of available RAM.
If you are using Kaspersky Web Traffic Security (Standalone), prior to running a virus scan, the application saves the contents of all transmitted files to the /tmp folder. To reduce the load on the disk subsystem, you can do one of the following:
- Migrate the folder to the tmpfs file system.
- Configure the settings for caching disk write operations.
It is recommended to use the following values for the caching settings:
- vm.dirty_bytes = <maximum cache size>.
The value for the maximum cache size is provided in the table above. It is specified in bytes.
- vm.dirty_background_bytes = 80% of the vm.dirty_bytes parameter value.
- vm.dirty_expire_centisecs = 18000.
- vm.dirty_bytes = <maximum cache size>.
You can enable logging of traffic processing events, system events of the application, and Kaspersky Anti Targeted Attack Platform server file transfer events to a Syslog event log. If you are using Kaspersky Web Traffic Security (Standalone), when enabling logging you need to do the following on the operating system side:
- Configure logging of event details to a separate file.
- Configure rules for rotating log files (logrotate).
The value for the maximum size of log files is provided in the table above.
- Disable the limit for the system log write frequency (rate limits).
- Configure logging of events via rsyslog, bypassing journald.