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

8275 Builds Secured

View Case Study

CISA

37932 Builds Secured

View Case Study

Google

5285 Builds Secured

View Case Study

Redhat

5835 Builds Secured

View Case Study

Backstage

18764 Builds Secured

View Case Study

Newrelic

12009 Builds Secured

View Case Study

Block

616 Builds Secured

View Case Study

Intel

49646 Builds Secured

View Case Study

Kubernetes

1090 Builds Secured

View Case Study

Azure

6456 Builds Secured

View Case Study

Bazel

2107 Builds Secured

View Case Study

dotnet

4967 Builds Secured

View Case Study

Jaeger

16543 Builds Secured

View Case Study

U.S. Digital Response

78 Builds Secured

View Case Study

Samsung

1950 Builds Secured

View Case Study

Stirling PDF

4562 Builds Secured

View Case Study

Node.js

5820 Builds Secured

View Case Study

Atlantis

1432 Builds Secured

View Case Study

Picnic

1246 Builds Secured

View Case Study

Fleet

21040 Builds Secured

View Case Study

Sigstore

1230 Builds Secured

View Case Study

InstructLab

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