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
Kaspersky Web Traffic Security > Hardware and software requirements
Hardware and software requirements
Hardware and software requirements
Minimum hardware requirements for servers used for installing Kaspersky Web Traffic Security
- 8 processor cores
- 16 GB RAM
- Swap partition of at least 4 GB
- 200 GB of hard drive space, which includes:
- 25 GB for temporary file storage
- 25 GB for log file storage
Minimum hardware requirements for the server hosting a hypervisor for deployment of a virtual machine ISO image
If the server has less than 1 GB of RAM or less than 100 GB of disk space, installation is canceled.
- 8 processor cores
- 16 GB RAM
- 200 GB of disk space
The software requirements below list the lowest tested versions of software products required for the installation of Kaspersky Web Traffic Security.
Software requirements for servers used for installing Kaspersky Web Traffic Security
Kaspersky Web Traffic Security can only be installed on 64-bit operating systems.
- Red Hat Enterprise Linux versions 7.7, 8.
- Ubuntu 18.04.3 LTS.
- Debian 9.11, 10.1.
- SUSE Linux Enterprise Server 15 SP1.
- CentOS version 7.7.
- ALT Server 10.
Software requirements for enterprise LAN computers
- Windows 8.1.
- Windows 10 (1809, 1903).
Software requirements for the hypervisor for deployment of the virtual machine
- VMware ESXi 6.5 Update 2 / 6.7 Update 1.
- Microsoft Hyper-V Server 2016 / 2019.
Software requirements for configuring integration with an LDAP server
- Windows Server 2012 R2 Standard.
- Windows Server 2016 Standard.
- Windows Server 2019 Standard.
Additional requirements
- Nginx versions 1.10.3, 1.12.2 and 1.14.0.
- Load Balancing HAProxy version 1.5 (not included in the distribution kit).
- Squid versions 3.5.28, 4.6, 4.7, 4.8, if you are installing the Squid service and Kaspersky Web Traffic Security on the same server.
For Kaspersky Web Traffic Security to process the traffic of your network, you must install and configure a HTTP(S) proxy server that supports ICAP and Request Modification (REQMOD) and Response Modification (RESPMOD) services. You can use a separate proxy server or, for example, install the Squid service on the server hosting Kaspersky Web Traffic Security.
Software requirements for managing Kaspersky Web Traffic Security via the web interface
To run the web interface, one of the following browsers must be installed on the computer:
- Mozilla Firefox versions 69, 70.
- Internet Explorer version 11.
- Google Chrome versions 77, 78.
- Microsoft Edge version 44 (Microsoft Edge 44.17763.1.0 for Windows 1809 and Microsoft Edge 44.18362.1.0 for Windows 1903).
|
See also Kaspersky Web Traffic Security |
Article ID: 173470, Last review: Dec 19, 2024