How to find credit card numbers and Social Security numbers in Confluence and Jira
By Jake Marsh · Updated
To find card numbers and Social Security numbers in Confluence and Jira, install Spillproof, run Scan Confluence and Scan Jira from the Scans tab in its settings, then filter the Findings tab by Financial (cards, bank accounts) or Identity (SSN, NI, SIN, passport). A card number is only reported if it passes the Luhn check and fits a real issuer's range and length, and an SSN only if it follows the Social Security Administration's numbering rules, so order numbers, phone numbers and invoice IDs stay off the list.
Steps
- Install Spillproof in Confluence from the Atlassian Marketplace, and add it to Jira on the same site if your tickets need checking too.
- Open Confluence settings > Spillproof (or Jira settings > Apps > Spillproof).
- On the Detectors tab, check that the financial and identity detectors you care about are on. They all are by default. Click Save settings if you change anything.
- On the Scans tab, click Scan Confluence and Scan Jira.
- On the Findings tab, set the type filter to Financial (cards, bank accounts) or Identity (SSN, NI, SIN, passport). Each row shows a masked value such as "Visa ending 4242" and where it sits.
- Click Export CSV to get the filtered list with masked values only, for an audit file or a spreadsheet.
- Clean up: Redact replaces the number with
[redacted <type>]in the current text; Restrict page limits a Confluence page to you and its author; Fixed closes the finding.
How each number is checked
| Detector | Reported when |
|---|---|
| Payment card number | It passes Luhn and matches a Visa, Mastercard, Amex, Discover, JCB, Diners, UnionPay or Maestro range and length. Published test cards and evenly repeated digits are skipped. |
| Bank account (IBAN) | It passes the ISO 7064 mod 97 check and has the right length for its country. Documentation examples are skipped. |
| US bank account with routing number | A routing number that passes its checksum, labelled as routing or ABA, sits next to a labelled account number. |
| US Social Security number | It's written as 123-45-6789 and follows SSA numbering rules, or it's 9 digits right after "SSN" or "social security". |
| UK National Insurance number | It follows HMRC's prefix rules, written like AB 12 34 56 C. |
| Canadian Social Insurance number | It passes Luhn and is labelled "SIN" or "social insurance". |
| Passport number | It's labelled "passport no." or "passport number", or it's a machine-readable passport line with valid check digits. |
Need an ID format that isn't listed, like your own employee or customer numbers? Add it under Custom patterns on the Detectors tab with Add a pattern.
Where this data turns up
- Service requests. A customer pastes a full card number into a Jira Service Management request about a refund, and an agent copies it into a comment.
- HR pages. An onboarding checklist in Confluence with a new hire's SSN or NI number in a table.
- Finance tickets. A vendor's IBAN and account details in an issue description, next to the invoice.
- Travel pages. Passport numbers in a conference trip planning page.
Contact details
Email addresses and phone numbers count as personal data too, but Confluence and Jira are full of colleagues' addresses, so those two detectors are off by default. Turn Email address on and it reports only addresses outside your own domains.
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, covering Confluence and Jira together. Install it from 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
Does the CSV export contain the full card numbers?
No. It holds masked values only, and Spillproof never stores the full value at all: just the masked preview and a fingerprint.
Will a 16-digit order number be flagged as a card?
Not unless it passes the Luhn check and fits a real issuer's range and length for that number of digits.
Does it find card numbers in attachments, like a scanned form?
No. Attachments aren't scanned, only the text of pages, blog posts, comments and issue fields.
Can it flag our test card numbers?
Only if you tick Also report published test card numbers, documentation IBANs and Stripe test keys on the Detectors tab. They're skipped by default.
More Spillproof guides
- How to find passwords and API keys in Confluence
- How to scan Jira issues and comments for secrets
- 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)