Protecting websites with traffic filter rules (including WAF rules)
Last update: Tue May 14 2024 00:00:00 GMT+0000 (Coordinated Universal Time)
CREATED FOR:
- Intermediate
- Admin
- Developer
Learn about traffic filter rules, including its subcategory of Web Application Firewall (WAF) rules in AEM as a Cloud Service (AEMCS). Read about how to create, deploy, and test the rules. Also, analyze the results to protect your AEM sites.
What if you could prevent malicious traffic from ever reaching any of the AMS Cloud Service tiers, like dispatcher, author, and publish service? Welcome to the traffic filter rules, including WAF rules featured in AMS Cloud Service. This powerful feature empowers customers to block or allow requests based on various attributes, such as URI, request headers, IP address, country, the number of requests, and more. Additionally, by licensing the web application Firewall, the OS protection add-on, customers can protect against various types of attacks, including cross-site scripting, SQL injection, and command execution. This provides maximum flexibility to reduce the risk of security breaches while expanding your content reach. In this tutorial, you will learn the setup process to create, deploy, and test traffic filter rules, including WAF rules. You will also discover how to analyze the results using AMS Cloud Service CDN logs and dashboard tool. The dashboard tool provided by Adobe includes Elasticsearch, Logstash, and Kibana, also known as ELKstack, which parses AMS Cloud Service CDN logs and present result analysis in the form of informative charts and graphs. This enables you to gain insights into traffic patterns and further optimize rule configurations. The sample AM beacon project is used to demonstrate traffic filter rules, including WAF rules feature, although you can apply this concept to your own AM project. Let’s get started.
Overview
Reducing the risk of security breaches is a top priority for any organization. AEMCS offers the traffic filter rules feature, including WAF rules, to safeguard websites and applications.
Traffic filter rules are deployed to the built-in CDN and are evaluated before the request reaches the AEM infrastructure. With this feature, you can significantly enhance the security of your website, ensuring that only legitimate requests are allowed to access the AEM infrastructure.
This tutorial guides you through the process of creating, deploying, testing, and analyzing the results of traffic filter rules, including WAF rules.
You can read more about traffic filter rules in this article.
A subcategory of traffic filter rules called “WAF rules” require a WAF-DDoS Protection or Enhanced Security license.
We invite you to give feedback or ask questions about traffic filter rules by emailing aemcs-waf-adopter@adobe.com.
Next step
Learn how to set up the feature so you can create, deploy, and test traffic filter rules. Read about setting up the Elasticsearch, Logstash, and Kibana (ELK) stack dashboard tooling to analyze the results of your AEMCS CDN logs.