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

14388 Builds Secured

View Case Study

CISA

28763 Builds Secured

View Case Study

Google

3802 Builds Secured

View Case Study

Newrelic

20672 Builds Secured

View Case Study

Redhat

198 Builds Secured

View Case Study

Intel

27957 Builds Secured

View Case Study

Backstage

17867 Builds Secured

View Case Study

Block

8732 Builds Secured

View Case Study

Kubernetes

1978 Builds Secured

View Case Study

Azure

5480 Builds Secured

View Case Study

Bazel

1992 Builds Secured

View Case Study

dotnet

3326 Builds Secured

View Case Study

Jaeger

10366 Builds Secured

View Case Study

U.S. Digital Response

5872 Builds Secured

View Case Study

Samsung

260 Builds Secured

View Case Study

Stirling PDF

1934 Builds Secured

View Case Study

Node.js

3106 Builds Secured

View Case Study

Atlantis

1232 Builds Secured

View Case Study

Picnic

1264 Builds Secured

View Case Study

Fleet

29272 Builds Secured

View Case Study

Sigstore

1374 Builds Secured

View Case Study

InstructLab

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