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

9508 Builds Secured

View Case Study

CISA

82434 Builds Secured

View Case Study

Google

4822 Builds Secured

View Case Study

Redhat

3698 Builds Secured

View Case Study

Backstage

19074 Builds Secured

View Case Study

Newrelic

14022 Builds Secured

View Case Study

Block

1568 Builds Secured

View Case Study

Intel

64802 Builds Secured

View Case Study

Kubernetes

780 Builds Secured

View Case Study

Azure

6602 Builds Secured

View Case Study

Bazel

1898 Builds Secured

View Case Study

dotnet

9096 Builds Secured

View Case Study

Jaeger

11125 Builds Secured

View Case Study

U.S. Digital Response

210 Builds Secured

View Case Study

Samsung

262 Builds Secured

View Case Study

Stirling PDF

4940 Builds Secured

View Case Study

Node.js

1818 Builds Secured

View Case Study

Atlantis

3538 Builds Secured

View Case Study

Picnic

1608 Builds Secured

View Case Study

Fleet

30673 Builds Secured

View Case Study

Sigstore

1542 Builds Secured

View Case Study

InstructLab

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