This search looks for cloud provisioning activities from previously unseen IP addresses. Provisioning activities are defined broadly as any event that runs or creates something.
- Type: Anomaly
- Product: Splunk Security Analytics for AWS, Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Datamodel: Change
- Last Updated: 2020-08-16
- Author: Rico Valdez, Splunk
- ID: f86a8ec9-b042-45eb-92f4-e9ed1d781078
|T1078||Valid Accounts||Defense Evasion, Persistence, Privilege Escalation, Initial Access|
| tstats earliest(_time) as firstTime, latest(_time) as lastTime, values(All_Changes.object_id) as object_id from datamodel=Change where (All_Changes.action=started OR All_Changes.action=created) All_Changes.status=success by All_Changes.src, All_Changes.user, All_Changes.command | `drop_dm_object_name("All_Changes")` | lookup previously_seen_cloud_provisioning_activity_sources src as src OUTPUT firstTimeSeen, enough_data | eventstats max(enough_data) as enough_data | where enough_data=1 | eval firstTimeSeenSrc=min(firstTimeSeen) | where isnull(firstTimeSeenSrc) OR firstTimeSeenSrc > relative_time(now(), `previously_unseen_cloud_provisioning_activity_window`) | table firstTime, src, user, object_id, command | `cloud_provisioning_activity_from_previously_unseen_ip_address_filter` | `security_content_ctime(firstTime)`
Associated Analytic Story
How To Implement
You must be ingesting your cloud infrastructure logs from your cloud provider. You should run the baseline search
Previously Seen Cloud Provisioning Activity Sources - Initial to build the initial table of source IP address, geographic locations, and times. You must also enable the second baseline search
Previously Seen Cloud Provisioning Activity Sources - Update to keep this table up to date and to age out old data. You can adjust the time window for this search by updating the
previously_unseen_cloud_provisioning_activity_window macro. You can also provide additional filtering for this search by customizing the
Kill Chain Phase
Known False Positives
This is a strictly behavioral search, so we define "false positive" slightly differently. Every time this fires, it will accurately reflect the first occurrence in the time period you're searching within, plus what is stored in the cache feature. But while there are really no "false positives" in a traditional sense, there is definitely lots of noise.
This search will fire any time a new IP address is seen in the GeoIP database for any kind of provisioning activity. If you typically do all provisioning from tools inside of your country, there should be few false positives. If you are located in countries where the free version of MaxMind GeoIP that ships by default with Splunk has weak resolution (particularly small countries in less economically powerful regions), this may be much less valuable to you.
|42.0||70||60||User $user$ is starting or creating an instance $object_id$ for the first time from IP address $src$|
source | version: 1