Skip to content

DataKit Security

This document covers CA trust store updates and common permissions for Kubernetes node deployments, including how to adjust them.

eMudhra Incident Response

In October 2026, weak keys were discovered in eight eMudhra intermediate CA certificates. Attackers can use these keys to forge certificates and impersonate servers to clients that still trust the affected chains. See Cloudflare's incident report for details.

DataKit v2 upgraded to Go 1.26.10 in 2.16.1 to reject affected chains during certificate verification. Upgrade to that release or later.

DataKit v1 remains pinned to Go 1.19.12 for compatibility and requires CA trust store updates according to deployment mode:

  1. Container images: CA trust store updates are included for 1.94.3. This version has not been released; it will be released after the UOS base image update. Once available, pull the new image and redeploy.
  2. Linux hosts: Update system CAs yourself and restart DataKit. On Ubuntu, install the fixed package for your OS release listed in USN-8944-1. For example, Ubuntu 22.04 requires ca-certificates version 20260816ubuntu0.22.04.1 or later. Follow vendor guidance for other distributions or offline hosts. Upgrading DataKit alone does not update system CAs.
  3. Windows hosts: Confirm receipt of Microsoft's certificate trust list (CTL) updates for this incident; hosts that have received them need no additional CA import. If automatic updates are disabled or the host is offline, ask the administrator to apply the updates following Microsoft's guidance, then restart DataKit.

If you configure ca_certs, or set SSL_CERT_FILE / SSL_CERT_DIR for DataKit on Linux, also review and update the corresponding CA files or directories.

After updating, restart DataKit v1 by running datakit service -R with administrator privileges. Check the runtime logs for certificate verification errors and confirm that newly collected data continues to arrive on the platform.

Privilege Details

Some DataKit collectors need to read host files, access host networks, or load eBPF programs. Required permissions depend on the enabled collectors and deployment mode.

Pod-Level Privileges

Setting Purpose and impact
hostPID: true Uses the host process namespace so the container can see host processes. Disabling it affects collectors that depend on this process view.
hostNetwork: true Uses the host network namespace, allowing DataKit to access host interfaces and listen on node addresses. When disabling it, check data senders' destination addresses against the new network configuration.

Container-Level Privileges

Setting Purpose and impact
securityContext.privileged: true Grants broad kernel and device access. Standard node deployment templates enable it for collection features such as eBPF that need these permissions.
Running as root Provides access to protected files and directories. Before switching to a non-root user, check access to collection and runtime directories.
ports.hostPort Maps a container port to a node port for incoming data. A Kubernetes Service can provide a data endpoint after this mapping is removed.
securityContext.readOnlyRootFilesystem: false Allows writes to the container root filesystem. Before setting it to true, provide writable volumes for runtime paths such as caches and logs.

Permissions and host directory mounts together determine which resources a container can access. Existing hostPath mounts require a separate check when disabling a permission. See Kubernetes security contexts for field definitions.

Adjust Configuration

  1. Identify the collectors to retain and the host directories, networks, and devices they access before changing permissions. Disabling one collector does not remove another collector's need for the same permission.
  2. When switching data reception to a Kubernetes Service, update application destination addresses and ports, and check connectivity.
  3. Use nodeSelector or node affinity to select deployment nodes. Configure tolerations as needed for tainted nodes.
  4. After making changes, check collector startup logs and reported data to confirm that the required collection features still work.

GKE Autopilot uses dedicated deployment settings. See the GCP GKE Autopilot deployment guide.