Unusual Group Name Accessed by a User
A machine learning job has detected a user accessing an uncommon group name for privileged operations, indicating potential privileged access activity. This indicates that a user has accessed a group name that is…
Description
A machine learning job has detected a user accessing an uncommon group name for privileged operations, indicating potential privileged access activity. This indicates that a user has accessed a group name that is unusual for their typical operations, particularly for actions requiring elevated privileges. This could point to an attempt to manipulate group memberships or escalate privileges on a system.
Detection logic
Its licence does not clear it for publishing here
Sunturai publishes a detection's own text where the licence it arrived under has been reviewed and permits it, and Elastic License 2.0 has not. The query as its source wrote it, its canonical form and the hash that pins this revision are in the workspace record.
Detection requirements
- Platform
- ContainersESXiIaaSIdentity ProviderLinuxmacOSNetwork DevicesOffice SuiteSaaSWindows
The rule states no platform. This is derived from the 4 ATT&CK techniques it maps to.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| docs.elastic.co/en/integrations/pad | 21 |
| www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html | 103 |
From the source
- At source
- Open at source
- Upstream identifier
- fb5d91d0-3b94-4f91-bf20-b6fbc4b2480a
- Tagged by the source as
- Data Source: Windows Security Event LogsDomain: EndpointOS: WindowsPlatform: WindowsResources: Investigation GuideRule Type: Machine LearningRule Type: MLTactic: Privilege EscalationUse Case: Privileged Access Detection
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Sep 20, 2026
- Version
- 2