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

30898 Builds Secured

View Case Study

CISA

52814 Builds Secured

View Case Study

Google

4178 Builds Secured

View Case Study

Redhat

5484 Builds Secured

View Case Study

Backstage

68392 Builds Secured

View Case Study

Newrelic

16536 Builds Secured

View Case Study

Block

1502 Builds Secured

View Case Study

Intel

75746 Builds Secured

View Case Study

Kubernetes

2580 Builds Secured

View Case Study

Azure

8754 Builds Secured

View Case Study

Bazel

3960 Builds Secured

View Case Study

dotnet

11664 Builds Secured

View Case Study

Jaeger

26794 Builds Secured

View Case Study

U.S. Digital Response

6 Builds Secured

View Case Study

Samsung

2620 Builds Secured

View Case Study

Stirling PDF

13210 Builds Secured

View Case Study

Node.js

9652 Builds Secured

View Case Study

Atlantis

10144 Builds Secured

View Case Study

Picnic

2182 Builds Secured

View Case Study

Fleet

60986 Builds Secured

View Case Study

Sigstore

2504 Builds Secured

View Case Study

InstructLab

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