Configure Firewall Settings in Seqrite Endpoint Security (EPS)

Quick Answer

You can configure firewall settings in Seqrite Endpoint Security (EPS) through its centralized web console. For the documented EPS interface, sign in to the web console and navigate to Settings > Client Settings > Firewall. Enable the firewall, select an appropriate security level, configure exceptions for specific applications or network traffic, and click Save Policy.

Seqrite EPS supports the Block all, High, Medium, and Low firewall security levels. Exception rules can allow or deny traffic based on supported protocols, IP addresses, ports, and, where available, application paths. The firewall feature applies to Windows clients. Menu names and rule-configuration steps can differ between EPS versions and cloud or on-premises deployments. Refer to the official Seqrite EPS firewall documentation.

How to Access and Enable Firewall Settings

1. Sign in to the Seqrite Endpoint Security web console using an account authorized to manage client settings.
2. Navigate to Settings > Client Settings > Firewall in the documented interface.
3. Select the Enable Firewall checkbox.
4. If prompted, review the warning about the Windows Firewall before confirming the change.
5. Select the required security level.
6. Review the existing exceptions and add or modify rules as necessary.
7. Configure the available monitoring, alert, and reporting options according to your organization's requirements.
8. Click Save Policy to save the configuration.

Before applying a policy broadly, test it on a small group of endpoints. Confirm that essential business applications, remote administration tools, DNS resolution, internet access, and required management or update communications continue to work.

Understanding the Four Firewall Security Levels

The security level determines how the firewall handles incoming and outgoing network connections. Choose a level based on the organization's security requirements and the applications that must communicate.

These descriptions follow Seqrite's documented firewall behavior. An exception's effect depends on its configuration, direction, status, and position in the rule list. A restrictive security level does not replace the need to design and test rules carefully.

How to Create a Firewall Exception Rule

Firewall exceptions let administrators permit or deny specific network communications. They are useful when an application needs network access that the current policy blocks, or when an application or network destination must be restricted.

Step 1: Open the Exceptions section

1. Open the firewall settings in the Seqrite EPS web console.
2. Ensure the firewall feature is enabled.
3. Locate the Exceptions section.
4. Click Add to create a new exception.
5. Enter a descriptive exception name, such as Allow Approved Business Application or Deny Unapproved Remote Access.

Step 2: Select the protocol and application

The documented firewall rule configuration supports these protocols:

• TCP (Transmission Control Protocol): Used by many applications that require reliable, connection-oriented communication.
• UDP (User Datagram Protocol): Used by applications that send datagrams without TCP's connection-oriented delivery mechanism.
• ICMP (Internet Control Message Protocol): Used for network control and diagnostic messages, including some ping operations.

For TCP or UDP rules, select the applicable connection direction and configure the local and remote network criteria offered by your EPS version. Where the application selector is available, choose the option for all applications matching the specified conditions or specify the approved application's executable path.

Use the ICMP-specific configuration when creating an ICMP rule. TCP/UDP port settings do not apply to ICMP in the same way they do to TCP and UDP.

Step 3: Define the IP addresses and ports

Configure only the network details necessary for the intended rule. Depending on the protocol and product version, the interface can provide options for:

• Local IP address: The address associated with the endpoint's local side of the connection.
• Remote IP address: The address of the other system involved in the connection.
• Local TCP/UDP ports: Ports associated with the endpoint's local side.
• Remote TCP/UDP ports: Ports associated with the other side of the connection.
• IP address ranges: A range of addresses, when supported by the selected rule type.
• Application path: The executable path for an application-specific rule, when supported.

Depending on the interface, you may be able to choose any IP address, specify individual addresses, enter a range, or select specific ports or a port range. Some EPS interfaces also support domain-name criteria.

Do not open every port or allow every remote IP address simply to make an application work. Identify the application's documented communication requirements and use the narrowest rule that meets them.

Step 4: Choose the action and save

1. Select Allow to permit matching traffic or Deny to block it.
2. Where the interface provides a rule status option, ensure the exception is enabled if it should take effect.
3. Review the completed rule before saving it.
4. Click Finish to complete the exception configuration.
5. Review the rule's position in the Exceptions list. Seqrite documents that rule order determines precedence, with higher-positioned rules taking priority.
6. Use the available move-up or move-down controls if the order needs to change.
7. Click Save Policy.

Follow the wizard displayed by your installed EPS version, because the exact sequence of screens and available fields may differ.

Example: Blocking an Unapproved Application

Suppose an organization wants to restrict an unapproved remote-access application such as AnyDesk on managed Windows endpoints. The appropriate approach depends on whether the objective is to block the application's network communication or prevent the application from running altogether.

1. Confirm the organization's authorization to restrict the application and identify the executable path and legitimate business use.
2. Open the firewall Exceptions section.
3. Create a rule using the application-specific option if your EPS version supports it.
4. Select the relevant protocol, connection direction, and network criteria based on the intended restriction.
5. Select Deny, where applicable, and review the rule's precedence against existing exceptions.
6. Save the policy and test the result on a designated endpoint.

Important limitation: A firewall rule controls matching network traffic; it does not necessarily prevent an application from launching or communicating through every possible protocol or executable. If the requirement is to prevent the application from running, use an appropriate supported application-control or endpoint policy feature, if available in your product edition, rather than relying on a firewall rule alone.

Firewall Monitoring, Alerts, and Reports

The documented EPS firewall settings include additional monitoring options. Availability and placement may vary by version.

• Monitor Wi-Fi Networks: The documented interface enables this option by default. It can alert users to unsecured Wi-Fi networks and attempts to access an unsecured client Wi-Fi hotspot, with reports generated at the server.
• Display alert message when firewall violation occurs: Enables alerts when a firewall violation is detected.
• Enable firewall reports: Enables reporting for blocked connections.

Reporting can help administrators identify blocked application traffic and investigate connectivity problems. However, the Block all level can generate many reports and may affect network performance. Enable detailed reporting where it is useful, and review the reporting load when managing many endpoints.

How to Edit, Delete, Import, or Export Exception Rules

Edit an existing exception

1. Open the Firewall settings and locate the Exceptions list.
2. Select the exception you need to change.
3. Modify the supported application, protocol, direction, address, port, action, or status fields as needed.
4. Finish the editing wizard and click Save Policy.
5. Test the updated rule against the intended traffic.

Delete an exception

1. Locate and select the exception to remove.
2. Use the available Delete action in the interface.
3. Confirm the change if prompted and click Save Policy.
4. Verify that removing the exception has not interrupted a required business application.

Import or export rules

Seqrite documentation describes importing and exporting firewall exceptions, but the exact procedure and file format vary between product versions. For example, documented interfaces have used different formats, including fwexcp.db and firewall_exception.json.

Before importing an exception file, confirm that it is compatible with the installed EPS version and comes from a trusted source. Export the existing configuration first when the interface permits it, and review imported rules before deploying them to other endpoints. Do not assume that a file exported from one EPS version can be imported unchanged into another.

Firewall Troubleshooting

An application cannot connect to the internet or network

1. Confirm that the endpoint has network connectivity independently of the application.
2. Check whether the problem affects one application, one destination, or all network traffic.
3. Review the current firewall security level and the applicable exception rules.
4. Verify the executable path, protocol, direction, local and remote addresses, and ports in the relevant rule.
5. Review firewall alerts or reports if reporting is enabled.
6. Create or adjust a narrowly scoped Allow rule only when the required traffic is known and authorized.
7. Save the policy and test the application again.

Remote administration stops working

If a remote administration tool stops connecting after a firewall policy change, determine whether the blocked connection is inbound, outbound, or both. Check the application's documented ports and protocols and restrict access to trusted systems wherever possible.

Do not broadly allow all inbound traffic or disable endpoint protection to restore access. If the endpoint is remote, confirm that you have another supported management or recovery route before applying a policy that could disconnect it.

Internet access stops after applying a policy

Check whether the Block all level or a high-priority Deny rule is blocking required communications. Review the policy, exception order, and any relevant firewall reports. Correct the specific rule or restore a previously approved policy if needed.

If the endpoint cannot communicate with the EPS management server, use an approved administrative recovery method for the deployment. Do not assume that the central console can deliver a corrective policy to a device that is no longer reachable.

Firewall changes do not appear to take effect

• Confirm that the policy was saved successfully.
• Check whether the intended endpoint or group is assigned the policy.
• Verify the exception's enabled status, action, and position in the rule list.
• Allow for policy delivery and application according to your deployment's normal management process.
• Confirm the behavior on the actual endpoint instead of relying only on the console configuration.

How to Verify the Firewall Configuration

After saving the policy, verify both the intended restrictions and the required business communications.

1. Confirm that the endpoint is receiving the intended EPS policy.
2. Test the application or connection that the rule was designed to allow or deny.
3. Where relevant, test from a trusted remote system and from an unauthorized or out-of-scope system.
4. Review firewall alerts and reports, if enabled, to check whether the expected traffic was allowed or blocked.
5. Confirm that ordinary network access and endpoint management remain functional.

A saved rule is not proof that a connection is blocked or permitted in every circumstance. The result depends on rule matching, precedence, the selected security level, application behavior, and other network controls.

Restore the Previous Configuration

If a firewall change interrupts business operations, restore the last approved configuration using the recovery method supported by your EPS deployment. The documented EPS interface includes a Default or equivalent reset option in some versions; this may restore default settings rather than the exact previous configuration.

Before resetting or replacing a policy, record the existing settings and export the exceptions when supported. If the change was deployed to multiple endpoints, identify the affected group and follow your organization's change-control procedure. Re-test both security restrictions and essential network access after recovery.

Security Best Practices

• Use the least-permissive security level that meets operational requirements.
• Create specific rules for known applications, protocols, ports, and trusted remote addresses.
• Avoid broad Allow rules and unrestricted inbound access.
• Review exception order so that higher-priority rules do not unintentionally override the intended behavior.
• Test policy changes on a limited group before organization-wide deployment.
• Maintain a record of rule purpose, owner, business justification, and review date.
• Review obsolete exceptions and remove rules that are no longer needed.
• Keep endpoint security software and supported operating-system components maintained according to the vendor's guidance.

Frequently Asked Questions

Does enabling the Seqrite EPS firewall disable Windows Firewall?

The documented EPS configuration warns that enabling its firewall disables the default Windows Firewall on the endpoint. Confirm the behavior for your installed product version and configuration, and ensure that an effective firewall remains active.

What is the difference between High and Medium firewall security?

High blocks inbound and outbound connections except as governed by exception rules. Medium blocks inbound connections by default while allowing outbound connections, subject to configured exceptions. The appropriate level depends on the network requirements and the traffic you need to control.

Can I block a particular application using Seqrite EPS?

You can configure application-specific firewall exceptions where supported by your EPS version. These rules control matching network traffic; blocking an application from launching may require a separate supported application-control feature.

Can I block a specific IP address or port?

Yes. The documented exception configuration supports IP address and TCP/UDP port criteria, including ranges where available. Select the correct connection direction and Deny action, then review rule precedence and test the result.

Does the firewall work on every operating system?

Seqrite's cited firewall documentation states that the feature is available on Windows clients. Confirm the supported operating systems for your particular EPS release in the applicable product documentation.

Why does a firewall rule not block an application?

Possible causes include an incorrect executable path, a mismatched protocol or direction, an incorrect address or port, an inactive rule, rule precedence, or a different communication method used by the application. Review the rule and available firewall reports before making broader changes.

Which network ports should I allow for Seqrite cloud and updates?

Required ports depend on the Seqrite product, deployment type, and enabled services. Consult the official network requirements documentation applicable to your installed version. Do not open a port solely because it appears in a generic list without confirming that your deployment requires it.

Sources

• Seqrite Endpoint Security — Firewall settings and exception rules
• Seqrite Endpoint Protection — Firewall policy configuration
• Seqrite Endpoint Security — Administrator Guide