StepSecurity
Harden-Runner Adds Runtime Security to Kata and Nitro Pods
Harden-Runner now extends runtime security into GitHub Actions runner pods by monitoring inside the microVMs used with Kata Containers and Amazon EKS Nitro Sandboxes. The feature set in Harden-Runner agent v1.9.7 and later provides the same level of coverage as a self-hosted VM: monitoring of network activity, DNS, processes and HTTPS events, plus egress policy enforcement to control outbound connections.
Job visibility is joined with a job summary, so investigators can see, under the Workflow Runs view, the processes, domains resolved, network connections and HTTPS requests generated by each job. The agent runs inside the VM boundary, and the job hooks associate the VM activity with the corresponding workflow run, enabling end-to-end visibility without altering workflows.
For Nitro Sandboxes, where the guest kernel is rebuilt with eBPF tracing enabled, the setup uses the Bottlerocket kernel kit sources and patches, with Packer baked into the sandbox guest image on the node AMI; Kata Containers rely on the existing kata-deploy image with the eBPF-enabled guest kernel. The guest image includes the Harden-Runner agent so monitoring starts at VM boot, before the runner itself.
Job hooks link the agent’s activity to each job, adding summaries and logs to the job output at the start and end. The article notes that two VM-per-pod runtimes are supported for ARC runners, and that Nitro Sandbox pods must set runtimeClassName: isolated-sandbox. Harden-Runner remains open source, with installation steps available in the StepSecurity documentation.