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

25430 Builds Secured

View Case Study

CISA

29262 Builds Secured

View Case Study

Google

30712 Builds Secured

View Case Study

Redhat

6120 Builds Secured

View Case Study

Backstage

91582 Builds Secured

View Case Study

Newrelic

7942 Builds Secured

View Case Study

Block

2310 Builds Secured

View Case Study

Intel

105500 Builds Secured

View Case Study

Kubernetes

2294 Builds Secured

View Case Study

Azure

14198 Builds Secured

View Case Study

Bazel

4396 Builds Secured

View Case Study

dotnet

12028 Builds Secured

View Case Study

Jaeger

22104 Builds Secured

View Case Study

U.S. Digital Response

6 Builds Secured

View Case Study

Samsung

806 Builds Secured

View Case Study

Stirling PDF

10854 Builds Secured

View Case Study

Node.js

17224 Builds Secured

View Case Study

Atlantis

11686 Builds Secured

View Case Study

Picnic

2084 Builds Secured

View Case Study

Fleet

104288 Builds Secured

View Case Study

Sigstore

294 Builds Secured

View Case Study

InstructLab

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