TCP Connections

The Unica DiscoverNetwork Capture Application requires to monitor the start of all TCP connections. If TCP persistent connections are enabled, then the DNCA is able to reassemble hits from in-progress connections.

Please check with your IT team to see whether TCP persistent connections is enabled in the IT infrastructure. Individual TCP persistent connections can be used by multiple visitors to your web application. It can also be deployed by a load balancer such as an F5 network device, a front-end proxy such as an Akamai server, or the web server itself.

For SSL sessions, pooling SSL transactions is considered an optimization. However, SSL pooling transactions to a set of TCP persistent connections can cause issues, which prevent these sessions from being decrypted. If a new SSL session is not seen to allow the DNCA to cache the SSL session ID information, then any subsequent SSL sessions that reuse the session ID cannot be decrypted.

In such an environment, connections can persist up to 24 hours, which introduces a latency in the capture of sessions when the DNCA is installed, upgraded, or rebooted. There can be possible workarounds or compromise configuration settings on the source network devices which can mitigate the latency period.

• For more information, contact your IT team.