A verdict such as “Suspicious” raises the next question: how did SilentShield get there? For plans that include it, every entry in the log has a derivation that answers this in seven steps. This post shows it. The film below shows it on the real dashboard with sample data, silent and with short captions. The text under it says the same in words, so you can follow along without playing the film.
The film in short
The film opens an entry from “Behavior Logs” with “View”, points at the button “How did this verdict come about?”, opens it and highlights the seven steps on the left. The last caption says the view depends on the plan. The entry in the film is from sample data: the visitors are scripts, and the film makes no statement about how many real visitors are judged correctly. It has no sound and does not start by itself.
Step 1: open an entry
In the behavior log, “View” opens the detail page of one submission with its verdict and its technical data, and “What the verdict is built on”, the measured signals. At the top right sits “How did this verdict come about?”, when your plan includes it. How to read the entry itself is shown in understand the result.
Step 2: the seven steps
The derivation lists seven steps on the left: “1 · Entry” (key, page, form), “2 · Blocks” (honeypot, Tor, data center), “3 · Signals” (seven behavior values), “4 · Reasons” (anomalies that lower the score), “5 · Limits” (the score against the bot and human limits), “6 · Policy” (your own rules and action) and “7 · Verdict” (the result). Each step carries a status such as “In order”, “Note” or “Decisive”. On the right the selected step is explained, for the signals with one bar per value.
Step 3: where the verdict was decided
In the film, step “5 · Limits” is marked “Decisive”: the score was compared with the bot and the human limit, and that comparison decided. The limits are part of your security policy (see set up the security policy).
What the film does not show
Whether the derivation is available depends on your plan; the film names no plan. It also does not claim that the derivation is a proof that a verdict is right; it shows how the score led to the result. The documentation page for the overview describes the log and its entries.