Repository navigation
Deprecated Detect Large ICMP Traffic Based On .conf Telemetry - #4313
Conversation
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. More of your lovely PRs please. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
| NOT Web.url_domain IN ( | ||
| "-", | ||
| "unknown" | ||
| "-", "unknown", "*tanium.com", "*tailscale.com", "*rapid7.com", "*sophos.com","*sophosupd.com","*beyondtrustcloud.com","*nordcdn.com","*amazonaws.com" |
There was a problem hiding this comment.
This update is no longer needed, since @onurmerdogan is changing the logic to leverage a lookup instead - See https://github.com/splunk/security_content/pull/4328/changes#diff-903092178090db05d6da7eeed46db2edae6c71f128cadaff35e926d1fb2afa40
I will revert this change and continue the discussion in the other PR
Detect Large ICMP Traffic Based On .conf Telemetry
This PR deprecated
Detect Large ICMP Trafficbased on feedback obtained from .conf SOC telemetry