Stepwise Secret & PII Scanner for Jira

Find the secrets and personal data hiding in your work items

A password in a description, an AWS key in a comment, a card number in a support request: everyone who can open the work item can read it. The scanner finds them in work items, comments and Jira Service Management requests, shows you where, and helps you clean up.

  • Runs entirely on Atlassian
  • Jira Service Management included
  • Never stores the value it finds

Jira makes work easy to share. Stepwise Secret & PII Scanner helps you see what should not have been shared.

Found where people paste them

Summary, description, comments, text fields and JSM requests are checked as they are created or edited.

Masked and reported

Mask a secret in a comment, email the Jira groups you choose, and keep a journal of what happened.

Your history, scanned

One run goes through every space, so what was pasted last year is found too.

What changes for your team

Six things your team gets from day one.

42 detectors for what people really paste

Built-in detectors work without AI and without any outside service: a pattern plus a check such as a checksum.

  • Cloud keys: AWS, Google Cloud, Azure
  • Tokens: GitHub, GitLab, Slack, Stripe, Atlassian, OpenAI and more
  • Private keys, JWTs, and passwords written in text, configs and links
  • Card numbers (Luhn-checked) and IBANs (checksum-checked)
  • US Social Security numbers on by default; email, phone, UK NINO and Spanish DNI when you want them

Work items, comments and JSM requests

The text people write in Jira is checked when it is created or edited, in the places it hides.

  • Summary and description
  • Comments, including JSM customer comments and internal notes
  • Single-line and multi-line text fields
  • A finding shows whether a comment was public or internal
  • Delete the comment or work item and the finding is closed

Mask it. Tell your team.

Turn masking on and a secret in a comment is replaced by a label. Alerts reach the people who can act.

  • ***REDACTED: AWS key*** replaces the value; only the current comment text is edited
  • Safety checks first: if anything else would change, the comment is left as it is
  • Email alerts to up to five Jira groups, and optionally to the author
  • Alerts say what and where, never the value
  • Descriptions are not rewritten: you are told to remove the value and rotate the key

Hold a create until the secret is gone

Add one validator to the Create transition, or any other, and the work item waits while its text holds a secret.

  • Open the workflow, select the transition, add Stepwise: no secrets in the text, publish
  • The message names the kind of secret and never shows it
  • Choose what holds a transition: secrets, secrets and financial data, everything, or nothing
  • If the scanner itself fails, the transition passes, so your work never stops because of it

Scan your history, see where it gathers

Run the one-off scan once and every space is checked, in chunks, in the background.

  • Pause, resume or stop at any time
  • Insights: findings by space, by kind and by week
  • JSM: how many are in public comments and how many in internal notes
  • Findings by space, for space admins too

Fewer false alarms

Placeholders such as <password> or ${VAR} are not findings, and well-known test data is skipped.

  • Switch each kind on or off
  • Add up to 50 values to ignore, for example example.com
  • Exclude test spaces
  • Dismiss a finding as Not sensitive, Test data or Accepted risk

Roll out in four steps

Scan, choose, alert, hold. Each step is useful on its own.

  1. Run the history scan

    From the Overview, scan every space once. Findings appear as it goes.

  2. Choose what counts

    Switch kinds on or off, skip test data, add values to ignore.

  3. Tell your team

    Pick the Jira groups that get an email. Turn masking on if you want it.

  4. Hold a create

    A workflow admin adds the validator to the Create transition.

Runs entirely on Atlassian

Findings, not values

The scanner stores where a finding is and what kind it is, and nothing about what it says. It keeps no value, no hash of a value and no text around it. It runs on Atlassian Forge and sends nothing to any other server. It uses no AI.

No value, no hash, no text around it

A hash of a short value such as a card or an SSN can be guessed, so none is kept. A finding is a place and a kind.

No external servers

No copies elsewhere, no analytics, no third parties.

Jira permissions apply

Preview reads the text as the person who clicked, so they see only what Jira lets them see.

Four permissions, each with a reason

Read and write work items, read users for the group picker, and app storage. See the docs.

Premium

For security teams that need their own patterns and evidence they can hand over.

Your own patterns

Add up to 20 patterns for internal ID formats, customer numbers or key prefixes, with a name, a category and a severity. Each is tested when you save it.

CSV export of findings

Download the findings list: state, severity, kind, space, where, line and column, and when it was first and last seen. Never the value.

CSV export of the journal

Download what was found, masked, dismissed or scanned, with time, space, kind and who did it, for a period you choose.

Questions and answers

What does Stepwise Secret & PII Scanner for Jira find?

AWS, Google Cloud and Azure keys; GitHub, GitLab, Slack, Stripe, Atlassian and OpenAI tokens; private keys; JWTs; passwords written in text and configs; credentials in links; card numbers (Luhn-checked); IBANs; and US Social Security numbers. Email addresses, phone numbers, UK NINO and Spanish DNI can be switched on. 42 built-in detectors in all.

Does it work with Jira Service Management?

Yes. Requests, customer comments and internal notes are checked, and each finding shows whether the comment was public or internal.

Can it hide a secret?

In comments, yes. Turn masking on and the app replaces the value with ***REDACTED: AWS key*** and edits only that comment text. Summaries and descriptions are not rewritten: the finding tells you where the value is, and you remove it and rotate the key.

How quickly does it check?

When Jira reports that a work item or comment was created or changed, the app checks it. To cover what already exists, run the one-off scan of your history from the Overview.

Can it stop a work item from being created?

Add the workflow validator “Stepwise: no secrets in the text” to the Create transition. While the text holds a secret, the transition does not pass and the message says what to remove. The docs walk through it.

Who gets alerts?

The Jira groups the admin chooses, and optionally the author of the text. The email says what was found and where, never the value.

Does it store the secrets it finds?

No. It stores where a finding is (work item, field, line and column), its kind and its state. It does not store the value, a hash of it or any text around it.

How do I cut false alarms?

Switch off kinds you do not need, keep “Ignore well-known test data” on, add values to ignore, exclude whole spaces, and dismiss a finding with a reason.

Does it use AI?

No. Detectors are patterns with checks such as a checksum, and everything runs inside Atlassian.

Does it work with the Confluence version?

They are separate apps. Each is installed on its own. See Stepwise Secret & PII Scanner for Confluence.

Does it support dark theme?

Yes, it follows each person’s Jira theme automatically.

Also for Confluence

The same scan across your Confluence pages

Stepwise Secret & PII Scanner for Confluence checks pages, titles, blog posts and comments, and lists old page versions that still hold a removed value. It is a separate app.

See Stepwise Secret & PII Scanner for Confluence

Find out what is hiding in your work items

Install it, run the scan, choose who is alerted. Add the create check when you are ready.