Workload attestation is the process of proving what software is actually running before a system issues trust or identity to it. In Kubernetes and similar platforms, an attestor may check signals such as node state, process details, or Linux cgroup information to decide whether a workload is genuine and allowed to receive credentials.
This matters because modern identity systems, including SPIFFE and SPIRE, rely on attestation to stop impostors from getting valid workload identities. If an attacker gains root on a node, they may tamper with the evidence used for attestation and make a malicious process look legitimate. Defenders reduce this risk by hardening nodes, limiting privileged access, and protecting the integrity of the attestation inputs and the trusted execution path.