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

31748 Builds Secured

View Case Study

CISA

33864 Builds Secured

View Case Study

Google

6778 Builds Secured

View Case Study

Redhat

4130 Builds Secured

View Case Study

Backstage

90332 Builds Secured

View Case Study

Newrelic

20054 Builds Secured

View Case Study

Block

2570 Builds Secured

View Case Study

Intel

55084 Builds Secured

View Case Study

Kubernetes

1550 Builds Secured

View Case Study

Azure

5894 Builds Secured

View Case Study

Bazel

2514 Builds Secured

View Case Study

dotnet

4766 Builds Secured

View Case Study

Jaeger

14880 Builds Secured

View Case Study

U.S. Digital Response

6 Builds Secured

View Case Study

Samsung

1430 Builds Secured

View Case Study

Stirling PDF

11330 Builds Secured

View Case Study

Node.js

5452 Builds Secured

View Case Study

Atlantis

8534 Builds Secured

View Case Study

Picnic

2854 Builds Secured

View Case Study

Fleet

37854 Builds Secured

View Case Study

Sigstore

3010 Builds Secured

View Case Study

InstructLab

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