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

42141 Builds Secured

View Case Study

CISA

73119 Builds Secured

View Case Study

Google

5262 Builds Secured

View Case Study

Newrelic

20748 Builds Secured

View Case Study

Redhat

1730 Builds Secured

View Case Study

Intel

77806 Builds Secured

View Case Study

Backstage

38871 Builds Secured

View Case Study

Block

4455 Builds Secured

View Case Study

Kubernetes

3344 Builds Secured

View Case Study

Azure

8026 Builds Secured

View Case Study

Bazel

3742 Builds Secured

View Case Study

dotnet

12410 Builds Secured

View Case Study

Jaeger

26688 Builds Secured

View Case Study

U.S. Digital Response

5152 Builds Secured

View Case Study

Samsung

1874 Builds Secured

View Case Study

Stirling PDF

3242 Builds Secured

View Case Study

Node.js

4958 Builds Secured

View Case Study

Atlantis

15812 Builds Secured

View Case Study

Picnic

2664 Builds Secured

View Case Study

Fleet

31490 Builds Secured

View Case Study

Sigstore

3786 Builds Secured

View Case Study

InstructLab

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