Skip to main content
Automatically creating Linear issues
Language

Linear

Automatically create Linear issues from cside security alerts, with control over the target team, the labels applied, and the details in each issue.

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 Linear issues

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

Prerequisites

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

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

Adding a Linear 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 Linear
  4. In the Configuration panel:
    • Team: select the Linear team where issues should be created
    • Labels (optional): add labels from your existing Linear labels or create new ones
  5. Click Save or Save & Test
Digest triggers

Linear 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.

What does a Linear issue look like?

Each Linear issue created by cside includes:

  • Title: 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 (in markdown): 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

Testing

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

Removing a Linear destination

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

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

Was this page helpful?