EN

Ftrans Gateway Secure File Transfer Gateway

One entry point for external file access. Keep services and data inside your network.

PRODUCT OVERVIEW

Product Overview: A Dedicated Access Layer for File Exchange

Ftrans Gateway is a secure access gateway for enterprise file exchange. It provides a dedicated DMZ access layer for Ftrans products that offer external file access or transfer. By separating internet access from internal file services, it lets you exchange files with customers, suppliers and partners while keeping file services, business file storage and user permissions inside your network.

The gateway runs in the DMZ. A component inside the internal network initiates an authenticated, encrypted tunnel, through which external requests reach the designated Ftrans service. The inner firewall does not need to allow new connections initiated from the DMZ, and external users do not connect directly to internal file service addresses.

Layered protection combines architectural separation, protocol session boundaries and IP-based access restrictions. A dedicated access layer reduces internet exposure of the core file platform, while Ftrans protocol services handle business sessions. Access can be restricted by IP address or address range. The DMZ does not store business files or maintain a persistent file cache; processing, storage and authorization remain inside the internal network.

01 / CLEAR BOUNDARIES

Product Benefits: Open Access, Clear Boundaries

Separate external access from your core file platform to reduce direct exposure of file services, storage and identity resources.

01 — SEPARATE ACCESS

DMZ Entry, Internal Services

The gateway handles perimeter access and relaying. Internal Ftrans services manage file processing, authorization and storage.

02 — OUTBOUND TUNNEL

Control Connection Direction

The internal network initiates a controlled tunnel to the DMZ. Firewall policies do not need to permit new DMZ-initiated connections into the internal network.

03 — KEEP DATA INSIDE

Reduce Files at the Perimeter

The DMZ is not a file repository or persistent cache, reducing sensitive file copies and residual data at the network perimeter.

02 / DEPLOYMENT

Deployment: Access in the DMZ, Data Inside

External users connect with standard tools. The gateway provides the entry point; processing, storage and permissions stay inside.

EXTERNAL NETWORK

Customers / Suppliers / Partners

Browser or standard file transfer tool

DMZ / PERIMETER ZONE

Ftrans Gateway
Gateway Service

Unified access · Controlled relay
No persistent business file storage

INTERNAL NETWORK

Keep Services and Data Inside

Processing · Storage · Permissions

Simplified logical architecture. Bidirectional arrows indicate uploads and downloads; they do not imply that the DMZ can initiate new connections into the internal network.
The internal network initiates the tunnel. Firewall rules allow only the required traffic. Delivered as software, Gateway can run on a compatible general-purpose server or virtual machine.
03 / CAPABILITIES

Key Features: Access and Day-to-Day Operations

SFTPFTP/SHTTPHTTPSTCP

Multi-Protocol Access

Publish access endpoints through protocol-specific forwarding rules. For FTP/S, configure control ports and passive data port ranges to support multi-connection transfers.

Service Routing

Use port mappings for dedicated endpoints. For HTTP/HTTPS, route by business domain name to publish different sites on a shared listening port.

Protected Component Connections

Management and cross-zone gateway connections use token authentication and TLS encryption. Protection of each business connection depends on its protocol and service configuration.

Configuration and Monitoring

Configure, start, stop and inspect gateways and forwarding rules. Connection checks, management activity records and runtime logs support maintenance and troubleshooting.

Security: IP Access Restrictions

Restrict access by IP address or address range to define which sources can reach external file service endpoints.

Transparent Access with Standard Tools

External users keep their browsers and familiar file transfer tools, with no dedicated Gateway client to install. Internal file services continue to authenticate business accounts.

04 / USE CASES

Use Cases: Three Ways to Enable External Access

Connect partner deliveries, internal file portals and multiple file services through a clear access path.

Suppliers / CustomersOrders · Drawings · Statements⇄ Gateway ⇄Internal Network
PARTNER COLLABORATION

Exchange Files with Partners

Provide one entry point for orders, statements, design drawings and delivery files. Partners connect over SFTP, FTP/S or a browser, while account and folder permissions remain managed internally.

External BrowserFile Upload / Download⇄ Gateway ⇄Internal File Portal
SEPARATE NETWORK ZONES

Publish an Internal File Portal

Keep the file platform deployed internally and publish a web access endpoint through Gateway. Configure domains, certificates and ports for external uploads and downloads.

External Access MethodsSFTP · FTP/S · HTTPS⇄ Gateway ⇄Multiple File Services
PERIMETER GOVERNANCE

Unify Access to File Services

Organize access groups by product, protocol and security zone. Apply consistent access principles while preserving each service’s accounts, permissions and data boundaries.

05 / APPLICATION EXAMPLES

Application Examples: Two Common Access Upgrades

These illustrative deployment examples show the requirement, access design and expected benefit.

SFTP FILE EXCHANGE

Upgrade Supplier File Access

Supplier→Gateway→Internal
Requirement
Suppliers upload over SFTP. The file server is not mapped directly to the internet, and the DMZ does not initiate connections into the internal network.
Access Design
Gateway publishes the designated SFTP endpoint. The internal network initiates a controlled tunnel, and suppliers continue using their existing transfer tools.
Expected Benefit
Separate the external entry point from the file server. Internal services continue to manage account authentication and folder permissions.
HTTPS FILE PORTAL

Enable External Portal Access

Browser→Gateway→Internal
Requirement
External users need to upload and download files, while the enterprise wants the file website and transfer services to remain inside the internal network.
Access Design
Publish an HTTPS endpoint. Configure domains, certificates and redirects, then verify upload, download and resume workflows.
Expected Benefit
Keep the file platform deployed internally while giving external users an accessible file portal.
LET’S CONNECT

Build a Clear Entry Point for File Services

Discuss network zones, access protocols and file exchange requirements with Ftrans to plan the right gateway deployment.