Compromise Accounts: Cloud Accounts T1586.003
Tactic: Resource Development
Adversaries may compromise cloud accounts that can be used during targeting. Adversaries can use compromised cloud accounts to further their operations, including leveraging cloud storage services such as Dropbox, Microsoft OneDrive, or AWS S3 buckets for Exfiltration to Cloud Storage or to Upload Tools. Cloud accounts can also be used in the acquisition of infrastructure, such as Virtual Private Servers or Serverless infrastructure. Additionally, cloud-based messaging services such as Twilio, SendGrid, AWS End User Messaging, AWS SNS (Simple Notification Service), or AWS SES (Simple Email Service) may be leveraged for spam or Phishing. Compromising cloud accounts may allow adversaries to develop sophisticated capabilities without managing their own servers.
Authoring guide
Patterns shared across the 36 rules above: which fields they filter on, what specific values they look for, and what they exclude. The catalog normalizes field names across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.
Fields filtered most (46 distinct)
The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.
Top indicator values (84 distinct)
Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique. Click a value to expand the rules under this technique that use it.
Exclusions (14 distinct)
Field/operator/value combinations excluded by rules under this technique (top-level not() clauses), sorted by how many rules exclude each. These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths. Click a value to expand the rules under this technique that exclude it.
Rules under this technique
Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.
Sigma 1 rule
Splunk 35 rules
- ASL AWS Credential Access GetPasswordData
- ASL AWS Credential Access RDS Password reset
- ASL AWS Multi-Factor Authentication Disabled
- AWS Console Login Failed During MFA Challenge
- AWS Credential Access Failed Login
- AWS Credential Access GetPasswordData
- AWS Credential Access RDS Password reset
- AWS Multi-Factor Authentication Disabled
- AWS Multiple Failed MFA Requests For User
- AWS Successful Single-Factor Authentication
- AWS Unusual Number of Failed Authentications From Ip
- Azure Active Directory High Risk Sign-in
- Azure AD Authentication Failed During MFA Challenge
- Azure AD Multi-Factor Authentication Disabled
- Azure AD Multi-Source Failed Authentications Spike
- Azure AD Multiple Failed MFA Requests For User
- Azure AD Multiple Users Failing To Authenticate From Ip
- Azure AD Successful PowerShell Authentication
- Azure AD Successful Single-Factor Authentication
- Azure AD Unusual Number of Failed Authentications From Ip
- Detect AWS Console Login by New User
- Detect AWS Console Login by User from New City
- Detect AWS Console Login by User from New Country
- Detect AWS Console Login by User from New Region
- GCP Authentication Failed During MFA Challenge
- GCP Multi-Factor Authentication Disabled
- GCP Multiple Failed MFA Requests For User
- GCP Multiple Users Failing To Authenticate From Ip
- GCP Successful Single-Factor Authentication
- GCP Unusual Number of Failed Authentications From Ip
- O365 Multi-Source Failed Authentications Spike
- O365 Multiple Users Failing To Authenticate From Ip
- Okta Authentication Failed During MFA Challenge
- Okta Successful Single Factor Authentication
- Okta User Logins from Multiple Cities