> 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-to-enable-network-and-runtime-monitoring-harden-runner-for-runners.md).

# How to enable network and runtime monitoring (Harden-Runner) for runners

### Adding Harden-Runner to GitHub-Hosted Runners

You can integrate Harden-Runner into your workflows in three ways:

#### 1. Secure Workflow (Recommended for Specific Workflow Files)

Use [Secure Workflow](/github/orchestrate-security/secure-workflow.md) to quickly and securely add Harden-Runner to individual workflows via an interactive setup.

Follow the interactive demo for Secure Workflow:

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

#### 2. Secure Repo (Recommended for Entire Repositories)

Apply Harden-Runner across all workflows in your repository with a single configuration using [Secure Repo](/github/orchestrate-security/secure-repo.md).

Follow the interactive demo for Secure Repo:

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

#### 3. Policy Driven PRs (Recommended for Production)

Policy-driven automation lets StepSecurity automatically generate GitHub Issues or Pull Requests to enable runtime monitoring (Harden-Runner) across your organization.

Follow this interactive walkthrough to see how it works:

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

### Adding Harden-Runner to Self-Hosted Runners

For self-hosted runners, you install the Harden-Runner agent on the runner itself. Once the agent is deployed, it monitors every job on that runner, so you do not need to add the Harden-Runner Action to your workflows for `audit` mode.

To get started:

1. In the StepSecurity app, go to [**Harden-Runner → Installation**](/github-actions/harden-runner/harden-runner-installation.md).
2. Select your runner environment, for example ARC (Actions Runner Controller) or Self-Hosted VM (virtual machine).
3. Follow the setup instructions shown for that environment.

{% hint style="info" %}
To apply [Policy Store](/github-actions/harden-runner/policy-store.md) policies on self-hosted runners, also configure the StepSecurity pre-job hook. See [Runner Job Hooks](/github-actions/harden-runner/harden-runner-installation/runner-job-hooks.md).
{% endhint %}


---

# 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-to-enable-network-and-runtime-monitoring-harden-runner-for-runners.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.