Kubernetes Azure detect sensitive role access
THIS IS A DEPRECATED DETECTION
This detection has been marked deprecated by the Splunk Threat Research team. This means that it will no longer be maintained or supported.
Description
This search provides information on Kubernetes accounts accessing sensitve objects such as configmpas or secrets
- Type: Hunting
-
Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Last Updated: 2020-05-20
- Author: Rod Soto, Splunk
- ID: f27349e5-1641-4f6a-9e68-30402be0ad4c
Annotations
ATT&CK
Kill Chain Phase
NIST
- DE.AE
CIS20
- CIS 10
CVE
Search
1
2
3
4
5
6
`kubernetes_azure` category=kube-audit
| spath input=properties.log
| search objectRef.resource=clusterroles OR clusterrolebindings
| table sourceIPs{} user.username user.groups{} objectRef.namespace requestURI annotations.authorization.k8s.io/reason
| dedup user.username user.groups{}
|`kubernetes_azure_detect_sensitive_role_access_filter`
Macros
The SPL above uses the following Macros:
kubernetes_azure_detect_sensitive_role_access_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
Required fields
List of fields required to use this analytic.
- _time
How To Implement
You must install the Add-on for Microsoft Cloud Services and Configure Kube-Audit data diagnostics
Known False Positives
Sensitive role resource access is necessary for cluster operation, however source IP, namespace and user group may indicate possible malicious use.
Associated Analytic Story
RBA
Risk Score | Impact | Confidence | Message |
---|---|---|---|
25.0 | 50 | 50 | tbd |
The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.
Reference
Test Dataset
Replay any dataset to Splunk Enterprise by using our replay.py
tool or the UI.
Alternatively you can replay a dataset into a Splunk Attack Range
source | version: 1