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

13396 Builds Secured

View Case Study

CISA

10120 Builds Secured

View Case Study

Google

6888 Builds Secured

View Case Study

Redhat

3286 Builds Secured

View Case Study

Backstage

37388 Builds Secured

View Case Study

Newrelic

5682 Builds Secured

View Case Study

Block

1626 Builds Secured

View Case Study

Intel

52920 Builds Secured

View Case Study

Kubernetes

1280 Builds Secured

View Case Study

Azure

6238 Builds Secured

View Case Study

Bazel

2452 Builds Secured

View Case Study

dotnet

3892 Builds Secured

View Case Study

Jaeger

11314 Builds Secured

View Case Study

U.S. Digital Response

6 Builds Secured

View Case Study

Samsung

812 Builds Secured

View Case Study

Stirling PDF

8010 Builds Secured

View Case Study

Node.js

10312 Builds Secured

View Case Study

Atlantis

5278 Builds Secured

View Case Study

Picnic

2754 Builds Secured

View Case Study

Fleet

63576 Builds Secured

View Case Study

Sigstore

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