---
title: "Firewall Policy Configuration in CPE "
id: "firewall-policy-configuration-in-cpe"
project: "SC//Connect™ | OS v8.5"
url: "https://docs.scalecomputing.com/articles/sc-connect-os-v8-5/firewall-policy-configuration-in-cpe"
updated: 2026-11-19T17:09:04Z
---

# Firewall Policy Configuration in CPE 

This topic provides information on how users can configure the firewall policy through their Customer Premises Equipment (CPE).

To perform this action, an Admin login is required.

* [Overview](/articles/sc-connect-os-v8-5/firewall-policy-configuration-in-cpe/a/h2__773755849)
* [Inbound Policies (L4)](/articles/sc-connect-os-v8-5/firewall-policy-configuration-in-cpe/a/h2__2137105230)
* [Outbound Policies (L4)](/articles/sc-connect-os-v8-5/firewall-policy-configuration-in-cpe/a/h2_1017061995)
* [Application Policies (L7)](/articles/sc-connect-os-v8-5/firewall-policy-configuration-in-cpe/a/h2__1123253714)
* [Policies Fields Explanation](/articles/sc-connect-os-v8-5/firewall-policy-configuration-in-cpe/a/h2_780139094)
* [Application Lookup](/articles/sc-connect-os-v8-5/firewall-policy-configuration-in-cpe/a/h2_1751408822)

##  **Overview**

The firewall is a critical security feature that allows users to control whether traffic is allowed or denied through their device. By applying the firewall policies, users can protect their internal resources, prevent unauthorized access or even optimize their network traffic flows. 
 We provide solutions that allow users to configure firewall policies either through the **SC//Connect™ Orchestrator** or directly via the **remote CPE GUI** (Customer Premises Equipment Graphical User Interface). After [logging in](/articles/sc-connect-os-v8-5/remote-access-management/a/access-credentials), users will find this feature under the **Network** section. In general, the Firewall Policy Configuration feature supports defining and managing three types of policies:

* [**Inbound Policies (L4)**](/articles/sc-connect-os-v8-5/firewall-policy-configuration-in-cpe/a/h2__2137105230) – define policies for traffic **incoming** to the CPE.

* **[Outbound Policies (L4)](/articles/sc-connect-os-v8-5/firewall-policy-configuration-in-cpe/a/h2_1017061995)** – define policies for traffic **leaving** the CPE.

* **[Application Traffic Policies (L7)](/articles/sc-connect-os-v8-5/firewall-policy-configuration-in-cpe/a/h2__1123253714)** – define policies at the **application level.**

These policies give users the flexibility to enforce security and optimize network performance by specifying which flows should be **allowed, denied, prioritized,****and/or overridden.**

From AOS v8.4, Firewall Policy Override Configuration is available on the CPE GUI. This feature allows users to configure a specific ALLOW (!) policy that overrides broader DENY policies. Refer to [this article](/articles/sc-connect-os-v8-5/override-policy) for more details.

In summary, by configuring the firewall policy, users could have:

* Full control over inbound, outbound, and application traffic.
* Enhance security by preventing high-risk external threats and unauthorized access.
* Improved network efficiency by prioritizing business-critical applications.

##  **Inbound Policies (L4)**

The **inbound policy** controls the traffic **coming into a customer's internal network** (CPE- Customer Premises Equipment) from the outside.

Users can configure whether traffic is:

* ALLOW
* DENY
* ALLOW (!) (Override Policy – applied from AOS v8.4)

*Example:* 
 ![](/resources/Storage/sc-connect-os-v8-5/firewall-policy-configuration-in-cpe/firewall-policy-configuration-in-cpe-2026-10-19.png) 
 *From the above screenshot, Inbound Policies are configured to deny access to traffic from 2 ports: 22 & 3389.* *SSH (port 22) and RDP (Remote Desktop Protocol, port 3389) are remote access protocols. Allowing them from external sources could expose the internal network to attackers, potentially giving unauthorized control over internal devices. Blocking this access helps to protect the internal network against potential hacking.*

###  Add inbound Policy

### 

1. **Provide Inputs**: Users fill all required and optional [Policies Fields](/articles/sc-connect-os-v8-5/firewall-policy-configuration-in-cpe/a/h2_780139094).
2. **Add Policy**: After all the fields are completed, click **Add**(button on the right-hand side).
3. **Result**: The new policy is created and applied to the firewall rules list. 
  * When a user adds a policy without entering any input, the system will automatically apply the default value from the placeholder attribute. An error message will be displayed when the user enters an incorrect input format. Refer to the [Policy Fields](/articles/sc-connect-os-v8-5/firewall-policy-configuration-in-cpe/a/h2_780139094) format section for more details.
    * An error will display if the user tries to add a duplicate existing policy.

###  Modify Inbound Policy

###   

1. **Select Input**: User selects the policy to update and then clicks **EDIT**.
2. **Modify Input**: User inputs the needed modification fields. 
 The updated value in this step must follow the correct [Policy Fields](/articles/sc-connect-os-v8-5/firewall-policy-configuration-in-cpe/a/h2_780139094)format.
3. **Apply the changes**: User clicks **Apply** to save the changes
4. **Result:** The selected modified policy is updated with the new values and remains active in the firewall rules list. 
 The user can click **Cancel**to discard the adjustment and return to the previous window. 
  An error message will be displayed when the user enters incorrect input format. Refer to the [Policy Fields](/articles/sc-connect-os-v8-5/firewall-policy-configuration-in-cpe/a/h2_780139094) format section for more details.

###  Delete Inbound Policy

###   

1. **Select Policy**: User selects the policy they want to remove then click **EDIT**.
2. **Delete Policy**: Click the **Delete** button.
3. **Result:** The selected deleted policy is permanently removed from the firewall rules list. 
 ![](/resources/Storage/sc-connect-os-v8-5/firewall-policy-configuration-in-cpe/firewall-policy-configuration-in-cpe-2026-10-19.gif) 
 
  Once deleted, the policy is permanently removed from the firewall rules list. 
 Deleted policies must be re-created if needed later. 
 Use caution when deleting critical policies, as this may affect network security.

##  **Outbound Policies (L4)**

**The outbound policy** controls the **traffic leaving from the customer's internal network** (CPE- Customer Premises Equipment) to an external destination.

Users can configure whether traffic is:

* ALLOW
* DENY
* ALLOW (!) (Override Policy – applied from AOS v8.4)

Example: Only allowing employees access to secure Internet destinations or blocking access to specific risky websites or entertainment domains.

The steps for adding, modifying, and deleting outbound policy are the same as for Inbound Policies. Users can refer to its action for [Inbound Policies](/articles/sc-connect-os-v8-5/firewall-policy-configuration-in-cpe/a/h3__860957318) as their workflow and interface are consistent with.

##  **Application Policies (L7)**

Unlike **[Inbound](/articles/sc-connect-os-v8-5/firewall-policy-configuration-in-cpe/a/h2__2137105230)**or [**Outbound**](/articles/sc-connect-os-v8-5/firewall-policy-configuration-in-cpe/a/h2_1017061995) policy, the **[Application Policies (L7)](/articles/sc-connect-os-v8-5/firewall-policy-configuration-in-cpe/a/h2__1123253714)**control the flow of the traffic based on application type (application, category or domains) rather than the IP addresses, port or protocols. 
 ![](/resources/Storage/sc-connect-os-v8-5/firewall-policy-configuration-in-cpe/firewall-policy-configuration-in-cpe-2026-10-19-2.png)

Users can configure whether traffic is:

* ALLOW
* DENY
* ALLOW (!) (Override Policy – applied from AOS v8.4)

Example: 
 **Allowing** collaboration tools (such as Microsoft Teams, Zoom) while **blocking** Adult Content advertising. At the same time, **de-prioritizing** bandwidth for video gaming during working hours to prevent it from impacting the business traffic.

The steps to **add, modify and delete** application policies are the same as for Inbound Policies. Users can refer to the same workflow and interface as [Inbound Policies](/articles/sc-connect-os-v8-5/firewall-policy-configuration-in-cpe/a/h3__860957318), with the exception that some [Policies Field input](/articles/sc-connect-os-v8-5/firewall-policy-configuration-in-cpe/a/h4_1319328677)will be slightly different from Inbound & Outbound Policies.

##  **Policies Fields Explanation**

### 

####  **Action:**Defines the action applied to the traffic. Options include:

* Allow — Permit the traffic. (Default value)
* Deny — Block the traffic.
* Allow (!) — An [Override Allow policy](/articles/sc-connect-os-v8-5/override-policy)that permits traffic even if broader DENY rules exist.

####  **Source:**Specifies the origin of the traffic, defined by the IP address. 
 Default value: 0.0.0.0/0 (any source). Example: 192.168.29.0/24

####   **Destination:**Specifies the intended target of the traffic, defined by the IP address. 
 Default value: 0.0.0.0/0 (any destination). Example: 192.168.1.10.

####  **Ports:**Defines which port(s) the policy applies to. (Range from 0 to 65535). 
 Default value: 0-65535. 

####  **Protocol:**Defines the transport layer protocol for the inbound policy. Default value: any. 
Options: TCP, UDP, ICMP, or Any. Examples: 80 or 443 (TCP), 0-65535 (UDP), or None for ICMP.

####  **Priority:**Specifies traffic priority when multiple policies apply. Default value: normal. 
Levels: highest &gt; high &gt; normal &gt; low &gt; lowest.

####  **Paths:**Specifies which traffic path or interface the policy applies to.

* **Gateway** – Traffic via the gateway.
* **Inbound** – Direct traffic from the external (WAN) to the internal (LAN).
* **Breakout** – Local internet breakout at the edge.
* Default value: Depending on the policy, the default value will differ.
    * For Inbound Policies (default value=inbound).
    * For Outbound & Application Policies (default value=gateway)

####  **Paused:**Instead of completely deleting the policy, the user may use **Pause** to temporarily activate or deactivate a policy. 
 Default value: False. Example: True = policy is inactive. False = policy is active.

####  **Description:**Optional text field for notes or additional context about the policies.

####   **Name (for Application Policies only):**A mandatory text field used to identify the specific application or group of applications targeted by the policy. 
 Example: Finance, Accounting & Billing

####   Type (for Application Policies only): Mandatory option fields to define the clarification of the name fields. Options include:

* Application – A single or specific application (example: Zoom, Microsoft Teams...)
* Category – A group of related applications (example: Video Gaming, Social Networks...)
* Domain – A domain name (example: facebook.com)

##  **Application Lookup**

The Application Lookup functionality is a simple yet powerful widget that helps users find more information about applications. Based on the three search parameters below (Name, URL Domain and IPv4), it provides flexibility to look up applications. Depending on the parameters selected, the required lookup input will be different. This feature can help users quickly search and identify a specific application and verify whether the application is recognized and categorized correctly by the system.

To use Application Lookup, users need to:

* Step 1: Select the **[available search parameters](/articles/sc-connect-os-v8-5/firewall-policy-configuration-in-cpe/a/search-params).**
* Step 2: Input the required search input based on the selected search parameters.
* Step 3: Click****the **Find** button to display the results. 
 ![](/resources/Storage/sc-connect-os-v8-5/firewall-policy-configuration-in-cpe/firewall-policy-configuration-in-cpe-2026-10-19-3.png)

**Available search parameters**:

* **Name** — Searches the application by name. The user must enter the name of the application.
* **URL Domain** — Searches the application by URL Domain. User must enter the URL domain in a valid format.
* **IPv4 (IP address)** — Searches the application by IP address. User must enter a valid IP address.