Category Network Training

“Welcome to my channel! In this video, I will describe how to configure firewall policies with multiple source and destination interfaces in FortiGate. We’ll be looking at how to allow traffic between multiple interfaces on your FortiGate firewall, which is particularly useful when you have different subnets that you want to control traffic between or when you have multiple VLANs that need to communicate with each other. By the end of this video, you’ll have a better understanding of how to configure these policies in FortiGate and how they can help secure your network.

1. Network Interfaces:
   • In a FortiGate device, you typically have multiple network interfaces, each connected to a different network segment or zone. These interfaces can be physical (Ethernet ports) or virtual (VLANs, subinterfaces, loopback interfaces, etc.).
2. Traffic Flow:
   • Traffic flows between these interfaces as data packets are transmitted through the FortiGate device. Each interface represents a different security zone, and traffic between these zones must be controlled and inspected for security purposes.
3. Security Policies:
   • FortiGate uses security policies to determine how traffic is treated as it passes between these interfaces. Security policies are rules that define the permitted actions for specific types of traffic. They include criteria like source and destination IP addresses, ports, protocols, and more.
4. Multiple Interface Policy:
   • The “Multiple Interface Policy” feature in FortiGate allows you to create a single security policy that applies to traffic flowing between multiple interfaces or zones. This is especially useful when you want to define a consistent policy for a specific category of traffic across multiple interfaces.
5. Use Cases:
   • There are several use cases for Multiple Interface Policies:
     • DMZ Configuration: If you have a DMZ zone with multiple servers that need different levels of access, you can create a single policy to control traffic from different internal zones to the DMZ.
     • Guest Network Isolation: You can use this feature to control traffic from the guest network to multiple internal networks with a single policy.
     • VPN Traffic: When you have multiple VPN tunnels terminating on different interfaces, you can create a policy that applies to traffic from all those tunnels.
6. Policy Configuration:
   • When configuring a Multiple Interface Policy, you define the policy’s source and destination interfaces (security zones), specify the criteria for matching traffic (source/destination addresses, services, users, etc.), and define the action to take (allow, deny, NAT, etc.).
7. Policy Order:
   • Policy order is important. FortiGate processes policies from top to bottom, and the first matching policy is applied. So, you should order your Multiple Interface Policies appropriately to ensure that more specific policies are evaluated before broader ones.
8. Logging and Monitoring:
   • FortiGate provides extensive logging and monitoring capabilities, allowing you to track traffic as it traverses the different interfaces and the policies applied to it.
9. Traffic Inspection:
   • Depending on your policy settings, FortiGate can perform various security functions like antivirus scanning, intrusion detection and prevention, content filtering, and more on the traffic as it flows between interfaces.

In summary, FortiGate Multiple Interface Policies are a crucial part of network security configuration. They enable you to manage and secure traffic between multiple network interfaces by defining specific security policies that dictate how traffic should be handled. This feature is particularly useful in complex network environments with diverse security requirements.

Hello everyone, in this video, I will introduce how you can set up 2-step verification for SSL VPN users by sending a token through email. By default, there is no way to enable this option via the graphical user interface. We must enable this feature from the CLI.

1. User Login Request:

• When a user attempts to log in to a FortiGate-protected resource, such as a VPN, web portal, or firewall management interface, they provide their username and password as the first authentication factor.

2. Verification of Username and Password:

• FortiGate first verifies the provided username and password against its user database or an external authentication source, such as LDAP, RADIUS, or Active Directory. If the credentials are valid, the user passes the first authentication factor.

3. Request for Second Authentication Factor:

• Once the user successfully completes the first factor (username and password), FortiGate prompts the user for the second authentication factor. In this case, it’s an email-based authentication.

4. Email-Based Authentication:

• FortiGate sends an email containing a one-time passcode (OTP) or a link to the user’s registered email address. This email typically includes instructions on what the user should do next.

5. Retrieving and Entering the OTP:

• The user checks their email and retrieves the OTP or clicks on the provided link. The OTP is typically time-limited and can only be used once for security purposes.

6. Entering the OTP or Confirming Access:

• The user enters the OTP from the email into the FortiGate login prompt or clicks on the link, which confirms their identity as the second authentication factor.

7. Verification of Second Factor:

• FortiGate verifies the entered OTP or link against its records to ensure it matches the one it sent to the user’s email. If the OTP or link is valid and within the time window, the user passes the second authentication factor.

8. Access Granted:

• Once both factors are successfully authenticated (username/password and email-based OTP/link), FortiGate grants the user access to the requested resource or system.

9. Continuous Monitoring:

• FortiGate may also implement continuous monitoring and session management to ensure that user sessions remain secure throughout their usage.

It’s worth noting that while email-based 2FA is a common method, FortiGate also supports various other second-factor authentication methods, including SMS-based codes, hardware tokens, software tokens, and push notifications through mobile apps. The choice of the second-factor method can depend on the organization’s security policies and user preferences.

Implementing 2FA with email in FortiGate enhances security by adding an extra layer of authentication, making it more challenging for unauthorized users to gain access to critical resources and helping protect against unauthorized access and data breaches.

Hello, today we will install GNS3 with you and then we will install CISCO ASA on it. I will also explain how we can connect to Cisco ASA with ASDM.

Let’s start.

Step 1: Obtain Cisco ASA Image

You’ll need a Cisco ASA image file to run it in GNS3. You can acquire this image from legal and legitimate sources, such as Cisco’s official website, or if you have a Cisco ASA device, you may be able to extract it. Make sure you have the proper licensing to use the image.

Step 2: Install GNS3

If you haven’t already, download and install GNS3 on your computer from the official website (https://www.gns3.com/). Follow the installation instructions for your specific operating system.

Step 3: GNS3 Initial Setup

1. Launch GNS3 and complete the initial setup wizard. This typically includes configuring preferences like where to store your projects and images.
2. Make sure you have the GNS3 VM (Virtual Machine) configured and running. You can download the GNS3 VM from the GNS3 website and follow the installation instructions provided there.

Step 4: Add Cisco ASA to GNS3

1. In GNS3, go to “Edit” > “Preferences.”
2. In the Preferences window, click on “QEMU VMs” on the left sidebar.
3. Click the “New” button to add a new virtual machine.
4. Provide a name for the virtual machine (e.g., “Cisco ASA”).
5. In the “Type” dropdown menu, select “ASA” for Cisco ASA.
6. In the “QEMU binary” section, browse and select the QEMU binary executable. This binary should be located in your GNS3 VM.
7. Set the RAM and CPU settings based on your system resources and requirements.
8. Click “Next” and follow the on-screen instructions to complete the virtual machine setup.

Step 5: Add ASA Image to GNS3

1. In GNS3, go to “Edit” > “Preferences” again.
2. In the Preferences window, click on “QEMU” on the left sidebar.
3. Click the “QEMU VMs” tab.
4. Select the “Cisco ASA” virtual machine you created earlier.
5. In the “QEMU Options” section, click the “Browse” button next to “QEMU image” and select the Cisco ASA image file you obtained.

Step 6: Configure Cisco ASA in GNS3

1. Drag and drop the Cisco ASA device from the GNS3 device list onto your GNS3 workspace.
2. Right-click on the ASA device and choose “Start.”
3. Right-click again and select “Console” to open the console window for the ASA.
4. Configure the ASA as needed using the command-line interface (CLI). This includes setting up interfaces, IP addresses, access control policies, and any other configurations you require.
5. Save your configurations to ensure they persist across sessions.

With these steps, you should have a Cisco ASA running in GNS3, ready for configuration and testing in your simulated network environment. Remember to follow proper licensing and usage guidelines when using Cisco ASA images.

Hello everyone, in this video I will show how can you extend VLANs over IP. In FortiGate by using vxlan you can do this.

1. Access the FortiGate GUI:

• Open a web browser and enter the IP address of your FortiGate firewall to access the graphical user interface (GUI).
• Log in with administrator credentials.

2. Create VXLAN Interface:

• Navigate to Network > Interfaces.
• Click Create New and select VXLAN.
• Fill in the following details for the VXLAN interface:
  • Name: A descriptive name for the VXLAN interface (e.g., VXLAN1).
  • Alias: An optional alias for identification purposes.
  • VLAN ID (Optional): If you want to associate the VXLAN interface with a specific VLAN, provide the VLAN ID.
  • VXLAN ID (VNI): Specify a unique VXLAN ID. This is critical, as it is used to identify the VXLAN segment. Ensure that VNIs match across devices in your VXLAN network.
  • VXLAN Port: Specify the UDP port for VXLAN traffic (default is 4789).
• Click OK to create the VXLAN interface.

3. Configure VXLAN Settings:

• Under Network > VXLAN, select the VXLAN interface you just created.
• Configure the following VXLAN settings:
  • Local IP Address: Enter the IP address associated with the FortiGate’s VXLAN interface. This IP should be on the same subnet as the VXLAN endpoints.
  • Multicast Address (Optional): If you intend to use multicast for VXLAN traffic, specify a multicast IP address. Ensure that both ends of the VXLAN have the same multicast settings.
  • Remote IP Address (Peer): Enter the IP address of the remote FortiGate firewall or VXLAN endpoint that you want to connect to.
• Click OK to save the VXLAN settings.

4. Create VXLAN Overlay Network:

• Go to Policy & Objects > Objects.
• Click Create New and select Virtual Network.
• Fill in the VXLAN overlay network details:
  • Name: A descriptive name for the VXLAN overlay network.
  • Interface: Select the VXLAN interface you created in step 2.
  • VXLAN ID (VNI): Set the same VNI as you did in the VXLAN interface configuration.
• Click OK to create the VXLAN overlay network object.

5. Create Firewall Policies:

• Under Policy & Objects > IPv4 Policy, create firewall policies to allow traffic between VXLAN overlay networks or between VXLAN networks and the physical network.
• In the policy settings:
  • Define the source and destination addresses using the VXLAN overlay network objects you created.
  • Specify the desired action (e.g., allow).
  • Set any required security profiles, such as antivirus or intrusion prevention.
• Click OK to create the firewall policy.

6. Routing (if needed):

• If routing between VXLAN overlay networks or between VXLAN and physical networks is necessary, configure routing on the FortiGate firewall.

7. Security Profiles (if needed):

• Apply security profiles to the firewall policies to enhance security for VXLAN traffic. These profiles can include antivirus scanning, intrusion prevention, and application control.

8. Monitor and Troubleshoot:

• Use the FortiGate GUI or CLI to monitor the VXLAN interface’s status and traffic.
• Check logs for any issues or errors related to VXLAN.
• Verify that routes are correctly configured, especially if you have multiple VXLAN segments.

9. Repeat on Remote FortiGate (if applicable):

• If you have multiple FortiGate firewalls participating in the VXLAN network, repeat the configuration steps on the remote FortiGate(s), ensuring that VXLAN settings match on both ends.

10. Test and Verify:

• Test connectivity between devices on the VXLAN overlay networks to ensure that traffic is correctly routed and policies are applied.

Always consult the Fortinet documentation for your specific FortiGate model and firmware version, as there may be slight variations in the user interface and configuration options.