Stop User Enumeration is single-purpose. It blocks the two probes attackers run before everything else, ?author= scans and unauthenticated /wp-json/wp/v2/users calls. The plugin keeps a log of those blocks with the endpoint, IP, user agent, and time, then exposes it on a simple admin screen. That screen is enough to confirm the protection is on, but it cannot tell you how the volume of probes has changed week over week, which endpoint is hit most often, or which IPs return again and again.

SleekView Charts reads the enumeration log as a normal data source. The endpoint, ip, user_agent, and blocked_at fields become groupable the moment the source is mapped. A donut splits blocks between author scans and REST probes, a Number card shows the weekly total, a horizontal bar surfaces the top probing IPs, and an area chart traces daily volume so a scanner wave is obvious before it hits the rest of the stack.

Nothing is rewritten on the plugin's side. Stop User Enumeration keeps blocking, the log keeps growing, and the dashboard renders the same rows in a shape that supports a daily security review without forcing the team back into a flat list.

User enumeration is the cheapest reconnaissance step an attacker takes. Most sites see it constantly, and Stop User Enumeration handles the block automatically. That makes each individual row uninteresting and the whole stream very interesting.

The shape of the probe traffic, the endpoint mix, and the IP distribution carry the actual signal. The data exists in the plugin's own log table with all the columns it maintains. Rendering it as Number, Pie, Bar, and Area cards costs nothing on the writing side and turns the same rows into a dashboard.

The cadence of enumeration review shifts from never to a daily glance.