Check ID:
Provider: AWS
Service:
Severity: CRITICAL
Categories:
Resource type:
cloudtrail_threat_detection_enumerationProvider: AWS
Service:
cloudtrailSeverity: CRITICAL
Categories:
threat-detectionResource type:
AwsCloudTrailTrailWhat this check verifies
CloudTrail activity is analyzed for AWS identities executing a broad mix of discovery APIs likeList*, Describe*, and Get* within a recent time window.
An identity exceeding a configurable ratio of these actions indicates potential enumeration behavior by that principal.
Risk
Concentrated discovery activity signals reconnaissance with valid credentials. Adversaries can map assets and policies to enable privilege escalation, target data stores for exfiltration (confidentiality), and identify services to disrupt (availability), supporting stealthy lateral movement.Recommendation
Apply least privilege to limitList*/Describe*/Get* to necessary resources and roles; use separation of duties.
- Enforce MFA and short-lived sessions
- Use SCPs to curb unnecessary discovery
- Baseline expected reads and alert on spikes as defense in depth
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
aws iam update-access-key —user-name <USER_NAME> —access-key-id <ACCESS_KEY_ID> —status Inactive
References
- https://medium.com/falconforce/falconfriday-detecting-enumeration-in-aws-0xff25-orangecon-25-edition-4aee83651088
- https://www.elastic.co/guide/en/security/8.19/aws-discovery-api-calls-via-cli-from-a-single-resource.html
- https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-concepts.html#cloudtrail-concepts-logging-data-events
- https://aws.plainenglish.io/aws-cloudtrail-event-cheatsheet-a-detection-engineers-guide-to-critical-api-calls-part-1-04fb1588556f
- https://support.icompaas.com/support/solutions/articles/62000233455-ensure-there-are-no-potential-enumeration-threats-in-cloudtrail-
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = cloudtrail_threat_detection_enumeration. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks