WebSocket

WAF Connected — What Next? How to Configure Web Application Firewalls for Real Protection Without Disruption

After successful pilot testing, organizations often struggle when scaling WAF protection across dozens or hundreds of applications. Each app brings unique technology stacks, traffic patterns, and legitimate anomalies that can break existing rules. The article stresses starting in monitoring mode rather than blocking to avoid false positives that frustrate users and damage business operations. A structured Risk Score and Priority Score system helps teams prioritize applications based on exposure, business impact, control weaknesses, technical risks, and data sensitivity. Regular tuning, log analysis, and quarterly re-evaluation of the application registry are required because applications evolve constantly. Well-configured WAF solutions must deliver low false-positive rates, rapid exception handling, and resilience under peak loads without creating new operational burdens for security teams.

Telegram Desktop Adds WEB Proxy to Hide MTProxy Traffic Inside HTTPS and WebSocket Connections

Telegram Desktop has received an initial implementation of a new WEB proxy designed to conceal messenger connections within ordinary HTTPS and WebSocket traffic. The feature makes user activity appear as simple website browsing to network providers while MTProxy continues to operate underneath. Developers inserted more than 3,000 lines of code, including a dedicated WEB-proxy transport, domain configuration options, and interface elements such as “Open browser” and “Waiting for browser.” The mechanism works by opening an embedded web page that establishes a secure WebSocket link to a domain resembling a regular site. Multiple MTProxy connections are multiplexed into a single stream and sent through this channel. On the server side an intermediate node demultiplexes the stream and forwards the individual connections to a standard MTProxy instance without decrypting message content.