Skip to content

Commit b1fbcc0

Browse files
authored
Merge pull request #381 from splunk/container_bug
updated manifests for container implantation
2 parents 9ae3889 + 7c53ce1 commit b1fbcc0

File tree

3 files changed

+17
-15
lines changed

3 files changed

+17
-15
lines changed

detections/container_implant_aws_detection.yml

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ confidence: medium
33
creation_date: '2020-02-20'
44
data_metadata:
55
data_models:
6-
- Vulnerabilities
6+
- Cloud_Infrastructure
77
data_source:
88
- AWS Cloud Trail logs
99
data_sourcetypes:
@@ -17,14 +17,13 @@ detect:
1717
splunk:
1818
correlation_rule:
1919
notable:
20-
nes_fields: awsRegion
21-
rule_description: An AWS instance is started in a new, previously unseen,
22-
region
23-
rule_title: AWS instance is started in a new region
20+
nes_fields: image_id, src_user, region, user_type
21+
rule_description: A new container with image id $image_id$ uploaded to AWS ECR by user $src_user$
22+
rule_title: New container uploaded to AWS ECR
2423
risk:
25-
risk_object: awsRegion
24+
risk_object: src_user
2625
risk_object_type:
27-
- other
26+
- user
2827
risk_score: 30
2928
macros:
3029
- container_implant_aws_detection_filter
@@ -40,6 +39,10 @@ how_to_implement: You must install the AWS App for Splunk (version 5.1.0 or lat
4039
AWS (version 4.4.0 or later), then configure your CloudTrail inputs. You must also install Cloud Infrastructure data model.
4140
id: f0f70b40-f7ad-489d-9905-23d149da8099
4241
known_false_positives: Uploading container is a normal behavior from developers or users with access to container registry.
42+
investigations:
43+
- id: 6027623f-7d10-4847-af3b-8d7e87970451
44+
name: Investigate AWS ECR container listing activity
45+
type: splunk
4346
maintainers:
4447
- company: Splunk
4548

detections/container_implant_gcp_detection.yml

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ confidence: medium
33
creation_date: '2020-02-20'
44
data_metadata:
55
data_models:
6-
- Vulnerabilities
6+
- Cloud_Infrastructure
77
data_source:
88
- google:gcp:pubsub:messages
99
providing_technologies:
@@ -13,14 +13,13 @@ detect:
1313
splunk:
1414
correlation_rule:
1515
notable:
16-
nes_fields: awsRegion
17-
rule_description: An AWS instance is started in a new, previously unseen,
18-
region
19-
rule_title: AWS instance is started in a new region
16+
nes_fields: src_user, account, bucket_name, event_name
17+
rule_description: An GCP GCR container uploaded by $src_user$
18+
rule_title: GCP GCR container uploaded
2019
risk:
21-
risk_object: awsRegion
20+
risk_object: src_user
2221
risk_object_type:
23-
- other
22+
- user
2423
risk_score: 30
2524
macros:
2625
- container_implant_gcp_detection_filter

stories/container_implant_story.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ description: Use the searches in this story to monitor your Kubernetes registry
1010
and Azure Container Registry.
1111
detections:
1212
- detection_id: f0f70b40-f7ad-489d-9905-23d149da8099
13-
name: AWS ECR container uploaded
13+
name: New container uploaded to AWS ECR
1414
type: splunk
1515
- detection_id: 4f00ca88-e766-4605-ac65-ae51c9fd185b
1616
name: GCP GCR container uploaded

0 commit comments

Comments
 (0)