Skip to content
Notifications
Clear all

TIL: You can automate Checkmarx findings directly into Jira Service Desk

4 Posts
4 Users
0 Reactions
58 Views
(@devops_rookie_2025)
Prominent Member
Joined: 6 months ago
Posts: 467
Topic starter   [#27483]

Hey everyone! Just learned something cool today and wanted to share. I was exploring the Checkmarx API docs and found out you can automatically push new findings as tickets into Jira Service Desk. This seems perfect for making sure vulnerabilities don't get lost in the dashboard.

Could someone walk me through a basic setup? I'm still new to APIs and webhooks. Maybe a simple example of the API call or a config snippet? I'm curious about what data gets sent over and if you can customize the ticket fields. Thanks so much for any guidance! 😊



   
Quote
(@bent36)
Estimable Member
Joined: 4 months ago
Posts: 114
 

That's a useful feature. I set up something similar last month. The Checkmarx webhook sends a JSON payload with the finding details like severity, file path, and CWE. You can map those fields to Jira ticket fields in the webhook configuration.

One thing I noticed - you'll need to handle authentication for both systems in your webhook script. The Jira Service Desk API requires a token, and Checkmarx needs its own API key.

Can the webhook filter findings by severity before creating tickets? I'd rather not have low-severity issues cluttering the queue.



   
ReplyQuote
(@bookworm42)
Reputable Member
Joined: 4 months ago
Posts: 378
 

Good find. That integration saves a ton of manual triage time.

For a basic setup, you'll create a webhook in Checkmarx pointing to your Jira Service Desk API endpoint. The payload is JSON and includes the project name, finding ID, severity, and CWE. You absolutely can customize the ticket fields - the webhook config lets you map those JSON values to specific Jira fields like summary, description, and priority.

Since you're new to APIs, start by testing the Checkmarx webhook with a tool like Postman to see the exact payload structure first. Then build your Jira integration.



   
ReplyQuote
(@devops_not_grunt)
Honorable Member
Joined: 8 months ago
Posts: 506
 

Cool until your service desk queue becomes a dumpster fire of automated noise. That dashboard isn't just a pretty chart, it's a prioritization tool. When everything is a ticket, nothing is.

You'll get a dozen "Medium" severity tickets for libraries that have no actual exploit path in your code, and your devs will just start auto-closing them. Then a real one slips through.

Test it with a filter that only creates tickets for "Critical" findings that are actually reachable in the runtime. Otherwise you're just building a ticket factory, not a security process.



   
ReplyQuote