A week before an audit, a security reviewer asks for the list of namespaces that accept any inbound traffic. You have no answer to hand, and no latency graph holds it. That is the gap KSPM Kubernetes (Kubernetes Security Posture Management) fills in Dynatrace: a running inventory of configuration drift, kept by the platform you already use for monitoring.
I treat it here as an operations decision rather than a recipe: what the tool reads, what it costs in privileges, how to wire it through the DynaKube, and which rules to open first. Everything applies to Dynatrace SaaS , based on the « Latest Dynatrace » pages I read. I checked nothing for Dynatrace Managed and will not pretend otherwise.
KSPM Kubernetes: two sources, one pool of events
KSPM does not scan the cluster from outside. It combines two separate reads. A node configuration collector, run as a DaemonSet, re-reads each machine every minute. The ActiveGate queries the Kubernetes API once an hour.…