Tealeaf Web Server Agent

General Requirements…

* A "Tealeaf web server agent" in an upper layer of the TCP/IP stack, after packets are decrypted.

* The TL server agent will forwards packets to a collector.
Avoids the Diffie Hellman encryption issues.
Avoids maintaining RSA SSL keys at a PCA.
Forward from the endpoint at the web server and avoid the security concerns between endpoints of web server and client browser.

* Runs on both Azure/Windows/.NET/IIS platform and Linux/Apache/Java platform.

* The TL server agent will send directly to a Tealeaf health-based router (HBR) which will act as a collector.
No network taps, no PCAs, no IP addresses to maintain, no certificates to maintain.

* In addition, the TL server agent can inject a TLSID cookie and provide a corporate sessionID.
A TLTSID sessinID might even be able to combine customer session that start as Internet '.com' and change to intranet '.net' domains.

* The TL server agent might also work in concert with the browser Tealeaf UIC and mobile frameworks.