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

20512 Builds Secured

View Case Study

CISA

15206 Builds Secured

View Case Study

Google

10506 Builds Secured

View Case Study

Redhat

4282 Builds Secured

View Case Study

Backstage

49854 Builds Secured

View Case Study

Newrelic

8676 Builds Secured

View Case Study

Block

2810 Builds Secured

View Case Study

Intel

71332 Builds Secured

View Case Study

Kubernetes

1974 Builds Secured

View Case Study

Azure

7768 Builds Secured

View Case Study

Bazel

3132 Builds Secured

View Case Study

dotnet

6330 Builds Secured

View Case Study

Jaeger

13148 Builds Secured

View Case Study

U.S. Digital Response

6 Builds Secured

View Case Study

Samsung

860 Builds Secured

View Case Study

Stirling PDF

9386 Builds Secured

View Case Study

Node.js

13542 Builds Secured

View Case Study

Atlantis

7548 Builds Secured

View Case Study

Picnic

3468 Builds Secured

View Case Study

Fleet

86460 Builds Secured

View Case Study

Sigstore

366 Builds Secured

View Case Study

InstructLab

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