Branch was auto-updated.

baselines/previously_seen_users_in_cloudtrail.yml

@@ -5,16 +5,16 @@ date: '2018-04-30'
 description: This search looks for CloudTrail events where a user logs into the console,
   then creates a baseline of the latest and earliest times, City, Region, and Country
   we have encountered this user in our dataset, grouped by ARN, within the last 30
-  days.
+  days. NOTE - This baseline search is deprecated and has been updated to use the Authentication Datamodel
 how_to_implement: You must install the AWS App for Splunk (version 5.1.0 or later)
   and Splunk Add-on for AWS (version 4.4.0 or later), then configure your CloudTrail
-  inputs. Please validate the user name entries in `previously_seen_users_console_logins`,
+  inputs. Please validate the user name entries in `previously_seen_users_console_logins_cloudtrail`,
   which is a lookup file created as a result of running this support search.
 author: Jason Brewer, Splunk
 search: '`cloudtrail` eventName=ConsoleLogin | rename userIdentity.arn as user | iplocation
   src | eval City=if(City LIKE "",src,City),Region=if(Region LIKE "",src,Region) |
   stats earliest(_time) as firstTime latest(_time) as lastTime by user src City Region
-  Country | outputlookup previously_seen_users_console_logins | stats count'
+  Country | outputlookup previously_seen_users_console_logins_cloudtrail | stats count'
 tags:
   analytics_story:
   - Suspicious AWS Login Activities

baselines/update_previously_seen_users_in_cloudtrail.yml

@@ -4,18 +4,18 @@ version: 1
 date: '2018-04-30'
 description: This search looks for CloudTrail events where a user logs into the console,
   then updates the baseline of the latest and earliest times, City, Region, and Country
-  we have encountered this user in our dataset, grouped by ARN, within the last hour.
+  we have encountered this user in our dataset, grouped by ARN, within the last hour. NOTE - This baseline search is deprecated and has been updated to use the Authentication Datamodel
 how_to_implement: You must install the AWS App for Splunk (version 5.1.0 or later)
   and Splunk Add-on for AWS (version 4.4.0 or later), then configure your CloudTrail
-  inputs. Please validate the user name entries in `previously_seen_users_console_logins`,
+  inputs. Please validate the user name entries in `previously_seen_users_console_logins_cloudtrail`,
   which is a lookup file created as a result of running this support search.
 author: Jason Brewer, Splunk
 search: '`cloudtrail` eventName=ConsoleLogin | rename userIdentity.arn as user | iplocation
   src | eval City=if(City LIKE "",src,City),Region=if(Region LIKE "",src,Region) |
   stats earliest(_time) AS firstTime latest(_time) AS lastTime by user src City Region
-  Country | inputlookup append=t previously_seen_users_console_logins | stats
+  Country | inputlookup append=t previously_seen_users_console_logins_cloudtrail | stats
   min(firstTime) as firstTime max(lastTime) as lastTime by user src City Region Country
-  | outputlookup previously_seen_users_console_logins'
+  | outputlookup previously_seen_users_console_logins_cloudtrail'
 tags:
   analytics_story:
   - Suspicious AWS Login Activities

detections/cloud/detect_aws_console_login_by_new_user.yml

@@ -9,9 +9,8 @@ description: This search looks for CloudTrail events wherein a console login eve
   the last hour
 how_to_implement: You must install and configure the Splunk Add-on for AWS (version
   5.1.0 or later) and Enterprise Security 6.2, which contains the required updates
-  to the Authentication data model for cloud use cases. Run the `Previously Seen Users
-  in CloudTrail` support search only once to create a baseline of previously seen
-  IAM users within the last 30 days. Run `Update previously seen users in CloudTrail`
+  to the Authentication data model for cloud use cases. Run the `Previously Seen Users in CloudTrail - Initial` support search only once to create a baseline of previously seen
+  IAM users within the last 30 days. Run `Previously Seen Users in CloudTrail - Update`
   hourly (or more frequently depending on how often you run the detection searches)
   to refresh the baselines.
 type: ESCU

detections/cloud/detect_aws_console_login_by_user_from_new_city.yml

@@ -7,13 +7,12 @@ description: This search looks for CloudTrail events wherein a console login eve
   file of previously seen users (by ARN values) who have logged into the console.
   The alert is fired if the user has logged into the console for the first time within
   the last hour
-how_to_implement: You must be ingesting your cloud infrastructure logs from your cloud
-  provider. You should run the baseline search `Previously seen users in CloudTrail
-  - Initial` to build the initial table of source IP address, geographic locations,
-  and times. You must also enable the second baseline search `Previously Seen users
-  in Cloudtrail - Update` to keep this table up to date and to age out old data. You
-  can also provide additional filtering for this search by customizing the `detect_aws_console_login_by_user_from_new_city_filter`
-  macro.
+how_to_implement: You must install and configure the Splunk Add-on for AWS (version
+  5.1.0 or later) and Enterprise Security 6.2, which contains the required updates
+  to the Authentication data model for cloud use cases. Run the `Previously Seen Users in CloudTrail - Initial` support search only once to create a baseline of previously seen
+  IAM users within the last 30 days. Run `Previously Seen Users in CloudTrail - Update`
+  hourly (or more frequently depending on how often you run the detection searches)
+  to refresh the baselines. You can also provide additional filtering for this search by customizing the `detect_aws_console_login_by_user_from_new_city_filter` macro.
 type: ESCU
 author: Bhavin Patel, Splunk
 search: '| tstats earliest(_time) as firstTime latest(_time) as lastTime from datamodel=Authentication

detections/cloud/detect_aws_console_login_by_user_from_new_country.yml

@@ -7,11 +7,12 @@ description: This search looks for CloudTrail events wherein a console login eve
   file of previously seen users (by ARN values) who have logged into the console.
   The alert is fired if the user has logged into the console for the first time within
   the last hour
-how_to_implement: You must be ingesting your cloud infrastructure logs from your cloud
-  provider. You should run the baseline search `Previously seen users in CloudTrail
-  - Initial` to build the initial table of source IP address, geographic locations,
-  and times. You must also enable the second baseline search `Previously Seen users
-  in Cloudtrail - Update` to keep this table up to date and to age out old data. You
+how_to_implement: You must install and configure the Splunk Add-on for AWS (version
+  5.1.0 or later) and Enterprise Security 6.2, which contains the required updates
+  to the Authentication data model for cloud use cases. Run the `Previously Seen Users in CloudTrail - Initial` support search only once to create a baseline of previously seen
+  IAM users within the last 30 days. Run `Previously Seen Users in CloudTrail - Update`
+  hourly (or more frequently depending on how often you run the detection searches)
+  to refresh the baselines. You
   can also provide additional filtering for this search by customizing the `detect_aws_console_login_by_user_from_new_country_filter`
   macro.
 type: ESCU

detections/cloud/detect_aws_console_login_by_user_from_new_region.yml

@@ -7,11 +7,12 @@ description: This search looks for CloudTrail events wherein a console login eve
   file of previously seen users (by ARN values) who have logged into the console.
   The alert is fired if the user has logged into the console for the first time within
   the last hour
-how_to_implement: You must be ingesting your cloud infrastructure logs from your cloud
-  provider. You should run the baseline search `Previously seen users in CloudTrail
-  - Initial` to build the initial table of source IP address, geographic locations,
-  and times. You must also enable the second baseline search `Previously Seen users
-  in Cloudtrail - Update` to keep this table up to date and to age out old data. You
+how_to_implement: You must install and configure the Splunk Add-on for AWS (version
+  5.1.0 or later) and Enterprise Security 6.2, which contains the required updates
+  to the Authentication data model for cloud use cases. Run the `Previously Seen Users in CloudTrail - Initial` support search only once to create a baseline of previously seen
+  IAM users within the last 30 days. Run `Previously Seen Users in CloudTrail - Update`
+  hourly (or more frequently depending on how often you run the detection searches)
+  to refresh the baselines. You
   can also provide additional filtering for this search by customizing the `detect_aws_console_login_by_user_from_new_region_filter`
   macro.
 type: ESCU

detections/deprecated/detect_new_user_aws_console_login.yml

@@ -6,18 +6,18 @@ description: This search looks for CloudTrail events wherein a console login eve
   by a user was recorded within the last hour, then compares the event to a lookup
   file of previously seen users (by ARN values) who have logged into the console.
   The alert is fired if the user has logged into the console for the first time within
-  the last hour
+  the last hour. Deprecated now this search is updated to use the Authentication datamodel.
 how_to_implement: You must install the AWS App for Splunk (version 5.1.0 or later)
   and Splunk Add-on for AWS (version 4.4.0 or later), then configure your CloudTrail
   inputs. Run the "Previously seen users in CloudTrail" support search only once to
   create a baseline of previously seen IAM users within the last 30 days. Run "Update
   previously seen users in CloudTrail" hourly (or more frequently depending on how
-  often you run the detection searches) to refresh the baselines.
+  often you run the detection searches) to refresh the baselines. 
 type: ESCU
 author: Bhavin Patel, Splunk
 search: '`cloudtrail` eventName=ConsoleLogin | rename userIdentity.arn as user | stats
   earliest(_time) as firstTime latest(_time) as lastTime by user | inputlookup append=t
-  previously_seen_users_console_logins  | stats min(firstTime) as firstTime max(lastTime)
+  previously_seen_users_console_logins_cloudtrail  | stats min(firstTime) as firstTime max(lastTime)
   as lastTime by user | eval userStatus=if(firstTime >= relative_time(now(), "-70m@m"),
   "First Time Logging into AWS Console","Previously Seen User") | `security_content_ctime(firstTime)`|`security_content_ctime(lastTime)`|
   where userStatus ="First Time Logging into AWS Console"  | `detect_new_user_aws_console_login_filter`'