1. Keeper generates an alert
A security event occurs, such as a BreachWatch detection or policy violation. Keeper detects the event and triggers an alert through the Advanced Reporting & Alerts Module (ARAM).
How the Jira ITSM integration works
2. Webhook sends data to Jira
The alert is sent via webhook to the Keeper Security Jira ITSM app, which validates the payload and applies your configured mappings for fields, priorities and issue types.
3. A Jira issue is created
The app creates a new Jira issue in the designated project, pre-populated with alert details and full context. Teams are notified automatically and can respond immediately.
![Keeper ITSM Jira alert ticket for “bw_record_high_risk,” showing user [jsmith@acme.com] and an alert timestamp.](/assets/images/pages/features/jira-itsm/fr_FR/jira-ticket-desktop@2x.webp)
Automate ticket creation from every alert
When a security event is triggered in Keeper, a Jira issue is created instantly. Each ticket includes full context, such as event type, user, timestamp and raw JSON, for complete visibility and audit readiness.
Built to streamline incident management
Map alert fields to your Jira environment
Define how Keeper fields, such as alert_name, username and timestamp, map to Jira fields. Support both standard and custom fields to fit your team's workflows and reporting needs.
Assign ticket priorities automatically
Automatically prioritize incidents based on alert type. Critical events like breach detections can be flagged as "Highest," while low-risk activity is set accordingly, with no manual sorting required.
Route events to the right issue types
Send each alert to the right place. Map alert categories to Jira issue types such as Incidents, Tasks or Sub-tasks to keep queues organized and teams focused.
Operate across projects with ease
Support both company-managed and team-managed projects without extra configuration. The integration adapts to your Jira setup and scales with your teams.
