Detection: Detect new user AWS Console Login

REMOVED DETECTION

This detection has been removed from the Splunk Threat Research content library and is no longer maintained or supported.

Reason: Detections updated to use the new search logic and field names due to the TA update

Removed in version: 5.2.0

Replacement: Detect AWS Console Login by New User

If you have any questions or concerns, please reach out to us at research@splunk.com.

Description

This search looks for AWS CloudTrail events wherein a console login event 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. Deprecated now this search is updated to use the Authentication datamodel.

 1`cloudtrail` eventName=ConsoleLogin 
 2| rename userIdentity.arn as user 
 3| stats earliest(_time) as firstTime latest(_time) as lastTime by user 
 4| inputlookup append=t previously_seen_users_console_logins  
 5| stats min(firstTime) as firstTime max(lastTime) as lastTime by user 
 6| eval userStatus=if(firstTime >= relative_time(now(), "-70m@m"), "First Time Logging into AWS Console","Previously Seen User") 
 7| `security_content_ctime(firstTime)`
 8|`security_content_ctime(lastTime)`
 9| where userStatus ="First Time Logging into AWS Console"  
10| `detect_new_user_aws_console_login_filter`

Data Source

No data sources specified for this detection.

Macros Used

Name Value
cloudtrail sourcetype=aws:cloudtrail
detect_new_user_aws_console_login_filter ``
detect_new_user_aws_console_login_filter is an empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Annotations

- MITRE ATT&CK
+ Kill Chain Phases
+ NIST
+ CIS
- Threat Actors
ID Technique Tactic
T1078.004 Cloud Accounts Initial Access

Default Configuration

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

Setting Value
Disabled true
Cron Schedule N/A
Earliest Time N/A
Latest Time N/A
Schedule Window N/A
Creates Finding (Notable) No
Creates Intermediate Finding (Risk Event) No
Hunting detections do not generate a Finding (Notable) or Intermediate Findings (Risk Events).

Implementation

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 AWS CloudTrail inputs. Run the "Previously seen users in AWS 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 AWS CloudTrail" hourly (or more frequently depending on how often you run the detection searches) to refresh the baselines.

Known False Positives

When a legitimate new user logins for the first time, this activity will be detected. Check how old the account is and verify that the user activity is legitimate.

Associated Analytic Story

Detection Testing

Test Type Status Dataset Source Sourcetype
Validation Not Applicable N/A N/A N/A
Unit Not Applicable N/A N/A N/A

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: 5