Skip to content

updated manifests for container implantation #381

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
patel-bhavin merged 1 commit into from
Mar 2, 2020
Merged

updated manifests for container implantation #381

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 10 additions & 7 deletions detections/container_implant_aws_detection.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ confidence: medium
creation_date: '2020-02-20'
data_metadata:
data_models:
- Vulnerabilities
- Cloud_Infrastructure
data_source:
- AWS Cloud Trail logs
data_sourcetypes:
Expand All @@ -17,14 +17,13 @@ detect:
splunk:
correlation_rule:
notable:
nes_fields: awsRegion
rule_description: An AWS instance is started in a new, previously unseen,
region
rule_title: AWS instance is started in a new region
nes_fields: image_id, src_user, region, user_type
rule_description: A new container with image id $image_id$ uploaded to AWS ECR by user $src_user$
rule_title: New container uploaded to AWS ECR
risk:
risk_object: awsRegion
risk_object: src_user
risk_object_type:
- other
- user
risk_score: 30
macros:
- container_implant_aws_detection_filter
Expand All @@ -40,6 +39,10 @@ how_to_implement: You must install the AWS App for Splunk (version 5.1.0 or lat
AWS (version 4.4.0 or later), then configure your CloudTrail inputs. You must also install Cloud Infrastructure data model.
id: f0f70b40-f7ad-489d-9905-23d149da8099
known_false_positives: Uploading container is a normal behavior from developers or users with access to container registry.
investigations:
- id: 6027623f-7d10-4847-af3b-8d7e87970451
name: Investigate AWS ECR container listing activity
type: splunk
maintainers:
- company: Splunk
email: rsoto@splunk.com, rvaldez@splunk.com
Expand Down
13 changes: 6 additions & 7 deletions detections/container_implant_gcp_detection.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ confidence: medium
creation_date: '2020-02-20'
data_metadata:
data_models:
- Vulnerabilities
- Cloud_Infrastructure
data_source:
- google:gcp:pubsub:messages
providing_technologies:
Expand All @@ -13,14 +13,13 @@ detect:
splunk:
correlation_rule:
notable:
nes_fields: awsRegion
rule_description: An AWS instance is started in a new, previously unseen,
region
rule_title: AWS instance is started in a new region
nes_fields: src_user, account, bucket_name, event_name
rule_description: An GCP GCR container uploaded by $src_user$
rule_title: GCP GCR container uploaded
risk:
risk_object: awsRegion
risk_object: src_user
risk_object_type:
- other
- user
risk_score: 30
macros:
- container_implant_gcp_detection_filter
Expand Down
2 changes: 1 addition & 1 deletion stories/container_implant_story.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ description: Use the searches in this story to monitor your Kubernetes registry
and Azure Container Registry.
detections:
- detection_id: f0f70b40-f7ad-489d-9905-23d149da8099
name: AWS ECR container uploaded
name: New container uploaded to AWS ECR
type: splunk
- detection_id: 4f00ca88-e766-4605-ac65-ae51c9fd185b
name: GCP GCR container uploaded
Expand Down