> 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/application-security/application-security-posture-management-aspm/unified-application-security-policies/reference-d-trigger-and-actions-mapping.md).

# Reference D: Trigger and actions mapping

Triggers define when the policy evaluates findings. Actions define what the policy does when a finding matches

**Triggers and actions**

**Code Scanners configuration rules**

* Select at least **one trigger** and at least **one action per trigger**
* If no code-related finding types are selected in the conditions, code-related triggers are disabled
* If no image-related finding types are selected in the conditions, image-related triggers are disabled
* When only third-party scanner finding types are selected in the conditions, **only the Periodic Scan trigger** is available. PR Scan and CI Scan triggers are disabled for third-party scanner findings

**Code scanners triggers**

| Trigger           | Available actions                                        | Default behavior                                               |
| ----------------- | -------------------------------------------------------- | -------------------------------------------------------------- |
| **PR scan**       | Block PR, PR Comment, Create Issue (+ Override Severity) | PR Comment is enabled by default when the trigger is activated |
| **CI scan**       | Block CI, CLI Report, Create Issue (+ Override Severity) | CLI Report is enabled by default when the trigger is activated |
| **Periodic scan** | Create Issue (+ Override Severity)                       | —                                                              |

**Image-category triggers (available when image-related finding types are selected)**

| Trigger                 | SDLC stage             | Shift-left value                                                                                | Available actions                                        | Use when                                                                                                                               |
| ----------------------- | ---------------------- | ----------------------------------------------------------------------------------------------- | -------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| **CI Image scan**       | Build pipeline (image) | High: Scans container images built during CI before they are pushed to a registry or deployed   | Block CI, CLI Report, Create Issue (+ Override Severity) | Enable when CI/CD pipelines build container images CI Image Scan detects vulnerabilities, secrets, and malware in images at build time |
| **Image Registry scan** | Image registry         | Baseline: Scans container images stored in registries for vulnerabilities, secrets, and malware | Create Issue (+ Override Severity)                       | Enable when monitoring container image registries for newly disclosed vulnerabilities in existing images                               |

**CI/CD Configuration Scanners triggers**

* The Periodic Scan trigger is the only available trigger. PR Scan and CI Scan triggers are not available
* **Important**: CI/CD Configuration Scanners policies cannot include non-CI/CD finding types (such as Secrets, Vulnerabilities, or IaC Misconfigurations). The CI/CD Risks finding type is exclusive to the CI/CD Configuration Scanners policy type. To create policies for non-CI/CD finding types, select the Code Scanners policy type

| Trigger           | Available actions                  | Default behavior                                                             |
| ----------------- | ---------------------------------- | ---------------------------------------------------------------------------- |
| **Periodic scan** | Create Issue (+ Override Severity) | The Periodic Scan trigger and the Create Issue action are enabled by default |

**Drift Detection Scanner triggers**

* The Periodic Scan trigger is the only available trigger. PR Scan and CI Scan triggers are not available
* **Important**: Drift Detection Scanner policies cannot include non-drift finding types (such as Secrets, Vulnerabilities, or CI/CD Risks). The IaC Drift finding type is exclusive to the Drift Detection Scanner policy type. To create policies for non-drift finding types, select the Code Scanners or CI/CD Configuration Scanners policy type

| Trigger           | Available actions                  | Default behavior                                                             |
| ----------------- | ---------------------------------- | ---------------------------------------------------------------------------- |
| **Periodic scan** | Create Issue (+ Override Severity) | The Periodic Scan trigger and the Create Issue action are enabled by default |


---

# 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/application-security/application-security-posture-management-aspm/unified-application-security-policies/reference-d-trigger-and-actions-mapping.md?ask=<question>&goal=<endgoal>
```

`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.
