What is a one sentence summary of your feature request?
Enable support for HTTP/3 (QUIC) in the Netwrix Cloud Agent for all communications with the Netwrix 1Secure SaaS platform endpoints via Azure Front Door
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
Currently, the Netwrix Cloud Agent communicates with 1Secure using HTTP/1.1 or HTTP/2 over traditional TCP transport. This approach can sometimes result in higher connection establishment times and poor responsiveness over unreliable or high-latency networks, such as those with high packet loss rates. TCP-based protocols also suffer from head-of-line blocking and can be less resilient to changing network conditions, for example, if a device’s IP changes during a connection.
Why HTTP/3 is the Best Solution:
Reduced Latency and Faster Handshakes: HTTP/3 (running over QUIC) significantly reduces connection establishment time due to its combined handshake process, which is particularly beneficial for frequent, short-lived agent-to-cloud communications.
Improved Reliability: QUIC is more resilient to packet loss and network changes (e.g., roaming between different networks or changing IPs). This would make cloud agent connectivity more robust, especially in environments with less stable internet connections.
No Head-of-Line Blocking: QUIC’s stream multiplexing prevents slowdowns caused by packet loss in one stream affecting the others, yielding better performance when syncing or sending telemetry.
State-of-the-Art Security: QUIC uses modern encryption (TLS 1.3) by default, aligning with best practices.
Future-Readiness: By supporting HTTP/3, the platform demonstrates ongoing commitment to modern web standards and can accommodate future enhancements from Azure and the broader ecosystem.
In summary, adding support for HTTP/3 to the Netwrix Cloud Agent will increase performance, reliability, and security for users—especially those with challenging network environments—by taking advantage of the capabilities already available in Azure Front Door and modern HTTP standards.
How do you currently solve the challenges you have by not having this feature?
Currently, we rely on HTTP/1.1 or HTTP/2 over TCP for all communications between the Netwrix Cloud Agent and the cloud platform.