Skip to content

Issue Tracker Integration

SentriKat can automatically create issues in your project management tools when new vulnerabilities are detected, streamlining your remediation workflow.

New in v1.0.2

Issue tracker integrations were added in SentriKat v1.0.2.

PRO Feature

Issue tracker integration requires a PRO license.

Supported Platforms

Platform Issue Creation Status Sync Labels/Tags
Jira
GitHub Issues
GitLab Issues
YouTrack

Configuration

Jira

  1. Go to Integrations > Issue Trackers > Jira
  2. Configure:
  3. Server URL: Your Jira instance URL (e.g., https://company.atlassian.net)
  4. Email: Your Jira account email
  5. API Token: Generate at id.atlassian.com/manage-profile/security/api-tokens
  6. Project Key: The Jira project to create issues in (e.g., SEC)
  7. Issue Type: Task, Bug, or Story (default: Task)
  8. Click Test Connection
  9. Save

GitHub Issues

  1. Go to Integrations > Issue Trackers > GitHub
  2. Configure:
  3. Repository: Owner/repo format (e.g., company/security-tracking)
  4. Personal Access Token: Generate at github.com/settings/tokens with repo scope
  5. Click Test Connection
  6. Save

GitLab Issues

  1. Go to Integrations > Issue Trackers > GitLab
  2. Configure:
  3. GitLab URL: Your GitLab instance (e.g., https://gitlab.com or self-hosted)
  4. Project ID: Numeric project ID from Settings > General
  5. Personal Access Token: Generate in User Settings > Access Tokens with api scope
  6. Click Test Connection
  7. Save

YouTrack

  1. Go to Integrations > Issue Trackers > YouTrack
  2. Configure:
  3. Server URL: Your YouTrack instance URL
  4. Project ID: The YouTrack project short name
  5. Permanent Token: Generate in Profile > Account Security > Tokens
  6. Click Test Connection
  7. Save

Automatic Issue Creation

Configure rules for when issues are created automatically:

  1. Go to Integrations > Issue Trackers > Rules
  2. Create a rule:
  3. Trigger: New vulnerability match, status change, or due date approaching
  4. Severity Filter: Minimum severity to create issues (e.g., High and above)
  5. Platform: Which issue tracker to use
  6. Assignee: Auto-assign to a team member (optional)
  7. Labels: Tags to apply (e.g., security, kev, critical)

Example Rules

Rule Trigger Severity Platform
Critical and exploited New match Critical Jira
Everything exploited New match All GitHub Issues
Overdue items Due date passed High+ GitLab

Issue Format

Created issues include:

  • Title: [KEV] CVE-2024-3400, Palo Alto PAN-OS (Critical)
  • Description:
    • CVE details and CVSS score
    • Affected products in your inventory
    • remediation due date
    • Ransomware indicator
    • exploit probability
    • Remediation guidance
    • Link back to SentriKat vulnerability detail

Status Sync

When you acknowledge or resolve a vulnerability in SentriKat, the linked issue is automatically updated:

SentriKat Status Issue Action
AFFECTED Issue created (Open)
LIKELY RESOLVED Comment added
RESOLVED Issue closed with comment
Acknowledged Comment added with acknowledgment note

Manual Issue Creation

You can also create issues manually from any vulnerability:

  1. On the dashboard, open a vulnerability
  2. Click Create issue
  3. Select the target platform
  4. Review and confirm

Troubleshooting

Issues Not Being Created

  1. Verify the integration is configured in Integrations > Issue Trackers
  2. Check the API token has the required permissions
  3. Verify the project/repository exists and is accessible
  4. Review logs: docker compose logs sentrikat | grep issue_tracker

Authentication Errors

  • Jira: Ensure you're using an API token, not your password
  • GitHub: Token needs repo scope for private repositories
  • GitLab: Token needs api scope
  • YouTrack: Use a permanent token, not a session token

Next Steps