WARNING THIS IS A EXPERIMENTAL object
We have not been able to test, simulate, or build datasets for this object. Use at your own risk. This analytic is NOT supported.
This search looks for network traffic defined by port and transport layer protocol in the Enterprise Security lookup table “lookup_interesting_ports”, that is marked as prohibited, and has an associated ‘allow’ action in the Network_Traffic data model. This could be indicative of a misconfigured network device.
- Type: TTP
- Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Datamodel: Network_Traffic
- Last Updated: 2020-07-21
- Author: Rico Valdez, Splunk
- ID: ce5a0962-849f-4720-a678-753fe6674479
|T1048||Exfiltration Over Alternative Protocol||Exfiltration|
Kill Chain Phase
- Command & Control
- CIS 9
- CIS 12
1 2 3 4 5 6 7 8 | tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) as lastTime from datamodel=Network_Traffic where All_Traffic.action = allowed by All_Traffic.src_ip All_Traffic.dest_ip All_Traffic.dest_port All_Traffic.action | lookup update=true interesting_ports_lookup dest_port as All_Traffic.dest_port OUTPUT app is_prohibited note transport | search is_prohibited=true | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `drop_dm_object_name("All_Traffic")` | `prohibited_network_traffic_allowed_filter`
The SPL above uses the following Macros:
Note that prohibited_network_traffic_allowed_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
How To Implement
In order to properly run this search, Splunk needs to ingest data from firewalls or other network control devices that mediate the traffic allowed into an environment. This is necessary so that the search can identify an ‘action’ taken on the traffic of interest. The search requires the Network_Traffic data model be populated.
Known False Positives
Associated Analytic story
source | version: 2