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

14751 Builds Secured

View Case Study

CISA

22842 Builds Secured

View Case Study

Google

11092 Builds Secured

View Case Study

Redhat

13266 Builds Secured

View Case Study

Backstage

34358 Builds Secured

View Case Study

Newrelic

3621 Builds Secured

View Case Study

Block

1280 Builds Secured

View Case Study

Intel

70230 Builds Secured

View Case Study

Kubernetes

2512 Builds Secured

View Case Study

Azure

5786 Builds Secured

View Case Study

Bazel

3216 Builds Secured

View Case Study

dotnet

4174 Builds Secured

View Case Study

Jaeger

22670 Builds Secured

View Case Study

U.S. Digital Response

6 Builds Secured

View Case Study

Samsung

1746 Builds Secured

View Case Study

Stirling PDF

8642 Builds Secured

View Case Study

Node.js

8182 Builds Secured

View Case Study

Atlantis

7018 Builds Secured

View Case Study

Picnic

1398 Builds Secured

View Case Study

Fleet

103242 Builds Secured

View Case Study

Sigstore

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