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

20951 Builds Secured

View Case Study

CISA

86947 Builds Secured

View Case Study

Google

6978 Builds Secured

View Case Study

Redhat

8911 Builds Secured

View Case Study

Backstage

39333 Builds Secured

View Case Study

Newrelic

20428 Builds Secured

View Case Study

Block

1670 Builds Secured

View Case Study

Intel

75226 Builds Secured

View Case Study

Kubernetes

2766 Builds Secured

View Case Study

Azure

12334 Builds Secured

View Case Study

Bazel

3935 Builds Secured

View Case Study

dotnet

11623 Builds Secured

View Case Study

Jaeger

10280 Builds Secured

View Case Study

U.S. Digital Response

312 Builds Secured

View Case Study

Samsung

1954 Builds Secured

View Case Study

Stirling PDF

4348 Builds Secured

View Case Study

Node.js

7464 Builds Secured

View Case Study

Atlantis

1636 Builds Secured

View Case Study

Picnic

3161 Builds Secured

View Case Study

Fleet

24555 Builds Secured

View Case Study

Sigstore

2180 Builds Secured

View Case Study

InstructLab

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