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
Installing the kwts_upgrade_6.1.0.4762_os_security_november_2024 update package on a node with role Secondary
To install the update package on the node with role Secondary:
- Exclude the node being updated from traffic processing and distribute the load to other cluster nodes.
The method of turning off traffic to the node and then turning it back on depends on the load balancing method that is being used. For example, you can edit the configuration file of the load balancer or modify DNS records.
- Use an administrator account to sign in to the web interface of the Secondary node.
- In the upper-right corner, click the Install patch button.
- On the Install patch page, click Browse to the right of the text box.
The file selection window opens.
- Select the archive containing the update package, and click Open.
The name of the selected archive is displayed in the entry field.
- Click the Upload file button.
The Update Package Installation Wizard starts.
- Follow the instructions of the Wizard.
If restarting the node is necessary for installing the update package, wait until the restart is completed.
- Make sure the update package is successfully installed:
- Sign in to the web interface of the Control node. Make sure the status of the updated node has changed to Synchronized.
- Sign in to the updated node over SSH and run the following command:
rpm -qa openssh-server squid nginx
The output of the command must be as follows:
openssh-server-7.4p1-23.el7_9.x86_64
squid-6.12-14.kwts.el7.x86_64
nginx-1.26.1-2.el7.ngx.x86_64
- Run the following command:
tail /var/log/kaspersky/kwts/patch.log
The last line in the log must look as follows:
Upgrade finished, automatic system reboot initiated
- Restore traffic to the updated node.
The update package is installed on the Secondary node of the cluster.