Skip to main content
Automatically creating Jira issues
Language

Jira

Automatically create Jira issues from cside security alerts. Configure the project, issue type, and labels, and see what each issue contains.

Available on Enterprise and for teams whose feature access includes this capability. If the option is unavailable, contact cside to confirm your team’s access.

Automatically creating Jira issues

Connect cside to your Jira instance to automatically create issues when notification triggers fire. Each alert creates a Jira issue in the project and issue type you configure, keeping your team’s existing workflow intact.

Prerequisites

Before adding Jira as a destination, connect your Jira account as a team integration:

  1. Open the dashboard and navigate to Team Settings
  2. Select the Integrations tab
  3. Click Connect Jira and follow the OAuth authorization flow
  4. Once authorized, Jira becomes available as a destination in your notification configs

Adding a Jira destination

  1. Open the dashboard and navigate to Team Settings > Notifications
  2. Create a new notification config or edit an existing one
  3. Under Send To, click Add destination and select Jira
  4. In the Configuration panel:
    • Project: select the Jira project where issues should be created
    • Issue Type: select the issue type (e.g., Bug, Task, Epic)
    • Labels (optional): add labels to categorize issues
  5. Click Save or Save & Test
Digest triggers

Jira is not available for the triggers that are delivered by scheduled jobs: PCI Report Available, Script Blocked by CSP, Vulnerable Script Detected on a daily or weekly schedule, Outbound Connections Pending Review, and CSP Policy Digest. Those accept email and webhook destinations, and PCI Report Available also accepts S3. To get them into Jira, send them to a webhook and create the work items with Jira Automation.

What does a Jira issue look like?

Each Jira issue created by cside includes:

  • Summary: a title that depends on the trigger, for example:
    • [cside] Malicious Script: {ruleset} on {domain} for Script Threat Detected
    • [cside] Vulnerable Script: {CVE} on {domain} and [cside] High-risk Vulnerability: {CVE} on {domain} for vulnerability triggers
    • [cside / Flagged]: Known Threat Detected on {domain} for Managed List: Flagged
    • [cside / Flagged]: Malicious Outbound Connection on {domain} for Malicious Outbound Connection
    • [cside / Flagged]: Suspicious Tag Manager Container on {domain} for Malicious Tag Manager
  • Description: a table with the details of the alert:
    • Domain: the affected domain
    • Threat and Why: the ruleset that matched and its description (for threat alerts), or Vulnerability, Severity, and Package for vulnerability alerts. Managed list issues carry a Type or Action row with a Why explanation instead
    • Script URL 1 to Script URL 3: the scripts involved, plus a More Scripts row when there are more than three
    • Action: the action cside took, or N/A
  • A View in dashboard link that opens the alert in cside

If you configured labels when setting up the destination, they are applied to every issue created by this config.

Testing

Click Save & Test when creating or editing a notification config to send a test notification to Jira. This creates a test issue in your project so you can verify the integration is working.

Removing a Jira destination

To remove Jira from a notification config, edit the config under Team Settings > Notifications and remove the Jira destination from the Send To list.

To disconnect the Jira integration entirely, go to Team Settings > Integrations and click Disconnect Jira.

Was this page helpful?