How AWS Security Incident Response Triages Threat Findings

Summary
AWS explains how Security Incident Response ingests and triages threat findings, routes them to archiving or proactive cases, and helps teams monitor the process through dashboards, reports, and GuardDuty.
Key points
- GuardDuty findings are ingested through EventBridge rules; eligible third-party threat findings can enter through Security Hub CSPM.
- The service triages active-threat findings, but leaves posture and compliance findings for customers to address through existing remediation processes.
- Triage evaluates finding data alongside CloudTrail and VPC Flow Logs, AWS threat intelligence, and customer environment context.
- Benign findings are archived; findings that cannot be confirmed as benign may become proactive cases, while posture findings remain current without a case.
- For third-party findings in Security Hub CSPM, triage changes workflow status from NEW to NOTIFIED, then to SUPPRESSED if cleared as benign.
- AWS says fewer than 1% of ingested findings result in a customer-facing escalation across its customers.
- Teams can review triage activity in the proactive response dashboard, monthly report, and archived findings in GuardDuty.
Article Details
- Defense Focus
- Triage threat findings against known-good activity and environmental context to distinguish expected or benign activity from findings that require investigation or a customer response.
- Detection Methods
- Evaluate finding payloads against related AWS activity, threat intelligence, and learned environmental context.
- Compare activity with profiles of trusted IP ranges, domains, IAM principals, and workload behavior.
- Investigate findings that automated triage cannot confirm as benign, including unusual use of temporary instance credentials from outside AWS.
- Review triage activity through the Proactive response dashboard, monthly reports, and archived GuardDuty findings.
- Data Sources
- GuardDuty findings
- Third-party threat detection findings sent to Security Hub CSPM
- Finding payload details, including resource ID, account ID, timestamp, and threat details
- AWS CloudTrail activity
- Amazon VPC Flow Logs
- AWS threat intelligence
- Environmental context, including trusted IP ranges, domains, IAM principals, and workload behavior
- Rule Types
- Amazon EventBridge rules for ingesting GuardDuty findings
- GuardDuty suppression rules for automatically archiving matching future findings
- Defensive Actions
- Ensure third-party findings sent to Security Hub CSPM include complete payload information.
- Submit known-good activity, such as trusted IP ranges and authorized scanning tools, through an AWS Support case to improve environmental context.
- Investigate proactive cases and respond promptly with relevant context.
- Use the dashboard and monthly report to review ingested findings, investigations, escalations, and learned context.
- Review GuardDuty archived findings to confirm triage dispositions; distinguish triage archiving from suppression rules.
- Handle posture and compliance findings through the existing remediation process rather than treating them as active threats.
Vendors
Products
Amazon EventBridgeAWS Security Incident Response ingests threat findings from GuardDuty through Amazon EventBridge rules that are automatically deployed to your accounts during the onboarding process.Amazon GuardDutyAWS Security Incident Response continuously triages the threat findings from Amazon GuardDuty and AWS Security Hub CSPM, but most of that work never shows up as a case.Amazon VPC Flow LogsIt evaluates the finding payload, related AWS activity from AWS CloudTrail and Amazon VPC Flow Logs, AWS threat intelligence, and the context you provide about your environment.AWS CloudTrailIt evaluates the finding payload, related AWS activity from AWS CloudTrail and Amazon VPC Flow Logs, AWS threat intelligence, and the context you provide about your environment.AWS EC2finding: temporary credentials created on an Amazon Elastic Compute Cloud (Amazon EC2) instance were used from an IP address outside AWS.AWS Identity and Access ManagementEscalated – The IP is in a hosting-provider range with no prior association to your accounts, and the AWS Identity and Access Management (IAM) role has never made calls from outside AWS.AWS Security Hub CSPMAWS Security Incident Response continuously triages the threat findings from Amazon GuardDuty and AWS Security Hub CSPM, but most of that work never shows up as a case.AWS Security Incident ResponseAWS Security Incident Response continuously triages the threat findings from Amazon GuardDuty and AWS Security Hub CSPM, but most of that work never shows up as a case.
