Pull-mirror of github.com/step-security/harden-runner
Find a file
2021-12-06 17:15:40 -08:00
.github/workflows Create release.yml 2021-12-06 13:36:17 -08:00
dist Print as string 2021-11-30 15:24:00 -08:00
src Print as string 2021-11-30 15:24:00 -08:00
.gitignore Add code for GH action 2021-10-28 10:16:48 -07:00
action.yml Update metadata 2021-11-19 07:21:14 -08:00
LICENSE Initial commit 2021-10-28 09:58:47 -07:00
package-lock.json Call monitor run 2021-11-30 14:16:09 -08:00
package.json Call monitor run 2021-11-30 14:16:09 -08:00
README.md Update README.md 2021-12-06 17:15:13 -08:00
SECURITY.md Create SECURITY.md 2021-11-19 13:19:40 -08:00
tsconfig.json Add code for GH action 2021-10-28 10:16:48 -07:00

Step Security Logo

Harden Runner

First-of-its-kind technology that automatically discovers and correlates outbound traffic with each step of a GitHub Actions workflow.

To use this GitHub Action, add the following code to your GitHub Actions workflow file as the first step.

steps:
    - uses: step-security/harden-runner@v1
      with:
        egress-policy: audit

In the workflow logs, you should see a link to security insights and recommendations.

Link in build log

Click on the link (example link) to view security insights and recommended egress policy (example below).

Step Security Logo

Step Security Logo

You can then add the correlated outbound endpoints to your workflow file, and only traffic to these endpoints will be allowed, thereby reducing risk from software supply chain attacks.