DMZ Gateway is a multi-platform solution that works in conjunction with EFT Server to create a multi-layered security solution for data storage and retrieval, authentication, and firewall transversal. Using a two-way connection originating from the back-end (internal) EFT Server, the DMZ Gateway acts as a communication proxy to process requests that replaces inherently insecure inbound connections from the Demilitarized Zone (DMZ) to your network.
DMZ Gateway benefits
- Facilitates compliance with mandates such as PCI DSS requirement §1.3.4 that forbid storage of sensitive data in the demilitarized zone (DMZ).
- Eliminates the need for compensating methods of securing data in the DMZ, such as file encryption, store-and-forward systems, or polling for changes.
- Single outbound connection means greatly reduced overhead as compared to traditional proxy and firewall configuration.
- Save time and reduce points of failure over traditional store-and-forward or polling for changes. Data is made available to back-end systems in real-time.
- Eliminates the need for a file transfer system in the DMZ or for exposing any part of your network to the DMZ, such as AD services for user authentication or SQL services for auditing.
How does DMZ Gateway work?
DMZ Gateway resides in the DMZ. EFT Server resides inside your network and initiates a persistent session with the DMZ Gateway in an outbound (east-west) fashion.
When a client (partner) connects to the DMZ Gateway, DMZ Gateway will notify EFT Server over the pre-established session. Subsequently, EFT Server will initiate another outbound session to the DMZ Gateway, and the DMZ Gateway then glues together this new session and the client’s session. From that point forward, all client and server communications are streamed through DMZ Gateway to EFT Server.
From the client’s view point, DMZ Gateway makes the back-end EFT Server appear to be inside the DMZ, when EFT Server actually resides securely behind your corporate firewall. No transferred data resides in the DMZ (not even temporarily), client authentication takes place on the back-end EFT Server, and no firewall holes are punched through your internal firewall in the wrong direction.
