webApp.secure™ SE is positioned between the Web/application server and the Internet-facing network firewall. It accepts all client connections and validates their requests before allowing them to be processed by the Web/application server through a separate connection.

Request validation along with the isolation provided by a separate connection means the Web/application server communicates with a single, trusted client - webApp.secure. It never accepts connections, or processes requests from an un-trusted source.

As depicted above, the Internet-facing network firewall limits incoming traffic to standard HTTP TCP port(s).

webApp.secure accepts client connections that pass through the network firewall on the standard HTTP TCP port(s).

The site's unique Intended Use Guidelines™ (IUG) are automatically identified using unique web/insite™ technology.

Requests from the client are evaluated by webApp.secure to ensure they conform to the IUG, the HTTP specification, and user-defined policies.

Valid requests are forwarded to the Web/application server through a separate connection (generally using a non-standard TCP port).

Invalid requests are automatically rejected and never processed by the Web/application server. webApp.secure can be configured to generate real-time alerts/notifications (in the form of email's and/or Windows® network messages) when invalid requests are blocked.