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
Appendix 2. Configuring integration of the Squid service with Active Directory > Configuring Kerberos authentication > Configuring time synchronization
Configuring time synchronization
Configuring time synchronization
To configure time synchronization with NTP servers:
- Install the chrony package. To do so, run one of the following commands depending on the utilized operating system:
- CentOS or Red Hat Enterprise Linux:
yum install -y chrony
- SUSE Linux Enterprise Server:
zypper install chrony
- Ubuntu, Debian, or ALT Server:
apt-get install chrony
- CentOS or Red Hat Enterprise Linux:
- Enable autostart of the chronyd service. To do so, run one of the following commands depending on the utilized operating system:
- Ubuntu, Debian, or ALT Server:
systemctl enable chrony
- Other operating systems:
systemctl enable chronyd
- Ubuntu, Debian, or ALT Server:
- Depending on the operating system, open one of the following files:
- CentOS, Red Hat Enterprise Linux or SUSE Linux Enterprise Server:
/etc/chrony.conf
- Debian, Ubuntu, or ALT Server:
/etc/chrony/chrony.conf
- CentOS, Red Hat Enterprise Linux or SUSE Linux Enterprise Server:
- Add strings with the IP addresses of those NTP servers with which you want to configure time synchronization. For example:
server <IP address of the NTP server> iburst
- Comment the strings beginning with the word pool or server that have the IP addresses of those NTP servers that you do not want to use for time synchronization (to "comment" means to add the # character at the beginning of the string).
- If you are using a Windows domain controller for time synchronization, add the following string:
maxdistance 16.0
- Save and close the /etc/chrony.conf file.
- Restart the chronyd service. To do so, run one of the following commands depending on the utilized operating system:
- Ubuntu, Debian, or ALT Server:
systemctl restart chrony
- Other operating systems:
systemctl restart chronyd
- Ubuntu, Debian, or ALT Server:
- Verify the time synchronization. To do so, execute the command:
chronyc sources -v
If the displayed IP addresses match the addresses of the NTP servers that you specified in the chrony.conf file, synchronization was correctly configured.
Time synchronization between the Squid server and NTP servers will be configured.
Article ID: 166343, Last review: Dec 19, 2024