This search provides detection of users with KMS keys performing encryption specifically against S3 buckets.
- Type: Anomaly
Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Last Updated: 2022-11-11
- Author: Rod Soto, Patrick Bareiss Splunk
- ID: 884a5f59-eec7-4f4a-948b-dbde18225fdc
Kill Chain Phase
- Actions On Objectives
- CIS 10
1 2 3 4 5 6 `cloudtrail` eventName=CopyObject requestParameters.x-amz-server-side-encryption="aws:kms" | rename requestParameters.bucketName AS bucketName, requestParameters.x-amz-copy-source AS src_file, requestParameters.key AS dest_file | stats count min(_time) as firstTime max(_time) as lastTime values(bucketName) as bucketName values(src_file) AS src_file values(dest_file) AS dest_file values(userAgent) AS userAgent values(region) AS region values(src) AS src by user | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` |`aws_detect_users_with_kms_keys_performing_encryption_s3_filter`
The SPL above uses the following Macros:
aws_detect_users_with_kms_keys_performing_encryption_s3_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
List of fields required to use this analytic.
How To Implement
You must install Splunk AWS add on and Splunk App for AWS. This search works with AWS CloudTrail logs
Known False Positives
There maybe buckets provisioned with S3 encryption
Associated Analytic Story
|15.0||30||50||User $user$ with KMS keys is performing encryption, against S3 buckets on these files $dest_file$|
The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.
source | version: 2