detection.wiki

DaemonSets

OperationDescriptionSampleRule
get-daemonsetsYY
list-daemonsetsYY
watch-daemonsetsYY
create-daemonsetsDaemonSet created (runs on every node; used for lateral movement / persistence).YY
update-daemonsetsYY
patch-daemonsetsDaemonSet patched (sidecar injection or workload modification).YY
delete-daemonsetsYN
deletecollection-daemonsetsYN
get-daemonsets-statusYN
update-daemonsets-statusYN
patch-daemonsets-statusYN
any-daemonsetsSynthetic aggregation for rules that filter the daemonsets resource with no specific verb. Not a distinct audit record; hosts rule listings that key on objectRef.resource alone.NN

get daemonsets

#
Resource
daemonsets

Example Audit Event #

{
  "kind": "Event",
  "apiVersion": "audit.k8s.io/v1",
  "level": "Metadata",
  "auditID": "00000000-0000-0000-0000-000000000000",
  "stage": "ResponseComplete",
  "requestURI": "/apis/apps/v1/namespaces/dw-harn/daemonsets/dw-harn-daemonsets",
  "verb": "get",
  "user": {
    "username": "kubernetes-admin",
    "groups": [
      "kubeadm:cluster-admins",
      "system:authenticated"
    ],
    "extra": {
      "authentication.kubernetes.io/credential-id": [
        "X509SHA256=9bb0383c49b319fbf6b5ed61ab944378956d4292c784d32244ce2fa4dd846a3c"
      ]
    }
  },
  "sourceIPs": [
    "203.0.113.10"
  ],
  "userAgent": "kubectl/v1.36.2 (linux/amd64) kubernetes/24e2b02",
  "objectRef": {
    "resource": "daemonsets",
    "namespace": "dw-harn",
    "name": "dw-harn-daemonsets",
    "apiGroup": "apps",
    "apiVersion": "v1"
  },
  "responseStatus": {
    "metadata": {},
    "code": 200
  },
  "requestReceivedTimestamp": "2026-07-02T04:47:28.833154Z",
  "stageTimestamp": "2026-07-02T04:47:28.834546Z",
  "annotations": {
    "authorization.k8s.io/decision": "allow",
    "authorization.k8s.io/reason": "RBAC: allowed by ClusterRoleBinding \"kubeadm:cluster-admins\" of ClusterRole \"cluster-admin\" to Group \"kubeadm:cluster-admins\""
  }
}

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Elastic #

  • Direct Interactive Kubernetes API Request by Unusual Utilities source low: This rule leverages a combination of Defend for Containers and Kubernetes audit logs to detect the execution of direct interactive Kubernetes API requests via unusual utilities. An adversary may need to execute direct interactive Kubernetes API requests to gain access to the Kubernetes API server or other resources within the cluster. These requests are often used to enumerate the Kubernetes API server or other resources within the cluster, and may indicate an attempt to move laterally within the cluster.T1059, T1059.004, T1069, T1087, T1609, T1610↳ also matches list-daemonsets: list daemonsets, watch-daemonsets: watch daemonsets, create-daemonsets: create daemonsets, update-daemonsets: update daemonsets, patch-daemonsets: patch daemonsets
    Investigation guide

    Triage and analysis#

    Disclaimer: This investigation guide was created using generative AI technology and has been reviewed to improve its accuracy and relevance. While every effort has been made to ensure its quality, we recommend validating the content and adapting it to suit your specific environment and operational needs.

    Investigating Direct Interactive Kubernetes API Request by Unusual Utilities#

    This rule detects interactive commands executed inside containers that use atypical utilities to hit the Kubernetes API, paired with near-simultaneous API activity on pods, secrets, service accounts, roles/bindings, or pod exec/attach/log/portforward. It surfaces hands-on-keyboard discovery and lateral movement using custom scripts that evade common tool allowlists; for example, an intruder opens a shell in a pod, uses Python to query the in-cluster API to list secrets, then triggers pods/exec to pivot into another workload.

    Possible investigation steps#

    • Identify the implicated pod, container image, and executing service account, then quickly review its RBAC bindings and effective permissions to determine blast radius.
    • Inspect the container’s interactive session context by pulling recent command lines, shell history, environment variables, and mounted service account tokens, and look for custom scripts or binaries issuing HTTP requests.
    • Correlate nearby Kubernetes audit entries tied to the same principal and pod to map accessed resources and verbs, noting any exec/attach/portforward or sensitive object interactions across namespaces.
    • Review network activity from the pod to the API server and any in-pod proxies, including DNS lookups and outbound connections, to spot nonstandard clients or tunneling behavior.
    • If suspicious, isolate the pod or node, capture runtime artifacts (e.g., process memory or HTTP client traffic), revoke and rotate the service account credentials, and verify image provenance and integrity.

    False positive analysis#

    • An operator interactively attaches to a pod and uses a Python REPL or bash with /dev/tcp to call the in-cluster API for routine troubleshooting (e.g., list pods, read ConfigMaps, or run selfsubjectaccessreviews), producing normal audit entries that match the rule signature.
    • A correlation artifact arises when two namespaces have pods with the same name: one pod starts an interactive shell while another independently performs get/list/watch calls, and the 1-second sequence keyed only on pod-name links the unrelated events.

    Response and remediation#

    • Immediately isolate the implicated pod that issued direct API calls using a nonstandard utility by applying a deny-all egress NetworkPolicy in its namespace (including to kubernetes.default.svc:443), terminating the interactive session, and scaling its owning Deployment/Job/StatefulSet to zero replicas.
    • Before teardown, capture a runtime snapshot of the container and node including the binary or script used to query the API (e.g., files under /tmp or /dev/tcp usage), shell history, environment, and the mounted service account token and CA bundle at /var/run/secrets/kubernetes.io/serviceaccount/.
    • Revoke access by removing the service account’s RoleBindings/ClusterRoleBindings, deleting all pods that mount that service account to force token rotation, rotating any Secrets and ConfigMaps that were read or created during the window, and deleting any unauthorized Jobs, CronJobs, or Deployments created by the same principal.
    • Restore workloads from a known-good image digest, re-enable the Deployment only after image scan and integrity checks pass, and monitor subsequent Kubernetes audit logs for pods/exec, portforward, and access to secrets across the affected namespaces.
    • Escalate to incident response leadership and consider cluster-wide containment if audit logs show create/patch of ClusterRoleBindings, access to secrets outside the workload’s namespace, or use of pods/exec to pivot into other nodes or system namespaces such as kube-system.
    • Harden access by enforcing least-privilege RBAC that denies pods/exec and attach for application service accounts, setting automountServiceAccountToken: false on workloads that do not need it, restricting egress to the API server with NetworkPolicies, and requiring just-in-time break-glass roles for interactive access.

References #

list daemonsets

#
Resource
daemonsets

Example Audit Event #

{
  "kind": "Event",
  "apiVersion": "audit.k8s.io/v1",
  "level": "Metadata",
  "auditID": "00000000-0000-0000-0000-000000000000",
  "stage": "ResponseComplete",
  "requestURI": "/apis/apps/v1/namespaces/dw-harn/daemonsets?limit=500&timeout=3s",
  "verb": "list",
  "user": {
    "username": "kubernetes-admin",
    "groups": [
      "kubeadm:cluster-admins",
      "system:authenticated"
    ],
    "extra": {
      "authentication.kubernetes.io/credential-id": [
        "X509SHA256=9bb0383c49b319fbf6b5ed61ab944378956d4292c784d32244ce2fa4dd846a3c"
      ]
    }
  },
  "sourceIPs": [
    "203.0.113.10"
  ],
  "userAgent": "kubectl/v1.36.2 (linux/amd64) kubernetes/24e2b02",
  "objectRef": {
    "resource": "daemonsets",
    "namespace": "dw-harn",
    "apiGroup": "apps",
    "apiVersion": "v1"
  },
  "responseStatus": {
    "metadata": {},
    "code": 200
  },
  "requestReceivedTimestamp": "2026-07-02T04:47:28.960798Z",
  "stageTimestamp": "2026-07-02T04:47:28.962651Z",
  "annotations": {
    "authorization.k8s.io/decision": "allow",
    "authorization.k8s.io/reason": "RBAC: allowed by ClusterRoleBinding \"kubeadm:cluster-admins\" of ClusterRole \"cluster-admin\" to Group \"kubeadm:cluster-admins\""
  }
}

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Elastic #

  • Direct Interactive Kubernetes API Request by Unusual Utilities source low: This rule leverages a combination of Defend for Containers and Kubernetes audit logs to detect the execution of direct interactive Kubernetes API requests via unusual utilities. An adversary may need to execute direct interactive Kubernetes API requests to gain access to the Kubernetes API server or other resources within the cluster. These requests are often used to enumerate the Kubernetes API server or other resources within the cluster, and may indicate an attempt to move laterally within the cluster.T1059, T1059.004, T1069, T1087, T1609, T1610↳ also matches get-daemonsets: get daemonsets, watch-daemonsets: watch daemonsets, create-daemonsets: create daemonsets, update-daemonsets: update daemonsets, patch-daemonsets: patch daemonsets
    Investigation guide

    Triage and analysis#

    Disclaimer: This investigation guide was created using generative AI technology and has been reviewed to improve its accuracy and relevance. While every effort has been made to ensure its quality, we recommend validating the content and adapting it to suit your specific environment and operational needs.

    Investigating Direct Interactive Kubernetes API Request by Unusual Utilities#

    This rule detects interactive commands executed inside containers that use atypical utilities to hit the Kubernetes API, paired with near-simultaneous API activity on pods, secrets, service accounts, roles/bindings, or pod exec/attach/log/portforward. It surfaces hands-on-keyboard discovery and lateral movement using custom scripts that evade common tool allowlists; for example, an intruder opens a shell in a pod, uses Python to query the in-cluster API to list secrets, then triggers pods/exec to pivot into another workload.

    Possible investigation steps#

    • Identify the implicated pod, container image, and executing service account, then quickly review its RBAC bindings and effective permissions to determine blast radius.
    • Inspect the container’s interactive session context by pulling recent command lines, shell history, environment variables, and mounted service account tokens, and look for custom scripts or binaries issuing HTTP requests.
    • Correlate nearby Kubernetes audit entries tied to the same principal and pod to map accessed resources and verbs, noting any exec/attach/portforward or sensitive object interactions across namespaces.
    • Review network activity from the pod to the API server and any in-pod proxies, including DNS lookups and outbound connections, to spot nonstandard clients or tunneling behavior.
    • If suspicious, isolate the pod or node, capture runtime artifacts (e.g., process memory or HTTP client traffic), revoke and rotate the service account credentials, and verify image provenance and integrity.

    False positive analysis#

    • An operator interactively attaches to a pod and uses a Python REPL or bash with /dev/tcp to call the in-cluster API for routine troubleshooting (e.g., list pods, read ConfigMaps, or run selfsubjectaccessreviews), producing normal audit entries that match the rule signature.
    • A correlation artifact arises when two namespaces have pods with the same name: one pod starts an interactive shell while another independently performs get/list/watch calls, and the 1-second sequence keyed only on pod-name links the unrelated events.

    Response and remediation#

    • Immediately isolate the implicated pod that issued direct API calls using a nonstandard utility by applying a deny-all egress NetworkPolicy in its namespace (including to kubernetes.default.svc:443), terminating the interactive session, and scaling its owning Deployment/Job/StatefulSet to zero replicas.
    • Before teardown, capture a runtime snapshot of the container and node including the binary or script used to query the API (e.g., files under /tmp or /dev/tcp usage), shell history, environment, and the mounted service account token and CA bundle at /var/run/secrets/kubernetes.io/serviceaccount/.
    • Revoke access by removing the service account’s RoleBindings/ClusterRoleBindings, deleting all pods that mount that service account to force token rotation, rotating any Secrets and ConfigMaps that were read or created during the window, and deleting any unauthorized Jobs, CronJobs, or Deployments created by the same principal.
    • Restore workloads from a known-good image digest, re-enable the Deployment only after image scan and integrity checks pass, and monitor subsequent Kubernetes audit logs for pods/exec, portforward, and access to secrets across the affected namespaces.
    • Escalate to incident response leadership and consider cluster-wide containment if audit logs show create/patch of ClusterRoleBindings, access to secrets outside the workload’s namespace, or use of pods/exec to pivot into other nodes or system namespaces such as kube-system.
    • Harden access by enforcing least-privilege RBAC that denies pods/exec and attach for application service accounts, setting automountServiceAccountToken: false on workloads that do not need it, restricting egress to the API server with NetworkPolicies, and requiring just-in-time break-glass roles for interactive access.

References #

watch daemonsets

#
Resource
daemonsets

Example Audit Event #

{
  "kind": "Event",
  "apiVersion": "audit.k8s.io/v1",
  "level": "Metadata",
  "auditID": "00000000-0000-0000-0000-000000000000",
  "stage": "ResponseComplete",
  "requestURI": "/apis/apps/v1/namespaces/dw-harn/daemonsets?resourceVersion=1518&timeout=3s&watch=true",
  "verb": "watch",
  "user": {
    "username": "kubernetes-admin",
    "groups": [
      "kubeadm:cluster-admins",
      "system:authenticated"
    ],
    "extra": {
      "authentication.kubernetes.io/credential-id": [
        "X509SHA256=9bb0383c49b319fbf6b5ed61ab944378956d4292c784d32244ce2fa4dd846a3c"
      ]
    }
  },
  "sourceIPs": [
    "203.0.113.10"
  ],
  "userAgent": "kubectl/v1.36.2 (linux/amd64) kubernetes/24e2b02",
  "objectRef": {
    "resource": "daemonsets",
    "namespace": "dw-harn",
    "apiGroup": "apps",
    "apiVersion": "v1"
  },
  "responseStatus": {
    "metadata": {},
    "code": 200
  },
  "requestReceivedTimestamp": "2026-07-02T04:47:28.963708Z",
  "stageTimestamp": "2026-07-02T04:47:31.964663Z",
  "annotations": {
    "authorization.k8s.io/decision": "allow",
    "authorization.k8s.io/reason": "RBAC: allowed by ClusterRoleBinding \"kubeadm:cluster-admins\" of ClusterRole \"cluster-admin\" to Group \"kubeadm:cluster-admins\""
  }
}

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Elastic #

  • Direct Interactive Kubernetes API Request by Unusual Utilities source low: This rule leverages a combination of Defend for Containers and Kubernetes audit logs to detect the execution of direct interactive Kubernetes API requests via unusual utilities. An adversary may need to execute direct interactive Kubernetes API requests to gain access to the Kubernetes API server or other resources within the cluster. These requests are often used to enumerate the Kubernetes API server or other resources within the cluster, and may indicate an attempt to move laterally within the cluster.T1059, T1059.004, T1069, T1087, T1609, T1610↳ also matches get-daemonsets: get daemonsets, list-daemonsets: list daemonsets, create-daemonsets: create daemonsets, update-daemonsets: update daemonsets, patch-daemonsets: patch daemonsets
    Investigation guide

    Triage and analysis#

    Disclaimer: This investigation guide was created using generative AI technology and has been reviewed to improve its accuracy and relevance. While every effort has been made to ensure its quality, we recommend validating the content and adapting it to suit your specific environment and operational needs.

    Investigating Direct Interactive Kubernetes API Request by Unusual Utilities#

    This rule detects interactive commands executed inside containers that use atypical utilities to hit the Kubernetes API, paired with near-simultaneous API activity on pods, secrets, service accounts, roles/bindings, or pod exec/attach/log/portforward. It surfaces hands-on-keyboard discovery and lateral movement using custom scripts that evade common tool allowlists; for example, an intruder opens a shell in a pod, uses Python to query the in-cluster API to list secrets, then triggers pods/exec to pivot into another workload.

    Possible investigation steps#

    • Identify the implicated pod, container image, and executing service account, then quickly review its RBAC bindings and effective permissions to determine blast radius.
    • Inspect the container’s interactive session context by pulling recent command lines, shell history, environment variables, and mounted service account tokens, and look for custom scripts or binaries issuing HTTP requests.
    • Correlate nearby Kubernetes audit entries tied to the same principal and pod to map accessed resources and verbs, noting any exec/attach/portforward or sensitive object interactions across namespaces.
    • Review network activity from the pod to the API server and any in-pod proxies, including DNS lookups and outbound connections, to spot nonstandard clients or tunneling behavior.
    • If suspicious, isolate the pod or node, capture runtime artifacts (e.g., process memory or HTTP client traffic), revoke and rotate the service account credentials, and verify image provenance and integrity.

    False positive analysis#

    • An operator interactively attaches to a pod and uses a Python REPL or bash with /dev/tcp to call the in-cluster API for routine troubleshooting (e.g., list pods, read ConfigMaps, or run selfsubjectaccessreviews), producing normal audit entries that match the rule signature.
    • A correlation artifact arises when two namespaces have pods with the same name: one pod starts an interactive shell while another independently performs get/list/watch calls, and the 1-second sequence keyed only on pod-name links the unrelated events.

    Response and remediation#

    • Immediately isolate the implicated pod that issued direct API calls using a nonstandard utility by applying a deny-all egress NetworkPolicy in its namespace (including to kubernetes.default.svc:443), terminating the interactive session, and scaling its owning Deployment/Job/StatefulSet to zero replicas.
    • Before teardown, capture a runtime snapshot of the container and node including the binary or script used to query the API (e.g., files under /tmp or /dev/tcp usage), shell history, environment, and the mounted service account token and CA bundle at /var/run/secrets/kubernetes.io/serviceaccount/.
    • Revoke access by removing the service account’s RoleBindings/ClusterRoleBindings, deleting all pods that mount that service account to force token rotation, rotating any Secrets and ConfigMaps that were read or created during the window, and deleting any unauthorized Jobs, CronJobs, or Deployments created by the same principal.
    • Restore workloads from a known-good image digest, re-enable the Deployment only after image scan and integrity checks pass, and monitor subsequent Kubernetes audit logs for pods/exec, portforward, and access to secrets across the affected namespaces.
    • Escalate to incident response leadership and consider cluster-wide containment if audit logs show create/patch of ClusterRoleBindings, access to secrets outside the workload’s namespace, or use of pods/exec to pivot into other nodes or system namespaces such as kube-system.
    • Harden access by enforcing least-privilege RBAC that denies pods/exec and attach for application service accounts, setting automountServiceAccountToken: false on workloads that do not need it, restricting egress to the API server with NetworkPolicies, and requiring just-in-time break-glass roles for interactive access.

References #

create daemonsets

#
Resource
daemonsets

Description

DaemonSet created (runs on every node; used for lateral movement / persistence).

Example Audit Event #

{
  "kind": "Event",
  "apiVersion": "audit.k8s.io/v1",
  "level": "RequestResponse",
  "auditID": "0030660c-9015-41ea-8400-922acaaa25fe",
  "stage": "ResponseComplete",
  "requestURI": "/apis/apps/v1/namespaces/kube-system/daemonsets?fieldManager=kubectl-client-side-apply&fieldValidation=Strict",
  "verb": "create",
  "user": {
    "username": "kubernetes-admin",
    "uid": "aws-iam-authenticator",
    "groups": [
      "system:masters",
      "system:authenticated"
    ]
  },
  "sourceIPs": [
    "203.0.113.10"
  ],
  "userAgent": "kubectl/v1.27.2 (darwin/arm64) kubernetes/7f6f68f",
  "objectRef": {
    "resource": "daemonsets",
    "namespace": "kube-system",
    "name": "fluentd-elasticsearch",
    "apiGroup": "apps",
    "apiVersion": "v1"
  },
  "responseStatus": {
    "metadata": {},
    "code": 201
  },
  "requestObject": {
    "kind": "DaemonSet",
    "apiVersion": "apps/v1",
    "metadata": {
      "name": "fluentd-elasticsearch",
      "namespace": "kube-system",
      "creationTimestamp": null,
      "labels": {
        "k8s-app": "fluentd-logging"
      },
      "annotations": {
        "deprecated.daemonset.template.generation": "0",
        "kubectl.kubernetes.io/last-applied-configuration": {
          "apiVersion": "apps/v1",
          "kind": "DaemonSet",
          "metadata": {
            "annotations": {},
            "labels": {
              "k8s-app": "fluentd-logging"
            },
            "name": "fluentd-elasticsearch",
            "namespace": "kube-system"
          },
          "spec": {
            "selector": {
              "matchLabels": {
                "name": "fluentd-elasticsearch"
              }
            },
            "template": {
              "metadata": {
                "labels": {
                  "name": "fluentd-elasticsearch"
                }
              },
              "spec": {
                "containers": [
                  {
                    "image": "quay.io/fluentd_elasticsearch/fluentd:v2.5.2",
                    "name": "fluentd-elasticsearch",
                    "resources": {
                      "limits": {
                        "memory": "200Mi"
                      },
                      "requests": {
                        "cpu": "100m",
                        "memory": "200Mi"
                      }
                    },
                    "volumeMounts": [
                      {
                        "mountPath": "/var/log",
                        "name": "varlog"
                      }
                    ]
                  }
                ],
                "terminationGracePeriodSeconds": 30,
                "tolerations": [
                  {
                    "effect": "NoSchedule",
                    "key": "node-role.kubernetes.io/control-plane",
                    "operator": "Exists"
                  },
                  {
                    "effect": "NoSchedule",
                    "key": "node-role.kubernetes.io/master",
                    "operator": "Exists"
                  }
                ],
                "volumes": [
                  {
                    "hostPath": {
                      "path": "/var/log"
                    },
                    "name": "varlog"
                  }
                ]
              }
            }
          }
        }
      }
    },
    "spec": {
      "selector": {
        "matchLabels": {
          "name": "fluentd-elasticsearch"
        }
      },
      "template": {
        "metadata": {
          "creationTimestamp": null,
          "labels": {
            "name": "fluentd-elasticsearch"
          }
        },
        "spec": {
          "volumes": [
            {
              "name": "varlog",
              "hostPath": {
                "path": "/var/log",
                "type": ""
              }
            }
          ],
          "containers": [
            {
              "name": "fluentd-elasticsearch",
              "image": "quay.io/fluentd_elasticsearch/fluentd:v2.5.2",
              "resources": {
                "limits": {
                  "memory": "200Mi"
                },
                "requests": {
                  "cpu": "100m",
                  "memory": "200Mi"
                }
              },
              "volumeMounts": [
                {
                  "name": "varlog",
                  "mountPath": "/var/log"
                }
              ],
              "terminationMessagePath": "/dev/termination-log",
              "terminationMessagePolicy": "File",
              "imagePullPolicy": "IfNotPresent"
            }
          ],
          "restartPolicy": "Always",
          "terminationGracePeriodSeconds": 30,
          "dnsPolicy": "ClusterFirst",
          "securityContext": {},
          "schedulerName": "default-scheduler",
          "tolerations": [
            {
              "key": "node-role.kubernetes.io/control-plane",
              "operator": "Exists",
              "effect": "NoSchedule"
            },
            {
              "key": "node-role.kubernetes.io/master",
              "operator": "Exists",
              "effect": "NoSchedule"
            }
          ]
        }
      },
      "updateStrategy": {
        "type": "RollingUpdate",
        "rollingUpdate": {
          "maxUnavailable": 1,
          "maxSurge": 0
        }
      },
      "revisionHistoryLimit": 10
    },
    "status": {
      "currentNumberScheduled": 0,
      "numberMisscheduled": 0,
      "desiredNumberScheduled": 0,
      "numberReady": 0
    }
  },
  "responseObject": {
    "kind": "DaemonSet",
    "apiVersion": "apps/v1",
    "metadata": {
      "name": "fluentd-elasticsearch",
      "namespace": "kube-system",
      "uid": "29198900-9b6a-4d5c-b518-dd3c8f792ca3",
      "resourceVersion": "2798981",
      "generation": 1,
      "creationTimestamp": "2023-12-14T12:00:14Z",
      "labels": {
        "k8s-app": "fluentd-logging"
      },
      "annotations": {
        "deprecated.daemonset.template.generation": "1",
        "kubectl.kubernetes.io/last-applied-configuration": {
          "apiVersion": "apps/v1",
          "kind": "DaemonSet",
          "metadata": {
            "annotations": {},
            "labels": {
              "k8s-app": "fluentd-logging"
            },
            "name": "fluentd-elasticsearch",
            "namespace": "kube-system"
          },
          "spec": {
            "selector": {
              "matchLabels": {
                "name": "fluentd-elasticsearch"
              }
            },
            "template": {
              "metadata": {
                "labels": {
                  "name": "fluentd-elasticsearch"
                }
              },
              "spec": {
                "containers": [
                  {
                    "image": "quay.io/fluentd_elasticsearch/fluentd:v2.5.2",
                    "name": "fluentd-elasticsearch",
                    "resources": {
                      "limits": {
                        "memory": "200Mi"
                      },
                      "requests": {
                        "cpu": "100m",
                        "memory": "200Mi"
                      }
                    },
                    "volumeMounts": [
                      {
                        "mountPath": "/var/log",
                        "name": "varlog"
                      }
                    ]
                  }
                ],
                "terminationGracePeriodSeconds": 30,
                "tolerations": [
                  {
                    "effect": "NoSchedule",
                    "key": "node-role.kubernetes.io/control-plane",
                    "operator": "Exists"
                  },
                  {
                    "effect": "NoSchedule",
                    "key": "node-role.kubernetes.io/master",
                    "operator": "Exists"
                  }
                ],
                "volumes": [
                  {
                    "hostPath": {
                      "path": "/var/log"
                    },
                    "name": "varlog"
                  }
                ]
              }
            }
          }
        }
      }
    },
    "spec": {
      "selector": {
        "matchLabels": {
          "name": "fluentd-elasticsearch"
        }
      },
      "template": {
        "metadata": {
          "creationTimestamp": null,
          "labels": {
            "name": "fluentd-elasticsearch"
          }
        },
        "spec": {
          "volumes": [
            {
              "name": "varlog",
              "hostPath": {
                "path": "/var/log",
                "type": ""
              }
            }
          ],
          "containers": [
            {
              "name": "fluentd-elasticsearch",
              "image": "quay.io/fluentd_elasticsearch/fluentd:v2.5.2",
              "resources": {
                "limits": {
                  "memory": "200Mi"
                },
                "requests": {
                  "cpu": "100m",
                  "memory": "200Mi"
                }
              },
              "volumeMounts": [
                {
                  "name": "varlog",
                  "mountPath": "/var/log"
                }
              ],
              "terminationMessagePath": "/dev/termination-log",
              "terminationMessagePolicy": "File",
              "imagePullPolicy": "IfNotPresent"
            }
          ],
          "restartPolicy": "Always",
          "terminationGracePeriodSeconds": 30,
          "dnsPolicy": "ClusterFirst",
          "securityContext": {},
          "schedulerName": "default-scheduler",
          "tolerations": [
            {
              "key": "node-role.kubernetes.io/control-plane",
              "operator": "Exists",
              "effect": "NoSchedule"
            },
            {
              "key": "node-role.kubernetes.io/master",
              "operator": "Exists",
              "effect": "NoSchedule"
            }
          ]
        }
      },
      "updateStrategy": {
        "type": "RollingUpdate",
        "rollingUpdate": {
          "maxUnavailable": 1,
          "maxSurge": 0
        }
      },
      "revisionHistoryLimit": 10
    },
    "status": {
      "currentNumberScheduled": 0,
      "numberMisscheduled": 0,
      "desiredNumberScheduled": 0,
      "numberReady": 0
    }
  },
  "requestReceivedTimestamp": "2023-12-14T12:00:14.969470Z",
  "stageTimestamp": "2023-12-14T12:00:14.981816Z",
  "annotations": {
    "authorization.k8s.io/decision": "allow",
    "authorization.k8s.io/reason": ""
  }
}

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
kubernetes.audit.objectRef.resource (elastic rule field)incronjobs3 ruleselastic
kubernetes.audit.objectRef.resource (elastic rule field)indaemonsets3 ruleselastic
kubernetes.audit.objectRef.resource (elastic rule field)indeployments3 ruleselastic
verbeqcreate3 rulespanther, splunk
EventType (elastic rule field)inio.k8s.apps.v1.daemonsets.create2 ruleselastic
EventType (elastic rule field)inio.k8s.apps.v1.daemonsets.patch2 ruleselastic
EventType (elastic rule field)inio.k8s.apps.v1.deployments.create2 ruleselastic
EventType (elastic rule field)inio.k8s.apps.v1.deployments.patch2 ruleselastic
EventType (elastic rule field)inio.k8s.batch.v1.cronjobs.create2 ruleselastic
EventType (elastic rule field)inio.k8s.batch.v1.cronjobs.patch2 ruleselastic
client.user.email (elastic rule field)is_not_null2 ruleselastic

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Elastic #

  • Direct Interactive Kubernetes API Request by Unusual Utilities source low: This rule leverages a combination of Defend for Containers and Kubernetes audit logs to detect the execution of direct interactive Kubernetes API requests via unusual utilities. An adversary may need to execute direct interactive Kubernetes API requests to gain access to the Kubernetes API server or other resources within the cluster. These requests are often used to enumerate the Kubernetes API server or other resources within the cluster, and may indicate an attempt to move laterally within the cluster.T1059, T1059.004, T1069, T1087, T1609, T1610↳ also matches get-daemonsets: get daemonsets, list-daemonsets: list daemonsets, watch-daemonsets: watch daemonsets, update-daemonsets: update daemonsets, patch-daemonsets: patch daemonsets
    Investigation guide

    Triage and analysis#

    Disclaimer: This investigation guide was created using generative AI technology and has been reviewed to improve its accuracy and relevance. While every effort has been made to ensure its quality, we recommend validating the content and adapting it to suit your specific environment and operational needs.

    Investigating Direct Interactive Kubernetes API Request by Unusual Utilities#

    This rule detects interactive commands executed inside containers that use atypical utilities to hit the Kubernetes API, paired with near-simultaneous API activity on pods, secrets, service accounts, roles/bindings, or pod exec/attach/log/portforward. It surfaces hands-on-keyboard discovery and lateral movement using custom scripts that evade common tool allowlists; for example, an intruder opens a shell in a pod, uses Python to query the in-cluster API to list secrets, then triggers pods/exec to pivot into another workload.

    Possible investigation steps#

    • Identify the implicated pod, container image, and executing service account, then quickly review its RBAC bindings and effective permissions to determine blast radius.
    • Inspect the container’s interactive session context by pulling recent command lines, shell history, environment variables, and mounted service account tokens, and look for custom scripts or binaries issuing HTTP requests.
    • Correlate nearby Kubernetes audit entries tied to the same principal and pod to map accessed resources and verbs, noting any exec/attach/portforward or sensitive object interactions across namespaces.
    • Review network activity from the pod to the API server and any in-pod proxies, including DNS lookups and outbound connections, to spot nonstandard clients or tunneling behavior.
    • If suspicious, isolate the pod or node, capture runtime artifacts (e.g., process memory or HTTP client traffic), revoke and rotate the service account credentials, and verify image provenance and integrity.

    False positive analysis#

    • An operator interactively attaches to a pod and uses a Python REPL or bash with /dev/tcp to call the in-cluster API for routine troubleshooting (e.g., list pods, read ConfigMaps, or run selfsubjectaccessreviews), producing normal audit entries that match the rule signature.
    • A correlation artifact arises when two namespaces have pods with the same name: one pod starts an interactive shell while another independently performs get/list/watch calls, and the 1-second sequence keyed only on pod-name links the unrelated events.

    Response and remediation#

    • Immediately isolate the implicated pod that issued direct API calls using a nonstandard utility by applying a deny-all egress NetworkPolicy in its namespace (including to kubernetes.default.svc:443), terminating the interactive session, and scaling its owning Deployment/Job/StatefulSet to zero replicas.
    • Before teardown, capture a runtime snapshot of the container and node including the binary or script used to query the API (e.g., files under /tmp or /dev/tcp usage), shell history, environment, and the mounted service account token and CA bundle at /var/run/secrets/kubernetes.io/serviceaccount/.
    • Revoke access by removing the service account’s RoleBindings/ClusterRoleBindings, deleting all pods that mount that service account to force token rotation, rotating any Secrets and ConfigMaps that were read or created during the window, and deleting any unauthorized Jobs, CronJobs, or Deployments created by the same principal.
    • Restore workloads from a known-good image digest, re-enable the Deployment only after image scan and integrity checks pass, and monitor subsequent Kubernetes audit logs for pods/exec, portforward, and access to secrets across the affected namespaces.
    • Escalate to incident response leadership and consider cluster-wide containment if audit logs show create/patch of ClusterRoleBindings, access to secrets outside the workload’s namespace, or use of pods/exec to pivot into other nodes or system namespaces such as kube-system.
    • Harden access by enforcing least-privilege RBAC that denies pods/exec and attach for application service accounts, setting automountServiceAccountToken: false on workloads that do not need it, restricting egress to the API server with NetworkPolicies, and requiring just-in-time break-glass roles for interactive access.
  • GKE Sensitive RBAC Change Followed by Workload Modification source medium: Detects when the same GKE identity creates or modifies a Role or ClusterRole with high-risk permissions (wildcard access, RBAC escalation verbs, or access to secrets / privileged APIs) and also creates or patches a DaemonSet, Deployment, or CronJob within five minutes. This correlation is consistent with RBAC-based privilege escalation followed by payload deployment.T1098, T1098.006↳ also matches patch-daemonsets: patch daemonsets
    Investigation guide

    Triage and analysis#

    Investigating GKE Sensitive RBAC Change Followed by Workload Modification#

    This ES|QL rule correlates two successful GKE audit behaviors from the same client.user.email within five minutes:

    1. Role or ClusterRole create/update/patch that grants high-risk permissions (wildcards, escalate / bind / impersonate, secret read, or privileged API resources such as pods/exec and serviceaccounts/token)
    2. DaemonSet, Deployment, or CronJob create or patch after the sensitive RBAC change

    Esql.rbac_to_workload_minutes is the gap from the latest sensitive RBAC event to the earliest workload modification in the lookback window.

    Possible investigation steps#

    • Review Esql.event_action_values and Esql.gcp_audit_resource_name_values for the Role/ClusterRole and workload objects touched.
    • Inspect Esql.user_agent_original_values and Esql.source_ip_values for unexpected clients or networks.
    • Check for RoleBinding or ClusterRoleBinding activity around the same identity and time window.
    • Correlate with secret access, pod exec, or token creation from the same actor.

    False positive analysis#

    • GitOps pipelines that manage both RBAC manifests and workloads in one sync cycle.
    • Platform bootstrap that patches built-in roles and reconciles addon workloads.

    Response and remediation#

    • Roll back unauthorized Role/ClusterRole and workload changes, revoke the actor's credentials, and tighten who can mutate RBAC and sensitive workloads.
  • GKE Unusual Sensitive Workload Modification source low: Detects the first occurrence of create or patch activity against sensitive GKE workloads (DaemonSets, Deployments, or CronJobs) from an unusual combination of user agent, source IP, and user identity, which may indicate privilege escalation or unauthorized access within the cluster.T1098, T1098.006↳ also matches patch-daemonsets: patch daemonsets
    Investigation guide

    Triage and analysis#

    Investigating GKE Unusual Sensitive Workload Modification#

    This new-terms rule alerts on the first create or patch of a DaemonSet, Deployment, or CronJob from a new combination of user_agent.original, source.ip, and client.user.email.

    Possible investigation steps#

    • Review the audit request for image, command, service account, and privileged settings changes.
    • Attribute the actor to its backing identity and validate whether the source network is expected.
    • Correlate with RBAC, secret, or exec activity from the same identity.

    False positive analysis#

    • Legitimate on-call changes from new workstations or updated kubectl versions are common in lab clusters.

    Response and remediation#

    • Roll back unauthorized workload changes, revoke the credential used, and tighten RBAC on workload controllers.

Show 2 more (5 total) on the rules page

Splunk #

  • Kubernetes DaemonSet Deployed source: The following analytic detects the creation of a DaemonSet in a Kubernetes cluster. This behavior is identified by monitoring Kubernetes Audit logs for the creation event of a DaemonSet. DaemonSets ensure a specific pod runs on every node,…T1204

Panther #

  • Kubernetes DaemonSet Created source informational: This detection monitors for creation of DaemonSets in Kubernetes clusters. DaemonSets ensure that a copy of a pod runs on all (or selected) nodes in the cluster. Attackers may abuse DaemonSets to deploy malicious containers across all nodes for cluster-wide persistence, credential harvesting, cryptomining, or lateral movement. This detection works across AWS EKS, Azure AKS, and GCP GKE clusters.T1543, T1610
  • New DaemonSet Deployed to Kubernetes source medium linked query: New DaemonSet Deployed to Kubernetes: This detection monitors for a new DaemonSet deployed to a kubernetes cluster. A daemonset is a workload that guarantees the presence of exactly one instance of a specific pod on every node in the cluster. This can be a very powerful tool for establishing peristence.
  • New DaemonSet Deployed to Kubernetes source: This detection monitors for a new DaemonSet deployed to a kubernetes cluster. A daemonset is a workload that guarantees the presence of exactly one instance of a specific pod on every node in the cluster. This can be a very powerful tool for establishing peristence.

References #

update daemonsets

#
Resource
daemonsets

Example Audit Event #

{
  "kind": "Event",
  "apiVersion": "audit.k8s.io/v1",
  "level": "RequestResponse",
  "auditID": "00000000-0000-0000-0000-000000000000",
  "stage": "ResponseComplete",
  "requestURI": "/apis/apps/v1/namespaces/dw-harn/daemonsets/dw-harn-daemonsets?fieldManager=kubectl-replace&fieldValidation=Strict",
  "verb": "update",
  "user": {
    "username": "kubernetes-admin",
    "groups": [
      "kubeadm:cluster-admins",
      "system:authenticated"
    ],
    "extra": {
      "authentication.kubernetes.io/credential-id": [
        "X509SHA256=4cf95d11cbd90036bab41cdc6b88cc8f91550e9135ed4bb61495b02f647812ff"
      ]
    }
  },
  "sourceIPs": [
    "203.0.113.10"
  ],
  "userAgent": "kubectl/v1.36.2 (linux/amd64) kubernetes/24e2b02",
  "objectRef": {
    "resource": "daemonsets",
    "namespace": "dw-harn",
    "name": "dw-harn-daemonsets",
    "uid": "00000000-0000-0000-0000-000000000000",
    "apiGroup": "apps",
    "apiVersion": "v1",
    "resourceVersion": "680"
  },
  "responseStatus": {
    "metadata": {},
    "code": 200
  },
  "requestObject": {
    "kind": "DaemonSet",
    "apiVersion": "apps/v1",
    "metadata": {
      "name": "dw-harn-daemonsets",
      "namespace": "dw-harn",
      "uid": "00000000-0000-0000-0000-000000000000",
      "resourceVersion": "680",
      "generation": 1,
      "creationTimestamp": "2026-07-02T21:30:54Z",
      "labels": {
        "dw-harn-patched": "1"
      },
      "annotations": {
        "deprecated.daemonset.template.generation": "1"
      }
    },
    "spec": {
      "selector": {
        "matchLabels": {
          "app": "dw-harn"
        }
      },
      "template": {
        "metadata": {
          "labels": {
            "app": "dw-harn"
          }
        },
        "spec": {
          "containers": [
            {
              "name": "c",
              "image": "docker.io/library/busybox:1.36",
              "command": [
                "sh",
                "-c",
                "sleep 3600"
              ],
              "resources": {},
              "terminationMessagePath": "/dev/termination-log",
              "terminationMessagePolicy": "File",
              "imagePullPolicy": "IfNotPresent"
            }
          ],
          "restartPolicy": "Always",
          "terminationGracePeriodSeconds": 0,
          "dnsPolicy": "ClusterFirst",
          "securityContext": {},
          "schedulerName": "default-scheduler"
        }
      },
      "updateStrategy": {
        "type": "RollingUpdate",
        "rollingUpdate": {
          "maxUnavailable": 1,
          "maxSurge": 0
        }
      },
      "revisionHistoryLimit": 10
    },
    "status": {
      "currentNumberScheduled": 1,
      "numberMisscheduled": 0,
      "desiredNumberScheduled": 1,
      "numberReady": 1,
      "observedGeneration": 1,
      "updatedNumberScheduled": 1,
      "numberAvailable": 1
    }
  },
  "responseObject": {
    "kind": "DaemonSet",
    "apiVersion": "apps/v1",
    "metadata": {
      "name": "dw-harn-daemonsets",
      "namespace": "dw-harn",
      "uid": "00000000-0000-0000-0000-000000000000",
      "resourceVersion": "680",
      "generation": 1,
      "creationTimestamp": "2026-07-02T21:30:54Z",
      "labels": {
        "dw-harn-patched": "1"
      },
      "annotations": {
        "deprecated.daemonset.template.generation": "1"
      }
    },
    "spec": {
      "selector": {
        "matchLabels": {
          "app": "dw-harn"
        }
      },
      "template": {
        "metadata": {
          "labels": {
            "app": "dw-harn"
          }
        },
        "spec": {
          "containers": [
            {
              "name": "c",
              "image": "docker.io/library/busybox:1.36",
              "command": [
                "sh",
                "-c",
                "sleep 3600"
              ],
              "resources": {},
              "terminationMessagePath": "/dev/termination-log",
              "terminationMessagePolicy": "File",
              "imagePullPolicy": "IfNotPresent"
            }
          ],
          "restartPolicy": "Always",
          "terminationGracePeriodSeconds": 0,
          "dnsPolicy": "ClusterFirst",
          "securityContext": {},
          "schedulerName": "default-scheduler"
        }
      },
      "updateStrategy": {
        "type": "RollingUpdate",
        "rollingUpdate": {
          "maxUnavailable": 1,
          "maxSurge": 0
        }
      },
      "revisionHistoryLimit": 10
    },
    "status": {
      "currentNumberScheduled": 1,
      "numberMisscheduled": 0,
      "desiredNumberScheduled": 1,
      "numberReady": 1,
      "observedGeneration": 1,
      "updatedNumberScheduled": 1,
      "numberAvailable": 1
    }
  },
  "requestReceivedTimestamp": "2026-07-02T21:30:58.166660Z",
  "stageTimestamp": "2026-07-02T21:30:58.169978Z",
  "annotations": {
    "authorization.k8s.io/decision": "allow",
    "authorization.k8s.io/reason": "RBAC: allowed by ClusterRoleBinding \"kubeadm:cluster-admins\" of ClusterRole \"cluster-admin\" to Group \"kubeadm:cluster-admins\""
  }
}

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Elastic #

  • Direct Interactive Kubernetes API Request by Unusual Utilities source low: This rule leverages a combination of Defend for Containers and Kubernetes audit logs to detect the execution of direct interactive Kubernetes API requests via unusual utilities. An adversary may need to execute direct interactive Kubernetes API requests to gain access to the Kubernetes API server or other resources within the cluster. These requests are often used to enumerate the Kubernetes API server or other resources within the cluster, and may indicate an attempt to move laterally within the cluster.T1059, T1059.004, T1069, T1087, T1609, T1610↳ also matches get-daemonsets: get daemonsets, list-daemonsets: list daemonsets, watch-daemonsets: watch daemonsets, create-daemonsets: create daemonsets, patch-daemonsets: patch daemonsets
    Investigation guide

    Triage and analysis#

    Disclaimer: This investigation guide was created using generative AI technology and has been reviewed to improve its accuracy and relevance. While every effort has been made to ensure its quality, we recommend validating the content and adapting it to suit your specific environment and operational needs.

    Investigating Direct Interactive Kubernetes API Request by Unusual Utilities#

    This rule detects interactive commands executed inside containers that use atypical utilities to hit the Kubernetes API, paired with near-simultaneous API activity on pods, secrets, service accounts, roles/bindings, or pod exec/attach/log/portforward. It surfaces hands-on-keyboard discovery and lateral movement using custom scripts that evade common tool allowlists; for example, an intruder opens a shell in a pod, uses Python to query the in-cluster API to list secrets, then triggers pods/exec to pivot into another workload.

    Possible investigation steps#

    • Identify the implicated pod, container image, and executing service account, then quickly review its RBAC bindings and effective permissions to determine blast radius.
    • Inspect the container’s interactive session context by pulling recent command lines, shell history, environment variables, and mounted service account tokens, and look for custom scripts or binaries issuing HTTP requests.
    • Correlate nearby Kubernetes audit entries tied to the same principal and pod to map accessed resources and verbs, noting any exec/attach/portforward or sensitive object interactions across namespaces.
    • Review network activity from the pod to the API server and any in-pod proxies, including DNS lookups and outbound connections, to spot nonstandard clients or tunneling behavior.
    • If suspicious, isolate the pod or node, capture runtime artifacts (e.g., process memory or HTTP client traffic), revoke and rotate the service account credentials, and verify image provenance and integrity.

    False positive analysis#

    • An operator interactively attaches to a pod and uses a Python REPL or bash with /dev/tcp to call the in-cluster API for routine troubleshooting (e.g., list pods, read ConfigMaps, or run selfsubjectaccessreviews), producing normal audit entries that match the rule signature.
    • A correlation artifact arises when two namespaces have pods with the same name: one pod starts an interactive shell while another independently performs get/list/watch calls, and the 1-second sequence keyed only on pod-name links the unrelated events.

    Response and remediation#

    • Immediately isolate the implicated pod that issued direct API calls using a nonstandard utility by applying a deny-all egress NetworkPolicy in its namespace (including to kubernetes.default.svc:443), terminating the interactive session, and scaling its owning Deployment/Job/StatefulSet to zero replicas.
    • Before teardown, capture a runtime snapshot of the container and node including the binary or script used to query the API (e.g., files under /tmp or /dev/tcp usage), shell history, environment, and the mounted service account token and CA bundle at /var/run/secrets/kubernetes.io/serviceaccount/.
    • Revoke access by removing the service account’s RoleBindings/ClusterRoleBindings, deleting all pods that mount that service account to force token rotation, rotating any Secrets and ConfigMaps that were read or created during the window, and deleting any unauthorized Jobs, CronJobs, or Deployments created by the same principal.
    • Restore workloads from a known-good image digest, re-enable the Deployment only after image scan and integrity checks pass, and monitor subsequent Kubernetes audit logs for pods/exec, portforward, and access to secrets across the affected namespaces.
    • Escalate to incident response leadership and consider cluster-wide containment if audit logs show create/patch of ClusterRoleBindings, access to secrets outside the workload’s namespace, or use of pods/exec to pivot into other nodes or system namespaces such as kube-system.
    • Harden access by enforcing least-privilege RBAC that denies pods/exec and attach for application service accounts, setting automountServiceAccountToken: false on workloads that do not need it, restricting egress to the API server with NetworkPolicies, and requiring just-in-time break-glass roles for interactive access.

References #

patch daemonsets

#
Resource
daemonsets

Description

DaemonSet patched (sidecar injection or workload modification).

Example Audit Event #

{
  "kind": "Event",
  "apiVersion": "audit.k8s.io/v1",
  "level": "RequestResponse",
  "auditID": "00000000-0000-0000-0000-000000000000",
  "stage": "ResponseComplete",
  "requestURI": "/apis/apps/v1/namespaces/dw-harn/daemonsets/dw-harn-daemonsets?fieldManager=kubectl-patch",
  "verb": "patch",
  "user": {
    "username": "kubernetes-admin",
    "groups": [
      "kubeadm:cluster-admins",
      "system:authenticated"
    ],
    "extra": {
      "authentication.kubernetes.io/credential-id": [
        "X509SHA256=9bb0383c49b319fbf6b5ed61ab944378956d4292c784d32244ce2fa4dd846a3c"
      ]
    }
  },
  "sourceIPs": [
    "203.0.113.10"
  ],
  "userAgent": "kubectl/v1.36.2 (linux/amd64) kubernetes/24e2b02",
  "objectRef": {
    "resource": "daemonsets",
    "namespace": "dw-harn",
    "name": "dw-harn-daemonsets",
    "apiGroup": "apps",
    "apiVersion": "v1"
  },
  "responseStatus": {
    "metadata": {},
    "code": 200
  },
  "requestObject": {
    "metadata": {
      "labels": {
        "dw-harn-patched": "1"
      }
    }
  },
  "responseObject": {
    "kind": "DaemonSet",
    "apiVersion": "apps/v1",
    "metadata": {
      "name": "dw-harn-daemonsets",
      "namespace": "dw-harn",
      "uid": "00000000-0000-0000-0000-000000000000",
      "resourceVersion": "1529",
      "generation": 1,
      "creationTimestamp": "2026-07-02T04:47:28Z",
      "labels": {
        "dw-harn-patched": "1"
      },
      "annotations": {
        "deprecated.daemonset.template.generation": "1"
      }
    },
    "spec": {
      "selector": {
        "matchLabels": {
          "app": "dw-harn"
        }
      },
      "template": {
        "metadata": {
          "labels": {
            "app": "dw-harn"
          }
        },
        "spec": {
          "containers": [
            {
              "name": "c",
              "image": "docker.io/library/busybox:1.36",
              "command": [
                "sh",
                "-c",
                "sleep 3600"
              ],
              "resources": {},
              "terminationMessagePath": "/dev/termination-log",
              "terminationMessagePolicy": "File",
              "imagePullPolicy": "IfNotPresent"
            }
          ],
          "restartPolicy": "Always",
          "terminationGracePeriodSeconds": 0,
          "dnsPolicy": "ClusterFirst",
          "securityContext": {},
          "schedulerName": "default-scheduler"
        }
      },
      "updateStrategy": {
        "type": "RollingUpdate",
        "rollingUpdate": {
          "maxUnavailable": 1,
          "maxSurge": 0
        }
      },
      "revisionHistoryLimit": 10
    },
    "status": {
      "currentNumberScheduled": 1,
      "numberMisscheduled": 0,
      "desiredNumberScheduled": 1,
      "numberReady": 1,
      "observedGeneration": 1,
      "updatedNumberScheduled": 1,
      "numberAvailable": 1
    }
  },
  "requestReceivedTimestamp": "2026-07-02T04:47:32.064200Z",
  "stageTimestamp": "2026-07-02T04:47:32.069404Z",
  "annotations": {
    "authorization.k8s.io/decision": "allow",
    "authorization.k8s.io/reason": "RBAC: allowed by ClusterRoleBinding \"kubeadm:cluster-admins\" of ClusterRole \"cluster-admin\" to Group \"kubeadm:cluster-admins\""
  }
}

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
kubernetes.audit.objectRef.resource (elastic rule field)incronjobs3 ruleselastic
kubernetes.audit.objectRef.resource (elastic rule field)indaemonsets3 ruleselastic
kubernetes.audit.objectRef.resource (elastic rule field)indeployments3 ruleselastic
EventType (elastic rule field)inio.k8s.apps.v1.daemonsets.create2 ruleselastic
EventType (elastic rule field)inio.k8s.apps.v1.daemonsets.patch2 ruleselastic
EventType (elastic rule field)inio.k8s.apps.v1.deployments.create2 ruleselastic
EventType (elastic rule field)inio.k8s.apps.v1.deployments.patch2 ruleselastic
EventType (elastic rule field)inio.k8s.batch.v1.cronjobs.create2 ruleselastic
EventType (elastic rule field)inio.k8s.batch.v1.cronjobs.patch2 ruleselastic
client.user.email (elastic rule field)is_not_null2 ruleselastic

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Elastic #

  • Direct Interactive Kubernetes API Request by Unusual Utilities source low: This rule leverages a combination of Defend for Containers and Kubernetes audit logs to detect the execution of direct interactive Kubernetes API requests via unusual utilities. An adversary may need to execute direct interactive Kubernetes API requests to gain access to the Kubernetes API server or other resources within the cluster. These requests are often used to enumerate the Kubernetes API server or other resources within the cluster, and may indicate an attempt to move laterally within the cluster.T1059, T1059.004, T1069, T1087, T1609, T1610↳ also matches get-daemonsets: get daemonsets, list-daemonsets: list daemonsets, watch-daemonsets: watch daemonsets, create-daemonsets: create daemonsets, update-daemonsets: update daemonsets
    Investigation guide

    Triage and analysis#

    Disclaimer: This investigation guide was created using generative AI technology and has been reviewed to improve its accuracy and relevance. While every effort has been made to ensure its quality, we recommend validating the content and adapting it to suit your specific environment and operational needs.

    Investigating Direct Interactive Kubernetes API Request by Unusual Utilities#

    This rule detects interactive commands executed inside containers that use atypical utilities to hit the Kubernetes API, paired with near-simultaneous API activity on pods, secrets, service accounts, roles/bindings, or pod exec/attach/log/portforward. It surfaces hands-on-keyboard discovery and lateral movement using custom scripts that evade common tool allowlists; for example, an intruder opens a shell in a pod, uses Python to query the in-cluster API to list secrets, then triggers pods/exec to pivot into another workload.

    Possible investigation steps#

    • Identify the implicated pod, container image, and executing service account, then quickly review its RBAC bindings and effective permissions to determine blast radius.
    • Inspect the container’s interactive session context by pulling recent command lines, shell history, environment variables, and mounted service account tokens, and look for custom scripts or binaries issuing HTTP requests.
    • Correlate nearby Kubernetes audit entries tied to the same principal and pod to map accessed resources and verbs, noting any exec/attach/portforward or sensitive object interactions across namespaces.
    • Review network activity from the pod to the API server and any in-pod proxies, including DNS lookups and outbound connections, to spot nonstandard clients or tunneling behavior.
    • If suspicious, isolate the pod or node, capture runtime artifacts (e.g., process memory or HTTP client traffic), revoke and rotate the service account credentials, and verify image provenance and integrity.

    False positive analysis#

    • An operator interactively attaches to a pod and uses a Python REPL or bash with /dev/tcp to call the in-cluster API for routine troubleshooting (e.g., list pods, read ConfigMaps, or run selfsubjectaccessreviews), producing normal audit entries that match the rule signature.
    • A correlation artifact arises when two namespaces have pods with the same name: one pod starts an interactive shell while another independently performs get/list/watch calls, and the 1-second sequence keyed only on pod-name links the unrelated events.

    Response and remediation#

    • Immediately isolate the implicated pod that issued direct API calls using a nonstandard utility by applying a deny-all egress NetworkPolicy in its namespace (including to kubernetes.default.svc:443), terminating the interactive session, and scaling its owning Deployment/Job/StatefulSet to zero replicas.
    • Before teardown, capture a runtime snapshot of the container and node including the binary or script used to query the API (e.g., files under /tmp or /dev/tcp usage), shell history, environment, and the mounted service account token and CA bundle at /var/run/secrets/kubernetes.io/serviceaccount/.
    • Revoke access by removing the service account’s RoleBindings/ClusterRoleBindings, deleting all pods that mount that service account to force token rotation, rotating any Secrets and ConfigMaps that were read or created during the window, and deleting any unauthorized Jobs, CronJobs, or Deployments created by the same principal.
    • Restore workloads from a known-good image digest, re-enable the Deployment only after image scan and integrity checks pass, and monitor subsequent Kubernetes audit logs for pods/exec, portforward, and access to secrets across the affected namespaces.
    • Escalate to incident response leadership and consider cluster-wide containment if audit logs show create/patch of ClusterRoleBindings, access to secrets outside the workload’s namespace, or use of pods/exec to pivot into other nodes or system namespaces such as kube-system.
    • Harden access by enforcing least-privilege RBAC that denies pods/exec and attach for application service accounts, setting automountServiceAccountToken: false on workloads that do not need it, restricting egress to the API server with NetworkPolicies, and requiring just-in-time break-glass roles for interactive access.
  • GKE Sensitive RBAC Change Followed by Workload Modification source medium: Detects when the same GKE identity creates or modifies a Role or ClusterRole with high-risk permissions (wildcard access, RBAC escalation verbs, or access to secrets / privileged APIs) and also creates or patches a DaemonSet, Deployment, or CronJob within five minutes. This correlation is consistent with RBAC-based privilege escalation followed by payload deployment.T1098, T1098.006↳ also matches create-daemonsets: create daemonsets
    Investigation guide

    Triage and analysis#

    Investigating GKE Sensitive RBAC Change Followed by Workload Modification#

    This ES|QL rule correlates two successful GKE audit behaviors from the same client.user.email within five minutes:

    1. Role or ClusterRole create/update/patch that grants high-risk permissions (wildcards, escalate / bind / impersonate, secret read, or privileged API resources such as pods/exec and serviceaccounts/token)
    2. DaemonSet, Deployment, or CronJob create or patch after the sensitive RBAC change

    Esql.rbac_to_workload_minutes is the gap from the latest sensitive RBAC event to the earliest workload modification in the lookback window.

    Possible investigation steps#

    • Review Esql.event_action_values and Esql.gcp_audit_resource_name_values for the Role/ClusterRole and workload objects touched.
    • Inspect Esql.user_agent_original_values and Esql.source_ip_values for unexpected clients or networks.
    • Check for RoleBinding or ClusterRoleBinding activity around the same identity and time window.
    • Correlate with secret access, pod exec, or token creation from the same actor.

    False positive analysis#

    • GitOps pipelines that manage both RBAC manifests and workloads in one sync cycle.
    • Platform bootstrap that patches built-in roles and reconciles addon workloads.

    Response and remediation#

    • Roll back unauthorized Role/ClusterRole and workload changes, revoke the actor's credentials, and tighten who can mutate RBAC and sensitive workloads.
  • GKE Unusual Sensitive Workload Modification source low: Detects the first occurrence of create or patch activity against sensitive GKE workloads (DaemonSets, Deployments, or CronJobs) from an unusual combination of user agent, source IP, and user identity, which may indicate privilege escalation or unauthorized access within the cluster.T1098, T1098.006↳ also matches create-daemonsets: create daemonsets
    Investigation guide

    Triage and analysis#

    Investigating GKE Unusual Sensitive Workload Modification#

    This new-terms rule alerts on the first create or patch of a DaemonSet, Deployment, or CronJob from a new combination of user_agent.original, source.ip, and client.user.email.

    Possible investigation steps#

    • Review the audit request for image, command, service account, and privileged settings changes.
    • Attribute the actor to its backing identity and validate whether the source network is expected.
    • Correlate with RBAC, secret, or exec activity from the same identity.

    False positive analysis#

    • Legitimate on-call changes from new workstations or updated kubectl versions are common in lab clusters.

    Response and remediation#

    • Roll back unauthorized workload changes, revoke the credential used, and tighten RBAC on workload controllers.

Show 2 more (5 total) on the rules page

References #

delete daemonsets

#
Resource
daemonsets

Example Audit Event #

{
  "kind": "Event",
  "apiVersion": "audit.k8s.io/v1",
  "level": "RequestResponse",
  "auditID": "00000000-0000-0000-0000-000000000000",
  "stage": "ResponseComplete",
  "requestURI": "/apis/apps/v1/namespaces/dw-harn/daemonsets/dw-harn-daemonsets",
  "verb": "delete",
  "user": {
    "username": "kubernetes-admin",
    "groups": [
      "kubeadm:cluster-admins",
      "system:authenticated"
    ],
    "extra": {
      "authentication.kubernetes.io/credential-id": [
        "X509SHA256=9bb0383c49b319fbf6b5ed61ab944378956d4292c784d32244ce2fa4dd846a3c"
      ]
    }
  },
  "sourceIPs": [
    "203.0.113.10"
  ],
  "userAgent": "kubectl/v1.36.2 (linux/amd64) kubernetes/24e2b02",
  "objectRef": {
    "resource": "daemonsets",
    "namespace": "dw-harn",
    "name": "dw-harn-daemonsets",
    "apiGroup": "apps",
    "apiVersion": "v1"
  },
  "responseStatus": {
    "metadata": {},
    "status": "Success",
    "details": {
      "name": "dw-harn-daemonsets",
      "group": "apps",
      "kind": "daemonsets",
      "uid": "00000000-0000-0000-0000-000000000000"
    },
    "code": 200
  },
  "requestObject": {
    "kind": "DeleteOptions",
    "apiVersion": "meta.k8s.io/__internal",
    "propagationPolicy": "Background"
  },
  "responseObject": {
    "kind": "Status",
    "apiVersion": "v1",
    "metadata": {},
    "status": "Success",
    "details": {
      "name": "dw-harn-daemonsets",
      "group": "apps",
      "kind": "daemonsets",
      "uid": "00000000-0000-0000-0000-000000000000"
    }
  },
  "requestReceivedTimestamp": "2026-07-02T04:47:32.186553Z",
  "stageTimestamp": "2026-07-02T04:47:32.203107Z",
  "annotations": {
    "authorization.k8s.io/decision": "allow",
    "authorization.k8s.io/reason": "RBAC: allowed by ClusterRoleBinding \"kubeadm:cluster-admins\" of ClusterRole \"cluster-admin\" to Group \"kubeadm:cluster-admins\""
  }
}

References #

deletecollection daemonsets

#
Resource
daemonsets

Example Audit Event #

{
  "kind": "Event",
  "apiVersion": "audit.k8s.io/v1",
  "level": "RequestResponse",
  "auditID": "00000000-0000-0000-0000-000000000000",
  "stage": "ResponseComplete",
  "requestURI": "/apis/apps/v1/namespaces/dw-harn/daemonsets?labelSelector=dw-harn-patched",
  "verb": "deletecollection",
  "user": {
    "username": "kubernetes-admin",
    "groups": [
      "kubeadm:cluster-admins",
      "system:authenticated"
    ],
    "extra": {
      "authentication.kubernetes.io/credential-id": [
        "X509SHA256=3ffde68ef687218e01296d94b0aa59c81cc98de2bd73ab70e21510c8cd4b9cec"
      ]
    }
  },
  "sourceIPs": [
    "203.0.113.10"
  ],
  "userAgent": "kubectl/v1.36.2 (linux/amd64) kubernetes/24e2b02",
  "objectRef": {
    "resource": "daemonsets",
    "namespace": "dw-harn",
    "apiGroup": "apps",
    "apiVersion": "v1"
  },
  "responseStatus": {
    "metadata": {},
    "code": 200
  },
  "responseObject": {
    "kind": "DaemonSetList",
    "apiVersion": "apps/v1",
    "metadata": {
      "resourceVersion": "796"
    },
    "items": [
      {
        "metadata": {
          "name": "dw-harn-daemonsets",
          "namespace": "dw-harn",
          "uid": "00000000-0000-0000-0000-000000000000",
          "resourceVersion": "794",
          "generation": 1,
          "creationTimestamp": "2026-07-02T23:12:56Z",
          "labels": {
            "dw-harn-patched": "1"
          },
          "annotations": {
            "deprecated.daemonset.template.generation": "1"
          }
        },
        "spec": {
          "selector": {
            "matchLabels": {
              "app": "dw-harn"
            }
          },
          "template": {
            "metadata": {
              "labels": {
                "app": "dw-harn"
              }
            },
            "spec": {
              "containers": [
                {
                  "name": "c",
                  "image": "docker.io/library/busybox:1.36",
                  "command": [
                    "sh",
                    "-c",
                    "sleep 3600"
                  ],
                  "resources": {},
                  "terminationMessagePath": "/dev/termination-log",
                  "terminationMessagePolicy": "File",
                  "imagePullPolicy": "IfNotPresent"
                }
              ],
              "restartPolicy": "Always",
              "terminationGracePeriodSeconds": 0,
              "dnsPolicy": "ClusterFirst",
              "securityContext": {},
              "schedulerName": "default-scheduler"
            }
          },
          "updateStrategy": {
            "type": "RollingUpdate",
            "rollingUpdate": {
              "maxUnavailable": 1,
              "maxSurge": 0
            }
          },
          "revisionHistoryLimit": 10
        },
        "status": {
          "currentNumberScheduled": 1,
          "numberMisscheduled": 0,
          "desiredNumberScheduled": 1,
          "numberReady": 1,
          "observedGeneration": 1,
          "updatedNumberScheduled": 1,
          "numberAvailable": 1
        }
      }
    ]
  },
  "requestReceivedTimestamp": "2026-07-02T23:13:00.284529Z",
  "stageTimestamp": "2026-07-02T23:13:00.290514Z",
  "annotations": {
    "authorization.k8s.io/decision": "allow",
    "authorization.k8s.io/reason": "RBAC: allowed by ClusterRoleBinding \"kubeadm:cluster-admins\" of ClusterRole \"cluster-admin\" to Group \"kubeadm:cluster-admins\""
  }
}

References #

get daemonsets/status

#
Resource
daemonsets

Example Audit Event #

{
  "kind": "Event",
  "apiVersion": "audit.k8s.io/v1",
  "level": "Metadata",
  "auditID": "00000000-0000-0000-0000-000000000000",
  "stage": "ResponseComplete",
  "requestURI": "/apis/apps/v1/namespaces/dw-harn/daemonsets/dw-harn-daemonsets/status",
  "verb": "get",
  "user": {
    "username": "kubernetes-admin",
    "groups": [
      "kubeadm:cluster-admins",
      "system:authenticated"
    ],
    "extra": {
      "authentication.kubernetes.io/credential-id": [
        "X509SHA256=4cf95d11cbd90036bab41cdc6b88cc8f91550e9135ed4bb61495b02f647812ff"
      ]
    }
  },
  "sourceIPs": [
    "203.0.113.10"
  ],
  "userAgent": "kubectl/v1.36.2 (linux/amd64) kubernetes/24e2b02",
  "objectRef": {
    "resource": "daemonsets",
    "namespace": "dw-harn",
    "name": "dw-harn-daemonsets",
    "apiGroup": "apps",
    "apiVersion": "v1",
    "subresource": "status"
  },
  "responseStatus": {
    "metadata": {},
    "code": 200
  },
  "requestReceivedTimestamp": "2026-07-02T21:30:58.239770Z",
  "stageTimestamp": "2026-07-02T21:30:58.241760Z",
  "annotations": {
    "authorization.k8s.io/decision": "allow",
    "authorization.k8s.io/reason": "RBAC: allowed by ClusterRoleBinding \"kubeadm:cluster-admins\" of ClusterRole \"cluster-admin\" to Group \"kubeadm:cluster-admins\""
  }
}

References #

update daemonsets/status

#
Resource
daemonsets

Example Audit Event #

{
  "kind": "Event",
  "apiVersion": "audit.k8s.io/v1",
  "level": "RequestResponse",
  "auditID": "00000000-0000-0000-0000-000000000000",
  "stage": "ResponseComplete",
  "requestURI": "/apis/apps/v1/namespaces/dw-harn/daemonsets/dw-harn-daemonsets/status?fieldManager=kubectl-replace&fieldValidation=Strict",
  "verb": "update",
  "user": {
    "username": "kubernetes-admin",
    "groups": [
      "kubeadm:cluster-admins",
      "system:authenticated"
    ],
    "extra": {
      "authentication.kubernetes.io/credential-id": [
        "X509SHA256=4cf95d11cbd90036bab41cdc6b88cc8f91550e9135ed4bb61495b02f647812ff"
      ]
    }
  },
  "sourceIPs": [
    "203.0.113.10"
  ],
  "userAgent": "kubectl/v1.36.2 (linux/amd64) kubernetes/24e2b02",
  "objectRef": {
    "resource": "daemonsets",
    "namespace": "dw-harn",
    "name": "dw-harn-daemonsets",
    "uid": "00000000-0000-0000-0000-000000000000",
    "apiGroup": "apps",
    "apiVersion": "v1",
    "resourceVersion": "680",
    "subresource": "status"
  },
  "responseStatus": {
    "metadata": {},
    "code": 200
  },
  "requestObject": {
    "kind": "DaemonSet",
    "apiVersion": "apps/v1",
    "metadata": {
      "name": "dw-harn-daemonsets",
      "namespace": "dw-harn",
      "uid": "00000000-0000-0000-0000-000000000000",
      "resourceVersion": "680",
      "generation": 1,
      "creationTimestamp": "2026-07-02T21:30:54Z",
      "labels": {
        "dw-harn-patched": "1"
      },
      "annotations": {
        "deprecated.daemonset.template.generation": "1"
      }
    },
    "spec": {
      "selector": {
        "matchLabels": {
          "app": "dw-harn"
        }
      },
      "template": {
        "metadata": {
          "labels": {
            "app": "dw-harn"
          }
        },
        "spec": {
          "containers": [
            {
              "name": "c",
              "image": "docker.io/library/busybox:1.36",
              "command": [
                "sh",
                "-c",
                "sleep 3600"
              ],
              "resources": {},
              "terminationMessagePath": "/dev/termination-log",
              "terminationMessagePolicy": "File",
              "imagePullPolicy": "IfNotPresent"
            }
          ],
          "restartPolicy": "Always",
          "terminationGracePeriodSeconds": 0,
          "dnsPolicy": "ClusterFirst",
          "securityContext": {},
          "schedulerName": "default-scheduler"
        }
      },
      "updateStrategy": {
        "type": "RollingUpdate",
        "rollingUpdate": {
          "maxUnavailable": 1,
          "maxSurge": 0
        }
      },
      "revisionHistoryLimit": 10
    },
    "status": {
      "currentNumberScheduled": 1,
      "numberMisscheduled": 0,
      "desiredNumberScheduled": 1,
      "numberReady": 1,
      "observedGeneration": 1,
      "updatedNumberScheduled": 1,
      "numberAvailable": 1
    }
  },
  "responseObject": {
    "kind": "DaemonSet",
    "apiVersion": "apps/v1",
    "metadata": {
      "name": "dw-harn-daemonsets",
      "namespace": "dw-harn",
      "uid": "00000000-0000-0000-0000-000000000000",
      "resourceVersion": "680",
      "generation": 1,
      "creationTimestamp": "2026-07-02T21:30:54Z",
      "labels": {
        "dw-harn-patched": "1"
      },
      "annotations": {
        "deprecated.daemonset.template.generation": "1"
      }
    },
    "spec": {
      "selector": {
        "matchLabels": {
          "app": "dw-harn"
        }
      },
      "template": {
        "metadata": {
          "labels": {
            "app": "dw-harn"
          }
        },
        "spec": {
          "containers": [
            {
              "name": "c",
              "image": "docker.io/library/busybox:1.36",
              "command": [
                "sh",
                "-c",
                "sleep 3600"
              ],
              "resources": {},
              "terminationMessagePath": "/dev/termination-log",
              "terminationMessagePolicy": "File",
              "imagePullPolicy": "IfNotPresent"
            }
          ],
          "restartPolicy": "Always",
          "terminationGracePeriodSeconds": 0,
          "dnsPolicy": "ClusterFirst",
          "securityContext": {},
          "schedulerName": "default-scheduler"
        }
      },
      "updateStrategy": {
        "type": "RollingUpdate",
        "rollingUpdate": {
          "maxUnavailable": 1,
          "maxSurge": 0
        }
      },
      "revisionHistoryLimit": 10
    },
    "status": {
      "currentNumberScheduled": 1,
      "numberMisscheduled": 0,
      "desiredNumberScheduled": 1,
      "numberReady": 1,
      "observedGeneration": 1,
      "updatedNumberScheduled": 1,
      "numberAvailable": 1
    }
  },
  "requestReceivedTimestamp": "2026-07-02T21:30:58.331530Z",
  "stageTimestamp": "2026-07-02T21:30:58.335093Z",
  "annotations": {
    "authorization.k8s.io/decision": "allow",
    "authorization.k8s.io/reason": "RBAC: allowed by ClusterRoleBinding \"kubeadm:cluster-admins\" of ClusterRole \"cluster-admin\" to Group \"kubeadm:cluster-admins\""
  }
}

References #

patch daemonsets/status

#
Resource
daemonsets

Example Audit Event #

{
  "kind": "Event",
  "apiVersion": "audit.k8s.io/v1",
  "level": "RequestResponse",
  "auditID": "00000000-0000-0000-0000-000000000000",
  "stage": "ResponseComplete",
  "requestURI": "/apis/apps/v1/namespaces/dw-harn/daemonsets/dw-harn-daemonsets/status?fieldManager=kubectl-patch",
  "verb": "patch",
  "user": {
    "username": "kubernetes-admin",
    "groups": [
      "kubeadm:cluster-admins",
      "system:authenticated"
    ],
    "extra": {
      "authentication.kubernetes.io/credential-id": [
        "X509SHA256=786fc563dbb253683c44d23d0aac3742ea61ade7f27a43f50934a82662e15409"
      ]
    }
  },
  "sourceIPs": [
    "203.0.113.10"
  ],
  "userAgent": "kubectl/v1.36.2 (linux/amd64) kubernetes/24e2b02",
  "objectRef": {
    "resource": "daemonsets",
    "namespace": "dw-harn",
    "name": "dw-harn-daemonsets",
    "apiGroup": "apps",
    "apiVersion": "v1",
    "subresource": "status"
  },
  "responseStatus": {
    "metadata": {},
    "code": 200
  },
  "requestObject": {},
  "responseObject": {
    "kind": "DaemonSet",
    "apiVersion": "apps/v1",
    "metadata": {
      "name": "dw-harn-daemonsets",
      "namespace": "dw-harn",
      "uid": "00000000-0000-0000-0000-000000000000",
      "resourceVersion": "710",
      "generation": 1,
      "creationTimestamp": "2026-07-02T22:17:36Z",
      "labels": {
        "dw-harn-patched": "1"
      },
      "annotations": {
        "deprecated.daemonset.template.generation": "1"
      }
    },
    "spec": {
      "selector": {
        "matchLabels": {
          "app": "dw-harn"
        }
      },
      "template": {
        "metadata": {
          "labels": {
            "app": "dw-harn"
          }
        },
        "spec": {
          "containers": [
            {
              "name": "c",
              "image": "docker.io/library/busybox:1.36",
              "command": [
                "sh",
                "-c",
                "sleep 3600"
              ],
              "resources": {},
              "terminationMessagePath": "/dev/termination-log",
              "terminationMessagePolicy": "File",
              "imagePullPolicy": "IfNotPresent"
            }
          ],
          "restartPolicy": "Always",
          "terminationGracePeriodSeconds": 0,
          "dnsPolicy": "ClusterFirst",
          "securityContext": {},
          "schedulerName": "default-scheduler"
        }
      },
      "updateStrategy": {
        "type": "RollingUpdate",
        "rollingUpdate": {
          "maxUnavailable": 1,
          "maxSurge": 0
        }
      },
      "revisionHistoryLimit": 10
    },
    "status": {
      "currentNumberScheduled": 1,
      "numberMisscheduled": 0,
      "desiredNumberScheduled": 1,
      "numberReady": 1,
      "observedGeneration": 1,
      "updatedNumberScheduled": 1,
      "numberAvailable": 1
    }
  },
  "requestReceivedTimestamp": "2026-07-02T22:17:40.217296Z",
  "stageTimestamp": "2026-07-02T22:17:40.220019Z",
  "annotations": {
    "authorization.k8s.io/decision": "allow",
    "authorization.k8s.io/reason": "RBAC: allowed by ClusterRoleBinding \"kubeadm:cluster-admins\" of ClusterRole \"cluster-admin\" to Group \"kubeadm:cluster-admins\""
  }
}

References #

any verb on daemonsets (synthetic aggregation)

#
Resource
daemonsets

Description

Synthetic aggregation for rules that filter the daemonsets resource with no specific verb. Not a distinct audit record; hosts rule listings that key on objectRef.resource alone.