Data-loss rules, findings and scanning StackJack tool traffic
A data-loss rule looks for something in the text of an AI use, such as a card number or a project code. When a rule matches, AI Governance records a finding. A finding shows what matched by rule name.…
Written By Christopher Scaminaci
Last updated 13 days ago
A data-loss rule looks for something in the text of an AI use, such as a card number or a project code. When a rule matches, AI Governance records a finding. A finding shows what matched by rule name. It never shows the text itself.
At a glance
- What it does: scans the calls that go through StackJack's own tools against your data-loss rules, and explains the refusal messages.
- Plan: Free does not scan. Pro raises alerts only. Business and above enforce Block, Mask and Warn.
- Who: an Administrator changes the settings. A Reviewer or Administrator works findings.
- Where you set it up: AI Governance → Privacy and data → Security scanning. Rules are on Rules → Rule packs.
- Where you see the result: Activity → Findings and the Alerts inbox.
Findings
In a person's own view, the findings line reads:
- Findings about your AI use: times a rule matched something in your AI use in the last 30 days. A finding shows what matched by rule name; it never shows the text itself.
- No rule matched your AI use in the last 30 days.
Scan StackJack tool traffic
Scan StackJack tool traffic. When this is on, StackJack checks what your AI tools send to your connected systems (the arguments of a tool call) and what the connected systems answer (the result) against your data-loss rules, as the call happens. Only calls that go through StackJack are checked.
- On Pro, a rule set to Block, Mask or Warn raises an alert. It does not stop, change or hold the call.
- On Business and above, Block refuses the call, Mask hides the matched value in the result before your AI tool sees it, and Warn asks the person for a reason first.
- On Free, the setting is not available.
- StackJack keeps the text of a call only if your capture level says so. The check itself reads the text in memory and discards it.
What you see on the first day. Alerts only, until you set Block, Mask or Warn on a rule.
What it does not check. Rules that look for names of people, places or organizations do not run on StackJack tool traffic. Numbers and field names are not checked, only text values. A person you exclude from content collection is also not protected on this lane: StackJack does not block or mask their calls.
When it starts. The first time you turn it on, it can take up to about six minutes to start: StackJack creates the source for your organization within five minutes, and every server reads the setting within a minute. An EU or UK organization also needs its staff notice recorded first, and an organization with a works council needs the agreement recorded.
The status line next to the toggle uses these words:
- Active. Scanning is on and nothing holds it back.
- Waiting for the StackJack source. Scanning is on and StackJack is still creating the source for your organization. This passes within about five minutes.
- Staff notice not recorded. Record the staff notice, then scanning starts.
- Works council pending. Record the works council agreement, then scanning starts.
- Source set to facts only. The StackJack source collects counts only, so nothing is checked. Raise its capture level to scan.
- Plan below Pro. Scanning of StackJack tool traffic starts with Pro.
Refuse the call when the scan cannot finish
Refuse the call when the scan cannot finish (Business and above; off by default). By default, when StackJack cannot finish checking a call, the call goes through and the miss is logged. Turn this on and StackJack refuses the call instead.
What it costs you:
- A very large tool result, over the size StackJack can check, is then always refused.
- A check that runs too slow is refused rather than let through.
- A result refused after a write tool ran does not undo the action. The refusal says that the action has already happened and must not be run again.
Calls are not refused when scanning is off for your organization, or when StackJack's own scanner is paused or is not ready yet (for example just after a restart): they go through unchecked, StackJack logs each of those, and the Portal shows the state. One case differs: if the scanner could not start at all on a StackJack server (its rule catalog failed to load), then with this setting on, a call that reaches that server is refused, because StackJack cannot check it. StackJack sees that fault at once, and the refusals end when the server is fixed or restarted.
Filter personal data out of tool results
On Business and above, the PII filter can go one step past a rule: a StackJack tool that only reads data answers blank instead of returning a result that holds an email address, a phone number, a date of birth, a national or tax ID number, a bank account number or a driver's license number. The AI can ask to see the data for one call, and StackJack records each time it does. It needs no rule of yours. See Filter personal data out of tool results (the PII filter).
What an AI tool is told when a call is refused
There are nine messages, each with a next step. A rule's name goes where the text says {rule name}, and the link of the warning page where it says {link}. A message never holds a value from the call, a name from its text or a person.
A rule blocks the arguments
- StackJack blocked this call before it ran: its arguments matched the data-loss rule ''. Nothing was sent to the connector.
- Remove the matched data from the request and call again, or ask your AI Governance administrator about the rule.
A rule blocks the result of a read tool
- StackJack blocked this tool's result: it matched the data-loss rule ''.
- Narrow the request so the result leaves out the matched data, or ask your AI Governance administrator about the rule.
A rule blocks the result of a write tool
- The tool ran, but StackJack blocked its result: it matched the data-loss rule ''. The action has already happened. Do not run it again.
- Check the change in the connected system instead of running the tool again, and ask your AI Governance administrator about the rule.
A Warn rule, and the connection has no person
- This call matched the data-loss rule '', which asks a person for a reason before it runs. This connection has no person who can give one (an API key, an automation or a builder test), so StackJack blocked the call.
- Run the call from your own signed-in connection to give a reason, or ask your AI Governance administrator about the rule.
A Warn rule, and the person is offered the page
- This call matched the data-loss rule '', which asks for a reason before it runs. Open to give a reason. The exception lasts 15 minutes for this rule and this tool.
- After the reason is given, run the same call again within 15 minutes.
A Warn rule, and the page could not be offered
- This call matched the data-loss rule '', which asks for a reason before it runs, but StackJack could not offer the exception right now, so it blocked the call.
- Try again in a few minutes.
The scan of the arguments could not finish, and your organization refuses such a call
- StackJack could not finish its data-loss scan of this call's arguments, and your organization refuses a call it cannot scan. Nothing was sent to the connector.
- Try again in a few minutes, or send a smaller request, or ask your AI Governance administrator about the setting.
The scan of a read tool's result could not finish
- StackJack could not finish its data-loss scan of this tool's result, and your organization refuses a result it cannot scan.
- Try again in a few minutes, or narrow the request so the result is smaller, or ask your AI Governance administrator about the setting.
The scan of a write tool's result could not finish
- The tool ran, but StackJack could not finish its data-loss scan of its result, and your organization refuses a result it cannot scan. The action has already happened. Do not run it again.
- Check the change in the connected system instead of running the tool again, and ask your AI Governance administrator about the setting.
The warning page
When a data-loss rule asks for a reason, the person opens the warning page:
- The tool was held because the tool's arguments matched this rule. Give a reason to continue. The exception lasts 15 minutes for this rule and this tool.
- Give a reason and continue
- You can run the call again until .
- You already gave a reason. The exception lasts until .
- This link has expired. Run the call again to get a new one.
- This link is not valid for your account.
- This page is not available.
The page says "the tool's result" in place of "the tool's arguments" when the result matched. The reason a person types is kept with the exception, only for the person's own use of it, and is erased with the person.
For what a scan marked Complete means, see Capture levels and what your employer sees.
Was this helpful?
More in Control and respond
Rule packs, modes and custom rulesAI judgments (Jev)Client namesAlerts and the inboxStill need help? Ask the team