> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/admin-guide/32/alerts/jira.md).
# JIRA
Prisma Cloud continually scans your environment for vulnerabilities using the threat data in the Intelligence Stream. Prisma Cloud can open JIRA issues when new vulnerabilities are detected in your environment. This mechanism lets you implement continuous vulnerability assessment and remediation by hooking directly into the developer’s workflow.
New JIRA issues are opened when new vulnerabilities are found. A new issue is created for each discovery. Each JIRA issue lists the new vulnerabilities discovered, and a list of vulnerabilities that have already been reported but were still detected.
JIRA issues are opened based on policy. For example, an issue would be created when all of the following conditions are met:
* You have a rule that alerts on critical vulnerabilities,
* The rule is associated with your JIRA alert profile,
* The Prisma Cloud scanner finds a critical vulnerability in an image in your environment.
The following screenshot shows an example JIRA issue opened by Prisma Cloud.
## Intelligent issue routing
You can leverage image labels to intelligently route alerts to the right team, and eliminate manual ticket triage. For example, if team-a is responsible for image-a, and a vulnerability is found in image-a, you could set up the alert to flow directly to team-a’s JIRA queue.
Intelligent routing depends on a Prisma Cloud feature called [alert labels](/admin-guide/32/audit/annotate-audits.md), where you define labels that Prisma Cloud should watch. When rules trigger, Prisma Cloud extracts the value of the label from the resource, and applies it to the next phase of alert processing. For JIRA alerts, you can use labels to specify the JIRA project key, JIRA labels, and JIRA issue assignee.
For example, if you have an image with the following labels:
```
group=front-end-group
team=client-team
business-app=my-business-app
```
You could configure Prisma Cloud to open issues about this specific image in the JIRA project defined by the *group* label.
## Configuring alert frequency
You can configure the rate at which alerts are emitted. This is a global setting that controls the spamminess of the alert service. Alerts received during the specified period are aggregated into a single alert. For each alert profile, an alert is sent as soon as the first matching event is received. All subsequent alerts are sent once per period.
1. Open Console, and go to **Manage > Alerts**.
2. In **General settings**, select the default frequency for all alerts.
You can specify the following frequencies.
* **10 Minutes**
* **1 Hour**
* **1 Day**.
## Integrating Prisma Cloud with JIRA
Alert profiles specify which events should trigger the alert machinery, and to which channel alerts are sent. You can send alerts to any combination of channels by creating multiple alert profiles.
Alert profiles consist of two parts:
**(1) Alert settings — Who should get the alerts, and on what channel?** Configure Prisma Cloud to integrate with your messaging service and specify the people or places where alerts should be sent. For example, configure the email channel and specify a list of all the email addresses where alerts should be sent. Or for JIRA, configure the project where the issue should be created, along with the type of issue, priority, assignee, and so on.
**(2) Alert triggers — Which events should trigger an alert to be sent?** Specify which of the rules that make up your overall policy should trigger alerts.
If you use multi-factor authentication, you must create an exception or app-specific password to allow Console to authenticate to the service.
## Create new alert profile
Create a new alert profile.
1. In **Manage > Alerts**, click **Add profile**.
2. Enter a name for your alert profile.
3. In **Provider**, select **JIRA**.
## Configure the channel
Configure the channel.
1. In **Base URL**, specify the location of your JIRA service.
2. In **Credential**, create the credentials required to access the account.
1. Click **Add new**.
2. Select **Basic authentication**.
3. Enter a username and password.
If you are using Jira Cloud, this will be an email address and API token respectively. You can generate your API token [here](https://id.atlassian.com/manage-profile/security/api-tokens).
4. Click **Save**.
3. In **CA certificate**, enter a copy of the CA certificate in PEM format.
4. In **Project key**, enter a project key.
Alternatively, you can dynamically specify the project key based on a label. When an alert fires, the project key is taken from the label of the resource that triggered the action. To do so, click **Select labels…**, and choose a label that you know will contain the project key. If there are no labels in the drop-down list, go to **Manage > Alerts > Alert Labels**, and define them.
5. Enter an issue type.
6. Enter a priority.
7. Enter a comma delimited list of JIRA labels to apply to the issue.
You can dynamically define the list from a label. Click **Select labels…**, and select one or more labels.
8. Enter an assignee for the new issue.
You can dynamically define the assignee from a label. Click **Select labels…**, and select one or more labels.
9. Click **Send Test Alert** to test the connection.
## Configure the triggers
1. In **Select triggers**, select the events that should trigger an alert to be sent.
2. To specify specific rules that should trigger an alert, deselect **All rules**, and then select any individual rules.
3. Click **Next**.
---
# 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://docs.prismacloud.io/admin-guide/32/alerts/jira.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.