Apr 11, 2022 — Security Connector 3.0 now available

Security Connector 3.0 is now available for upgrade or download. This update includes:

New names for Security Connector interfaces. The Security Connector interfaces have been renamed to the following:

• The data interface is now called the en1 interface.
• The management interface is now called the en2 interface.

Use one or two interfaces for DNS Forwarder or HTTP Forwarder data. In the Security Connector console, you can select to use one interface for ingress and egress traffic, or you can use two interfaces where one is for ingress traffic and the other is for egress traffic. The following applies with this update:

• If you select one interface, the en1 interface is used for inbound and outbound traffic, while the en2 interface is used for the Web Console only.
• If you select two interfaces, the en1 interface is used for inbound traffic, while the en2 interface is used for outbound traffic. With this setup, the Web Console is part of the en1 interface.

This feature allows your organization to more easily define firewall rules for Security Connector traffic. For example, by using two interfaces, you can apply different firewall rules to inbound and outbound traffic.

Enhanced HTTP Forwarder. This update includes bug fixes.

Updates to Security Connector reporting. In the Security Connector activity report, the following updates apply:

• Additional fields now provide details on the status of HTTP Forwarder traffic, the proxy type that was used, how traffic was directed from HTTP Forwarder, and more.
• The Affected Internal IP field is now called Internal Client IP and the Affected Device field is now called Internal Client Name.

For more information on Security Connector issues and limitations, see Known issues and limitations.