You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Web Application Firewall DRS rule groups and rules
@@ -61,6 +61,53 @@ When your WAF uses older version of the default rule set (before DRS 2.0), your
61
61
62
62
The version of the DRS that you use also determines which content types are supported for request body inspection. For more information, see [What content types does WAF support?](waf-faq.yml#what-content-types-does-waf-support-) in the FAQ.
63
63
64
+
### DRS 2.1
65
+
66
+
DRS 2.1 rules offer better protection than earlier versions of the DRS. It includes additional rules developed by the Microsoft Threat Intelligence team and updates to signatures to reduce false positives. It also supports transformations beyond just URL decoding.
67
+
68
+
DRS 2.1 includes 17 rule groups, as shown in the following table. Each group contains multiple rules, and you can customize behavior for individual rules, rule groups, or entire rule set. For more information, see [Tuning Web Application Firewall (WAF) for Azure Front Door](waf-front-door-tuning.md).
69
+
70
+
71
+
72
+
> [!NOTE]
73
+
> DRS 2.1 is only available on Azure Front Door Premium.
|942430 |SQLI|Restricted SQL Character Anomaly Detection (args): # of special characters exceeded (12)|Too many false positives.|
105
+
|942440 |SQLI|SQL Comment Sequence Detected|Replaced by MSTIC rule 99031002 |
106
+
|99005006|MS-ThreatIntel-WebShells|Spring4Shell Interaction Attempt|Replaced by Microsoft threat intelligence rule.|
107
+
|99001014|MS-ThreatIntel-CVEs|Attempted Spring Cloud routing-expression injection [CVE-2022-22963](https://www.cve.org/CVERecord?id=CVE-2022-22963)|Replaced by Microsoft threat intelligence rule.|
108
+
|99001015|MS-ThreatIntel-WebShells|Attempted Spring Framework unsafe class object exploitation [CVE-2022-22965](https://www.cve.org/CVERecord?id=CVE-2022-22965)|Replaced by Microsoft threat intelligence rule.|
109
+
|99001016|MS-ThreatIntel-WebShells|Attempted Spring Cloud Gateway Actuator injection [CVE-2022-22947](https://www.cve.org/CVERecord?id=CVE-2022-22947)|Replaced by Microsoft threat intelligence rule.|
110
+
64
111
### DRS 2.0
65
112
66
113
DRS 2.0 rules offer better protection than earlier versions of the DRS. It also supports transformations beyond just URL decoding.
@@ -133,6 +180,280 @@ DRS 2.0 includes 17 rule groups, as shown in the following table. Each group con
133
180
134
181
The following rule groups and rules are available when using Web Application Firewall on Azure Front Door.
135
182
183
+
# [DRS 2.1](#tab/drs21)
184
+
185
+
## <aname="drs21"></a> 2.1 rule sets
186
+
187
+
### <aname="general-21"></a> General
188
+
|RuleId|Description|
189
+
|---|---|
190
+
|200002|Failed to parse request body.|
191
+
|200003|Multipart request body failed strict validation|
192
+
193
+
194
+
### <aname="drs911-21"></a> METHOD ENFORCEMENT
195
+
|RuleId|Description|
196
+
|---|---|
197
+
|911100|Method is not allowed by policy|
198
+
199
+
### <aname="drs920-21"></a> PROTOCOL-ENFORCEMENT
200
+
|RuleId|Description|
201
+
|---|---|
202
+
|920100|Invalid HTTP Request Line|
203
+
|920120|Attempted multipart/form-data bypass|
204
+
|920121|Attempted multipart/form-data bypass|
205
+
|920160|Content-Length HTTP header is not numeric.|
206
+
|920170|GET or HEAD Request with Body Content.|
207
+
|920171|GET or HEAD Request with Transfer-Encoding.|
|941320|Possible XSS Attack Detected - HTML Tag Handler|
333
+
|941330|IE XSS Filters - Attack Detected.|
334
+
|941340|IE XSS Filters - Attack Detected.|
335
+
|941350|UTF-7 Encoding IE XSS - Attack Detected.|
336
+
|941360|JavaScript obfuscation detected.|
337
+
|941370|JavaScript global variable found|
338
+
|941380|AngularJS client side template injection detected|
339
+
340
+
>[!NOTE]
341
+
> This article contains references to the term *blacklist*, a term that Microsoft no longer uses. When the term is removed from the software, we’ll remove it from this article.
342
+
343
+
### <aname="drs942-21"></a> SQLI - SQL Injection
344
+
|RuleId|Description|
345
+
|---|---|
346
+
|942100|SQL Injection Attack Detected via libinjection|
347
+
|942110|SQL Injection Attack: Common Injection Testing Detected|
|99001013|Attempted SharePoint insecure XML deserialization [CVE-2019-0604](https://www.cve.org/CVERecord?id=CVE-2019-0604)|
445
+
|99001014|Attempted Spring Cloud routing-expression injection [CVE-2022-22963](https://www.cve.org/CVERecord?id=CVE-2022-22963)|
446
+
|99001015|Attempted Spring Framework unsafe class object exploitation [CVE-2022-22965](https://www.cve.org/CVERecord?id=CVE-2022-22965)|
447
+
|99001016|Attempted Spring Cloud Gateway Actuator injection [CVE-2022-22947](https://www.cve.org/CVERecord?id=CVE-2022-22947)|
448
+
449
+
> [!NOTE]
450
+
> When reviewing your WAF's logs, you might see rule ID 949110. The description of the rule might include *Inbound Anomaly Score Exceeded*.
451
+
>
452
+
> This rule indicates that the total anomaly score for the request exceeded the maximum allowable score. For more information, see [Anomaly scoring](#anomaly-scoring-mode).
453
+
>
454
+
> When you tune your WAF policies, you need to investigate the other rules that were triggered by the request so that you can adjust your WAF's configuration. For more information, see [Tuning Web Application Firewall (WAF) for Azure Front Door](waf-front-door-tuning.md).
0 commit comments