Skip to content

[WAF] Update fields/functions for custom detection locations #17597

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 17, 2024
Merged

[WAF] Update fields/functions for custom detection locations #17597

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion src/content/docs/waf/detections/leaked-credentials/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,10 +71,11 @@ When specifying a custom detection location, only the location of the username f
Expressions used to specify custom detection locations can include the following fields and functions:

- Fields:
- [`http.request.body.form`](/ruleset-engine/rules-language/fields/http-request-body/#httprequestbodyform)
- [`http.request.body.raw`](/ruleset-engine/rules-language/fields/http-request-body/#httprequestbodyraw)
- Functions:
- [`lookup_json_string()`](/ruleset-engine/rules-language/functions/#lookup_json_string)
- [`lower()`](/ruleset-engine/rules-language/functions/#lower)
- [`url_decode()`](/ruleset-engine/rules-language/functions/#url_decode)

For instructions on configuring a custom detection location, refer to [Get started](/waf/detections/leaked-credentials/get-started/#4-optional-configure-a-custom-detection-location).

Expand Down
Loading