The Rules → Firewall screen allows you to define how your organization handles network traffic. By configuring Allow or Deny actions based on source, destination, service, and time schedule, you can enforce strict access controls and secure your environment—whether you’re blocking suspicious activity, protecting internal systems, or managing internet usage.
📍 To access this screen, go to Rules → Firewall
The Firewall Rules table lists all firewall rules in the order they are evaluated—top to bottom. The first matching rule is applied, so rule order directly impacts behavior. You can drag and drop rules to reprioritize them.
| Column | Description |
|---|---|
| ID | Unique identifier assigned to each rule |
| Type | Indicates whether the rule is created by your team (Client) or delivered by your partner as a security baseline (Global) |
| Source | Defines the traffic origin (e.g., IP, User, Device, Tag, or Interface) |
| Action | Choose to Allow or Deny traffic |
| Destination | Defines the target (e.g., IP, Application, Website Category) |
| Service | The type of traffic or protocol (e.g., HTTP, DNS, or a custom service) |
| Description | Short label explaining the rule’s purpose |
| Status | Current status of the rule |
Create a New Firewall Rule
Click Create New to open the rule configuration screen. Here’s a breakdown of the key:
| Field | Description |
|---|---|
| Description | (Required) A meaningful name for identifying the rule |
| Action | (Required) Choose whether to Allow or Deny matching traffic |
| Status | (Required) Enable or disable the rule upon creation |
| Sources | Default is Any. You may specify multiple entries, including: Network, Site, IP, Location, User, Team, Device, Tag, or Interface (with Gateway 14.0.0) |
| Destinations | Default is Any. You may specify: Network, Interface (with Gateway 14.0.0), Site, IP, Location, Website Category, Application, Application Category, User, Team, Device, Tag, or Keywords |
| Services | Select from predefined or custom service definitions |
| Custom Source Port | (Optional) Define a specific port range if necessary |
| Clear Sessions | Forcefully end current sessions that match this rule’s source, ensuring immediate enforcement |
| Enable Logging | Log matching traffic in Network Activity → Firewall |
| Schedule | Apply the rule only during specific hours or days (default: Everyday) |
Once saved, the rule is added to the table and takes effect immediately—according to its position in the list.
Rule Actions
Click the ••• next to any rule to:
- View / Edit – Review or update the rule configuration
- Enable/Disable – Temporarily toggle the rule’s active status
- Clear Sessions – Instantly drop all sessions affected by the rule
- Delete – Permanently remove the rule. Appears in records as Deleted Firewall Rule (ID: {id})
Bulk Actions
You can select multiple rules and use the Actions menu to:
- Enable/Disable – Temporarily toggle the selected rules’ active statuses
- Clear Sessions – Instantly drop all sessions affected by the selected rules
- Delete – Permanently remove the selected rules. Appear in records as Deleted Firewall Rule (ID: {id})
🆕 What’s New in This Version?
Global Policies
The Type column indicates whether a rule is created by you (Client) or pushed by your partner as part of a managed security baseline (Global). This enables consistent enforcement of critical protections across environments, while maintaining flexibility.
| Type | What it means |
|---|---|
Client |
Fully editable rules created in your own portal |
Global |
Non-editable rules delivered by your security provider or partner |
Why Global Policies?
Global rules are designed to help standardize and strengthen network security across all managed tenants—particularly useful for:
- MSP environments
- New customers needing out-of-the-box protections
- Preventing configuration gaps in high-risk areas
You can:
- Reorder
Globalrules to adjust their evaluation priority - Enable or disable them as needed to fit your context
They do not override your own rules—they simply provide a secure starting point.
Updated
Comments
0 comments
Please sign in to leave a comment.