We are using Fortinet Managed Rules for AWS WAF for one of our front-end applications called the lockers application, where it will be interacted with our postmen in Belgium. For that application to protect against hackers and bots, we are using these WAF rules. Currently, I have used Fortinet Managed Rules for AWS WAF in the AWS service provider for cloud. We have integrated this in the WAF for the locker application, which is an end customer application, and we receive around thousands to hundreds of thousands of requests coming to our application. Since this is publicly exposed, we are using it to make our application more secure and robust without any downtime or security attacks.
Project Manager at Pentagon System and Services Pvt. Ltd.
Real User
Top 5
May 16, 2026
My main use case for Fortinet Managed Rules for AWS WAF is to manage our rules and utilize its pre-configured security rules as an AWS WAF forensic provider.
My main use case for Fortinet Managed Rules for AWS WAF is to use it as a firewall to protect my internal device which is in the internal network in AWS and the internet. To protect my internal device, I had some servers inside the internal network in AWS, one of which is a published server, a web server, that we would like to publish some of this website's application to users outside in our previous company. We have an application hosted in AWS that has a web interface accessible through multiple tablets connected to around 110 trucks all around Egypt, and we have used Fortinet Managed Rules for AWS WAF to publish only this website to a specific number of tablets. Regarding my main use case, we choose the right rule which is only publishing this web interface with a specific port, and we changed this port to a non-standard port to be able to be secured, and changing the port also decreases the threats usually aimed at the default ports for HTTP and HTTPS.
I have been using Fortinet Managed Rules for AWS WAF mainly for protection against common web attacks like SQL injection, cross-site scripting, and remote code execution, securing AWS workloads, including virtual patching, API and application protection, and continuous threat intelligence updates. In virtual patching with Fortinet Managed Rules for AWS WAF, it blocks an exploit at the WAF layer before the code fix, which is illustrated by a typical scenario where I have a web app running on Amazon EC2 with a discovered vulnerability, such as an SQL injection in the login API, where an urgent fix is required but takes days, allowing attackers to exploit it. By enabling Fortinet Managed Rules for AWS WAF group in WAF, SQLi detection and payload pattern blocking are provided, so malicious requests are blocked before reaching the app. A fintech app had a login endpoint vulnerable to SQLi, and with a three-day patch ETA, Fortinet Managed Rules for AWS WAF rules immediately blocked the SQLi patterns with no downtime, avoiding the need for a hotfix.
Our primary use case is protecting public‑facing web applications hosted on AWS against common web threats while reducing the effort required to manage custom WAF rules. We use Fortinet Managed Rules to enhance baseline AWS WAF protection, particularly for OWASP Top 10 vulnerabilities, malicious bots, and abnormal web traffic. The managed rule sets help standardize application security across workloads fronted by AWS services such as Application Load Balancers and CloudFront, while allowing us to focus on operations rather than constant rule tuning.
Learn what your peers think about Fortinet Managed Rules for AWS WAF. Get advice and tips from experienced pros sharing their opinions. Updated: June 2026.
I work with Fortinet Managed Rules for AWS WAF and have been using it for the last eight months. I am using it for Web Application Firewall and API protection.
Fortinet Managed Rules for AWS WAF enhances security by offering pre-configured firewall rules designed to protect AWS applications from common exploits and vulnerabilities.Fortinet Managed Rules for AWS WAF offers advanced threat protection specifically tailored for the AWS environment. It seamlessly integrates with AWS WAF, providing security teams with a comprehensive solution to defend against sophisticated attacks without extensive configurations. The rules continually update to tackle...
We are using Fortinet Managed Rules for AWS WAF for one of our front-end applications called the lockers application, where it will be interacted with our postmen in Belgium. For that application to protect against hackers and bots, we are using these WAF rules. Currently, I have used Fortinet Managed Rules for AWS WAF in the AWS service provider for cloud. We have integrated this in the WAF for the locker application, which is an end customer application, and we receive around thousands to hundreds of thousands of requests coming to our application. Since this is publicly exposed, we are using it to make our application more secure and robust without any downtime or security attacks.
My main use case for Fortinet Managed Rules for AWS WAF is to manage our rules and utilize its pre-configured security rules as an AWS WAF forensic provider.
My main use case for Fortinet Managed Rules for AWS WAF is to use it as a firewall to protect my internal device which is in the internal network in AWS and the internet. To protect my internal device, I had some servers inside the internal network in AWS, one of which is a published server, a web server, that we would like to publish some of this website's application to users outside in our previous company. We have an application hosted in AWS that has a web interface accessible through multiple tablets connected to around 110 trucks all around Egypt, and we have used Fortinet Managed Rules for AWS WAF to publish only this website to a specific number of tablets. Regarding my main use case, we choose the right rule which is only publishing this web interface with a specific port, and we changed this port to a non-standard port to be able to be secured, and changing the port also decreases the threats usually aimed at the default ports for HTTP and HTTPS.
I have been using Fortinet Managed Rules for AWS WAF mainly for protection against common web attacks like SQL injection, cross-site scripting, and remote code execution, securing AWS workloads, including virtual patching, API and application protection, and continuous threat intelligence updates. In virtual patching with Fortinet Managed Rules for AWS WAF, it blocks an exploit at the WAF layer before the code fix, which is illustrated by a typical scenario where I have a web app running on Amazon EC2 with a discovered vulnerability, such as an SQL injection in the login API, where an urgent fix is required but takes days, allowing attackers to exploit it. By enabling Fortinet Managed Rules for AWS WAF group in WAF, SQLi detection and payload pattern blocking are provided, so malicious requests are blocked before reaching the app. A fintech app had a login endpoint vulnerable to SQLi, and with a three-day patch ETA, Fortinet Managed Rules for AWS WAF rules immediately blocked the SQLi patterns with no downtime, avoiding the need for a hotfix.
Our primary use case is protecting public‑facing web applications hosted on AWS against common web threats while reducing the effort required to manage custom WAF rules. We use Fortinet Managed Rules to enhance baseline AWS WAF protection, particularly for OWASP Top 10 vulnerabilities, malicious bots, and abnormal web traffic. The managed rule sets help standardize application security across workloads fronted by AWS services such as Application Load Balancers and CloudFront, while allowing us to focus on operations rather than constant rule tuning.
Fortinet Managed Rules for AWS WAF is used for security purposes. My major use case is API management these days.
I work with Fortinet Managed Rules for AWS WAF and have been using it for the last eight months. I am using it for Web Application Firewall and API protection.