About SSH Session Break

Just as Secure Proxy creates an SSL session break for the HTTP, FTP, and Connect:Direct® protocols, it creates an SSH session break when using the SFTP protocol. The SSH session break occurs because the trading partner connects to Secure Proxy in the DMZ and not to the application in the trusted zone. The trading partner is unaware that Secure Proxy is deployed and believes it is connecting to your backend system. Secure Proxy negotiates an SSH session with the remote trading partner and authenticates the trading partner's key and/or password as part of the SSH negotiation. After the SSH session is established, Secure Proxy initiates a separate SSH session to the application in the trusted zone. After the application in the trusted zone authenticates Secure Proxy using key and/or password authentication, Secure Proxy relays messages between the trading partner connection and the trusted zone application connection to allow the remote trading partner to move data into and out of the trusted zone application.

Following is a sample flow of an SSH session break: