From 3c62e835df39363c175c7631dfa16df7bf8af778 Mon Sep 17 00:00:00 2001 From: d1vious Date: Tue, 19 Jul 2022 12:59:03 -0400 Subject: [PATCH] removing --- .../deprecated/gcp_gcr_container_uploaded.yml | 49 ------------------- .../new_container_uploaded_to_aws_ecr.yml | 47 ------------------ 2 files changed, 96 deletions(-) delete mode 100644 detections/deprecated/gcp_gcr_container_uploaded.yml delete mode 100644 detections/experimental/cloud/new_container_uploaded_to_aws_ecr.yml diff --git a/detections/deprecated/gcp_gcr_container_uploaded.yml b/detections/deprecated/gcp_gcr_container_uploaded.yml deleted file mode 100644 index 4f3ce415e5..0000000000 --- a/detections/deprecated/gcp_gcr_container_uploaded.yml +++ /dev/null @@ -1,49 +0,0 @@ -name: GCP GCR container uploaded -id: 4f00ca88-e766-4605-ac65-ae51c9fd185b -version: 1 -date: '2020-02-20' -author: Rod Soto, Rico Valdez, Splunk -type: Hunting -datamodel: [] -description: This search show information on uploaded containers including source - user, account, action, bucket name event name, http user agent, message and destination - path. -search: '|tstats count min(_time) as firstTime max(_time) as lastTime FROM datamodel=Cloud_Infrastructure.Storage - where Storage.event_name=storage.objects.create by Storage.src_user Storage.account - Storage.action Storage.bucket_name Storage.event_name Storage.http_user_agent Storage.msg - Storage.object_path | `drop_dm_object_name("Storage")` | `gcp_gcr_container_uploaded_filter` ' -how_to_implement: You must install the GCP App for Splunk (version 2.0.0 or later), - then configure stackdriver and set a subpub subscription to be imported to Splunk. - You must also install Cloud Infrastructure data model. Please also customize the - `container_implant_gcp_detection_filter` macro to filter out the false positives. -known_false_positives: Uploading container is a normal behavior from developers or - users with access to container registry. GCP GCR registers container upload as a - Storage event, this search must be considered under the context of CONTAINER upload - creation which automatically generates a bucket entry for destination path. -references: [] -tags: - analytic_story: - - Container Implantation Monitoring and Investigation - asset_type: GCP GCR Container - mitre_attack_id: - - T1525 - product: - - Splunk Enterprise - - Splunk Enterprise Security - - Splunk Cloud - required_fields: - - _time - security_domain: threat - kill_chain_phases: - - Exploitation - confidence: 50 - impact: 50 - risk_score: 25 - context: - - Unknown - message: tbd - observable: - - name: field - type: Unknown - role: - - Unknown diff --git a/detections/experimental/cloud/new_container_uploaded_to_aws_ecr.yml b/detections/experimental/cloud/new_container_uploaded_to_aws_ecr.yml deleted file mode 100644 index b56038ae4e..0000000000 --- a/detections/experimental/cloud/new_container_uploaded_to_aws_ecr.yml +++ /dev/null @@ -1,47 +0,0 @@ -name: New container uploaded to AWS ECR -id: f0f70b40-f7ad-489d-9905-23d149da8099 -version: 1 -date: '2020-02-20' -author: Rod Soto, Rico Valdez, Splunk -type: Hunting -datamodel: [] -description: This searches show information on uploaded containers including source - user, image id, source IP user type, http user agent, region, first time, last time - of operation (PutImage). These searches are based on Cloud Infrastructure Data Model. -search: '| tstats count min(_time) as firstTime max(_time) as lastTime FROM datamodel=Cloud_Infrastructure.Compute - where Compute.user_type!="AssumeRole" AND Compute.http_user_agent="AWS Internal" - AND Compute.event_name="PutImage" by Compute.image_id Compute.src_user Compute.src - Compute.region Compute.msg Compute.user_type | `drop_dm_object_name("Compute")` - | `new_container_uploaded_to_aws_ecr_filter` ' -how_to_implement: 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. You must also install Cloud Infrastructure data model. Please also customize - the `container_implant_aws_detection_filter` macro to filter out the false positives. -known_false_positives: Uploading container is a normal behavior from developers or - users with access to container registry. -references: [] -tags: - analytic_story: - - Container Implantation Monitoring and Investigation - asset_type: AWS ECR container - mitre_attack_id: - - T1525 - product: - - Splunk Enterprise - - Splunk Enterprise Security - - Splunk Cloud - required_fields: - - _time - security_domain: threat - confidence: 50 - impact: 50 - risk_score: 25 - context: [] - observable: - - name: user - type: User - role: - - Victim - message: tbd - kill_chain_phases: - - Exploitation