WAF is not blocking after string match

0

I create a rule i.e.

Type --> Regular rule

Field to match --> URI path

Positional constraint ---> Contains string

Search string ----> /test/*

Text transformations --> Lowercase (Priority 0)

Action --> Block

Custom response code --> 404

But after loading a url https://a.xyz.com/test/a or https://a.xyz.com/test its still works but not blocking. Why? What is wrong with the rule. Can anyone guide me please

posta 2 anni fa1716 visualizzazioni
1 Risposta
1
Risposta accettata

I think the problem is your use of the wildcard in your search string. The string match condition is "contains string," so in order to match on both the examples you've provided, you would need to change it to "/test"

If /test will always be at the start of the URI path then you should change the string match condition to "starts with string" as this consumes fewer WCUs.

Documentation for this can be found here: https://docs.aws.amazon.com/waf/latest/developerguide/waf-rule-statement-type-string-match.html

AWS
ESPERTO
Paul_L
con risposta 2 anni fa
  • but what if I want to set URI --> /test/a/* what should be string match condition? and for abc.example.com/* what should be string match condition?

Accesso non effettuato. Accedi per postare una risposta.

Una buona risposta soddisfa chiaramente la domanda, fornisce un feedback costruttivo e incoraggia la crescita professionale del richiedente.

Linee guida per rispondere alle domande