Secret Scrubber

Secrets out of ticket attachments

Pre-release: not yet on the Atlassian Marketplace. This site says what is verified and what is not.

Evidence. Unless tagged, statements on this page are covered by automated tests, not confirmed on a live site. Exceptions: confirmed on a test site in testing

Secret Scrubber for Jira Service Management redacts secrets and personal data in HAR, log, JSON, text and .env attachments. It swaps in a sanitized_ copy and deletes the original only after the swap is verified.

fixture.har
"headers": [
  { "name": "Authorization",
    "value": "Bearer tok_EXAMPLE_7Qe2x9" },
  { "name": "Cookie",
    "value": "session=EXAMPLE-81c0aa" } ],
"postData": { "text":
  "email=[email protected]
  &card=4111 1111 1111 1111" }
sanitized_fixture.har
"headers": [
  { "name": "Authorization",
    "value": "Bearer [REDACTED_BY_SECRET_SCRUBBER_3f9a]" },
  { "name": "Cookie",
    "value": "session=[REDACTED_BY_SECRET_SCRUBBER_7c21]" } ],
"postData": { "text":
  "email=[REDACTED_BY_SECRET_SCRUBBER_a05e]
  &card=[REDACTED_BY_SECRET_SCRUBBER_91d4]" }
Synthetic test fixture. Hover or focusTap a value on the left to find its label on the right. Equal values get equal labels within one install.

What it does, and what it does not

What it does

  • Starts in dry-run: it scans and logs, and changes nothing until you turn dry-run off. See Settings.
  • Scans attachments in memory when they arrive, inside a Forge app on the platform.
  • Replaces each secret with a label such as [REDACTED_BY_SECRET_SCRUBBER_3f9a].
  • Uploads the sanitized_ copy, repoints inline references, and deletes the original only after it has checked the swap. confirmed on a test site
  • Writes an audit log of counts and rule names, never values.
  • Declares no external connections and calls no non-Atlassian hosts.

What it does not do

  • It does not stop a secret from being uploaded. The original is visible until the swap finishes: typically seconds, longer for large files or a slow site. No maximum is promised. See Security. confirmed on a test site
  • It does not catch everything. Detection is pattern-based, so it misses some secrets and redacts some harmless values. See Limits.
  • It cannot undo a deletion. Run dry-run first and read the audit log before going live. confirmed on a test site

Where to go next

For scopes, data flow and what is stored, read Security and data handling.

For what is confirmed, tested and still in testing, read Verified status.