← All topics

What is a firewall?

Customers need to reach your shop. Only selected people should be able to administer the server behind it. A firewall sets rules for connections entering or leaving that server.

Browsing the shop and administering its server need different access

A firewall allows or blocks network traffic according to rules. Those rules can consider the source address, destination, protocol, and port. They can apply to incoming or outgoing connections; the configuration determines which rules are in effect.

In this example, the shop needs public HTTPS access on port 443. SSH administration on port 22 is restricted to selected addresses. The database does not need public access if only the application connects to it.

A rule can lock out your own team

If the office’s public address changes, the existing SSH rule may block the maintenance connection. Customers may still be able to browse the shop because HTTPS follows a different rule. A running service is not necessarily reachable from every network.

The reverse mistake is easy to make, too: a connection opened temporarily for debugging can stay open longer than intended. Each rule needs a clear purpose and regular review, including a check for differences between development and production.

A permitted connection is not permission to view data

Allowing a connection does not determine who can sign in to an application or which records they may access. Those decisions belong to authentication and authorization.

A correctly configured firewall does not guarantee application security. Vulnerabilities in public features, missing permission checks, and software that needs maintenance still require attention.

Restricting SSH access in MainPath

When creating or editing a server in MainPath, you can enable Configure firewall. This setting restricts SSH on port 22 to the addresses you list. HTTP and HTTPS remain public. MainPath and the GitLab runners are always allowed.

You add further addresses or CIDR ranges yourself. Use current IP fills in the address you are connecting from. The Servers documentation explains the setting and its scope.

Thank you for your request

We have received your request and will get back to you as soon as possible.

Would you like to talk to us directly?

Choose a time here for an introductory call with Robin.

Open the calendar in a new tab