FortiGate
FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
Patterson
Staff
Staff
Article Id 231066
Description

 

This article describes that from the 7.2 version of FortiGate, the SD-WAN rule for the application category can be created, earlier it was needed to add applications individually.

 

Pre-Requisite

Internet link added as SD-WAN member and firewall policy enabled with application control profile.

 

Solution

 

1) Create an SDWAN rule.

 

Patterson_0-1669639162935.png

 

2) Select Destination.

 

Initially, the application control option needs to be enabled via CLI. So for creating a rule, define the destination address as 'all' or any specific entry.

 

Patterson_1-1669639162942.png

 

3) Select OK.

 

Patterson_2-1669639162944.png

 

4) Select 'CLI'.

 

Patterson_3-1669639162941.png

 

5) Via CLI, as mentioned enable Internet service, after having specified an application or category, attribute category 5 to video/audio.

 

Patterson_4-1669639162946.png

 

6) Other category IDs are also available as listed.

 

Patterson_5-1669639162938.png

 

7) Select SD-WAN to refresh the page.

 

Patterson_6-1669639162947.png

 

8) Now the changes made on the CLI are available in the GUI.

 

Patterson_7-1669639162948.png

 

9) Open the policy if adding more applications or categories is needed.

 

Patterson_8-1669639162949.png

 

10) Validating the traffic flow.

Confirm under the FortiView application for matching traffic once initiated from the client PC.

 

Patterson_9-1669639162951.png

 

11) Select highlight.

 

Patterson_10-1669639162952.png

 

12) Select Destination Interface to view the outgoing interface.

 

Patterson_11-1669639162953.png

 

 

13) Via CLI, a dynamic entry will be created for the matching application with the destination IP.

 

Patterson_14-1669639162957.png

 

14) This can be verified via CLI as mentioned below.

Two session outputs are listed for the same destination IP. Only the web access is matching to the SD-WAN rule and the ping traffic is matching to the default flow.

 

Patterson_15-1669639162958.png

 

Related document: