From 7115026c8125446252c7c10a66571055c62c7c8c Mon Sep 17 00:00:00 2001 From: Bhavin Patel Date: Thu, 22 Jun 2023 14:46:26 -0700 Subject: [PATCH 1/2] mionr --- detections/cloud/aws_createaccesskey.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/detections/cloud/aws_createaccesskey.yml b/detections/cloud/aws_createaccesskey.yml index 1181ecea20..21a1fcc341 100644 --- a/detections/cloud/aws_createaccesskey.yml +++ b/detections/cloud/aws_createaccesskey.yml @@ -5,7 +5,7 @@ date: '2022-03-03' author: Bhavin Patel, Splunk status: production type: Hunting -This detection rule monitors for the creation of AWS Identity and Access Management (IAM) access keys. +description: This detection rule monitors for the creation of AWS Identity and Access Management (IAM) access keys. An IAM access key consists of an access key ID and secret access key, which are used to sign programmatic requests to AWS services. While IAM access keys can be legitimately used by developers and administrators for API access, their creation can also be indicative of malicious activity. Attackers who have gained unauthorized access to an AWS environment might create access keys as a means to From 7f22bbcaece4bb529715c890c978ab6c4ba21240 Mon Sep 17 00:00:00 2001 From: Bhavin Patel Date: Thu, 22 Jun 2023 16:32:04 -0700 Subject: [PATCH 2/2] missing asl --- detections/cloud/asl_aws_createaccesskey.yml | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/detections/cloud/asl_aws_createaccesskey.yml b/detections/cloud/asl_aws_createaccesskey.yml index b735fa3f8b..acdb12b90f 100644 --- a/detections/cloud/asl_aws_createaccesskey.yml +++ b/detections/cloud/asl_aws_createaccesskey.yml @@ -5,10 +5,16 @@ date: '2022-05-23' author: Patrick Bareiss, Splunk status: experimental type: Hunting -description: This search looks for AWS CloudTrail events where a user A who has already - permission to create access keys, makes an API call to create access keys for another - user B. Attackers have been know to use this technique for Privilege Escalation - in case new victim(user B) has more permissions than old victim(user B) +description: This detection rule monitors for the creation of AWS Identity and Access Management (IAM) access keys. + An IAM access key consists of an access key ID and secret access key, which are used to sign programmatic requests to AWS services. + While IAM access keys can be legitimately used by developers and administrators for API access, their creation can also be indicative + of malicious activity. Attackers who have gained unauthorized access to an AWS environment might create access keys as a means to + establish persistence or to exfiltrate data through the APIs. Moreover, because access keys can be used to authenticate with AWS + services without the need for further interaction, they can be particularly appealing for bad actors looking to operate under the radar. + Consequently, it's important to vigilantly monitor and scrutinize access key creation events, especially if they are associated with + unusual activity or are created by users who don't typically perform these actions. This hunting query identifies when a potentially compromised user + creates a IAM access key for another user who may have higher privilleges, which can be a sign for privilege escalation. Hunting queries are designed to be executed + manual during threat hunting. data_source: [] search: '`amazon_security_lake` api.operation=CreateAccessKey http_request.user_agent!=console.amazonaws.com api.response.error=null | rename unmapped{}.key as unmapped_key , unmapped{}.value as unmapped_value