Globalscape Firewall

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

Deploying the Globalscape Firewall architecture assists organizations in meeting stringent regulatory requirements:

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 firewall

: Unlike traditional setups, the internal EFT server initiates a persistent outbound connection to the DMZ Gateway (the Peer Notification Channel).

| Component | Location | Function | |-----------|----------|-----------| | | DMZ | Terminates external client connections (FTP/S, HTTP/S, SFTP). Validates protocols. Proxies traffic to internal EFT server. | | Internal EFT Server | Corporate LAN | Stores user accounts, auditing logs, automation rules, and backend storage (disk, cloud). | | Database (SQL) | Internal LAN | Stores configuration, user metadata, and event history. | | | Internal EFT Server | Corporate LAN

Unlike traditional network firewalls, GlobalSCAPE’s firewall component operates at , acting as a reverse proxy and protocol validator.

If your paper requires a technical reference for firewall configuration (ports required for the EFT server itself), the following are standard requirements: and backend storage (disk

EFT includes a built-in IP Access engine that functions exactly like a network firewall. You can: