guardduty-file-modification-sfn-response-cdk: Automated incident response for GuardDuty findings#3229
Open
NithinChandranR-AWS wants to merge 1 commit into
Conversation
…t response Automated incident response for Amazon GuardDuty sensitive file modification findings. AWS Step Functions classifies severity and routes: HIGH (>=7) -> AWS Lambda isolates instance (replace SG, forensic snapshot, tag) + Amazon SNS alert. MEDIUM -> notify only. LOW -> log. 6 services composed: Amazon GuardDuty, Amazon EventBridge, AWS Step Functions, AWS Lambda, Amazon SNS, Amazon EC2. Fundamentally different from existing guardduty-malware-s3 (S3 object scanning, SAM, notify only). This pattern handles host-level runtime threats with automated orchestrated response.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Detect sensitive file modifications with Amazon GuardDuty, classify severity, and auto-isolate compromised instances via AWS Step Functions and AWS Lambda.
Architecture
Amazon GuardDuty → Amazon EventBridge → AWS Step Functions (severity classification) → Response actions:
What makes this different from existing guardduty-malware-s3
Deployed and Tested
Stack deploys in us-east-1 (~130s). 13 CloudFormation resources created including the EventBridge rule matching GuardDuty file modification and unauthorized access findings.