Create custom rules with AI Assistant (beta)

🚧

This is a beta feature. To enable it, contact your account team.

From Web Security Analytics (WSA), you can use AI Assistant to create custom rules based on applied filters. Supported dimension types include:

  • Client information (Client Fingerprint matches)
  • Network information (IP Address, AS Number, and GEO matches)
  • HTTP information (Request Header, Method, Query, and Host-related matches)
  • IP/Geo firewall (Client List matches)
📘

Before using this feature, review how AI Assistant handles WSA filters when generating custom rules. Note that not all filters in WSA are supported. For details, see Requirements and supported filters.

Create a custom rule with AI Assistant

To create a custom rule with AI Assistant:

  1. Navigate to Web Security Analytics.
  2. Apply the desired filters, ensuring they are supported filters and meet the requirements listed below.
  3. In the top navigation bar, click AI Assistant.
  4. Enter: “Create a custom rule based on the current filters applied.”

If the applied filters are supported, AI Assistant generates a custom rule based on them. You will be redirected to the custom rule builder with the filters pre-populated as conditions. Review the generated rule before saving and activating it.

🚧

If only some of the applied filters are supported, AI Assistant will generate custom rule conditions only from the supported filters.

Requirements and supported filters

You can use AI Assistant to create custom rules from applied filters that meet the supported dimensions, operators, and requirements below.

Filter compatibility requirements

Most supported filters have specific compatibility requirements. When using AI Assistant to create custom rules, if a filter isn't listed below as fully compatible, ensure it meets the following requirements:

  • Use only one operator per dimension (for example, only Match Any or only Does Not Match Any for Client H2 Fingerprint). Combining multiple operators for a single dimension is not supported.
  • Do not use filters with empty values unless the filter specifically supports them. For example, if you set the filter values for “Connecting AS Number ==ANY Match Any” as AS12345, AS67890, and [empty value], it will not work because this dimension does not support any empty values.
  • Even if a filter supports empty values, do not use a filter that contains only an empty value. For example, while the User-Agent dimension can accept empty values, AI Assistant cannot create a custom rule from a filter with only “[empty_value]” for “User-Agent ==ANY Match Any.”

Client information filters

Filter dimensionSupported operatorsSupports empty values?Compatibility
JA4 Client TLS Fingerprint
  • Match Any
  • Does Not Match Any
NoRequirements apply
Client H2 Fingerprint
  • Match Any
  • Does Not Match Any
NoRequirements apply
Client TLS Fingerprint V3
  • Match Any
  • Does Not Match Any
NoRequirements apply
Client TLS Fingerprint V2
  • Match Any
  • Does Not Match Any
NoRequirements apply

Network information filters

Filter dimensionSupported operatorsSupports empty values?Compatibility
Connecting IP Address
  • Match Any
  • Does Not Match Any
YesRequirements apply
Connecting IP Address CIDR
  • Match Any
  • Does Not Match Any
YesRequirements apply
Connecting IP Subnet
  • Match Any
  • Does Not Match Any
YesRequirements apply
Connecting AS Number
  • Match Any
  • Does Not Match Any
NoRequirements apply
Connecting Country/Area
  • Match Any
  • Does Not Match Any
YesRequirements apply
End User IP Address
  • Match Any
  • Does Not Match Any
YesRequirements apply
End User IP Address CIDR
  • Match Any
  • Does Not Match Any
YesRequirements apply
End User IP Subnet
  • Match Any
  • Does Not Match Any
YesRequirements apply
End User AS Number
  • Match Any
  • Does Not Match Any
NoRequirements apply
End User Country/Area
  • Match Any
  • Does Not Match Any
YesRequirements apply

HTTP information filters

Filter dimensionSupported operatorsSupports empty values?Compatibility
User-Agent
  • Match Any
  • Does Not Match Any
  • Starts With Any
  • Does Not Start With Any
  • Contains Any
  • Does Not Contain Any
  • Ends With Any
  • Does Not End With Any
YesFully compatible*
Hostname
  • Match Any
  • Does Not Match Any
  • Starts With Any
  • Does Not Start With Any
  • Contains Any
  • Does Not Contain Any
  • Ends With Any
  • Does Not End With Any
NoFully compatible*
Path
  • Contains Any
  • Does Not Contain Any
NoRequirements apply
Query
  • Match Any
  • Does Not Match Any
  • Starts With Any
  • Does Not Start With Any
  • Contains Any
  • Does Not Contain Any
  • Ends With Any
  • Does Not End With Any
NoRequirements apply
Request Header Set
  • Contains Any
  • Does Not Contain Any
YesRequirements apply
Accept-Language
  • Match Any
  • Does Not Match Any
  • Starts With Any
  • Does Not Start With Any
  • Contains Any
  • Does Not Contain Any
  • Ends With Any
  • Does Not End With Any
YesFully compatible*
Content-Length
  • Match Any
  • Does Not Match Any
  • Starts With Any
  • Does Not Start With Any
  • Contains Any
  • Does Not Contain Any
  • Ends With Any
  • Does Not End With Any
YesFully compatible*
Method
  • Match Any
  • Does Not Match Any
Not applicableRequirements apply
Sec-CH-UA
  • Match Any
  • Does Not Match Any
YesFully compatible*
Sec-CH-UA-Mobile
  • Match Any
  • Does Not Match Any
YesFully compatible*
Sec-CH-UA-Arch
  • Match Any
  • Does Not Match Any
YesFully compatible*
Sec-CH-UA-Platform
  • Match Any
  • Does Not Match Any
YesFully compatible*
Sec-CH-UA-Platform-Version
  • Match Any
  • Does Not Match Any
YesFully compatible*
Sec-CH-UA-Model
  • Match Any
  • Does Not Match Any
YesFully compatible*
Sec-CH-UA-Bitness
  • Match Any
  • Does Not Match Any
YesFully compatible*
Sec-CH-UA-Full-Version-List
  • Match Any
  • Does Not Match Any
YesFully compatible*
Sec-CH-UA-Form-Factors
  • Match Any
  • Does Not Match Any
YesFully compatible*
Sec-CH-UA-Full-Version
  • Match Any
  • Does Not Match Any
YesFully compatible*
Sec-CH-UA-WoW64
  • Match Any
  • Does Not Match Any
YesFully compatible*
Referer
  • Match Any
  • Does Not Match Any
YesFully compatible*

*These filters are fully compatible with custom rule matches. The Filter compatibility requirements above do not apply.

IP/Geo firewall filters

🚧

Only Client Lists are supported. Custom rules do not support Network Lists.

Filter dimensionSupported operatorsSupports empty values?
Client/Network Lists
  • Match Any
  • Does Not Match Any
No