Analytics Alerts
Browse the Cortex analytics alert reference.
1 alert match the current filters. technique: T1098 ✕
Download CSV Show ATT&CK heatmapA Kubernetes cluster role was created Informational Cloud 3 variations
A Kubernetes cluster role was created.
- Activation:
- 14 Days
- Training:
- 30 Days
- Test:
- N/A (single event)
- Deduplication:
- 1 Day
ATT&CK tactics: Persistence (TA0003) Privilege Escalation (TA0004)ATT&CK techniques: Account Manipulation: Additional Container Cluster Roles (T1098.006)Required data: AWS Audit Log Azure Audit Log Gcp Audit Log Kubernetes Audit LogsDetector tags: Kubernetes - APIAttacker's goals: Create overpermissive cluster roles to escalate privileges within the Kubernetes cluster.Investigative actions: Check the permissions granted to the newly created Kubernetes cluster role. Check whether this cluster role was bound to an identity via a ClusterRoleBinding or RoleBinding. Verify whether the identity that created the cluster role is authorized to perform RBAC operations. Review subsequent API calls made by the same identity for signs of privilege escalation or lateral movement.Variations
Administrative Kubernetes cluster role was created for the first time
Medium overridden
A Kubernetes cluster role with administrative permissions was created for the first time by the identity. overridden
A Kubernetes cluster role with administrative permissions was created
Low overridden
A Kubernetes cluster role with administrative permissions was created. overridden
A Kubernetes cluster role was created for the first time by the identity
Low overridden
A Kubernetes cluster role was created for the first time by the identity. overridden