Findings and triage
A finding is the record that a rule matched something in an AI use. A finding names the rule, its severity and what StackJack did. It never shows the matched text. This page covers how to find…
Written By Christopher Scaminaci
Last updated 16 days ago
A finding is the record that a rule matched something in an AI use. A finding names the rule, its severity and what StackJack did. It never shows the matched text. This page covers how to find findings, read them and work them: assign, review, close and reopen. Use it every day to decide what needs a person.
At a glance
- What it does: lists what your rules matched and lets you work each finding.
- Plan: Pro and above. Findings come from scanning, and rules scan text from Pro.
- Who: Reviewer or Administrator.
- Where: AI Governance → Activity → Findings.
- Needs: a rule pack that is on and a source that sends text.
Find findings
The Find findings panel narrows the list. Times are in UTC.
Read a finding
Each row shows:
- the Finding: the rule that matched,
- the Severity,
- the Person and client,
- Asked for, done: what the rule asked for and what StackJack did,
- the Status.
Open a finding's record to see the AI use around it. A finding shows its masked token. Neither the Portal nor an AI tool ever shows the matched value.
Work a finding
A finding has a status: Open, In review or Closed. Tick the findings you want. You can change up to 50 at once.
- Assign to me takes the finding and moves an Open finding to In review. You can also assign a finding to another reviewer or administrator, or unassign it.
- Close needs a reason: Remediated, False positive, Accepted risk, Duplicate or No action needed.
- Reopen a closed finding.
Every change is recorded in the audit trail.
Turn a finding into an incident
When a finding is serious enough to track, open an incident and link the finding. Incidents need the Business plan. See Incidents and notification clocks.
What you will see
- New findings also appear on the Overview in the Needs you band and on the Risk card.
- A Live rule that asks for an alert raises one in Alerts → Inbox.
- If AI judgments (Jev) is not sure about a text, the finding is a "Possible sensitive data to review (AI not sure)" alert. That alert stays in the Portal inbox and goes nowhere else. See Alerts and the inbox.
Troubleshooting
Next
Was this helpful?
More in Control and respond
Filter personal data out of tool results (the PII filter)AI judgments (Jev)Client namesAlerts and the inboxStill need help? Ask the team