AWS waf: WAF JA3/JA4 fingerprints usable in more rule statement types
Summary
Expands the JA3 and JA4 fingerprint documentation to state they can be inspected in string match, regex match, regex pattern set match, or size constraint statements (but not SQLi or XSS match statements), and adds guidance on matching single vs. groups of TLS configurations.
Security assessment
This documents an expansion of WAF rule capabilities for TLS fingerprint (JA3/JA4) matching, which is used to detect and block malicious clients based on TLS configuration. It is security feature documentation rather than a fix for a specific vulnerability, so it is medium severity.
Evidence
+You can inspect the JA3 fingerprint in a string match, regex match, regex pattern set match, or size constraint statement. You can't inspect it in an SQL injection or cross-site scripting match statement.
Diff
diff --git a/waf/latest/developerguide/waf-rule-statement-fields-list.md b/waf/latest/developerguide/waf-rule-statement-fields-list.md index 43df4fa..21f3e34 100644 --- a//waf/latest/developerguide/waf-rule-statement-fields-list.md +++ b//waf/latest/developerguide/waf-rule-statement-fields-list.md @@ -174 +174,5 @@ You can obtain the JA3 fingerprint for a client's requests from the protection p -You can inspect the JA3 fingerprint only inside a string match statement that's set to exactly match the string that you provide. Provide the JA3 fingerprint string from the logs in your string match statement specification, to match with any future requests that have the same TLS configuration. For information about the string match statement, see [String match rule statement](./waf-rule-statement-type-string-match.html). +You can inspect the JA3 fingerprint in a string match, regex match, regex pattern set match, or size constraint statement. You can't inspect it in an SQL injection or cross-site scripting match statement. + +To match a single TLS configuration, provide the JA3 fingerprint string from the logs in a string match statement that's set to exactly match the string that you provide. For information about the string match statement, see [String match rule statement](./waf-rule-statement-type-string-match.html). + +To match a group of TLS configurations with a single pattern, use a regex match statement or a regex pattern set match statement. For information about these statements, see [Regex match rule statement](./waf-rule-statement-type-regex-match.html) and [Regex pattern set match rule statement](./waf-rule-statement-type-regex-pattern-set-match.html). @@ -196 +200,5 @@ You can obtain the JA4 fingerprint for a client's requests from the protection p -You can inspect the JA4 fingerprint only inside a string match statement that's set to exactly match the string that you provide. Provide the JA4 fingerprint string from the logs in your string match statement specification, to match with any future requests that have the same TLS configuration. For information about the string match statement, see [String match rule statement](./waf-rule-statement-type-string-match.html). +You can inspect the JA4 fingerprint in a string match, regex match, regex pattern set match, or size constraint statement. You can't inspect it in an SQL injection or cross-site scripting match statement. + +To match a single TLS configuration, provide the JA4 fingerprint string from the logs in a string match statement that's set to exactly match the string that you provide. For information about the string match statement, see [String match rule statement](./waf-rule-statement-type-string-match.html). + +To match a group of TLS configurations with a single pattern, use a regex match statement or a regex pattern set match statement. For information about these statements, see [Regex match rule statement](./waf-rule-statement-type-regex-match.html) and [Regex pattern set match rule statement](./waf-rule-statement-type-regex-pattern-set-match.html).