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

14315 Builds Secured

View Case Study

CISA

31006 Builds Secured

View Case Study

Google

2792 Builds Secured

View Case Study

Redhat

6298 Builds Secured

View Case Study

Backstage

21384 Builds Secured

View Case Study

Newrelic

16141 Builds Secured

View Case Study

Block

1382 Builds Secured

View Case Study

Intel

57878 Builds Secured

View Case Study

Kubernetes

1282 Builds Secured

View Case Study

Azure

11920 Builds Secured

View Case Study

Bazel

2548 Builds Secured

View Case Study

dotnet

5538 Builds Secured

View Case Study

Jaeger

24118 Builds Secured

View Case Study

U.S. Digital Response

78 Builds Secured

View Case Study

Samsung

1086 Builds Secured

View Case Study

Stirling PDF

3254 Builds Secured

View Case Study

Node.js

6221 Builds Secured

View Case Study

Atlantis

13586 Builds Secured

View Case Study

Picnic

1000 Builds Secured

View Case Study

Fleet

28505 Builds Secured

View Case Study

Sigstore

1342 Builds Secured

View Case Study

InstructLab

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