DET0879: Detection of Cloud Accounts
DET0879 is a MITRE detection strategy for identifying activity related to Cloud Accounts, a resource-development technique where adversaries may use compro...
Analyst context for executives and security teams
DET0879 is a MITRE detection strategy for identifying activity related to Cloud Accounts, a resource-development technique where adversaries may use compromised cloud accounts during targeting. Its business value is in helping leaders ask whether the organization can recognize suspicious or unauthorized use of cloud accounts before those accounts support later operations such as cloud storage use, tool upload, or infrastructure acquisition.
Executive priority
Prioritize this as a readiness question rather than a finished detection package: can security, cloud, and identity teams prove they have visibility into cloud account ownership, access changes, and suspicious usage? Because the ATT&CK object has no official detection text or platform scope, executives should treat local telemetry, identity governance, and cloud audit evidence as the deciding factors for coverage.
Technical view
SOC and detection engineering teams should map DET0879 to T1586.003 Cloud Accounts in the resource-development phase. Validate whether logs and controls can distinguish expected cloud account creation, compromise recovery, access changes, storage usage, and account-linked infrastructure activity from abnormal or unauthorized behavior. Since ATT&CK provides no specific detection logic for this object, detections should be built from local identity, cloud control plane, and audit data rather than assumed from the strategy name alone.
Likely telemetry
- Cloud identity and access audit logs
- Cloud account creation, ownership, and configuration records
- Authentication and session activity for cloud accounts
- Access key, token, credential, and permission change events
- Cloud storage access and upload activity where available
Detection direction
- Confirm which cloud accounts are legitimate, who owns them, and what normal access patterns look like before alerting on anomalies.
- Correlate cloud account authentication, permission changes, storage activity, and resource provisioning rather than relying on a single event type.
- Tune for authorized administrative activity, service accounts, automation, and business-approved cloud storage use to reduce false positives.
- Use the relationship to T1586.003 to focus on early-stage resource-development indicators, not only later exfiltration or tool-hosting outcomes.
- Document blind spots where cloud audit logging, identity logs, or account inventory are incomplete.
Mitigation priorities
- Establish authoritative inventory and ownership for cloud accounts.
- Enforce identity governance processes for account creation, access review, and credential lifecycle management.
- Ensure cloud and identity audit logging is enabled, retained, and available to SOC and incident response teams.
- Review permissions and credential exposure paths for cloud accounts that could be repurposed by an adversary.
- Create incident response playbooks for suspected cloud account compromise, including validation, containment, credential reset, and evidence preservation.
Analyst notes and limits
The supplied ATT&CK object is a detection strategy with no official description, no official detection text, and no specified platforms or tactics. The most useful context comes from its relationship to T1586.003 Cloud Accounts, which places the behavior in resource development and describes adversary use of compromised cloud accounts during targeting.
This take does not assert active exploitation, attribution, vendor coverage, or specific platform applicability. Local cloud architecture, identity providers, logging configuration, and account governance records are required to determine practical detection coverage.
Detection of Cloud Accounts
No official description is available in the imported ATT&CK source object.
How security teams should use this page
Treat this object as behavior context, not an attribution claim. Validate the related groups, software, data sources, and mitigations against official ATT&CK relationships and your own telemetry before making control-coverage decisions.
Techniques used
This mirrors the MITRE pattern of making group, software, campaign, and technique relationships scannable. Relationship notes come from mirrored ATT&CK relationship text when available.
| Domain | ID | Name | Relationship / procedure |
|---|---|---|---|
| Enterprise | T1586.003 | Cloud Accounts Sub-technique | This object detects Cloud Accounts. |
All related ATT&CK context
Object version and sync metadata
The fields below describe the current mirrored snapshot. When Glexia retains multiple ATT&CK source imports, you can open the table to compare the same object across releases (hashes and MITRE timestamps). For MITRE’s own release notes and roadmap, see ATT&CK resources — Updates .
Imported snapshots across ATT&CK releases (1)
| Release | Bundle imported | Object version | Modified | Status | Raw hash |
|---|---|---|---|---|---|
| 19.1 | 1.0 | Current bundle | 705715ac8c8e… |
Mirrored ATT&CK source object
The raw object is retained through the mirrored ATT&CK source bundle and object hash. The raw endpoint returns the exact object from the mirrored bundle when available.
External references and citations
MITRE external references are preserved separately from Glexia analysis so citations remain traceable to their original source records.
-
[1]
mitre-attack DET0879Open source URL
Source: MITRE ATT&CK®. © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. MITRE ATT&CK and ATT&CK are registered trademarks of The MITRE Corporation. Glexia is not affiliated with or endorsed by MITRE.