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

28167 Builds Secured

View Case Study

CISA

101582 Builds Secured

View Case Study

Google

3826 Builds Secured

View Case Study

Redhat

3812 Builds Secured

View Case Study

Backstage

31526 Builds Secured

View Case Study

Newrelic

11388 Builds Secured

View Case Study

Block

5576 Builds Secured

View Case Study

Intel

66258 Builds Secured

View Case Study

Kubernetes

2896 Builds Secured

View Case Study

Azure

8074 Builds Secured

View Case Study

Bazel

3558 Builds Secured

View Case Study

dotnet

4902 Builds Secured

View Case Study

Jaeger

10208 Builds Secured

View Case Study

U.S. Digital Response

6180 Builds Secured

View Case Study

Samsung

134 Builds Secured

View Case Study

Stirling PDF

2026 Builds Secured

View Case Study

Node.js

4122 Builds Secured

View Case Study

Atlantis

4112 Builds Secured

View Case Study

Picnic

1386 Builds Secured

View Case Study

Fleet

29317 Builds Secured

View Case Study

Sigstore

1670 Builds Secured

View Case Study

InstructLab

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