Detection: ASL AWS IAM AccessDenied Discovery Events

Description

The following analytic identifies excessive AccessDenied events within an hour timeframe for IAM users in AWS. It leverages AWS CloudTrail logs to detect multiple failed access attempts from the same source IP and user identity. This activity is significant as it may indicate that an access key has been compromised and is being misused for unauthorized discovery actions. If confirmed malicious, this could allow attackers to gather information about the AWS environment, potentially leading to further exploitation or privilege escalation.

1`amazon_security_lake` api.response.error=AccessDenied OR api.response.error=OperationNotPermittedException OR api.response.error=*Unauthorized* actor.user.type=IAMUser 
2| bucket _time span=1h 
3| stats count as failures min(_time) as firstTime max(_time) as lastTime, dc(api.operation) as dc_operation, dc(api.service.name) as dc_service 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 >= 5 AND dc_operation >= 1 AND dc_service >= 1 
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_accessdenied_discovery_events_filter`

Data Source

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

Macros Used

Name Value
amazon_security_lake sourcetype=aws:asl
asl_aws_iam_accessdenied_discovery_events_filter search *
asl_aws_iam_accessdenied_discovery_events_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
Exploitation
DE.AE
CIS 10
Scattered Spider

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 Risk Event True
This configuration file applies to all detections of type anomaly. These detections will use Risk Based Alerting.

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

It is possible to start this detection will need to be tuned by source IP or user. In addition, change the count values to an upper threshold to restrict false positives.

Associated Analytic Story

Risk Based Analytics (RBA)

Risk Message:

User $user$ is seen to perform excessive number of discovery related api calls- $failures$, within an hour where the access was denied.

Risk Object Risk Object Type Risk Score Threat Objects
user user 10 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