Need help with ftw?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

243 Stars 63 Forks Apache License 2.0 320 Commits 18 Opened issues


Framework for Testing WAFs (FTW!)

Services available


Need anything else?

Contributors list

Framework for Testing WAFs (FTW)

Build Status


This project was created by researchers from ModSecurity and Fastly to help provide rigorous tests for WAF rules. It uses the OWASP Core Ruleset V3 as a baseline to test rules on a WAF. Each rule from the ruleset is loaded into a YAML file that issues HTTP requests that will trigger these rules.

Goals / Use cases include:

  • Find regressions in WAF deployments by using continuous integration and issuing repeatable attacks to a WAF
  • Provide a testing framework for new rules into ModSecurity, if a rule is submitted it MUST have corresponding positive & negative tests
  • Evaluate WAFs against a common, agreeable baseline ruleset (OWASP)
  • Test and verify custom rules for WAFs that are not part of the core rule set


  • git clone [email protected]:fastly/ftw.git
  • cd ftw
  • Make sure that pip is installed
    apt-get install python-pip
  • pip install -r requirements.txt

Running Tests with HTML contains and Status code checks only

  • Create YAML files that point to your webserver with a WAF in front of it
  • py.test test/ --ruledir test/yaml

Provisioning Apache+Modsecurity+OWASP CRS

If you require an environment for testing WAF rules, there has been one created with Apache, Modsecurity and version 3.0.0 of the OWASP core ruleset. This can be deployed by:

  • Checking out the repository:
    git clone
  • Typing
    vagrant up

Running Tests while overriding destination address in the yaml files to custom domain

  • start your test web server
  • py.test test/ --ruledir=test/yaml
    --port 443 --protocol https

Run integration test, local webserver, may have to use sudo

  • py.test test/integration/ -s --ruledir=test/integration/


  1. Create a
    file with the necessary imports, an example is shown in
  2. All functions with
    in the beginning will be ran by
    , so make a function
    def test_somewaf
  3. Implement a class that inherits
    1. Implement the
      function. FTW will call this function after it runs the test, and it will set datetimes of
    2. Use the information from the datetime variables to retrieve the files from your WAF, whether its a file or an API call
    3. Get the logs, store them in an array of strings and return it from
  4. Make use of
    py.test fixtures
    . Use a function decorator
    , return your new
    object. Whenever you use a function argument in your tests that matches the name of that
    , it will instantiate your object and make it easier to run tests. An example of this is in the python file from step 1.
  5. Write a testing configuration in the
    format as seen in
    , the
    line requires a string that is a regex. FTW will compile the
    string from each stage in the YAML file into a regex. This regex will then be used alongside the lines of logs passed in from
    to look for a match. The
    string, then, should be a unique rule-id as FTW is greedy and will pass on the first match. False positives are mitigated from the start/end time passed to the
    object, but it is best to stay safe and use unique regexes.
  6. For each stage, the
    function is called, so be sure to account for API calls if thats how you retrieve your logs.

Making HTTP requests programmatically

Although it is preferred to make requests using the YAML format, often automated tests require making many dynamic requests. In such a case it is recommended to make use of the py.test framework in order to produce test cases that can be run as part of the whole. Generally making an HTTP request is simple: 1. create an instance of the

class 2. create an instance of the
class providing whatever parameters you don\'t want to be defaulted 3. provide the instance of the input class to

For some examples see the http integration tests

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.