Anomaly scoring lets Azure WAF on Application Gateway evaluate suspicious requests cumulatively before deciding whether prevention mode should block them. section 3.3.1
Azure WAF assigns scores by rule severity:
- Critical: 5; Error: 4; Warning: 3; Notice: 2. section 3.3.1
- The score is cumulative across matching rules. section 3.3.1
- Prevention mode blocks requests with a total score of 5 or higher. section 3.3.1
Combined rule matches
A request matching one rule scored 3 and another scored 2 reaches a cumulative anomaly score of 5, so prevention mode blocks it. section 3.3.1
Table 3.1 Possible values of severities and scores used in anomaly scoring (view table figure)
Use the severity-and-score table to compare the values that contribute to an anomaly score. section 3.3.1

