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

32760 Builds Secured

View Case Study

CISA

35588 Builds Secured

View Case Study

Google

8760 Builds Secured

View Case Study

Redhat

6922 Builds Secured

View Case Study

Backstage

31148 Builds Secured

View Case Study

Newrelic

10048 Builds Secured

View Case Study

Block

1340 Builds Secured

View Case Study

Intel

64368 Builds Secured

View Case Study

Kubernetes

1742 Builds Secured

View Case Study

Azure

12336 Builds Secured

View Case Study

Bazel

3264 Builds Secured

View Case Study

dotnet

14098 Builds Secured

View Case Study

Jaeger

3858 Builds Secured

View Case Study

U.S. Digital Response

300 Builds Secured

View Case Study

Samsung

1046 Builds Secured

View Case Study

Stirling PDF

5326 Builds Secured

View Case Study

Node.js

6646 Builds Secured

View Case Study

Atlantis

11146 Builds Secured

View Case Study

Picnic

1760 Builds Secured

View Case Study

Fleet

37473 Builds Secured

View Case Study

Sigstore

1562 Builds Secured

View Case Study

InstructLab

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