✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for Solid Security Pro: logs, lockouts & user groups as tables

Solid Security Pro writes events to wp_itsec_logs and tracks blocks in wp_itsec_lockouts. SleekView joins both into a single grid you can filter by module, user, or IP and edit inline.

♾️ Lifetime License available

SleekView table view for Solid Security Pro

Security logs that bend to your questions

Solid Security Pro keeps its data in a small set of custom tables: wp_itsec_logs stores every event with a module, code, type, and JSON data column, while wp_itsec_lockouts holds active blocks for hosts and users alongside wp_itsec_temp for soft lockouts. The plugin's dashboard summarises this, but the listing screens force you into a fixed view per module rather than a single live grid across the whole audit trail.

SleekView reads wp_itsec_logs directly and joins wp_itsec_lockouts on host and user. Module, code, severity, host, user, and the unpacked data JSON become first-class columns. From there filters and saved views work the same way they do for posts in WP Admin, so a triage screen for failed logins or a watchlist for file change events takes a click rather than a SQL query.

Inline edits route through the plugin's own API where supported, so releasing a lockout or whitelisting an IP keeps Solid Security Pro's hooks firing. Where there is no public CRUD method, SleekView falls back to direct table writes with conflict detection so concurrent admin changes do not silently overwrite each other.

Workflow

From Solid Security Pro logs to a real triage grid

1

Connect to wp_itsec_logs

Create a SleekView against wp_itsec_logs. Native columns (module, code, type, host, user, timestamp) are detected and offered as the starting field set.
2

Promote data JSON keys

Pick the keys inside the data column that matter for your modules and surface them as columns. Brute force usernames, changed file paths, and two-factor methods all become filterable.
3

Join lockouts and users

Add joins to wp_itsec_lockouts and wp_users so each event row carries its current block state and the actor's display name and role.
4

Save views and edit inline

Pin views for failed logins, file changes, or active lockouts. Release a block, whitelist an IP, or annotate an event from the row, with writes routed through the plugin's API.

Sample columns

A typical Solid Security Pro audit view

One row per event with module, code, host, user, and severity from wp_itsec_logs.
Source: wp_itsec_logs, wp_itsec_lockouts, wp_itsec_temp
When Module Code Host User Severity
Today 08:14 brute_force failed-login 203.0.113.4 alex@studio.co Warning
Today 08:42 file_change file-modified internal ria@design.io Notice
Today 09:01 lockout host-lockout 198.51.100.7 (none) Critical
Today 09:30 two_factor auth-success 198.51.100.22 tom@hello.dev Info

Comparison

Default Solid Security Pro admin vs SleekView

Default Solid Security Pro admin

  • Logs are split across module-specific screens in wp_itsec_logs, with no unified grid for the full audit trail.
  • The data JSON column carries the richest detail but is not exposed as filterable columns in the default UI.
  • Active blocks in wp_itsec_lockouts show in a list, but cannot be cross-filtered with the log events that caused them.
  • Bulk releasing or whitelisting from a lockout list is limited to single-row actions in most views.
  • Exports are CSV from one module at a time, with the column set fixed by the plugin.

SleekView

  • Joins wp_itsec_logs and wp_itsec_lockouts so events and their resulting blocks sit on the same row.
  • Promotes keys from the data JSON to first-class columns for filtering, sorting, and grouping.
  • Saves named views for failed logins, file changes, or two-factor failures and reopens them across teams.
  • Inline release of a lockout, whitelist of an IP, or annotation of an event from the row.
  • Exports the visible column set as CSV or JSON with the active filter applied.

Features

What SleekView gives you for Solid Security Pro

Logs and lockouts joined

Reads wp_itsec_logs and joins wp_itsec_lockouts on host and user, so an event row carries its current block state and the lockout reason without a second screen.

JSON data as columns

Promotes keys from the data JSON column to typed columns. Module-specific fields like username, file path, or country become real filters rather than buried text.

Inline triage actions

Release a lockout, whitelist an IP via the plugin's allow list, or tag an event for review. Writes call Solid Security Pro's own functions where available, with table writes as a fallback.

Audience

Who uses SleekView for Solid Security Pro

Security ops

Run cross-module investigations against wp_itsec_logs. Pivot on user, host, or module to spot brute force patterns alongside file changes and two-factor failures in one grid.

Site administrators

Triage user lockouts in wp_itsec_lockouts with context about which event triggered them. Release, extend, or whitelist directly from the row without leaving the audit view.

Compliance owners

Export the visible columns for monthly access reviews. Saved views give auditors a stable, repeatable snapshot rather than a CSV regenerated by hand each cycle.

The bigger picture

Why a unified security grid matters

Solid Security Pro is built around modules, and each module solves its slice of WordPress hardening well. The cost of that modularity is fragmentation in the admin: brute force evidence sits in one screen, file change reports in another, lockouts in a third, and the JSON-encoded detail that ties them together is locked inside wp_itsec_logs. Real incidents rarely respect those module boundaries.

A failed-login burst usually correlates with a file change or a sudden surge in 404s, and the same IP can appear across modules within minutes. Treating the underlying tables as one grid lets a security admin see those correlations without writing SQL or exporting CSVs. Lockouts gain context because the row that caused them is one click away, and false positives get released with their reason annotated for the next reviewer.

Multisite networks gain the same view across sites, which matters when one tenant under attack indicates the same actor probing the others. Solid Security Pro already captures the data faithfully; a real grid turns that data into something an operations team can act on.

Questions

Common questions about SleekView for Solid Security Pro

No. SleekView reads wp_itsec_logs and wp_itsec_lockouts without intercepting the plugin's hooks. Solid Security Pro keeps writing events the same way it always has.

 

Yes. Any key inside the data column can be promoted to a column. Once promoted it behaves like any native field for filtering, sorting, and exports.

 

Where Solid Security Pro exposes a public function (for example to release a lockout or add an IP to the allow list), SleekView calls it. For columns without a public API, writes go to wp_itsec_lockouts directly with conflict detection.

 

Yes. SleekView respects multisite context. A network admin view can join logs across sites, while per-site admins see only their own slice of wp_itsec_logs.

 

No. SleekView paginates server-side using the existing indexes on module, code, and timestamp. Even installs with millions of rows in wp_itsec_logs stay responsive because each request fetches one page.

 

Yes. wp_itsec_logs stores a user_id that joins back to wp_users. SleekView can show display name and role alongside the event so user-by-user reviews do not require a separate query.

 

Yes. wp_itsec_temp is exposed as its own view for short-term blocks. You can also overlay it on the main lockout grid when a complete picture of active blocks is needed.

 

Exports respect the active filter and visible columns. CSV is the default for spreadsheets and ticket systems; JSON is available when piping into a SIEM or downstream automation.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView