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

20596 Builds Secured

View Case Study

CISA

36124 Builds Secured

View Case Study

Google

9628 Builds Secured

View Case Study

Redhat

11008 Builds Secured

View Case Study

Backstage

45132 Builds Secured

View Case Study

Newrelic

9068 Builds Secured

View Case Study

Block

1828 Builds Secured

View Case Study

Intel

79630 Builds Secured

View Case Study

Kubernetes

3038 Builds Secured

View Case Study

Azure

6994 Builds Secured

View Case Study

Bazel

2884 Builds Secured

View Case Study

dotnet

6944 Builds Secured

View Case Study

Jaeger

14182 Builds Secured

View Case Study

U.S. Digital Response

6 Builds Secured

View Case Study

Samsung

868 Builds Secured

View Case Study

Stirling PDF

11537 Builds Secured

View Case Study

Node.js

8300 Builds Secured

View Case Study

Atlantis

8276 Builds Secured

View Case Study

Picnic

1218 Builds Secured

View Case Study

Fleet

102682 Builds Secured

View Case Study

Sigstore

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