Azure Kubernetes Sensitive Role Access
Identifies when ClusterRoles/Roles are being modified or deleted.
Detection logic
Detection requirements
- Platform
- ContainersESXiIaaSLinuxmacOSSaaSWindows
The rule states no platform. This is derived from the 3 ATT&CK techniques it maps to.
- Log source product
- azure
- Log source service
- activitylogs
Known benign triggers
- ClusterRoles/Roles being modified and deleted may be performed by a system administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment.
- ClusterRoles/Roles modification from unfamiliar users should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
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 |
|---|---|
| learn.microsoft.com/en-us/azure/role-based-access-control/resource-provider-operations#microsoftkubernetes | 29 |
| medium.com/mitre-engenuity/att-ck-for-containers-now-available-4c2359654bf1 | 7 |
| www.microsoft.com/security/blog/2020/04/02/attack-matrix-kubernetes/ | 9from 2 sources |
| www.microsoft.com/security/blog/2021/03/23/secure-containerized-environments-with-updated-threat-matrix-for-kubernetes/ | 7 |
From the source
- At source
- Open at source
- Upstream identifier
- 818fee0c-e0ec-4e45-824e-83e4817b0887
- Tagged by the source as
- attack.impact
Licence
- Published under
- Detection Rule License 1.1Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Aug 26, 2026
- Version
- 1