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

19140 Builds Secured

View Case Study

CISA

29320 Builds Secured

View Case Study

Google

3568 Builds Secured

View Case Study

Redhat

5132 Builds Secured

View Case Study

Backstage

20420 Builds Secured

View Case Study

Newrelic

14342 Builds Secured

View Case Study

Block

2954 Builds Secured

View Case Study

Intel

44500 Builds Secured

View Case Study

Kubernetes

1378 Builds Secured

View Case Study

Azure

6312 Builds Secured

View Case Study

Bazel

2404 Builds Secured

View Case Study

dotnet

4286 Builds Secured

View Case Study

Jaeger

14694 Builds Secured

View Case Study

U.S. Digital Response

288 Builds Secured

View Case Study

Samsung

358 Builds Secured

View Case Study

Stirling PDF

7438 Builds Secured

View Case Study

Node.js

8080 Builds Secured

View Case Study

Atlantis

3918 Builds Secured

View Case Study

Picnic

1762 Builds Secured

View Case Study

Fleet

23940 Builds Secured

View Case Study

Sigstore

1306 Builds Secured

View Case Study

InstructLab

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