> 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-xsiam/cloud-security/cortex-cloud-saas-security/create-and-monitor-tickets.md).

# Create and monitor tickets

Integrate SaaS Security with Jira or ServiceNow to streamline misconfiguration remediation. This integration allows security teams to delegate manual remediation tasks directly to SaaS application administrators using your organization's existing issue tracking system.

***

### Prerequisites

Before managing tickets from the SSPM console, ensure:

* An active Jira or ServiceNow instance is connected and authenticated within your tenant settings. Follow these steps to activate [Issue Syncing](/cortex-xsiam/detect-investigate-and-respond-to-threats/investigation-and-response/investigate-issues/issue-syncing.md).

***

### Ticket Management Workflows

#### 1. Create a Ticket

When a SaaS Security issue requires manual intervention within a target SaaS application:

1. Open the target Issue in the Cortex console.
2. On the **Overview** page, select Jira under the issue properties. This takes you to the ticket’s sync settings.
3. Under **Sync Configuration**, select Bi-directional.
4. Assign the ticket to the appropriate team member or administrator for investigation and resolution.

Once created, SaaS Security automatically establishes a bi-directional reference linking the specific issue to the new ticket ID.

#### 2. View Linked Tickets

You can track remediation progress directly from the SaaS interface:

* Select the highlighted ticket reference within any issue view to open the issue directly in Jira or ServiceNow.


---

# 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-xsiam/cloud-security/cortex-cloud-saas-security/create-and-monitor-tickets.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.