> 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-agentix/detect-investigate-and-respond-to-threats/threat-intel-management/indicator-configuration/generate-issues-from-indicator-rules.md). # Generate issues from indicator rules Indicator rules enable you to generate issues from indicators in Cortex AgentiX for detection. These rules allow you to select indicators or indicator traits to be detected by the tenant. Indicator rules marked for detection, generate issues that you can then track and investigate. {% hint style="info" %} ### Note Indicators should be present in the Threat Intelligence database (**Threat Management** → **Threat Intelligence** → **Indicators**) before creating detection rules. {% endhint %} You can create rules based on filters that are applied to a file (SHA256, MD5) an IP address, and a domain. If an indicator rule applies, an issue is generated in Cortex AgentiX (source is Threat Intelligence). Indicator rules are designed to leverage threat intelligence indicators like MD5 and SHA256 hashes that are present in your TIM library. These rules directly integrate with and rely on the indicators ingested and managed by TIM. Indicators must be in the TIM database before creating these rules.
Create a Detection rule After you create a detection rule, Cortex AgentiX searches for indicators in your tenant and raises an issue if a match is detected. Detection rules apply for File, Domain, and IP Address indicator types. 1. Select Threat Management → Detection Rules → Indicator Rules → **Add Rule** → **Detection Rule**. 2. From the **Create New Detection Rule** wizard, in the **General** section, add the following parameters: | Parameter | Description | | ----------- | ---------------------------------- | | Rule Name | Add a meaningful name. | | Severity | Defines the severity of the issue. | | Description | Add a meaningful description. | 3. Click Next. 4. In the Target section, use the filters and/or select the file indicators to which to apply the rule.

Note

You can't change the Detectable = True and Status = Active filters, which comply with the requirements of the supported indicator type for detection.

| Filter | Description | | ---------------------- | ---------------------------------------------------------------------------------- | | Value | The hash value of the field (SHA256 or MD5), IP address, or domain. | | Verdict | The reputation of the indicator: Malicious, Suspicious, Benign, Unknown | | Has Created Issues | Whether the indicator has an issue that has been created. | | Campaign | Whether the indicator is part of an existing campaign. | | Mitre ID | Mitre ID associated with the related issues. | | Mitre Tactic | Mitre Tactic associated with the related issues. | | Tags | The tags applied to indicators. | | Confidence | The level of confidence. | | Aggregated Reliability | The reliability score, such as A - Completely reliable. | | Feed | The source (script, manual, etc.) that last set the indicator's expiration status. | | Type | The indicator type (Domain, File, IP) | 5. Click Next and then save the rule. 6. If the indicator rule has generated issues, right-click the rule and select **View related issues**. Example - Create a detection rule from feeds In this example, create a detection rule from many feeds, such as Unit 42, AzureRiskyUsers, and Mail-Sender, that returns a malicious verdict. 1. In the **General** section, add the following parameters. | Field | Value | | ----------- | ---------------------------------------------------------------------------------- | | Rule Name | JC-IR-Prevent-01 | | Severity | Medium | | Description | To raise detection on all indicators uploaded from feeds with a malicious verdict. | 2. In the **Target** Section, select **Feed** (**Select All**) and **Verdict = Malicious**. ![](/files/IjYkzv3faYAPYcoLIYhK) When a malicious verdict is found from the feed, an issue is generated. The Issue Source is **Threat Intelligence**, severity is **medium** and the Action is **Detected**. ![](/files/St719DOU8Wwcfaozwla7) {% hint style="info" %} ### Note The Issue source is Threat Intelligence. {% endhint %}
Manage Indicator Rules The **Indicator Rules** page displays the following fields for each rule: | Field | Description | | --------------------- | ----------------------------------------------------------------- | | **Rule ID** | A unique identifier for the rule. | | **Creation Date** | Timestamp of when the rule was created. | | **Modification Date** | Timestamp when the rule was edited. | | **Name** | Name of the rule. | | **Type** | Whether the rule is a **Prevention** or **Detection** type rule. | | **Target** | Hash, IP address, File, or domain value associated with the rule. | | **Severity** | Level of severity associated with the rule. | | **# of issues** | Number of issues generated by the rule. | | **Created by** | The email address of the user who created the rule. | | **Description** | An optional description associated with the rule. | | **Status** | Whether the rule is **Enabled** or **Disabled**. | {% hint style="info" %} ### Note If an indicator matches multiple indicator rules, the highest severity rule is used. If all have the same severity, the rules are used by the first created. {% endhint %} In the **Indicator Rules** table, right-click a rule to perform actions, including the following: | Action | Description | | ----------------------- | -------------------------------------------------------------------- | | **View related issues** | View issues generated by the rule. | | **Disable/Enable** | Depending on the current status, **Disable** or **Enable** the rule. | | **Edit Rule** | Modify the rule. | | **Save as new** | Create a new rule using the current rule configurations. | | **Delete** | Delete the rule. |
--- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-agentix/detect-investigate-and-respond-to-threats/threat-intel-management/indicator-configuration/generate-issues-from-indicator-rules.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.