docs(bots): clarify JA4 Signals Intelligence fields cannot be used in WAF rules#31983
Open
zeinjaber wants to merge 1 commit into
Open
docs(bots): clarify JA4 Signals Intelligence fields cannot be used in WAF rules#31983zeinjaber wants to merge 1 commit into
zeinjaber wants to merge 1 commit into
Conversation
… WAF rules Closes DEE-3697
zeinjaber
requested review from
a team,
elithrar,
jinhee-c-lee and
marinaelmore
as code owners
Contributor
Review✅ No issues found in commit Code ReviewThis code review is in beta and may not always be helpful — use your judgment. No code review issues found. ConventionsNo convention issues found. Style Guide ReviewNo style-guide issues found. CommandsOnly codeowners can run commands. Post a comment with the command to trigger it.
|
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a note at the bottom of the Signals Intelligence page clarifying that these fields are analytics-only — available in Security Analytics and Security Events, but not usable as filter fields in WAF custom rule expressions.
Why
Customers browsing the Signals Intelligence field reference assume these fields can be used in WAF custom rules (as other
cf.bot_management.*fields can). When they cannot find them in the rule builder, they open support cases. The note sets the expectation clearly at the point of discovery.Files changed
src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/signals-intelligence.mdx— new note block after the field table and render (+4 lines)How to verify
Navigate to /bots/additional-configurations/ja3-ja4-fingerprint/signals-intelligence/ and confirm the note appears at the bottom of the page.
Closes DEE-3697