# Jira ITSM

## About

The **Keeper Security ITSM Integration** is a Forge-based application that automatically converts security alerts from Keeper Security into actionable Jira tickets. The integration enables security teams, IT administrators, and compliance officers to respond to security incidents immediately without manual ticket creation, ensuring no alert goes unnoticed and maintaining complete audit trails for compliance requirements.

<figure><img src="/files/08C6Bhu7arNg43IwB3lB" alt=""><figcaption></figcaption></figure>

## Features

* **Automated Ticket Creation:** Receive security alerts from Keeper via webhooks and automatically create Jira issues with complete alert details including raw JSON payloads for full audit trails.
* **Flexible Field Mapping:** Map Keeper alert fields (`alert_name`, `description`, `audit_event`, `username`, `remote_address`, `timestamp`, etc.) to any Jira field including standard fields and custom fields.
* **Priority Mapping:** Automatically assign Jira priorities based on Keeper event categories (e.g., data breaches → Highest, routine audits → Low).
* **Issue Type Mapping:** Route different Keeper alert types to specific Jira issue types (e.g., breach alerts → Incidents, policy violations → Tasks).
* **Cross-Project Support:** Works with both Team-Managed and Company-Managed Jira projects for maximum flexibility.
* **Development Tools:** Built-in test functionality to verify webhook configuration and ticket creation before going live.

## Setup and Configuration

Full Setup and Configuration is documented below:

[Jira ITSM](/en/keeperpam/secrets-manager/integrations/jira-itsm.md)


---

# Agent Instructions: 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:

```
GET https://docs.keeper.io/en/enterprise-guide/event-reporting/jira-itsm.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.