Solid Security (formerly iThemes Security) tracks lockouts in wp_itsec_lockouts and a wide log of events in wp_itsec_logs covering brute force protection, file changes, 404 floods, user actions, and Patchstack vulnerability findings on Pro. The default admin spreads that across separate Lockouts, Logs, and Vulnerabilities screens, with limited cross-filtering and one-at-a-time releases that get awkward during an incident.

SleekView reads each table directly so the audit trail becomes a single workspace. Sort lockouts by reason, type (local or network), or expiry. Filter to network bans only, or to file change events from this week, or to failed logins by username. Inline release actions lift a soft lock or convert it to a permanent ban from the same row. Logs and lockouts can sit in the same view, so the event chain that triggered a lockout is visible without flipping screens.

SleekView is read-only by default and writes only through Solid Security's own release and ban actions, so the plugin's audit log stays authoritative. Pro features like User Logging, Patchstack vulnerabilities, and Trusted Devices keep their data in the same itsec tables and become available in SleekView automatically when Pro is active. Saved views with role-scoped access let a developer review file change events without seeing the full security settings tree.

Solid Security records the kind of data security people care about on their own database: who tried to log in and failed, which IPs got locked out for a 404 flood, which files changed in the last hour, and which plugins Patchstack flagged as vulnerable on Pro. The data is there, but the default UI is built for the most common single questions. The moment you need to answer something like which IPs that triggered a brute force lockout last week also generated file change events, you're either piecing it together by clicking through three screens or writing direct SQL against the itsec tables.

Both are slow during an actual incident. SleekView turns the audit trail into one surface and lets people who actually run security on the site read it in the order and shape they need. The plugin keeps writing the events; SleekView just exposes them as the joinable, filterable, role-scoped table the data already deserved.

When the audit log is also the working triage surface, response time drops and the chain of evidence stays clean.