> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xdr-3.x/cortex-xdr-3.x-documentation/investigate-and-respond-to-incidents/investigate-alerts/triage-and-investigate-alerts/view-generating-bioc-or-ioc-rule.md).

# View generating BIOC or IOC rule

You can view the BIOC or IOC rules that generated alerts directly from the Alerts table.

{% hint style="info" %}

### Notice

This functionality requires a Cortex XDR Pro license.
{% endhint %}

You can easily view and edit the BIOC and IOC rules that generated alerts directly from the **Alerts** table:

1. From the **Alerts** page, locate alerts with **Alert Sources**: **XDR BIOC** and **XDR IOC**.
2. Right-click the row, and select Manage Alert → **View generating rule**.

   Cortex XDR opens the BIOC rule that generated the alert in the **BIOC Rules** page. If the rule has been deleted, an empty table is displayed.
3. Review the rule, if necessary, right-click to perform available actions.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xdr-3.x/cortex-xdr-3.x-documentation/investigate-and-respond-to-incidents/investigate-alerts/triage-and-investigate-alerts/view-generating-bioc-or-ioc-rule.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.