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

· Original article ↗

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

Products

Tools

Related Articles