Dün 1 yıllık üyelik satın aldım fakat hiç bir şekilde vpni kullanamıyorum. Cihazımda veya internetimde bir sorun olacağını düşünmediğim için arkadaşım kendi üyeliğini benim cihazımda denedi. Hiç bir sorun teşkil etmeden çalıştı. Fakat o üyelikten çıkıp tekrar benim üyeliğime girdiğimde çalışmıyor. Hatta kendi üyeliğimde vpn açtığımda interneti hiç kullanamıyorum. Aynı internet aynı cihaz olmasına rağmen onun üyeliğinde vpn çalışıyorken benim üyeliğimde neden vpn çalışmıyor ?

Yes , You can , when configuring the task of Creating Backup of Administration Server at the destination section , please add network path . For example : //10.10.5.1/home/backup/ Regards Ahnaf Tahmeed

Декабрь 2025 - YouTube не открывается при подключении VPN от Касперского :(

Совсем перестал работать конект.Всю неделю ещё моргал серверами,то есть то нет,сейчас совсем потух.

Вы невнимательно читали, там есть ссылка. Но нет гарантий что расширение будет работать в неподдерживаемых браузерах.

Kaspersky Next EDR Expert requires 3 Bare-Metal for deploying KSC Server , KATA Server and Sandbox Server . A KATA (Kaspersky Anti-Targeted Attack Platform) deployment schema typically follows a tiered architecture designed to capture, analyze, and manage security data. Integrating it with Kaspersky Security Center (KSC) centralizes the management of the endpoint-side components. 1. KATA Deployment Schema (Components) The core architecture consists of three functional layers: Sensor Layer: Captures raw data. Network Sensors: Receive mirrored traffic (SPAN/TAP) or web/email traffic (via ICAP/SMTP). Endpoint Sensors: Lightweight agents (or built-in components of Kaspersky Endpoint Security) that send telemetry (process starts, file changes, etc.) to the Central Node. Processing Layer (Central Node & Sandbox): Central Node: The "brain" that aggregates data from all sensors and performs behavioral analysis. Sandbox: An isolated VM where suspicious files are executed to observe their behavior safely. Management Layer: The Web Interface used by security analysts for threat hunting and incident response. 2. Integration with KSC (Kaspersky Security Center) Integration with KSC is used to manage the Endpoint Sensors across your 3000+ workstations efficiently. Policy Management: You don't configure each workstation individually. Instead, you create a KATA Integration Policy in KSC. This policy tells the endpoints: Which Central Node IP/Port to send data to. Which Certificate to use for the encrypted connection. Deployment: KSC acts as the distribution point. You use KSC to push the "Kaspersky Endpoint Agent" or enable the "EDR Sensor" component within the existing Kaspersky Endpoint Security (KES) installation. Task Control: You can run remote "IOC Scans" (Indicators of Compromise) from the KSC console across all 4000 workstations simultaneously based on alerts found in KATA. License Management: KSC distributes the KATA/EDR licenses to the workstations. Summary of Traffic Flow Workstations → (Telemetry) → KATA Central Node. KSC → (Policies/Settings) → Workstations. KATA Central Node ↔ (Event/Alert sharing) ↔ KSC (Optional, for centralized dashboarding). Kaspersky Next EDR Expert and NDR License can be implemented using KATA Platfrom Regards Ahnaf Tahmeed

Да, на релизе тоже так же, а вот на бете другой вердикт. В принципе, какая разница. На TIP такие сайты не добавляют, я именно с этим вопросом обращался ранее в поддержку. То есть продукты их детектируют, а TIP нет. @andrew75 Думаю, это просто доработка в MR24, тут категория в заглушке соответствует категории из справки.

У меня он детектируется как подозрительный веб-ресурс. Возможно они поменяли тип детекта после проверки. Но на opentip он у меня зеленый.