✨ 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 iThemes Security: logs & lockouts as tables

iThemes Security 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, host, or user and act on inline.

♾️ Lifetime License available

SleekView table view for iThemes Security

Security logs that bend to your questions

iThemes Security (the free predecessor to Solid Security) stores its activity in a familiar set of custom tables: wp_itsec_logs holds every event with module, code, type, and a JSON data column, wp_itsec_lockouts tracks active blocks for hosts and users, and wp_itsec_temp backs the soft lockout flow. The plugin's default screens summarise each table, but the listing UI splits the audit trail across modules rather than presenting one grid.

SleekView reads wp_itsec_logs directly and joins wp_itsec_lockouts on host and user so an event and the block it caused share a row. Module, code, severity, host, user, and the unpacked data JSON become first-class columns. Filters and saved views work like any other SleekView source, so failed-login triage or file-change watchlists are a click rather than a SQL query.

Inline edits route through the plugin's own functions where supported (for example releasing a lockout) and fall back to direct table writes with conflict detection elsewhere. The event log itself stays read-only by design so the audit chain holds.

Workflow

From iThemes Security 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.

Sample columns

A typical iThemes Security log 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 02:14 brute_force failed-login 203.0.113.4 mia@brew.coop Warning
Today 02:42 file_change file-modified internal alex@studio.co Notice
Today 03:01 lockout host-lockout 198.51.100.7 (none) Critical
Today 03:30 user_logging login-success 203.0.113.22 tom@hello.dev Info

Comparison

Default iThemes Security admin vs SleekView

Default iThemes Security admin

  • Logs are presented per module in wp_itsec_logs with no unified grid across the audit trail.
  • The data JSON column carries the richest detail but is not exposed as filterable columns.
  • Active blocks in wp_itsec_lockouts cannot be cross-filtered with the log events that caused them in the default UI.
  • Bulk operations on lockouts (release a range or whitelist a subnet) are limited to single-row actions.
  • Exports are CSV per module with a fixed column set, not per saved view.

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 and grouping.
  • Saves named views for failed logins, file changes, or two-factor failures.
  • Inline release of a lockout or whitelist of an IP from the row, routed through the plugin's own functions.
  • Exports the visible columns as CSV or JSON with the active filter applied.

Features

What SleekView gives you for iThemes Security

Logs and lockouts joined

Reads wp_itsec_logs and joins wp_itsec_lockouts on host and user so each event row carries its 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.

Inline triage actions

Release a lockout, whitelist an IP, or annotate an event from the row. Writes call iThemes Security's own functions where available, with table writes as a fallback.

Audience

Who uses SleekView for iThemes Security

Security ops

Cross-module investigations against wp_itsec_logs. Pivot on user, host, or module to see 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.

Compliance owners

Export filtered audit rows for monthly access reviews and incident retrospectives. Saved views give auditors a stable, repeatable snapshot.

The bigger picture

Why a unified security grid still matters for iThemes

iThemes Security has been on WordPress sites long enough to accumulate millions of rows in wp_itsec_logs across the network of installs that still run the free build. That history is operationally valuable because patterns at a single site become harder to read once the log spans years, and the plugin's default UI was built around per-module screens rather than a flat grid. Real incidents tend to cross modules: a brute force burst often coincides with a file change in the same window, and a host lockout makes more sense when the failed login chain that produced it sits next to it.

Treating wp_itsec_logs and wp_itsec_lockouts as joined sources turns the audit trail from a record into a working triage surface. Saved views let the next on-call admin reopen the same investigation in one click rather than rebuilding filters from memory. Inline lockout actions keep the action where the evidence is.

The log itself stays read-only so the audit chain holds. iThemes Security captured the trail; a real grid is what makes the trail useful at speed.

Questions

Common questions about SleekView for iThemes Security

No. The plugin's dashboard keeps doing what it does. SleekView adds a real grid layer on top of wp_itsec_logs, wp_itsec_lockouts, and wp_itsec_temp so investigations are easier than scrolling lists.

 

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

 

Where iThemes Security exposes a public function (for example to release a lockout), SleekView calls it. For fields without a public API, writes go to wp_itsec_lockouts directly with conflict detection.

 

Yes. Solid Security ships the same table layout. SleekView reads wp_itsec_logs whether the site is on the older iThemes Security build or the rebranded Solid Security release.

 

No. SleekView paginates server-side using the existing indexes on module, code, and timestamp. Even installs with millions of rows stay responsive.

 

Yes. wp_itsec_logs stores a user_id that joins to wp_users. SleekView can show display name and role alongside the event.

 

Yes. wp_itsec_temp is exposed as its own view for short-term blocks and can overlay onto the main lockout grid when needed.

 

Exports respect the active filter and visible columns. CSV is the default for spreadsheets and ticket systems; JSON is available for SIEMs 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