1

In SmartConsole, from the left Navigation Panel, click Gateways & Servers.

2

Open the Virtual System object.

3

From the navigation tree, click HTTPS Inspection.

4

View and export the certificate.

5

Check Enable HTTPS Inspection.

6

Click OK.

1

In SmartConsole, from the left Navigation Panel, click Security Policies.

2

In the Shared Policies section, click HTTPS Inspection.

3

In the middle of the page, click Open HTTPS Inspection Policy in SmartDashboard.

The Legacy SmartDashboard opens.

4

Configure the HTTPS Inspection Rule Base.

For details, see Configuring HTTPS Inspection.

5

From the top toolbar, click Update (or press Ctrl+S) to save the changes in the database.

6

Close the SmartDashboard.

1

In SmartConsole, open the object of the VSX Gateway, or VSX Cluster.

2

From the navigation tree, click Physical Interfaces.

3

Check the box VLAN Trunk near the designated physical interface.

4

Click OK.

1

In SmartConsole, open the Virtual System object.

2

From the navigation tree, click Topology.

3

From the top toolbar, click New > Regular.

4

On the General tab:

1. In the Interface field, select the designated physical interface that you defined as VLAN Trunk.
2. In the VLAN Tag field, enter or select a VLAN ID.
3. In the IPv4 Configuration section:
   • In the IP Address field, enter a dummy IP address.
   • In the Net Mask field, enter the applicable net mask.

   Important - This IP address cannot collide with other IP addresses used in your environment. This IP address cannot belong to subnets used in your environment. Make sure to configure the correct subnet mask. After you enable traffic mirroring on this interface in SmartConsole, all other traffic that is routed to this interface is dropped.

4. Do not check the Propagate route to adjacent Virtual Devices (IPv4).
5. In the MTU field, enter the applicable MTU. See Mirror and Decrypt Requirements.
6. In the Security Zone field, leave the default None.
7. Click OK.

1

In SmartConsole, open the Virtual System object.

3

From the navigation tree of the gateway object, click the [+] near the Other and click Mirror and Decrypt.

4

Check Mirror gateway traffic to interface.

Mirror and Decrypt - User Disclaimer window opens.

1. Read the text carefully.
2. Check I agree to the terms and conditions.
3. Click OK to accept and close the disclaimer.

5

In the Mirror gateway traffic to interface field, select the VLAN interface (which is configured on top of the designated physical interface).

6

Click OK to save the changes and close the Virtual System properties window.

1

In SmartConsole, from the left Navigation Panel, click Security Policies.

2

Create a new Access Control Layer in the Access Control Policy.

2B

In SmartConsole top left corner, click Menu > Manage policies and layers.

2C

Select the existing policy and click Edit (the pencil icon).

Alternatively, create a new policy.

2D

From the navigation tree of the Policy window, click General.

2E

In the Policy Types section, make sure you select only the Access Control.

2F

In Access Control section, click on the + (plus) icon.

A pop up window opens.

2G

In the top right corner of this pop up window, click New Layer.

Layer Editor window opens.

2H

From the navigation tree of the Layer Editor window, click General.

2I

In the Blades section, make sure you select only the Firewall.

2J

On other pages of the Layer Editor window, configure additional applicable settings and click OK.

2K

In Access Control section, you see the Network Layer and the new Access Control Layer.

2L

Click OK to save the changes and close the Policy window.

3

In SmartConsole, at the top, click the tab of the applicable policy.

4

In the Access Control section, click the new Access Control Layer.

In the default rule, you must change the Action column from Drop to Accept to not affect the policy enforcement:

• Name - Cleanup rule

  You can change the default name to a desired text except these strings:

  <M&D>, <M&d>, <m&D>, or <m&d>

• Source - *Any
• Destination - *Any
• VPN - *Any
• Services & Applications - *Any
• Action - Must contain Accept
• Track - None
• Install On - *Policy Targets

5

Above the existing Cleanup rule, add the applicable rules for the traffic you wish to Mirror and Decrypt.

You must configure the Mirror and Decrypt rules as follows:

• Name - Must contain one of these strings (angle brackets are mandatory):

  <M&D>, <M&d>, <m&D>, or <m&d>

• Source - Select the applicable objects
• Destination - Select the applicable objects
• VPN - Must leave the default *Any
• Services & Applications - Select the applicable services (to decrypt the HTTPS traffic, select the applicable HTTP, HTTPS, or Proxy services)
• Action - Must contain Accept
• Track - Select the applicable option (None, Log, or Alert)
• Install On - Must contain one of these objects:
  • *Policy Targets (this is the default)
  • The objects of Virtual Systems, whose version is R80.20

Important:

• In the Mirror and Decrypt rules, you must not select Content criteria, such as Application, URL Filtering, Service matched by IP Protocol, Content Awareness.
• Above the Mirror and Decrypt rules in this Ordered Layer, you must not configure other rules that contain Content criteria, such as Application, URL Filtering, Service matched by IP Protocol, Content Awareness.
• You must configure rules that contain an excluded source or an excluded destination above the Mirror and Decrypt rules.

  The Name column of these rules cannot contain these strings:

  <M&D>, <M&d>, <m&D>, or <m&d>.

6

Publish the session and install the Access Control Policy.

7

If in a Mirror and Decrypt rule you set the Track to Log, then you can filter the logs for this rule by the Access Rule Name, which contains the configured string:

<M&D>, <M&d>, <m&D>, or <m&d>.