How can developers see and fix StepSecurity findings without security’s help?
StepSecurity enables developer self-service by surfacing actionable security findings directly in their existing workflows. This eliminates the need for back-and-forth with security teams and accelerates remediation.
We offer three key features to support this:
GitHub Checks integrate security insights directly into your pull requests, making issues visible at the point of change. Developers can review findings and take appropriate action as needed.
What it does:
Shows Harden-Runner findings in the GitHub Checks UI.
Detects anomalous outbound network calls during CI/CD runs.
Provides clear Pass/Fail statuses after workflows complete.
Show StepSecurity Checks (Required/Optional)
Follow this interactive walkthrough to see how it works:
Policy-driven automation lets StepSecurity automatically generates Pull Requests to fix security findings. Developers can then review the proposed changes and merge the PRs if they meet their standards.
Follow this interactive walkthrough to see how it works:
Workflow Run Policies allow you to enforce security controls by blocking GitHub Actions workflow runs that violate organization-defined policies. This is particularly useful for preventing misconfigurations and supply chain attacks in your CI/CD pipelines
Follow this interactive walkthrough to see how it works:
Last updated
Was this helpful?