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
Upgrading the application from version 6.0 to version 6.1
The standard upgrade procedure is currently unavailable for Kaspersky Web Traffic Security.
To upgrade the application on one server, you must remove application version 6.0 and install application version 6.1.
To upgrade a cluster with application version 6.0 (referred to as "cluster 6.0") to a cluster with application version 6.1 (referred to as "cluster 6.1"), you must complete the following scenario:
- Removing the first server from cluster 6.0
It is recommended to begin the cluster upgrade by removing the Secondary master server. Then you can install the node with role Control of cluster 6.1 on this server.
- Removing application version 6.0
- Installation and initial configuration of application version 6.1
You can install the application from a DEB or RPM package or from an ISO file.
- Creating cluster 6.1
When a new cluster is created, the Control node role will be assigned to the server.
- Exporting the settings of cluster 6.0
- Importing the settings to cluster 6.1
After importing the configuration file, the node with role Control will relay the new settings to all cluster nodes.
The settings that are not indicated in the configuration file will remain unchanged.
- Migrating Worker servers to cluster 6.1
You must complete the following steps for each Worker server:
- Assigning traffic processing to a different server of the cluster.
To ensure that traffic processing is not interrupted during an upgrade, it is recommended to switch traffic processing to a different cluster server in advance. If a load balancer is being used in the cluster, you need to open its configuration file and delete the entry containing the settings of the Worker server being upgraded.
- Removing a Worker server from cluster 6.0.
- Removing application 6.0 from a Worker server.
- Installation and initial configuration of application version 6.1.
You can install the application from a DEB or RPM package or from an ISO file.
- Adding a node to cluster 6.1.
After a node is added to cluster 6.1, the Secondary node role will be assigned to the node. It will automatically receive the up-to-date settings from the node with role Control.
- Configuring traffic processing.
If a load balancer is being used in the cluster, you need to open its configuration file and add an entry containing the settings of the new node with role Secondary.
- Assigning traffic processing to a different server of the cluster.
- Removing the Master server from cluster 6.0
After migrating Worker servers to cluster 6.1, only the Master server will remain in cluster 6.0. You can either take this server out of operation or add it to cluster 6.1 as a node with role Secondary (see steps 7.3–7.6).