Overview
SecurityScorecard’s Jira integration now supports the option of creating automated Jira ticket creation at the finding level, helping teams eliminate manual work with effective triage of tickets, helping to streamline remediation workflows.
- Automatically create Jira tickets for individual findings based on rule-based logic
- Tickets include full finding-level detail, including evidence metadata
- Each ticket references its parent issue ID for context
- Setup is available directly from the Rules Engine with an improved configuration wizard
This feature is currently in Early Access. Learn how to turn it on for your organization here.
Benefits
- Save Time: Automates a repetitive and manual process
- Improve Actionability: Tickets with context that can be assigned immediately
- Faster Remediation: Recipients have less need to log into SSC to gather additional details
- Scale with Confidence: Built to support high-volume ticket creation without hitting Jira API limits
How it works
- Step 1: Navigate to Rules Engine
→ Go to Automation, then Rules Builder
→ Click Create Rule or edit an existing rule - Step 2: Define Your Trigger
→ Select By issue type or By severity trigger options - Step 3: Add Jira Action
→ Select Jira as an action
→ Fill out the project and Jira issue type - Step 4: Select How Issues Will Be Created
→ Tickets will be created per issue (Default). This will create a Jira ticket with issue details and high-level finding details. For tickets with more than 5 findings, users can access the SecurityScorecard platform for more information on the findings.
→ Tickets will be created per issue finding. This will generate a separate ticket for each issue and any subsequent findings associated with it.
Caution: For issues that generate many findings, this will result in a high volume of ticket creation in your selected Jira project. Ensure appropriate filtering
Best practices
- Use filters or conditions to avoid ticket overload
- Assign dedicated projects to auto-generated tickets to differentiate from manually created ones
- Pair with Action Plans for full remediation loops