> For the complete documentation index, see [llms.txt](https://docs.stepsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stepsecurity.io/start-here/guides/how-can-developers-see-and-fix-stepsecurity-findings-without-securitys-help.md).

# 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](/github/github-checks.md)

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](/github/github-checks/configuration.md))

**Follow this interactive walkthrough to see how it works:**

{% embed url="<https://app.storylane.io/share/rrrcr1ybzzge>" %}

### [Policy Driven PRs](/github/orchestrate-security/policy-driven-prs.md)

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:**

{% embed url="<https://app.storylane.io/share/fqqaobdwgodp>" %}

### [Workflow Run Policies](/github-actions/workflow-run-policies.md)

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:**

{% embed url="<https://app.storylane.io/share/wqwt6rvtvcgf>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stepsecurity.io/start-here/guides/how-can-developers-see-and-fix-stepsecurity-findings-without-securitys-help.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.