How to scan Jira issues and comments for secrets
By Jake Marsh · Updated
To scan Jira for secrets, add Spillproof to Jira on a site where it's installed in Confluence, open Jira settings > Apps > Spillproof, and click Scan Jira on the Scans tab. It checks the summary, description, environment, text custom fields and all comments of every issue for API keys, tokens, private keys and passwords. New and edited issues and new comments are checked as they're saved, and you can find every affected issue with the JQL sensitiveData > 0.
Why Jira is a common place for leaks
Bug reports and support requests carry whatever the reporter pasted: a stack trace with a bearer token, a .env file, a curl command with an API key in the header. Comments pile up the same way while people debug. Jira's own search can't tell a real AWS key from the word "key", and the History tab keeps every old description value.
Steps
- Install Spillproof in Confluence from the Atlassian Marketplace, then add it to Jira on the same site (Apps, Manage apps). One subscription covers both, and Confluence is required.
- Open Jira settings > Apps > Spillproof. Only Jira admins see this page. It's the same page and the same findings as in Confluence settings.
- On the Scans tab, click Scan Jira. Type project keys such as
SUP, OPSin Space or project keys to scan (leave empty for all) to start with a few projects. - Open the Findings tab and set the product filter to Jira. Each row shows the issue key and summary, the field or comment the value is in, and the masked value.
- Turn on the Jira options under Notifications and access, then click Save settings:
- Make issues searchable with JQL: sensitiveData > 0 (stores only the count)
- Label issues with open findings, with a label such as
sensitive-data - Email the person who wrote it (reporter or comment author), sent through Jira's own notifications with the value masked
- Clean up each finding. Redact replaces the value in the current field or comment, as you, so you need permission to edit it. For keys and passwords, rotate them and click Rotated.
Finding affected issues with JQL
With the JQL option on, Spillproof writes the number of open findings onto each issue. Anyone can then search with it, and the search shows only the count, never the values.
| You want | JQL |
|---|---|
| Every issue with an open finding | sensitiveData > 0 |
| Open findings in one project | project = SUP AND sensitiveData > 0 |
| Recent ones | sensitiveData > 0 AND updated >= -7d |
Use the same query for a Jira filter or a dashboard gadget so the team sees the list shrink. If you set a label instead, it's added while an issue has open findings and removed after.
Edited comments
Jira doesn't send apps an event when a comment is edited. Spillproof's daily catch-up re-checks everything that changed in the last day, so a key added to an existing comment shows up within a day. New comments are checked within seconds.
Jira Service Management requests
Requests in a service project are Jira issues, so the same scan covers them, including comments agents and customers add. Customers who paste card numbers are covered by the financial detectors; see how to find card numbers and Social Security numbers.
What it costs
Spillproof is $5 a month for up to 10 users or $50 a year, and $1.75 per user a month from 11 users, with lower rates on larger sites. Atlassian bills it, with a 30-day free trial, and the one subscription covers both Jira and Confluence. Details and the install link are on the Spillproof page.
Spillproof: PII and Secret Scanner for Confluence and Jira
Find passwords, API keys, card numbers and ID numbers in Confluence and Jira. Checksum-verified, masked, nothing leaves Atlassian. From $5 a month for up to 10 users.
Questions
Can I install Spillproof in Jira only?
No. Confluence is required. Add it to Jira on the same site and both are scanned under one subscription.
Does it scan Jira attachments or the History tab?
No. It reads the current summary, description, environment, text custom fields and comments. Jira keeps old values in the History tab, which can't be edited, so rotate any key that was posted.
Can I keep a test project out of the scan?
Yes. On the Scope tab, add its key under Jira project keys to skip and click Save settings. Its open findings close.
Who sees the findings in Jira?
Jira admins and the reviewers an admin adds under Notifications and access. On a single issue, anyone who can see it can open Spillproof data check from the issue's "..." menu to see its masked findings and click Scan now.
More Spillproof guides
- How to find credit card numbers and Social Security numbers in Confluence and Jira
- How to find passwords and API keys in Confluence
- How to remove a leaked password from a Confluence page and its history
More Confluence guides
- How to export Jira issues to a Confluence page as a static table (Stillframe)
- How to set a reminder on a Jira issue (Remindwell)
- How to baseline requirements in Jira (Tracestitch)
- How to find duplicate issues in Jira (Mergewell)