Community

CI/CD Pipelines Secured

StepSecurity Harden-Runner secures CI/CD runners by providing network visibility and enforcing network egress filtering. See it in action with our interactive demo of how it detected the tj-actions breach.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Microsoft

33304 Builds Secured

View Case Study

CISA

164875 Builds Secured

View Case Study

Google

11524 Builds Secured

View Case Study

Redhat

9030 Builds Secured

View Case Study

Backstage

193163 Builds Secured

View Case Study

Newrelic

36629 Builds Secured

View Case Study

Block

366 Builds Secured

View Case Study

Intel

76250 Builds Secured

View Case Study

Kubernetes

1960 Builds Secured

View Case Study

Azure

13965 Builds Secured

View Case Study

Bazel

4530 Builds Secured

View Case Study

dotnet

12894 Builds Secured

View Case Study

Jaeger

21431 Builds Secured

View Case Study

U.S. Digital Response

60 Builds Secured

View Case Study

Samsung

1634 Builds Secured

View Case Study

Stirling PDF

22792 Builds Secured

View Case Study

Node.js

9766 Builds Secured

View Case Study

Atlantis

10352 Builds Secured

View Case Study

Picnic

2816 Builds Secured

View Case Study

Fleet

65228 Builds Secured

View Case Study

Sigstore

2138 Builds Secured

View Case Study

InstructLab

88 Builds Secured

View Case Study

There are no pipelines found matching your search query.

Add Harden Runner to your own repository

How-To

StepSecurity Harden-Runner secures CI/CD runners by providing network visibility and enforcing network egress filtering.

01

Update Your GitHub Actions Workflow

steps:

- uses: step-security/harden-runner@v2

with:

egress-policy: audit

Automate this change using a pull request.

02

Run Your Workflow

Execute your workflow as usual.

03

Review Security Insights

After completion, check the GitHub Actions Job summary for a link to detailed security insights, detections, and recommendations.