Cloud environments
Cloud data is reachable through APIs; collection is often just authorized reads by the wrong party. Without object-level logging it may be impossible to determine what was read.
TA0009Tactic 12 of 15
How do attackers collect data from cloud storage?
Collection covers techniques for locating and gathering the data an adversary is after — documents, databases, code, messages — usually as preparation for exfiltration or extortion. In cloud environments it frequently looks like ordinary authorized reads by an identity that should not be making them.
The adversary is trying to gather data of interest to their goal.
Collection consists of techniques adversaries may use to gather information and the sources information is collected from that are relevant to following through on the adversary's objectives. Frequently, the next goal after collecting data is to either steal (exfiltrate) the data or to use the data to gain more information about the target environment. Common target sources include various drive types, browsers, audio, video, and email. Common collection methods include capturing screenshots and keyboard input.
Cloud data is reachable through APIs; collection is often just authorized reads by the wrong party. Without object-level logging it may be impossible to determine what was read.
S3 GetObject, DynamoDB Scan, RDS snapshot creation, Athena queries over data lakes and reading code repositories are typical collection activities.
AI assistants connected to broad document sets can collect on an adversary’s behalf; ATLAS tracks data collection from AI services.
s3:GetObjectRead objects (data event).dynamodb:ScanRead whole tables.Reading from cloud object storage.
Reading from information repositories (wikis, tickets, document stores).
Reading code repositories, which often contain secrets and architecture.
View on MITRE ATT&CKAutomated collection at scale.
Bulk object reads by one identity
Table scans by unusual principals
For leadership
Whether an incident is "potential exposure" or "confirmed exposure of N records" depends on logging configured before the incident.
Myth
“CloudTrail shows every S3 read.”
Reality
Object-level reads are data events and are not logged unless enabled.
0 of 3 done
Saved only in this browser. Nothing is sent to Securitain.
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