WP Cerber Pro keeps one of the most thorough activity logs on WordPress. Every event flows into wp_cerber_log with an activity code, IP, user identifier, country (in Pro, via the bundled IP-to-country lookup), and a stamp column. Sibling tables hold the traffic inspector rows and the active lockouts. The native Activity screen is investigator-shaped: one row at a time, with simple filters and pagination.

SleekView reads wp_cerber_log and the sibling Cerber Pro tables as one workspace. Sort by stamp to see the last hour. Filter by activity code to isolate failed logins, by country to ignore expected traffic, by IP to follow one actor across multiple events. Inline action columns surface block and unblock through Cerber's own functions, so a row action in SleekView appears in the Cerber admin without a sync step.

Cerber Pro keeps owning enforcement, policies, and per-request decisions. SleekView only adds the sortable triage surface: saved views like Failed logins on /wp-login.php in the last hour or Lockouts from outside the EU make daily review a one-click operation instead of three Cerber screens.

WP Cerber Pro logs more about authentication and request behaviour than almost any other WordPress security plugin. The trade-off is that the admin was built around per-event drill-down. Anyone asking which IP failed login on which URL around the same minute as a suspicious request has to bounce between Activity, Lockouts, and Traffic Inspector.

SleekView reads the same tables Cerber already writes and renders them as one sortable, filterable workspace. The plugin keeps enforcing policies and lockouts. The team gets a triage queue with saved views, per-role scoping, and inline block actions that propagate to Cerber's own UI.

The result is faster daily review, cleaner incident reconstruction, and an investigation surface that matches the depth of the data Cerber Pro already captures.