Globalscape Firewall

The Globalscape EFT Network Firewall utilizes a . It functions as a gatekeeper residing in the DMZ (Demilitarized Zone), while the core EFT Server (processing the data and authenticating users) resides in the secure internal network.

GlobalSCAPE EFT firewall proper network firewall rules:

1.0 Last Updated: 2025 Based on: GlobalSCAPE EFT v8.x architecture (HelpSystems/Fortra) globalscape firewall

The firewall can limit the number of concurrent connections per IP address and per user. This mitigates Denial of Service (DoS) attacks and prevents resource exhaustion on the internal server.

: This creates a secure pipe that allows external users to access the internal server without opening inbound ports on your internal firewall. The Globalscape EFT Network Firewall utilizes a

💡 : GlobalSCAPE’s security is not just about a single feature, but the combination of the DMZ Gateway’s "no-inbound-holes" architecture and EFT’s granular IP access controls. If you'd like to dive deeper, let me know: Are you setting this up for PCI or HIPAA compliance?

While GlobalSCAPE handles the application-level security, it must work in tandem with your hardware firewalls. A typical secure deployment involves: This mitigates Denial of Service (DoS) attacks and

: Allows only the internal EFT server to talk to the DMZ Gateway over a specific "Peer" port.

: Zero inbound ports are opened from the DMZ to your internal "Trusted" network.

Below is a white paper structured to provide a comprehensive technical and functional overview of this technology.