Detection: ASL AWS IAM Assume Role Policy Brute Force

Updated Date: 2025-01-08 ID: 726959fe-316d-445c-a584-fa187d64e295 Author: Patrick Bareiss, Splunk Type: TTP Product: Splunk Enterprise Security

Description

The following analytic detects multiple failed attempts to assume an AWS IAM role, indicating a potential brute force attack. It leverages AWS CloudTrail logs to identify MalformedPolicyDocumentException errors with a status of failure and filters out legitimate AWS services. This activity is significant as repeated failures to assume roles can indicate an adversary attempting to guess role names, which is a precursor to unauthorized access. If confirmed malicious, this could lead to unauthorized access to AWS resources, potentially compromising sensitive data and services.

Search

1`amazon_security_lake` api.operation="AssumeRole" "api.response.error"=AccessDenied 
2| bucket _time span=1h 
3| stats count as failures min(_time) as firstTime max(_time) as lastTime values(api.operation) as api.operation values(src_endpoint.ip) as src_endpoint.ip values(cloud.region) as cloud.region by actor.user.uid _time 
4| where failures >= 3 
5| rename actor.user.uid as user, src_endpoint.ip as src_ip, cloud.region as region 
6| `security_content_ctime(firstTime)` 
7| `security_content_ctime(lastTime)` 
8| `asl_aws_iam_assume_role_policy_brute_force_filter`

Data Source

Name	Platform	Sourcetype	Source
ASL AWS CloudTrail	AWS	`'aws:asl'`	`'aws_asl'`

Macros Used

Name	Value
amazon_security_lake	`sourcetype=aws:asl`
asl_aws_iam_assume_role_policy_brute_force_filter	`search *`

asl_aws_iam_assume_role_policy_brute_force_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
T1580	Cloud Infrastructure Discovery	Discovery
T1110	Brute Force	Credential Access

Exploitation

DE.CM

CIS 10

Scattered Spider

APT28

APT38

APT39

APT41

Agrius

DarkVishnya

Dragonfly

Ember Bear

FIN5

Fox Kitten

HEXANE

OilRig

Turla

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 Notable	Yes
Rule Title	`%name%`
Rule Description	`%description%`
Notable Event Fields	user, dest
Creates Risk Event	True

This configuration file applies to all detections of type TTP. These detections will use Risk Based Alerting and generate Notable Events.

Implementation

The detection is based on Amazon Security Lake events from Amazon Web Services (AWS), which is a centralized data lake that provides security-related data from AWS services. To use this detection, you must ingest CloudTrail logs from Amazon Security Lake into Splunk. To run this search, ensure that you ingest events using the latest version of Splunk Add-on for Amazon Web Services (https://splunkbase.splunk.com/app/1876) or the Federated Analytics App.

Known False Positives

This detection will require tuning to provide high fidelity detection capabilties. Tune based on src addresses (corporate offices, VPN terminations) or by groups of users.

Associated Analytic Story

AWS IAM Privilege Escalation

Risk Based Analytics (RBA)

Risk Message:

User $user$ has caused multiple failures with errorCode AccessDenied, which potentially means adversary is attempting to identify a role name.

Risk Object	Risk Object Type	Risk Score	Threat Objects
user	user	28	src_ip

References

Detection Testing

Test Type	Status	Dataset	Source	Sourcetype
Validation	✅ Passing	N/A	N/A	N/A
Unit	✅ Passing	Dataset	`aws_asl`	`aws:asl`
Integration	✅ Passing	Dataset	`aws_asl`	`aws:asl`

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