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

30274 Builds Secured

View Case Study

CISA

51626 Builds Secured

View Case Study

Google

4076 Builds Secured

View Case Study

Redhat

5416 Builds Secured

View Case Study

Backstage

66822 Builds Secured

View Case Study

Newrelic

16462 Builds Secured

View Case Study

Block

1476 Builds Secured

View Case Study

Intel

73564 Builds Secured

View Case Study

Kubernetes

2568 Builds Secured

View Case Study

Azure

8660 Builds Secured

View Case Study

Bazel

3904 Builds Secured

View Case Study

dotnet

11598 Builds Secured

View Case Study

Jaeger

26554 Builds Secured

View Case Study

U.S. Digital Response

6 Builds Secured

View Case Study

Samsung

2620 Builds Secured

View Case Study

Stirling PDF

13110 Builds Secured

View Case Study

Node.js

9486 Builds Secured

View Case Study

Atlantis

9856 Builds Secured

View Case Study

Picnic

2114 Builds Secured

View Case Study

Fleet

59778 Builds Secured

View Case Study

Sigstore

2504 Builds Secured

View Case Study

InstructLab

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