Detection: Cisco NVM - Osascript Network Connection for a Long Duration

Description

This analytic detects the usage of the Utility osascript on a macOS device initiated a network connection lasting longer than 10 minutes (600 seconds). Adversaries may abuse osascript and AppleScript shell execution to establish long-lived command-and-control or remote connections.

1`cisco_network_visibility_module_flowdata`
2(
3    parent_process_name="osascript"
4    OR
5    process_name="osascript"
6)

FSS stands for Flow Start Seconds FES stands for Flow End Seconds

 1
 2| eval duration=fes-fss
 3
 4
 5| where duration>600
 6
 7
 8| stats count min(_time) as firstTime
 9              max(_time) as lastTime
10              values(parent_process_hash) as parent_process_hash
11              values(process_hash) as process_hash
12              values(dest_port) as dest_port
13              values(dest_hostname) as dest_hostname
14              values(http_method) as http_method
15by src dest transport parent_process_path parent_process_name
16   parent_process parent_process_id process_path process_name
17   process process_id user duration
18
19
20| eval duration=tostring(duration)." seconds"
21
22
23| `security_content_ctime(firstTime)`
24
25| `security_content_ctime(lastTime)`
26
27| `cisco_nvm___osascript_network_connection_for_a_long_duration_filter`

Data Source

Name Platform Sourcetype Source
Cisco Network Visibility Module Flow Data Network icon Network 'cisco:nvm:flowdata:v2' 'not_applicable'

Macros Used

Name Value
cisco_network_visibility_module_flowdata sourcetype IN ("cisco:nvm:flowdata", "cisco:nvm:flowdata:v2")
cisco_nvm___osascript_network_connection_for_a_long_duration_filter search *
cisco_nvm___osascript_network_connection_for_a_long_duration_filter is an empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Annotations

Default Configuration

This detection is configured by default in Splunk Enterprise Security to run with the following settings:

Setting Value
Disabled true
Cron Schedule 0 * * * *
Earliest Time -70m@m
Latest Time -10m@m
Schedule Window auto
Creates Finding (Notable) No
Creates Intermediate Finding (Risk Event) Yes
Anomaly detections generate Intermediate Findings (Risk Events). They do not generate a Finding (Notable) directly.

Implementation

This search requires Network Visibility Module logs, which includes the flow data sourcetype. This search uses an input macro named cisco_network_visibility_module_flowdata. We strongly recommend that you specify your environment-specific configurations (index, source, sourcetype, etc.) for Cisco Network Visibility Module logs. Replace the macro definition with configurations for your Splunk environment. The search also uses a post-filter macro designed to filter out known false positives. The logs are to be ingested using the Splunk Add-on for Cisco Endpoint Security Analytics (CESA) (https://splunkbase.splunk.com/app/4221).

Known False Positives

Legitimate administrative scripting, automation, software deployment, or support workflows that use osascript for long-running network operations.

Associated Analytic Story

Intermediate Findings

Message Entity Field Entity Type Risk Score
The macOS host [$src$] used the Osascript utility with the command line [$process$] and a parent process [$parent_process_name$] to initiate a network connection to [$dest$] lasting [$duration$]. src system 20

Threat Objects

Field Type
dest ip_address
process_name process_name
parent_process_name process_name

References

Detection Testing

Test Type Status Dataset Source Sourcetype
Validation Passing N/A N/A N/A
Unit Passing Dataset not_applicable cisco:nvm:flowdata:v2
Integration ✅ Passing Dataset not_applicable cisco:nvm:flowdata:v2

Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range


Source: GitHub |

Version: 1