Findings and triage
How to read a finding, and which of the four actions to use.
What this page is for. Working the queue. The Findings tab is where you spend your time; everything else configures it.
Secret Scanner
Detected secrets, credentials, PII and sensitive data exposed in Jira issues.
| Issue | Field | Category | Pattern | Match | Detected | Status | Actions |
|---|---|---|---|---|---|---|---|
SUP-1182 | Description | Cloud Providers | AWS Access Key ID | AKIA**** | 2 hours ago | Open | Create IssueDismiss |
SUP-1174 | Comment | AI & ML Services | OpenAI API Key | sk-p**** | 5 hours ago | In Progress | SEC-42 |
OPS-901 | Attachment · config.yaml | Database Connections | PostgreSQL connection string | post**** | yesterday | Resolved | Redacted |
How to read a row
- Issue
- The issue containing the secret. The link takes you straight to it.
- Field
- Where in the issue: the summary, the description, a comment, a custom field, the change history, or a named attachment.
- Category and Pattern
- What matched, for example Cloud Providers → AWS Access Key ID. This tells you what to rotate, which is the most important information on the row.
- Match
- The masked preview: the first four characters only. Enough to find the value in the issue, not enough to use it.
- Status
- Open, In Progress or Resolved. A finding linked to a remediation ticket follows that ticket's status.
- Redacted
- A badge shown when auto-redaction replaced the value in the issue.
The actions, and when to use each
Create Issue is a button in the Issue column. Resolve and Dismiss (false positive) are in the row's ⋮ menu. Restore lives on the Dismissed tab, and it is the way back from either of them.
| Action | Use it when | What happens |
|---|---|---|
| Create Issue | The finding is real and a credential must be rotated. | Creates a ticket in your tracking project — summary [Secret Detected] pattern in ISSUE-KEY — links it to the finding, and tracks its status on this row. It is created as you, so you need Create Issue permission in that project. |
| Resolve | You have dealt with it and do not need a ticket. | Takes the finding out of the working queue and records it on the Dismissed tab with the outcome Resolved. The value is not suppressed, so if the secret is still in the issue it will be found again on the next scan — which is the point. The action is logged in the Audit Log. |
| Dismiss (false positive) | It is a false positive. | Suppresses that value so it is not reported again, and records who, when and why on the Dismissed tab with the outcome Dismissed. |
| Restore | You dismissed or resolved something you should not have. | On the Dismissed tab, puts the finding back in the queue and lifts the suppression. There is a way back from every judgement on this screen. |
Dismissing a false positive
Dismiss Finding
This finding will be permanently dismissed and will not be detected again for this exact match.
SUP-1182 · DescriptionA dismissal covers that exact value, in that kind of field, on that one issue. So the same value in a different comment on the same issue counts as the same finding and stays suppressed, while the same value on another issue, or in a different kind of field, is a new finding.
Turn on Require Reason When Dismissing on Scanning Rules if anyone will ever audit this. The reason is stored with the dismissal, which is what makes the Dismissed tab useful six months later.
The tab lists dismissals and resolutions together, filterable by issue key, pattern, category and outcome, with Export CSV for the whole history and a per-row Restore.
Analytics
Security Analytics
Detection trends, compliance metrics and remediation progress over the last 90 days.
The Analytics tab answers the two questions a security review asks: is exposure going up or down, and where does it come from. Detections per day over 90 days, split by category and by field type, alongside totals for what is still open, what was dismissed, what was resolved and what was auto-redacted.