Security Scanner View

Security Scanner View (PII & DLP) helps teams detect sensitive data in Jira work items and their change history. It scans current content and past changes to highlight potential risks in one clear view.

This makes it easier for companies to reduce data exposure, stay compliant, and keep control over sensitive information stored in Jira.

Note: Security Scanner View is available during the trial period and included in the Advanced plan of Issue History for Jira app. After the trial ends, it is available only in the Advanced plan.

You can try the Advanced plan for 30 days free or upgrade at any time.

What Security Scanner View Does

Security Scanner View (PII & DLP) automatically scans Jira work items to find sensitive data, including:

Password / passphrase
Login credentials
Credit card number
Social Security Number (SSN)
Social Security Number (validated SSN format)
AWS access key ID
Amazon MWS key
AWS secret access key
Google API key
Google OAuth client ID
Google OAuth access token
GitHub access token / PAT
API key
Secret token or value
Stripe live API key
SendGrid API key
Slack token
Slack webhook URL
Azure storage account key
Mailgun API key
Mailchimp API key
Shopify token / secret
Shopify Partner API access token
Square access token
Square OAuth secret
SSH private key
SSH public key
RSA private key
PKCS#8 private key
PGP private key block
EC private key
Credentials embedded in URL
Driver’s license number
Passport number
Phone number
Email address
IP address
Street address
Username / login
ZIP / postal code
IPv6

Detected findings are displayed in a structured table, making it easy to review and prioritize work items that need attention.

How does it work?

Open the app in Jira and go to Security Scanner View.
Select what to scan using filters. You can filter work items by space, sprint, JQL, and more.
Set the date range to specify the time period to scan (current content and history within that range).
Review the generated report. It shows work items (Jira work items where sensitive data was detected), type of finding (category of detected sensitive data (for example, password or API key), security finding (detected sensitive data), score (indicates how much attention the finding may need).

Security Scanner View helps users quickly see where sensitive data appears in Jira work items and their history. Instead of manually checking work items one by one, you can get a clear list of findings in one place.

Historical finding (not present in the current state of work item)

Historical mark in the Field column indicates that the security finding is no longer present in the current content. It means sensitive data (such as a password, API key, or card number) appeared in a past change, for example, in an earlier comment or description, and was later removed or updated.

Why this matters:

Sensitive data may still exist in the work item history.
Historical exposure can be relevant for audits and compliance.
Teams can identify and address past data risks, not just current ones.

Haven't used Issue History for Jira app yet? 👉 Then you’re welcome to try it 🚀