Sucuri Security is the auditing and post-hack toolkit shipped by Sucuri Inc. It records failed and successful logins into the dedicated wp_sucuriscan_lastlogins table, monitors file integrity, and streams audit-log events to Sucuri's API so they survive a database compromise. The website firewall is the separate paid Sucuri CloudProxy product; the free plugin focuses on auditing and post-hack monitoring.

The plugin's default admin lists last-logins on one screen and the remote audit log on another, with separate filters and separate paginators. Comparing a failed-login spike to the file-integrity warnings that followed means clicking between two screens and cross-referencing timestamps by hand. The signal that ties them together is the user account.

SleekView reads the wp_sucuriscan_lastlogins table and pulls the audit log via the same Sucuri API the plugin uses. Both sources land in one grid, joined to wp_users by login. Each row carries the timestamp, the user, the event type, the IP, and the source. Saved filters carry across both surfaces, so a triage view becomes one screen instead of two.

Sucuri Security already does the hard work, it records logins into wp_sucuriscan_lastlogins and streams an audit log to Sucuri's API that survives a database compromise. The trouble is that those two sources land on two screens with two filters, which means joining a failed-login spike to the file-integrity warning that followed it is manual work. Security leads need both signals on the same morning queue.

Site admins need the per-user view that reads both stores at once. Agencies need the per-client CSV that carries both data sets. SleekView reads the lastlogins table and the audit-log API together, joins them to wp_users, and renders one grid where every event is one row.

Severity is a sortable column. Failures sort ahead of informational rows. The plugin keeps owning the audit work, and the team finally gets the triage queue the screens never tried to ship.