Name:Kubernetes newly seen UDP edge id:49b7daca-4e3c-4899-ba15-9a175e056fa9 version:3 date:2024-10-17 author:Matthew Moore, Splunk status:experimental type:Anomaly Description:The following analytic detects UDP communication between a newly seen source and destination workload pair within a Kubernetes cluster. It leverages Network Performance Monitoring metrics collected via an OTEL collector and pulled from Splunk Observability Cloud. This detection compares network activity over the last hour with the past 30 days to identify new inter-workload communication. Such changes in network behavior can indicate potential security threats or anomalies. If confirmed malicious, unauthorized connections may enable attackers to infiltrate the application ecosystem, leading to data breaches, privilege escalation, lateral movement, or disruption of critical services. Data_source:
search:| mstats count(udp.packets) as udp.packets_count where `kubernetes_metrics` AND earliest=-1h by k8s.cluster.name source.workload.name dest.workload.name | eval current="True" | append [ mstats count(udp.packets) as udp.packets_count where `kubernetes_metrics` AND earliest=-30d latest=-1h by source.workload.name dest.workload.name | eval current="false" ] | eventstats values(current) as current by source.workload.name dest.workload.name | search current="true" current!="false" | rename k8s.cluster.name as host | `kubernetes_newly_seen_udp_edge_filter`
how_to_implement:To gather NPM metrics the Open Telemetry to the Kubernetes Cluster and enable Network Performance Monitoring according to instructions found in Splunk Docs https://docs.splunk.com/observability/en/infrastructure/network-explorer/network-explorer-setup.html#network-explorer-setup In order to access those metrics from within Splunk Enterprise and ES, the Splunk Infrastructure Monitoring add-on must be installed and configured on a Splunk Search Head. Once installed, first configure the add-on with your O11y Cloud Org ID and Access Token. Lastly set up the add-on to ingest metrics from O11y cloud using the following settings, and any other settings left at default:
* Name sim_npm_metrics_to_metrics_index
* Metric Resolution 10000 known_false_positives:unknown References: -https://github.com/signalfx/splunk-otel-collector-chart drilldown_searches:
: tags: analytic_story: - 'Abnormal Kubernetes Behavior using Splunk Infrastructure Monitoring' asset_type:Kubernetes confidence:50 impact:50 message:Kubernetes newly seen UDP edge in kubernetes cluster $host$ mitre_attack_id: - 'T1204' observable: name:'host' type:'Hostname' - role: - 'Victim' product: - 'Splunk Enterprise' - 'Splunk Enterprise Security' - 'Splunk Cloud' required_fields: - 'k8s.cluster.name' - 'source.workload.name' - 'dest.workload.name' - 'udp.packets' risk_score:25 security_domain:network
