AWS access key compromise response
How an AI SOC responds to a leaked or misused AWS access key: trace its calls in CloudTrail, find where it leaked, and deactivate it with approval.
The short answer
An access key compromise means someone other than its owner is calling AWS with a long-lived key. The response traces what the key did, finds how it leaked, and shuts it off. Cotool agents read CloudTrail and current AWS state, and a person approves the shutdown.[1][2][8]
The problem
How an AI SOC handles it
Example
aws cloudtrail lookup-events \
--lookup-attributes AttributeKey=AccessKeyId,AttributeValue=AKIAIOSFODNN7EXAMPLE \
--max-results 50LookupEvents filters on one attribute at a time, here the access key ID, and covers management events in the current Region from the last 90 days.[9][13]
What people approve
How Cotool handles it
- Cotool's Detect page shows a coding agent building a detection for AWS access keys created outside Terraform, testing it on 30 days of logs, and deploying it.[7]
Integrations used
Sources
- AWS S3/SQS log ingest (Cotool docs) · accessed November 16, 2026
- AI SOC (Cotool) · accessed November 16, 2026
- Threat hunting (Cotool Hunt) · accessed November 16, 2026
- GitHub integration (Cotool docs) · accessed November 16, 2026
- Slack integration (Cotool docs) · accessed November 16, 2026
- Alerts (Cotool docs) · accessed November 16, 2026
- Detection engineering (Cotool Detect) · accessed November 16, 2026
- Valid Accounts: Cloud Accounts, T1078.004 (MITRE ATT&CK) · accessed November 16, 2026
- LookupEvents (AWS CloudTrail API Reference) · accessed November 16, 2026
- CloudTrail record contents (AWS CloudTrail User Guide) · accessed November 16, 2026
- SecurityAudit managed policy (AWS) · accessed November 16, 2026
- Exporting GuardDuty findings (Amazon GuardDuty User Guide) · accessed November 16, 2026
- LookupAttribute (AWS CloudTrail API Reference) · accessed November 16, 2026


