Kubernetes Azure pod scan fingerprint
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 of unauthenticated requests via source IP user agent, request URI and response status data against Kubernetes cluster pod in Azure
- Type: Hunting
-
Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Last Updated: 2020-05-20
- Author: Rod Soto, Splunk
- ID: 86aad3e0-732f-4f66-bbbc-70df448e461d
Annotations
ATT&CK
Kill Chain Phase
NIST
- DE.AE
CIS20
- CIS 10
CVE
Search
1
2
3
4
5
`kubernetes_azure` category=kube-audit
| spath input=properties.log
| search responseStatus.code=401
| table sourceIPs{} userAgent verb requestURI responseStatus.reason properties.pod
|`kubernetes_azure_pod_scan_fingerprint_filter`
Macros
The SPL above uses the following Macros:
kubernetes_azure_pod_scan_fingerprint_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
Not all unauthenticated requests are malicious, but source IPs, userAgent, verb, request URI and response status will provide context.
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