Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update unusual outbound traffic alert #644

Merged
merged 5 commits into from
Oct 3, 2024
Merged

Update unusual outbound traffic alert #644

Show file tree
Hide file tree
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
ef03708
Added filter for total_MB
hardikhdholariya Sep 26, 2024
bee7759
Added macro
hardikhdholariya Sep 26, 2024
d83d51f
macro value changes
hardikhdholariya Sep 26, 2024
6fe6a04
updated the condition
hardikhdholariya Sep 27, 2024
a666ce9
updated the min MB value
hardikhdholariya Sep 27, 2024
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
5 changes: 4 additions & 1 deletion cyences_app_for_splunk/default/macros.conf
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -386,6 +386,9 @@ definition = 0.5
# no. of packets in millions
definition = 0.5

[cs_network_outbound_min_MB_traffic]
definition = 10
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure on this value

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As outbound traffic varies for each src_ip maybe we can keep the minimal value 1 MB to avoid the false positives.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The problem is what if someone sending empty packets to attack the firewall somehow?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, correct but this is outbound traffic so I guess this is not a case of attacker, right?

actually upperbound value becomes 0 due to very low traffic. Can we use the max value of the traffic instead of avg. traffic only when avg. traffic is 0? this way we can see some valid upperbound instead 0.


# O365
[cs_o365_authorizationpolicy_change_internal_filter]
definition = search *
Expand Down Expand Up @@ -1644,4 +1647,4 @@ iseval = 0

[cs_f5_bigip_not_blocked_attacks_filter]
definition = search *
iseval = 0
iseval = 0
4 changes: 2 additions & 2 deletions cyences_app_for_splunk/default/savedsearches.conf
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3040,7 +3040,7 @@ search = | tstats `cs_summariesonly_network_traffic` sum(All_Traffic.bytes) as t
| fields - total_m_packets_] \
| stats sum(total_m_packets) as total_m_packets, sum(total_MB) as total_MB, list(dest_ip_mix) as dest_ip_mix, list(action_mix) as actions by src_ip \
| eval top5_dest_ip=mvindex(dest_ip_mix,0,4) | fields - dest_ip_mix \
| where total_m_packets>`cs_network_outbound_min_m_packets` \
| where total_m_packets>`cs_network_outbound_min_m_packets` AND total_MB> `cs_network_outbound_min_MB_traffic` \
| lookup cs_outbound_network_traffic_upperbound.csv src_ip \
| where total_m_packets>upperBound_total_m_packets OR total_MB > upperBound_total_MB \
| eval cyences_severity = case(total_m_packets>upperBound_total_m_packets*3 OR total_MB>upperBound_total_MB*3, "critical", total_m_packets>upperBound_total_m_packets*2 OR total_MB>upperBound_total_MB*2, "high", true(), "medium") \
Expand Down Expand Up @@ -6623,4 +6623,4 @@ action.cyences_notable_event_action.system_compromised_drilldown = `cs_f5_bigip
action.cyences_notable_event_action.attacker_search = | stats count by ip_client
action.cyences_notable_event_action.attacker_drilldown = `cs_f5_bigip_asm` ip_client="*" dest_ip="*" severity IN ("critical","high","medium") enforcement_action!=block attack_type!="JSON Parser Attack" ip_client=$row.ip_client$
action.cyences_send_email_action = 1
action.cyences_notable_event_action.products = F5 BIGIP
action.cyences_notable_event_action.products = F5 BIGIP