MITRE ATT&CK technique · T1580

Cloud Infrastructure Discovery

What does cloud infrastructure discovery look like in AWS? Once inside, adversaries enumerate compute, storage, snapshots, databases and networking to find valuable targets and understand defenses. In AWS this is a sequence of Describe/List API calls that look very similar to legitimate tooling.

DiscoveryPlatforms: IaaSATT&CK v20.1 · source modified · View on MITRE ATT&CK

For leadership

Executive takeaway

Discovery is noisy and comes before damage. Baselines for non-human identities give defenders their best early warning.

How it works in AWS

  1. Describe instances, volumes, snapshots and security groups.
  2. List buckets and databases, then probe access.
  3. Use automated tools that try many APIs and record which succeed.

What the attacker needs

  • Read permissions (Describe*/List*)

Relevant AWS API calls

AWS API calls relevant to T1580
API / eventWhy it matters
ec2:DescribeInstances / DescribeSnapshotsCompute and backup inventory.
s3:ListAllMyBucketsStorage inventory.
rds:DescribeDBInstancesDatabase inventory.

A risky permission is not an observed attack

Potential exposure

Workload roles with ReadOnlyAccess they do not need.

Observed behavior

Bursts of Describe/List calls across many services, often with AccessDenied errors.

Preventive and limiting controls

  • Remove broad read permissions from workloads
  • Use last-accessed data to trim permissions

Mapped cloud controls

  • restrictiveLeast-privilege identity policies

    Broad Describe*/List* permissions across services make reconnaissance trivial; scoping them reduces what a stolen identity reveals.

  • detectiveManaged threat detection across accounts and regions

    GuardDuty includes anomaly-based findings for unusual discovery API activity by an identity.

See assumptions and validation evidence in the Cloud Control Explorer →

Detection signals and telemetry

  • High-cardinality API enumeration from one identity — CloudTrail; GuardDuty discovery findings

MITRE detection strategies (official, cloud-relevant analytics)

  • DET0169 Detection Strategy for Cloud Infrastructure Discovery
    • AN0481 (IaaS): Defenders should monitor for suspicious enumeration of cloud infrastructure components via APIs or CLI tools. Observable behaviors include repeated listing or description operations for compute instances, snapshots, storage buckets, and volumes.Log sources: AWS:CloudTrail — DescribeInstances; AWS:CloudTrail — ListBuckets; AWS:CloudTrail — DescribeDBInstances

MITRE mitigations

Official MITRE description (excerpt)

An adversary may attempt to discover infrastructure and resources that are available within an infrastructure-as-a-service (IaaS) environment. This includes compute service resources such as instances, virtual machines, and snapshots as well as resources of other services including the storage and database services.

Common misconceptions

“Describe permissions cannot hurt us.”
They map the environment and sometimes return sensitive configuration such as user data.

Attack scenarios using this technique

References

MITRE ATT&CK® and ATT&CK® are registered trademarks of The MITRE Corporation. ATT&CK data © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation (ATT&CK v20.1). Securitain is not affiliated with or endorsed by MITRE. Explanations, scenarios and control mappings on this page are Securitain’s own analysis. Sources and licensing

Stay in the loop

Cloud security insights, early access & compliance updates

Weekly InsightsEarly AccessExpert Content
No spam, everUnsubscribe anytimeWeekly updates
Chat with Securitain