Free Open-Source WAF Rules for AEM as a Cloud Service
Free, self-updating CDN traffic filter rules for AEM as a Cloud Service, built from OWASP CRS and open threat lists. No WAF licence needed.
AEM as a Cloud Service has a CDN with traffic filter rules built in. The rules that recognise SQL injection, XSS and other attacks, the WAF flags, need Adobe's Extended Security or WAF-DDoS Protection licence. Many teams don't have it. Free Open-Source WAF Rules for AEM give them a solid filter anyway, using only the standard rules every AEM Cloud Service program can deploy.
What does it do?
A small generator builds config/cdn.yaml from maintained open-source threat data:
- attack patterns ported from the OWASP Core Rule Set: path traversal, SQL injection, XSS, remote code execution, Log4j and protocol attacks
- AEM hardening:
/bin/querybuilder,.infinity.json,/system/consoleand the PHP and WordPress probes that hit every AEM site - known attack scanners blocked by user agent
- a per-IP rate limit for traffic from around 930 datacenter networks, with real search engines left alone
- a policy for AI crawlers: training crawlers blocked, AI search and assistant traffic allowed, so the site stays visible in AI answers
- fake Googlebot, Bingbot, GPTBot and ClaudeBot traffic caught by checking the vendors' published IP ranges
- a matching
robots.txtwith AI usage signals
We rebuild the rules every day. When a source changes, for example a new Core Rule Set release, the new build is tested and reviewed before it replaces the files below. Download them again to pick up an update.
How well does it work?
Measured at build time against public attack payloads sent in a query parameter, the rules catch 99% of XSS, 100% of command injection, 87% of local file inclusion and 70% of SQL injection payloads. Most SQL injection misses are bare words like update that aren't attacks on their own.
It isn't a replacement for Adobe's licensed WAF. The CDN can't read JSON or XML request bodies, there is no IP reputation feed, and the higher-risk rules ship in log mode so you can watch for false positives before switching them to block. We wrote up the details in free WAF rules for AEM as a Cloud Service.
Where does it come from?
It comes from our AEM work. The WAF licence is an extra cost on top of AEM, and without it a Cloud Service site often runs with no attack filtering at the CDN. We built this so those sites get a sensible default, and made it open source under the Apache 2.0 licence.
How can you use it?
Download the latest build:
- cdn.yaml: the traffic filter rules, ready for
config/cdn.yamlin your AEM repository - robots.txt: the matching crawler policy, to merge with your own robots.txt
- NOTICE.txt: licences and attribution for the open-source sources, to keep with any copy you share
Deploy to a dev environment first. The setup steps and the one-request check to run before production are in the article. If you want help rolling it out or tuning it for your site, get in touch.
Adobe, Adobe Experience Manager and AEM are trademarks of Adobe Inc. This project is not affiliated with or endorsed by Adobe.
Follow the Lab
A short email when a Lab entry changes status or needs early testers. Nothing else.