Globalscape’s DMZ Gateway works in conjunction with EFT Server to create a multi-layered security solution that can be used for data storage and retrieval, authentication and firewall transversal. The DMZ Gateway uses a two-way connection originating from the back-end (internal) EFT Server. It acts as a communication proxy to process requests that replaces inherently insecure inbound connections from the Demilitarized Zone (DMZ) to your network.
How is Globalscape’s DMZ Gateway different?
Unlike other store-and-forward technologies, our DMZ Gateway does not store or process data. It’s simply a liaison to your internal network. Your data stays secure because it’s never stored in the DMZ. Your data remains safe behind the firewall for EFT Server to store and process.
DMZ Gateway Provides Security and Efficiency at the Same Time
You don’t need to choose between top security and being efficient. With DMZ Gateway, you can finally have both!
- 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.
- 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.
- 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.
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.
- No inbound (west to east) holes through the network firewall.
- No data is ever stored in the DMZ – data streams to the back-end EFT Server.
- Virtual authentication – DMZ Gateway acts as a proxy for authentication.
- Supports all protocols allowed by the EFT Server (FTP/S, SFTP, HTTP/S and AS2).
- Transparent to your partners – EFT Server’s services are virtualized in the DMZ.
- No storage, synchronization, or replication of user database needed in the DMZ.
- Support for Linux or Unix-based systems, Solaris, and Windows operating systems
- Gateway can map and route connections to all other EFT Server sites on the network, which not only reduces your total cost of ownership, but also simplifies network maintenance.