Traffic that Connection Isolation blocks is not logged

Technical Articles ID: KB92628
Last Modified: 2023-02-07 16:44:44 Etc/GMT

Environment

Endpoint Security (ENS) Firewall 10.7.x, 10.6.x

Problem

When the ENS Firewall Location Aware Group feature "Connection Isolation" blocks non-matching network adapter traffic, that traffic is not logged to the FirewallEventMonitor.log file.

Cause

Both ENS Firewall logging options Log all blocked and Log all allowed must be enabled for this traffic to be logged.

Solution

This issue is resolved in ENS 10.6.1 July 2020 Update and ENS 10.7.0 July 2020 Update.

Our product software, upgrades, maintenance releases, and documentation are available on the Product Downloads site.

NOTE: You need a valid Grant Number for access. See KB56057 - How to download product updates and documentation for more information about the Product Downloads site, and alternate locations for some products.

Workaround

For ENS Firewall 10.7.x:
To log the correct network traffic, enable the Log all blocked and Log all allowed options in the ENS Firewall Options policy.

If needed, you can adjust the ENS Activity log size values within the ENS Common policy. Use the Limit size (MB) of each of the activity log files setting. You might want to change the log size values because of the increased logging within the FirewallEventMonitor.log file.

For ENS Firewall 10.6.x:
There is no workaround.

Affected Products

Languages:

This article is available in the following languages:

Knowledge Center

Traffic that Connection Isolation blocks is not logged

Environment

Problem

Cause

Solution

Workaround

Affected Products

Languages:

Title

Title

Knowledge Center

Traffic that Connection Isolation blocks is not logged

Environment

Problem

Cause

Solution

Workaround

Affected Products

Languages:

Choose your region

Title

Title