<< Back to Insights

How to Configure IP Restrictions for FTP and SFTP Access

2578 words Human made

Published 2026-11-20 09:56:34.808471 by Carsten Blum


Restricting access to trusted IP addresses is an effective way to add another layer of security to your business file transfers.


With ftpGrid, you can configure IP restrictions for your managed FTP, FTPS, SFTP and REST API accounts directly from the web application. There is no need to manage firewall rules, configure server infrastructure, or install additional software.


Whether you want to restrict access to your corporate network or allow a specific supplier to connect to a dedicated SFTP account, ftpGrid makes it easy to manage IP-based access control.


In this guide, we'll explain how to configure global and account-specific IP restrictions, how the two types of restrictions work together, and how to verify that your configuration works as intended.


How to Configure IP Restrictions for FTP and SFTP Access


How IP Restrictions Work in ftpGrid

IP restrictions, sometimes referred to as IP allowlisting or IP whitelisting, allow you to control which IP addresses and networks can access your file transfer accounts.


When IP restrictions are configured, connections are only permitted from the specified IP addresses or network ranges. Connections from other IP addresses are rejected, even if valid authentication credentials are provided.


ftpGrid supports two levels of IP restrictions:

  • Global IP restrictions: Default access rules that apply across your ftpGrid account.

  • Account-specific IP restrictions: Individual access rules for a specific FTP/SFTP or REST API account.


By default, individual accounts inherit the global IP restrictions.


However, if you configure IP restrictions on an individual account, those restrictions replace the global rules for that particular account.


This allows you to establish a consistent security policy across your organization while maintaining the flexibility required for external partners, suppliers, and automated business integrations.


IP restrictions are optional. If neither global nor account-specific restrictions are configured, there are no IP-based limitations on access. Normal authentication and account permissions still apply.


Before You Get Started

IP restrictions are available on the following ftpGrid plans:

  • Professional

  • Business

  • Enterprise


Before configuring IP restrictions, you should identify the public IP addresses used by the users, applications, and external partners that need access to your storage accounts.


For automated integrations, your IT department or integration partner can typically provide the public outbound IP address used by their systems.


Keep in mind that the public IP address of a system may differ from its local IP address, particularly when it is located behind a corporate firewall, NAT gateway, or cloud networking service.


If a connection originates from a dynamic public IP address, it may stop working when that address changes.


For business-critical integrations, we recommend using fixed public IP addresses or known network ranges whenever possible.


How to Configure Global IP Restrictions

Global IP restrictions are useful when you want to establish a default network access policy for your entire ftpGrid environment.


For example, you might want all internal FTP/SFTP accounts and REST API integrations to be accessible only from your corporate network.


Rather than configuring the same IP restriction on every individual account, you can define it once at the global level.


Step 1: Open IP Restrictions

  1. Log in to your ftpGrid account.

  2. In the navigation menu, locate the Security section and select IP restriction.

  3. This opens the global IP access restriction page, where you can manage the default IP access rules for your ftpGrid account.

  4. If no global restrictions have been configured, an informational message indicates that accounts without individual IP restrictions can be accessed from any IP address.


Global IP restrictions


Step 2: Enter a Description

In the Description field, enter a recognizable name for the IP address or network you want to allow.


For example:

  • Corporate headquarters

  • London office

  • Production cloud environment

  • Corporate VPN

  • Internal ERP system


Descriptions are optional, but we recommend using them to make your access rules easier to identify and maintain.


This is particularly useful when multiple administrators manage the same ftpGrid environment.


Step 3: Enter an IP Address or Network

In the IP address field, enter the IP address or CIDR network range that should be permitted to connect.


To allow a single IP address, simply enter: 203.0.113.10

ftpGrid automatically treats individual IPv4 addresses as /32 networks.

You can also enter an entire network range using CIDR notation: 198.51.100.0/24


This allows connections from IP addresses within that network range. The addresses used in this guide are examples. Replace them with the actual public IP addresses or network ranges used by your organization.


Step 4: Add the IP Restriction

Click Add IP to add the restriction to your global allowlist.


Repeat the process for each additional IP address or network that requires access. Once global restrictions are configured, FTP/SFTP and REST API accounts without their own IP restrictions will only accept connections from the specified IP addresses and networks.

All other source IP addresses will be blocked.

Remember that adding the first global IP restriction changes the default access policy from unrestricted IP access to restricted IP access. Make sure that all required business integrations are covered by your global or account-specific rules.


How to Configure IP Restrictions for an Individual FTP Account

Global restrictions provide a convenient default security policy, but not every integration necessarily connects from the same network.


You may have suppliers, customers, or external applications that need access from their own infrastructure.


Instead of adding their IP addresses to your global allowlist, you can configure dedicated IP restrictions on their individual FTP/SFTP accounts.


This keeps access rules isolated to the accounts that actually require them.


Step 1: Open FTP Accounts

Select FTP accounts from the ftpGrid navigation menu.


You can configure account-specific IP restrictions when creating a new storage account or when editing an existing one.


Open the account you want to configure, or expand the form for manually adding a storage account.


Step 2: Locate IP Access Restrictions

Scroll down to the IP access restrictions section.


This section appears alongside the other account security and access settings, including authentication credentials, SSH public keys, access privileges, and chroot configuration.


If the account does not have its own IP restrictions, it automatically inherits the global restrictions, if configured.


Otherwise, there are no IP-based access restrictions on the account.


Account specific IP restrictions


Step 3: Add an Allowed IP Address

Enter a description identifying the source of the connection.


For example: Logistics partner - production


Then enter the public IP address or CIDR network range used by the partner: 203.0.113.50


Click Add IP to add the address to the account's allowlist.


You can add multiple IP addresses and network ranges if the partner connects from more than one location.


Step 4: Save the Account

Save your changes when creating the account, or click Update account when modifying an existing account. Once saved, the individual IP restrictions replace the global restrictions for this account. Only connections originating from the IP addresses and networks configured on this particular account will be permitted.

Other FTP/SFTP and REST API accounts continue to use their own individual restrictions or inherit the global rules.


Understanding Global and Account-Specific IP Restrictions

An important aspect of configuring IP restrictions in ftpGrid is understanding which rules apply to an individual account.


Account-specific restrictions take precedence over global restrictions. The two lists are not combined.


Consider an organization with the following global IP restriction: 203.0.113.10/32


The organization also has a dedicated SFTP account for an external supplier, with the following account-specific restriction: 198.51.100.25/32


The resulting access policy is:

Account

Allowed IP addresses

Internal FTP account

203.0.113.10

Internal SFTP account

203.0.113.10

Supplier SFTP account

198.51.100.25


The supplier can access its dedicated SFTP account without being granted network access to the other accounts.


Similarly, the corporate IP address is not automatically permitted to access the supplier's SFTP account.


If both the corporate network and the supplier need to access that account, both IP addresses must be added to its individual allowlist.


Removing all individual IP restrictions from an account restores inheritance of the global restrictions.


This design makes it possible to maintain a centralized default security policy without limiting the flexibility of individual business integrations.


Using IP Addresses and CIDR Network Ranges

ftpGrid supports both individual IPv4 addresses and CIDR network ranges.


CIDR notation is particularly useful when an organization or integration partner operates multiple systems within a known network.


The following examples illustrate how different network ranges work:

IP address or network

Permitted addresses

203.0.113.10

Only 203.0.113.10

203.0.113.10/32

Only 203.0.113.10

203.0.113.0/28

203.0.113.0–203.0.113.15

203.0.113.0/24

203.0.113.0–203.0.113.255


Multiple addresses and network ranges can be combined within the same allowlist.


For security reasons, we recommend using the smallest network range that meets your requirements. If an integration only uses one fixed public IP address, there is generally no reason to allow an entire network.


Testing Your IP Restrictions

After configuring IP restrictions, verify that your existing integrations continue to work as expected.


You can test FTP, FTPS, or SFTP access using your existing file transfer client, such as FileZilla or WinSCP.


First, establish a new connection from a network that is included in the effective allowlist.


The connection should succeed, provided that your authentication credentials and other account settings are correct.


Next, attempt to connect from a network that is not included in the allowlist.


The login should be rejected, even when using valid credentials.


If an expected connection is rejected, check the following:

  • The actual public outbound IP address of the connecting system.

  • Whether the account has individual IP restrictions that override the global rules.

  • Whether the configured CIDR range includes the connecting IP address.

  • Whether the IP restrictions have been saved.


For automated integrations, we recommend verifying connections with the relevant integration partner before considering the configuration complete.


Managing and Updating IP Restrictions

Business networks and external integrations change over time.


A supplier may migrate to a different hosting provider, an application may move to a new cloud environment, or your organization may introduce a new corporate network.


You can add or remove IP restrictions directly from the ftpGrid web application without changing your existing FTP/SFTP connection settings.


When migrating an integration to a new IP address, consider adding the new address before removing the old one. This allows you to verify the new connection before restricting access from the previous network.


You should also periodically review your allowlists and remove IP addresses that are no longer required.


Which ftpGrid Services Are Covered?

IP restrictions apply to authenticated FTP/SFTP and REST API accounts.


They do not apply to the following ftpGrid features:

  • Web hosting

  • Shared links

  • Upload links (Receive Files)


These features operate independently of your FTP/SFTP and REST API account restrictions.


IP restrictions also complement existing security features rather than replacing them. Continue to use strong passwords, SSH key authentication where appropriate, encrypted file transfer protocols, and dedicated accounts with suitable access privileges.


Secure Your Business File Transfers with ftpGrid

With global and account-specific IP restrictions, ftpGrid gives businesses flexible control over where their file transfer connections originate.


You can protect internal integrations, establish default security policies, and provide dedicated network access to external suppliers and customers, all from a single managed cloud FTP platform. There are no firewall rules to maintain, no FTP servers to configure, and no additional infrastructure to deploy. IP restrictions are available on ftpGrid Professional, Business, and Enterprise plans.


Log in to your ftpGrid account and select IP restriction under Security to get started.

Start in 30 seconds