AI Data Guard

The product runs in the window beside this column, and every control in it works.

Step 1 of 10

What left the bank in the last thirty days

Six data classes and the tools they went to, summed from the pilot’s event log for the trailing thirty days: 1,144 detections inside 3,805 AI interactions, of which 302 reached no destination at all, 337 were submitted with every detected span masked or tokenized, and 505 went as the person typed them. Discovery counts every interaction, detection counts the subset carrying a sensitive class, and the two denominators are never divided into one another without the page saying so.

This is the answer to the question an examiner opens with, and a bank running no monitoring has none. A detection is not an exfiltration either, which is why the headline carries the split rather than the total alone — the first figure a compliance officer would quote is the first one they would be corrected on.

Look atThe note under the tiles: those 1,144 detections carried 1,847 class instances, 1,840 of them in the six the tiles draw, because one event carries every class found in it — so the tiles sum past the headline and the page says why rather than leaving you to do the arithmetic.