> 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/azure-devops/harden-runner/suppression-rules.md).
# Suppression Rules
Suppression Rules allow you to ignore specific outbound network calls from known domains that are not a security concern.
For example, if your organization regularly makes outbound calls to `www.google.com`, but these calls are being flagged as anomalous, you can create a rule to prevent unnecessary alerts for this domain.
### Scope of Suppression Rules
You can create suppression rules at different levels, depending on how broadly you want to apply them:
* Job Level – Applies to a specific job.
* Project Level – Applies to an entire project.
* Organization Level – Applies across all repositories within the organization.
### How to Create a Rule
There are two ways to create a rule, from the:
* Suppression Rules page
* All Detections page
#### **Method 1: From the Suppression Rules Page**
**Step 1:** Navigate to Suppression`Rules` under the Harden Runner Section
**Step 2:** Click "Create rule"
**Step 3:** Enter the following details:
* Rule Name – Provide a meaningful name for the rule.
* Description – Add details about why this rule is being created.
* Endpoint to Ignore – Specify the domain or endpoint to suppress (use \* for wildcard matching).
* Scope – Choose the level of the rule: Job, Project or Organization.
**Step 4:** Click "Save"
#### **Method 2: Creating a Rule from the All Detections Page**
**Step 1:** Navigate to `Detections` locate the endpoint you wish to suppress under the `Anomalous Outbound Network Calls`, then click the three-dot menu (⋮) next to it
**Step 2:** Click "Suppress detection"
**Step 3:** You will be redirected to the Rules page with the detection details pre-filled, add the name and description.
**Step 4:** Click "Save"
---
# 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/azure-devops/harden-runner/suppression-rules.md?ask=&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.