Has collected data from insecure cloud buckets.1
Data from Cloud Storage T1530
- Tactic
- Collection
- Platforms
- IaaS, Office Suite, SaaS
- Version
- 2.2
- Created
- 30 August 2019
- Last modified
- 12 May 2026
- Contributors
- Netskope; Praetorian; AppOmni; Arun Seelagan, CISA
Adversaries may access data from cloud storage.
Data from Cloud Storage MITRE reference T1530
6 groups have been recorded using this technique. Newest first; each entry carries MITRE’s procedure text and a link to the group’s full record. Click a name to filter the rules below.
Had modified Azure Storage account resources through the Microsoft.Storage/storageAccounts/write operation to expose non-remotely accessible accounts for data exfiltration.1
Enumerates data stored in cloud resources for collection and exfiltration purposes.1
Has exfitrated data from OneDrive.1
Has obtained files from the victim's cloud storage instances.1
All 6 groups for this technique
2 campaigns have been recorded using this technique. Listed newest first; dates are year-granularity and attribution is MITRE’s.
During the 2025 Poland Wiper Attacks, the adversaries leveraged stolen credentials within cloud services to download targeted data from SharePoint, and Teams.1
During C0027, Scattered Spider accessed victim OneDrive environments to search for VPN and MFA enrollment information, help desk instructions, and new hire guides.1
All 2 campaigns for this technique
4 software entries are documented implementing this technique. MITRE files each as a tool or as malware; newest first, then by how many groups carry them.
Has the ability to scan cloud storage services for credentials to include Amazon (AWS) S3 and Google Cloud Storage.12
Can enumerate and download files stored in AWS storage services, such as S3 buckets.1
Can dump the contents of AWS S3 buckets. It can also retrieve service account tokens from kOps buckets in Google Cloud Storage or S3.1
Can collect files from a user’s OneDrive.1
All 4 software entries for this technique
Offense vs defense T1530
Is defensive coverage keeping up with adversary use? Eight counts, each ranked against all 697 ATT&CK techniques. Attack sits left, defense right, so a shape leaning left means adversaries are better documented here than defenders are equipped. Hover any spoke for its percentile and the share of techniques that have more. The timeline below shows when each side arrived.
How it got here
Adversary activity (campaign spans) over cumulative rule output. Each source is plotted independently from zero, so neither line includes the other. Campaign dates are year-granularity.
Data from Cloud Storage detection strategy DET0484
MITRE names one behaviour worth catching for this technique and breaks it into 3 analytics, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Multi-Platform Cloud Storage Exfiltration Behavior Chain
AN1328 · IaaS
Spike in object access from new IAM user or role followed by data exfiltration to external IPs
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| User Account MetadataDC0013 | AWS:CloudTrail | AssumeRole |
| Cloud Storage AccessDC0025 | AWS:CloudTrail | GetObject, CopyObject |
| Network Traffic ContentDC0085 | AWS:VPCFlowLogs | Unusual volume of data transferred from S3 storage endpoints to non-corporate IPs |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| TimeWindow | Timeframe for data transfer correlation (e.g., 10 minutes) |
| ExternalIPAllowList | Known list of corporate and expected outbound IP addresses |
AN1329 · SaaS
OAuth token granted to external app followed by download of high-volume files in OneDrive/Google Drive
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Cloud Storage AccessDC0025 | m365:unified | FileAccessed, FileDownloaded, ConsentGranted |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| AppRegistrationNamePattern | Pattern of suspicious OAuth app names (e.g., rclone, mega, backup*) |
| DownloadThresholdMB | Flag file downloads over X MB (e.g., >100MB) within short intervals |
AN1330 · Office Suite
Internal user account accesses shared links outside org followed by mass file download
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| User Account AuthenticationDC0002 | azure:signinlogs | SigninSuccess |
| Cloud Storage AccessDC0025 | m365:sharepoint | AnonymousLinkCreated, FileDownloaded |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| LinkVisibilityScope | Whether links allow anonymous/external access |
| DownloadBurstThreshold | # of files downloaded within <5 mins (e.g., >50 files) |
Frequently check permissions on cloud storage to ensure proper permissions are set to deny open or unprivileged access to resources.
Encrypt data stored at rest in cloud storage. Managed encryption keys can be rotated by most providers. At a minimum, ensure an incident response plan to storage breach includes rotating the keys and test for impact on client applications.
Cloud service providers support IP-based restrictions when accessing cloud resources. Consider using IP allowlisting along with user account management to ensure that data access is restricted not only to valid users but only from expected IP ranges to mitigate the use of stolen credentials to access data.
Consider using multi-factor authentication to restrict access to resources and cloud storage APIs.
Use access control lists on storage systems and objects.
Configure user permissions groups and roles for access to cloud storage. Implement strict Identity and Access Management (IAM) controls to prevent access to storage solutions except for the applications, users, and services that require access. Ensure that temporary access tokens are issued rather than permanent credentials, especially when access is being granted to entities outside of the internal security boundary.
Tests from Atomic Red Team (MIT licence) · technique definition