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

14371 Builds Secured

View Case Study

CISA

54365 Builds Secured

View Case Study

Google

4990 Builds Secured

View Case Study

Redhat

6213 Builds Secured

View Case Study

Backstage

27935 Builds Secured

View Case Study

Newrelic

15788 Builds Secured

View Case Study

Block

1132 Builds Secured

View Case Study

Intel

53562 Builds Secured

View Case Study

Kubernetes

2174 Builds Secured

View Case Study

Azure

8416 Builds Secured

View Case Study

Bazel

2347 Builds Secured

View Case Study

dotnet

6674 Builds Secured

View Case Study

Jaeger

6372 Builds Secured

View Case Study

U.S. Digital Response

300 Builds Secured

View Case Study

Samsung

1500 Builds Secured

View Case Study

Stirling PDF

2920 Builds Secured

View Case Study

Node.js

6090 Builds Secured

View Case Study

Atlantis

1326 Builds Secured

View Case Study

Picnic

904 Builds Secured

View Case Study

Fleet

15082 Builds Secured

View Case Study

Sigstore

1674 Builds Secured

View Case Study

InstructLab

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