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.
This article describes how to process a brute force attack on SSL VPN login attempts with random users/unknown users and how to protect from SSL VPN brute-force logins.
The attacker is trying to use a dynamic IP address and random admin user account to login via SSL VPN.
Scope
FortiGate.
Solution
In this situation, process as follows:
Use strong passwords for all accounts: This includes password rules like in this example:
Passwords must have a minimum length of 12 characters.
Passwords must contain numbers.
Passwords must contain special characters.
Passwords must contain upper '-' and lowercase letters.
Passwords must have an age below 8 weeks.
Implement Two-factor authentication for all accounts: Two-factor authentication prevents an attacker from being able to log in to an account only with a username and password.With the third factor, the attacker needs access to additional information like the smartphone (in case of push token) or a 6-digit number (in case of mobile or hardware Tokens).
Ensure, that admin users have no access to the SSL-VPN portal.It is recommended to differentiate user accounts that are allowed to access VPN solutions and administrative accounts that are only allowed to access the administrative interfaces.
Change the listening Port for the SSL-VPN portal. Using another port is an easy but effective measurement if an attacker is only probing the default port of an application.Do not forget to change the port on all VPN clients too. Otherwise, the connection will break.
Restrict the source IP address area. If users only need access to the SSL-VPN portal from a specific source address or range, it is possible to limit the allowed source addresses to those addresses and also restrict users based on country or geography addresses.
Filter by action="ssl-login-fail" tunneltype="ssl-web" Log & Report -> System Events -> VPN Events.
If there are no requirements for a specific authentication mechanism such as LDAP/Radius/Local authentication, do not include these users/groups within SSLVPN settings as it prevents servers from being contacted.
Creating an authentication rule or local-in policy to restrict SS LVPN connections will help to reduce the login and failed attempts seen under Log & Reports -> System Events -> VPN events.
