Skip to content

Commit

Permalink
[Serverless][Pt. Duex] Adding value list file size constraints to UI …
Browse files Browse the repository at this point in the history
…docs (#311)

* First draft

* Yara's input

* Adding updated text
  • Loading branch information
nastasha-solomon committed May 20, 2024
1 parent 13dc357 commit 2608635
Showing 1 changed file with 7 additions and 4 deletions.
11 changes: 7 additions & 4 deletions docs/rules/value-lists-exceptions.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -28,11 +28,12 @@ You can also use a value list as the <DocLink id="serverlessSecurityRulesUiCreat
<div id="create-value-lists"></div>

## Create value lists
When creating a value list for a rule exception, be mindful of the list's size and data type. In general, all rule types support value list exceptions, but there are some limitations for especially large lists or certain data types. The following value list types can _only_ be used with custom query, machine learning, and indicator match rule types:

* Keyword or IP address lists with more than 65,536 values
* IP range lists with more than 200 dash notation values (for example, `127.0.0.1-127.0.0.4` is one value) or more than 65,536 CIDR notation values
* Text data type lists of any size
When you create a value list for a rule exception, be mindful of the list's size and data type. All rule types support value list exceptions, but extremely large lists or certain data types have limitations.

Custom query, machine learning, and indicator match rules support the following value list types and sizes:
* **Keywords** or **IP addresses** list types with more than 65,536 values
* **IP ranges** list type with over 200 dash notation values (for example, `127.0.0.1-127.0.0.4` is one value) or more than 65,536 CIDR notation values

To create a value list:

Expand All @@ -46,6 +47,8 @@ To create a value list:

* Wildcards are not supported in value lists. Values must be literal values.

* The maximum accepted file size is 9 million bytes.

</DocCallOut>

1. Go to **Rules****Detection rules (SIEM)**.
Expand Down

0 comments on commit 2608635

Please sign in to comment.