Push DAST findings to your ticketing system!

Push DAST findings to your ticketing system!

## Overview

The DAST ticketing integration allows you to push your DAST findings to your ticketing system as soon as vulnerabilities are detected. This integration supports several ticketing systems, including but not limited to:

* Jira Cloud
* GitHub Issues
* Azure DevOps Boards

For a complete list of supported applications, please refer to the [available connectors](https://docs.cobalt.io/en-us/articles/connect-your-applications-OF9fGhmhcx) section.

## How it Works

The DAST ticketing integration uses Cobalt’s [Integration Builder](https://docs.cobalt.io/en-us/articles/integration-builder-Aelp0wU7EI) to push DAST findings to your ticketing system. The integration builder is a no-code workflow builder that enables you to create highly customizable integrations. We provide integration quickstart templates for the above-mentioned ticketing systems that allow you to get your DAST integration up and running quickly!

## Steps to Integrate with Ticketing Systems

[https://www.loom.com/share/7d61c971c7cc47daa750bf41ff247831](https://www.loom.com/share/7d61c971c7cc47daa750bf41ff247831)

## Frequently Asked Questions

Click to view answers.

### Does it create duplicate tickets?

\-The DAST ticketing integration will not create duplicate tickets as long as you follow our guidance regarding [external ticket references](https://docs.cobalt.io/en-us/articles/how-to-guides-I5guQ2qNXS#h-external-ticket-references).

### Can I route tickets from different targets to different tools or projects?

\-Yes. You can create one ticket-push recipe per DAST target and configure the recipes differently. You should use [trigger filters](https://docs.cobalt.io/en-us/articles/how-to-guides-I5guQ2qNXS#h-trigger-filters) to ensure that each recipe is triggered only by findings that are associated to the correct target. Checkout the video above for a walkthrough of this process.

### Can I update a DAST finding from my ticketing tool?

\-No. Our public API does not currently have functionality that can be used to update a DAST finding. The Integration Builder uses our public API, so it doesn’t support updating DAST findings either. This functionality is on our roadmap.

### How do I know if a ticket has been created for a finding?

\-When everything is working correctly, you can see tickets associated to your DAST findings directly within the DAST user interface. It is possible in failure scenarios that the integration could correctly create a ticket but fail to record an [external ticket references](https://docs.cobalt.io/en-us/articles/how-to-guides-I5guQ2qNXS#h-external-ticket-references). If this situation occurs, a ticket would exist, but it would not show up in the DAST user interface. You can investigate failures using our [troubleshooting steps](https://docs.cobalt.io/en-us/articles/troubleshooting-yCJ7jSNWIa).

## Troubleshooting

Checkout our general Integration Builder troubleshooting documentation [here](https://docs.cobalt.io/en-us/articles/troubleshooting-yCJ7jSNWIa).

Integrations

DAST Scanner Overview

Best Practices

Partial Scans: Reduced Scope

Scans

Sequence recorder

Targets

Target Authentication

Extra Hosts

Blackout Period

DAST Scanner

How to get started with Cobalt

Getting Started

Risk Advisories

Assets are what we pentest

Asset Types

Create an Asset

Assets

Pentests

Overview

Asset Details

Pentest Details

Scope & Test Period

Preparation

Create a Pentest

Pentest Process

Pentest States

Coverage Checklist

Pentest Expectations

Set Up an In-House Pentest

Complete an In-House Pentest (For Pentesters)

In House Pentests

Severity Levels

Finding States

Remediate Findings

Findings

Customize Your Report

Co-branded Reports

Contents of a Pentest Report

Reports

Engagements Overview

Digital Risk Assessment

Secure Code Review

Engagements

Insights

Planning

Cobalt Methodologies Overview

Web Methodologies

API Methodologies

External Network Methodologies

Internal Network Methodologies

Mobile Methodologies

Cloud Configuration Review Methodologies

Cloud Pentest Methodology

Desktop Methodologies

AI/LLM Methodologies

Digital Risk Assessment Methodology

Secure Code Review Methodologies

Methodologies

Attack Surface Monitoring (ASM)

Attack Surface

Account Overview

Account Settings

Password Best Practices

Sign In to Cobalt

Troubleshoot Sign-in Issues

User Account

Collaboration Overview

Collaborate on Pentests

Groups

Manage Pentest Collaborators

Manage Notifications

User Roles and Permissions

Collaboration

Organization Overview

Manage Users

Your Cobalt Contract

How to Configure SAML 2.0 for Cobalt 

SAML Migration: Update Your Configuration

Configure SAML SSO

SCIM Provisioning Setup Guide

Configure Organization Settings

Organization

Cobalt Credits

Track Your Credits

Cobalt PtaaS Tiers

Credits

Cobalt Integrations Overview

Connect your applications

Create GitHub tickets for Findings

Send MS Teams notifications for Findings

Create Azure DevOps Work Item for Findings

Create Jira tickets for Findings

Send email notifications for Findings from Outlook

Create GitLab tickets for Findings

HTTP Connector

Import Assets from Google Sheets

Map Cobalt Pentest Finding Severity to Jira Issue Priority

Modify Jira Issue Summary to contain Pentest Title

How to Guides

Troubleshooting

Integration Builder

Jira Data Center Integration

Push Cobalt Findings to Jira

Switching to a New Jira Instance

Jira Cloud Integration

Troubleshoot Your Jira Integration

Synchronize Cobalt Severity Levels with Jira

Integrate Jira with Cobalt

Slack

Microsoft Teams

Webhooks

DefectDojo

Kenna Security

Vanta

Carried Over Findings

Create Test Finding

Cobalt API Overview

Partner Integrations

API Versions

Events

Errors

Subscription

Introduction

Authentication

EU Data Center

Organizations

Engagement Findings

DAST Targets

DAST Scans

DAST Scheduled Scans

DAST Findings

External Ticket References

Tokens

Pagination

Idempotency

Rate Limits

Create a Personal Cobalt API Token

Changelog

Get an Organization Token

Revoke Your Personal Cobalt API Tokens

Create or Modify an Asset

Import Findings to Google Sheets

Cobalt API

Glossary

March 2026

February 2026

January 2026

November 2025 

August 2025

July 2025

June 2025

May 2025

April 2025

March 2025

January 2025

December 2024

November 2024

October 2024

September 2024

August 2024

July 2024

June 2024

May 2024

April 2024

March 2024

January 2024

What's New

Guide

Cobalt Product Documentation

Integrations

Share

Share

Integrations

Share

Share