I have been using Fortinet FortiGate for the past six years.
I have been using Fortinet FortiGate to provide security for network and perimeter networks and gateways, and I rely on Fortinet FortiGate to protect my applications from various Layer 4 and Layer 7 attacks and traffic from malicious IPs while blocking traffic from unwanted IPs.
Fortinet FortiGate is also mainly used to establish IPsec tunnel connectivity with other networks, and users from outside the office network can connect to resources via IPsec VPN as well as site-to-site and client-to-site VPN, which leverages access and resource availability across various networks and simplifies resource accessibility worldwide.
One of the main features that I use in real time with Fortinet FortiGate is web filtering and App IDs based on application control. Previously, I allowed application access policies based on ports, but it could not prevent traffic based on the same application port with different use cases. For example, port 443 can be used for various purposes, but it could not restrict access for some specific applications. The App ID based control is useful for me to restrict traffic based on application usage and user access, which is the primary purpose of Fortinet FortiGate in real time.