WAF Allowed IP restriction with Application Gateway

Thanks for the details,

What should be the Priority of those rules?

Hello @Harsh Thakor ,

The custom rules contain a rule name, rule priority, and an array of matching conditions. If these conditions are met, an action is taken (to allow, block, or log).

If a custom rule is triggered, and an allow or block action is taken, no further custom or managed rules are evaluated.

Priority in a custom rule determines the rule valuation order and it must be unique across all custom rules. The lower the value, the earlier the evaluation of the rule. The allowable range is from 1-100.

Example: A rule with priority 40 is evaluated before a rule with priority 80.

Refer: https://zcusa.951200.xyz/en-us/azure/web-application-firewall/ag/custom-waf-rules-overview#priority-required

As I mentioned earlier, you need to make sure that none of the address ranges in your custom rules has overlapping IP addresses and all the ranges have unique IP addresses. Similarly, the priority for each rule must be unique. How you define the priority of the custom rules completely depends on you.

But the lower the priority number, the earlier it gets evaluated. So, assign lower priority numbers to the rules which should get evaluated first.

Regards,

Gita

I Have created a new Allow Rule on top of the block rule, with a lower value compared to the block rule, still, the request has started failing from the newly defined block rule.

How does the sequence formation need to be done? I believe Allow rule should be on the TOP of the Block rule and it should be having lower value than the block rule, which I tried doing. but the result was negative because the other request started failing from that new rule.