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

19154 Builds Secured

View Case Study

CISA

140787 Builds Secured

View Case Study

Google

4704 Builds Secured

View Case Study

Redhat

6954 Builds Secured

View Case Study

Backstage

56716 Builds Secured

View Case Study

Newrelic

23026 Builds Secured

View Case Study

Block

4478 Builds Secured

View Case Study

Intel

65322 Builds Secured

View Case Study

Kubernetes

1650 Builds Secured

View Case Study

Azure

9121 Builds Secured

View Case Study

Bazel

4458 Builds Secured

View Case Study

dotnet

8506 Builds Secured

View Case Study

Jaeger

27950 Builds Secured

View Case Study

U.S. Digital Response

60 Builds Secured

View Case Study

Samsung

1052 Builds Secured

View Case Study

Stirling PDF

18386 Builds Secured

View Case Study

Node.js

9412 Builds Secured

View Case Study

Atlantis

7652 Builds Secured

View Case Study

Picnic

1976 Builds Secured

View Case Study

Fleet

49461 Builds Secured

View Case Study

Sigstore

2352 Builds Secured

View Case Study

InstructLab

84 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.