Triage console
INC-01 · 02:05–02:20 · iam-user/deploy-bot, s3/customer-exports
P1 Console login from an unusual location
Why this priority
- Highest severity
- 8.4 / 10
- Asset criticality
- Critical
- Corroboration
- ×2.05 4 signal types · 3 sources
- Confidence
- 80%
- Score
- 100
Evidence summary draft · review before use
4 findings from GuardDuty, Security Hub, CloudWatch appear related: they share an identity or address within 1 hour(s). At least one affected asset is business-critical.
- 02:05 Console login from an unusual location on iam-user/deploy-bot (GuardDuty)
- 02:11 API calls from an unusual network on iam-user/deploy-bot (GuardDuty)
- 02:18 Bucket policy allows public read on s3/customer-exports (Security Hub)
- 02:20 Spike in S3 GetObject requests on s3/customer-exports (CloudWatch)
Suggested next step for the analyst: verify with the asset owner and review access logs for the affected identity.
Findings
- GuardDutyConsole login from an unusual locationSuccessful console sign-in for a service user that normally only uses access keys.
iam-user/deploy-bot · actor 203.0.113.45 · sev 7.2 · conf 80% - GuardDutyAPI calls from an unusual networkListBuckets and GetObject calls from an autonomous system never seen for this identity.
iam-user/deploy-bot · actor 203.0.113.45 · sev 6.8 · conf 75% - Security HubBucket policy allows public readBucket policy changed to allow s3:GetObject for any principal.
s3/customer-exports · actor iam-user/deploy-bot · sev 8.4 · conf 95% - CloudWatchSpike in S3 GetObject requests4,812 GetObject requests in 6 minutes, 40× the usual rate.
s3/customer-exports · actor 203.0.113.45 · sev 5.5 · conf 70%