Live Active security incident? Get immediate response
MITRE ATT&CK® Detection Strategy

DET0251: Behavioral Detection of Cloud Group Enumeration via API and CLI Access

DET0251 is a detection strategy for spotting authenticated attempts to enumerate cloud groups and permission settings through API or CLI access. For leader...

EnterpriseDET0251Detection StrategyObject v1.0 Modified
Glexia's Take

Analyst context for executives and security teams

Analyst confidence Medium

DET0251 is a detection strategy for spotting authenticated attempts to enumerate cloud groups and permission settings through API or CLI access. For leaders, the significance is that group and role discovery often helps an intruder understand who has power, where sensitive access paths exist, and what accounts or groups may be useful later in an incident. Even without an official ATT&CK detection description, the related technique clearly points to cloud identity and permissions visibility as the business issue.

Executive priority

Prioritize this as a cloud identity and operational resilience control validation item. Ask whether the organization can prove who is querying cloud groups and roles across SaaS, IaaS, Office Suite, and identity provider environments, and whether unusual enumeration would be visible during an investigation. This supports incident decision-making, IAM governance, audit evidence, and cloud security assurance, especially where group membership drives privileged access.

Technical view

The detection strategy is linked to T1069.003 Cloud Groups under Discovery. SOC and detection teams should validate visibility into authenticated API and CLI activity that lists or queries cloud groups, roles, permissions, and group membership. Because the DET object has no official detection text or platform field, implementation should be driven by the related technique context: SaaS, IaaS, Office Suite, and Identity Provider logs. Where applicable, include monitoring for administrative PowerShell activity such as Get-MsolRole in Microsoft cloud environments, as referenced by ATT&CK.

Likely telemetry

  • Cloud provider audit logs for API calls related to groups, roles, permissions, and membership queries
  • Identity provider audit logs showing authenticated directory, role, or group lookup activity
  • SaaS and Office Suite administrative audit logs
  • CLI and administrative PowerShell execution records where collected
  • User, service account, source IP, device, session, and authentication context associated with enumeration activity

Detection direction

  • Baseline expected group and role lookup behavior for administrators, automation, and service accounts before alerting on volume alone.
  • Look for unusual principals, source locations, devices, timing, or bursts of group/role enumeration activity relative to normal administrative patterns.
  • Correlate enumeration with prior authentication events and subsequent access attempts to privileged groups or accounts.
  • Tune for legitimate IAM administration, compliance reviews, directory synchronization, and automation to reduce false positives.
  • Validate blind spots: missing cloud audit logs, short retention, unmanaged CLI access, limited identity provider logging, and lack of command telemetry for administrative shells.

Mitigation priorities

  • Ensure audit logging is enabled and retained for cloud identity, SaaS, IaaS, and Office Suite administrative activity.
  • Review and minimize permissions that allow broad visibility into groups, roles, and permission settings where business requirements do not justify it.
  • Separate and monitor administrative and automation accounts that legitimately perform directory or group discovery.
  • Use approved administrative workflows and change windows so unexpected enumeration is easier to distinguish.
  • Prepare IR procedures for suspicious cloud discovery activity, including rapid review of the authenticated principal, session context, and any follow-on access changes.
Analyst notes and limits

This take is based on the DET0251 name, external reference, and its relationship to T1069.003 Cloud Groups. The strongest defensive value is validating whether cloud identity discovery activity is observable and explainable, not assuming that every group query is malicious.

The supplied DET object has no official description, no official detection text, and no directly specified platforms or tactics. Platform and tactic context comes from the related T1069.003 technique only. Local cloud architecture, identity provider configuration, logging coverage, and normal administrative behavior are required to make this detection actionable.

Official MITRE ATT&CK definition

Behavioral Detection of Cloud Group Enumeration via API and CLI Access

No official description is available in the imported ATT&CK source object.

View the same entry on attack.mitre.org (MITRE-hosted reference; in-page links above use the Glexia ATT&CK library.)

Glexia analysis

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.

ATT&CK relationship table

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.

1 rows
Domain ID Name Relationship / procedure
Enterprise T1069.003 Cloud Groups Sub-technique This object detects Cloud Groups.
Relationship explorer

All related ATT&CK context

Change history

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 .

ATT&CK release
19.1
Object version
1.0
Created
Modified
Raw hash
7046f2584643eafd...
Imported snapshots across ATT&CK releases (1)
Release Bundle imported Object version Modified Status Raw hash
19.1 1.0 Current bundle 7046f2584643…
Raw source

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.

Source references

External references and citations

MITRE external references are preserved separately from Glexia analysis so citations remain traceable to their original source records.

  1. [1]
    mitre-attack DET0251
    Open source URL
Source and licensing

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.