Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WAF Solution Testing #665

Open
hahwul opened this issue Mar 14, 2025 · 1 comment
Open

WAF Solution Testing #665

hahwul opened this issue Mar 14, 2025 · 1 comment

Comments

@hahwul
Copy link
Owner

hahwul commented Mar 14, 2025

https://x.com/isacaya_/status/1900470572561399919 from @isacaya

@isacaya
Copy link

isacaya commented Mar 20, 2025

Hello, I hope you're doing well. At first, I thought about putting a web app on the cloud and using something like AWS WAF or Cloudflare’s WAF to see how well dalfox works. But after looking into it more, I realized that the "rule set" applied by the WAF is more important than the type of WAF itself, and a lot of WAFs commonly include the OWASP CRS(Core Rule Set).

  • AWS WAF rulesets
    Image

  • Cloudflare WAF rulesets
    Image

So I thought it’d be better to focus more on the rule set rather than specific vendors’ WAFs, and figured that testing with the OWASP Core Rule Set, which most WAFs rely on, might be a sound decision.

And I came across a Docker image that sets up an environment pretty easily, so I hooked up a WAF to XSSMaze. Let me know what you think if you get a chance to peek at it!

Quick Test

  1. git clone -b xssmaze-waf https://github.com/isacaya/xssmaze.git
  2. docker-compose up --build
  3. curl "http://127.0.0.1:8080"

XSSMaze Before and After WAF Implementation

Image
Left (port 3000): plain XSSMaze
Right (port 8080): XSSMaze with OWASP Core Rule Set applied

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants