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

11270 Builds Secured

View Case Study

CISA

17376 Builds Secured

View Case Study

Google

8462 Builds Secured

View Case Study

Redhat

10054 Builds Secured

View Case Study

Backstage

27400 Builds Secured

View Case Study

Newrelic

2340 Builds Secured

View Case Study

Block

3208 Builds Secured

View Case Study

Intel

67508 Builds Secured

View Case Study

Kubernetes

1648 Builds Secured

View Case Study

Azure

4678 Builds Secured

View Case Study

Bazel

1986 Builds Secured

View Case Study

dotnet

4870 Builds Secured

View Case Study

Jaeger

10972 Builds Secured

View Case Study

U.S. Digital Response

6 Builds Secured

View Case Study

Samsung

726 Builds Secured

View Case Study

Stirling PDF

11432 Builds Secured

View Case Study

Node.js

9088 Builds Secured

View Case Study

Atlantis

12110 Builds Secured

View Case Study

Picnic

2080 Builds Secured

View Case Study

Fleet

64304 Builds Secured

View Case Study

Sigstore

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