-
Notifications
You must be signed in to change notification settings - Fork 137
Add Snort configuration customization guidance to DPI topic #2537
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.
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -121,6 +121,13 @@ | |
| * you use a paid subscription to a Snort ruleset | ||
| * you have written your own Snort rules. | ||
|
|
||
| Beyond custom rules, if you have a paid Snort subscription, you can also customize Snort configuration to fine-tune how DPI generates alerts. For example, you can: | ||
| * **Limit alert rates** to reduce the volume of alerts generated for noisy rules | ||
| * **Suppress alerts** for specific rules or traffic sources that are known to be benign | ||
| * **Apply rate filters** to dynamically change alert behavior based on traffic patterns | ||
|
|
||
| These customizations are managed through the Snort configuration file (`snort.lua`) and are mounted into the DPI container using the same initContainers mechanism described below. For details on configuring filters, suppressions, and rate limits, see the [Snort3 documentation](https://docs.snort.org/). | ||
|
Check failure on line 129 in calico-enterprise/threat/deeppacketinspection.mdx
|
||
|
||
|
|
||
| :::important | ||
| If you install custom Snort rules, $[prodname] will stop updating the community rules with each minor release. | ||
| You will be responsible for making sure your rules are up to date. | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -121,6 +121,13 @@ | |
| * you use a paid subscription to a Snort ruleset | ||
| * you have written your own Snort rules. | ||
|
|
||
| Beyond custom rules, if you have a paid Snort subscription, you can also customize Snort configuration to fine-tune how DPI generates alerts. For example, you can: | ||
| * **Limit alert rates** to reduce the volume of alerts generated for noisy rules | ||
| * **Suppress alerts** for specific rules or traffic sources that are known to be benign | ||
| * **Apply rate filters** to dynamically change alert behavior based on traffic patterns | ||
|
|
||
| These customizations are managed through the Snort configuration file (`snort.lua`) and are mounted into the DPI container using the same initContainers mechanism described below. For details on configuring filters, suppressions, and rate limits, see the [Snort3 documentation](https://docs.snort.org/). | ||
|
Check failure on line 129 in calico-enterprise_versioned_docs/version-3.20-2/threat/deeppacketinspection.mdx
|
||
|
||
|
|
||
| :::important | ||
| If you install custom Snort rules, $[prodname] will stop updating the community rules with each minor release. | ||
| You will be responsible for making sure your rules are up to date. | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -121,6 +121,13 @@ | |
| * you use a paid subscription to a Snort ruleset | ||
| * you have written your own Snort rules. | ||
|
|
||
| Beyond custom rules, if you have a paid Snort subscription, you can also customize Snort configuration to fine-tune how DPI generates alerts. For example, you can: | ||
| * **Limit alert rates** to reduce the volume of alerts generated for noisy rules | ||
| * **Suppress alerts** for specific rules or traffic sources that are known to be benign | ||
| * **Apply rate filters** to dynamically change alert behavior based on traffic patterns | ||
|
|
||
| These customizations are managed through the Snort configuration file (`snort.lua`) and are mounted into the DPI container using the same initContainers mechanism described below. For details on configuring filters, suppressions, and rate limits, see the [Snort3 documentation](https://docs.snort.org/). | ||
|
Check failure on line 129 in calico-enterprise_versioned_docs/version-3.21-2/threat/deeppacketinspection.mdx
|
||
|
||
|
|
||
| :::important | ||
| If you install custom Snort rules, $[prodname] will stop updating the community rules with each minor release. | ||
| You will be responsible for making sure your rules are up to date. | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This paragraph says Snort configuration customizations are "mounted" via the same
initContainersmechanism shown below, but the steps below only demonstrate copying rule files into/usr/etc/snort/rules/. Consider clarifying the wording (mount vs copy) and add a brief note/example of how to providesnort.lua(including the target path) using that mechanism.