Try in Splunk Security Cloud

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-06-23
  • Author: Rod Soto, Splunk
  • ID: b6013a7b-85e0-4a45-b051-10b252d69569

Annotations

ATT&CK
Kill Chain Phase
  • Exploitation
NIST
CIS20
CVE
1
2
3
4
`aws_cloudwatchlogs_eks` objectRef.resource=clusterroles OR clusterrolebindings sourceIPs{}!=::1 sourceIPs{}!=127.0.0.1  
| table sourceIPs{} user.username user.groups{} objectRef.namespace requestURI annotations.authorization.k8s.io/reason 
| dedup user.username user.groups{} 
|`kubernetes_aws_detect_sensitive_role_access_filter`

Macros

The SPL above uses the following Macros:

:information_source: kubernetes_aws_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 field

  • _time

How To Implement

You must install splunk AWS add on and Splunk App for AWS. This search works with cloudwatch logs.

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

:information_source: 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