Harden-Runner Adds Runtime Monitoring and Egress Controls for Kata and Nitro Runner Pods

Summary
Step Security says Harden-Runner now provides runtime monitoring and outbound network policy enforcement inside GitHub Actions runner pods on Kata Containers and Amazon EKS Nitro Sandboxes, with job activity shown in workflow summaries.
Key points
- Harden-Runner agent v1.9.7 and later supports Actions Runner Controller pods on Kata Containers and Amazon EKS Nitro Sandboxes.
- The vendor says monitoring covers network, DNS, process and HTTPS activity inside each microVM.
- The product can enforce policies on a job’s outbound network access.
- Job views include processes, resolved domains, network connections and HTTPS requests, including Go and HTTP/2 requests.
- The agent is installed in the guest image and uses job hooks to associate activity and logs with workflow runs.
- Nitro Sandbox setup requires the runner pod runtimeClassName to be set to isolated-sandbox; configured workflows do not need changes to their steps.
Article Details
- Event Type
- Product capability and compatibility announcement
- Impact
- Harden-Runner agent v1.9.7 and later supports ARC runner pods on Kata Containers and Amazon EKS Nitro Sandboxes. It provides in-VM monitoring of network, DNS, process, and HTTPS activity, plus outbound egress policy enforcement and job summaries. The setup is performed in the runner infrastructure, and existing workflows can use the monitoring without changes to their steps.
Vendors
Amazon Web ServicesSandboxes, the installation steps rebuild the sandbox guest kernel with eBPF tracing enabled. They use AWS’s source, patches and configuration from the open source Bottlerocket kernel kit. Packer then bakes theGitHubMoving a GitHub Actions runner pod into a microVM gives it its own Linux kernel and a boundary around the job. But a malicious dependency or tampered action still runs inside that boundary, with access to the job’sStepSecurityOpen the StepSecurity app and go to Harden-Runner installation, then the Self-Hosted VM tab. Select ARC runners on Kata Containers or ARC runners on Amazon EKS Nitro Sandboxes for the installation steps. Your API key
Products
Actions Runner Controllernow supports those runners. We bring runtime monitoring and egress policy enforcement inside Actions Runner Controller (ARC) runner pods on Kata Containers and Amazon EKS (Elastic Kubernetes Service) Nitro Sandboxes.Amazon EKS Nitro Sandboxesthen the Self-Hosted VM tab. Select ARC runners on Kata Containers or ARC runners on Amazon EKS Nitro Sandboxes for the installation steps. Your API key and the current agent release are already filled in.GitHub ActionsMoving a GitHub Actions runner pod into a microVM gives it its own Linux kernel and a boundary around the job. But a malicious dependency or tampered action still runs inside that boundary, with access to the job’sHarden-RunnerHarden-Runner now supports those runners. We bring runtime monitoring and egress policy enforcement inside Actions Runner Controller (ARC) runner pods on Kata Containers and Amazon EKS (Elastic Kubernetes Service) NitroKata containersmonitoring and egress policy enforcement inside Actions Runner Controller (ARC) runner pods on Kata Containers and Amazon EKS (Elastic Kubernetes Service) Nitro Sandboxes. Your jobs keep their VM isolation, and
