Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
7 changes: 7 additions & 0 deletions calico-cloud/threat/deeppacketinspection.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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-cloud/threat/deeppacketinspection.mdx

View workflow job for this annotation

GitHub Actions / runner / vale

[vale] reported by reviewdog 🐶 [Vale.Spelling] Did you really mean 'suppressions'? Raw Output: {"message": "[Vale.Spelling] Did you really mean 'suppressions'?", "location": {"path": "calico-cloud/threat/deeppacketinspection.mdx", "range": {"start": {"line": 129, "column": 217}}}, "severity": "ERROR"}

Check failure on line 129 in calico-cloud/threat/deeppacketinspection.mdx

View workflow job for this annotation

GitHub Actions / runner / vale

[vale] reported by reviewdog 🐶 [Vale.Spelling] Did you really mean 'initContainers'? Raw Output: {"message": "[Vale.Spelling] Did you really mean 'initContainers'?", "location": {"path": "calico-cloud/threat/deeppacketinspection.mdx", "range": {"start": {"line": 129, "column": 139}}}, "severity": "ERROR"}
Copy link

Copilot AI Feb 19, 2026

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 initContainers mechanism 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 provide snort.lua (including the target path) using that mechanism.

Copilot uses AI. Check for mistakes.

:::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.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -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-cloud_versioned_docs/version-22-2/threat/deeppacketinspection.mdx

View workflow job for this annotation

GitHub Actions / runner / vale

[vale] reported by reviewdog 🐶 [Vale.Spelling] Did you really mean 'suppressions'? Raw Output: {"message": "[Vale.Spelling] Did you really mean 'suppressions'?", "location": {"path": "calico-cloud_versioned_docs/version-22-2/threat/deeppacketinspection.mdx", "range": {"start": {"line": 129, "column": 217}}}, "severity": "ERROR"}

Check failure on line 129 in calico-cloud_versioned_docs/version-22-2/threat/deeppacketinspection.mdx

View workflow job for this annotation

GitHub Actions / runner / vale

[vale] reported by reviewdog 🐶 [Vale.Spelling] Did you really mean 'initContainers'? Raw Output: {"message": "[Vale.Spelling] Did you really mean 'initContainers'?", "location": {"path": "calico-cloud_versioned_docs/version-22-2/threat/deeppacketinspection.mdx", "range": {"start": {"line": 129, "column": 139}}}, "severity": "ERROR"}

:::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.
Expand Down
7 changes: 7 additions & 0 deletions calico-enterprise/threat/deeppacketinspection.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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

View workflow job for this annotation

GitHub Actions / runner / vale

[vale] reported by reviewdog 🐶 [Vale.Spelling] Did you really mean 'suppressions'? Raw Output: {"message": "[Vale.Spelling] Did you really mean 'suppressions'?", "location": {"path": "calico-enterprise/threat/deeppacketinspection.mdx", "range": {"start": {"line": 129, "column": 217}}}, "severity": "ERROR"}

Check failure on line 129 in calico-enterprise/threat/deeppacketinspection.mdx

View workflow job for this annotation

GitHub Actions / runner / vale

[vale] reported by reviewdog 🐶 [Vale.Spelling] Did you really mean 'initContainers'? Raw Output: {"message": "[Vale.Spelling] Did you really mean 'initContainers'?", "location": {"path": "calico-enterprise/threat/deeppacketinspection.mdx", "range": {"start": {"line": 129, "column": 139}}}, "severity": "ERROR"}
Copy link

Copilot AI Feb 19, 2026

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 initContainers mechanism 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 provide snort.lua (including the target path) using that mechanism.

Copilot uses AI. Check for mistakes.

:::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.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -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

View workflow job for this annotation

GitHub Actions / runner / vale

[vale] reported by reviewdog 🐶 [Vale.Spelling] Did you really mean 'suppressions'? Raw Output: {"message": "[Vale.Spelling] Did you really mean 'suppressions'?", "location": {"path": "calico-enterprise_versioned_docs/version-3.20-2/threat/deeppacketinspection.mdx", "range": {"start": {"line": 129, "column": 217}}}, "severity": "ERROR"}

Check failure on line 129 in calico-enterprise_versioned_docs/version-3.20-2/threat/deeppacketinspection.mdx

View workflow job for this annotation

GitHub Actions / runner / vale

[vale] reported by reviewdog 🐶 [Vale.Spelling] Did you really mean 'initContainers'? Raw Output: {"message": "[Vale.Spelling] Did you really mean 'initContainers'?", "location": {"path": "calico-enterprise_versioned_docs/version-3.20-2/threat/deeppacketinspection.mdx", "range": {"start": {"line": 129, "column": 139}}}, "severity": "ERROR"}
Copy link

Copilot AI Feb 19, 2026

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 initContainers mechanism 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 provide snort.lua (including the target path) using that mechanism.

Copilot uses AI. Check for mistakes.

:::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.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -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

View workflow job for this annotation

GitHub Actions / runner / vale

[vale] reported by reviewdog 🐶 [Vale.Spelling] Did you really mean 'initContainers'? Raw Output: {"message": "[Vale.Spelling] Did you really mean 'initContainers'?", "location": {"path": "calico-enterprise_versioned_docs/version-3.21-2/threat/deeppacketinspection.mdx", "range": {"start": {"line": 129, "column": 139}}}, "severity": "ERROR"}
Copy link

Copilot AI Feb 19, 2026

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 initContainers mechanism 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 provide snort.lua (including the target path) using that mechanism.

Copilot uses AI. Check for mistakes.

:::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.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -121,6 +121,13 @@ You may want to install your own rules if:
* 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/).

:::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.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -121,6 +121,13 @@ You may want to install your own rules if:
* 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/).

:::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.
Expand Down
Loading