✨ 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 BlogVault Security: scan results & firewall logs as tables

BlogVault Security writes scan summaries to wp_options and firewall events to its own bvft tables. SleekView turns each into a tracked grid where findings, blocks, and logins get pivoted and acted on locally.

♾️ Lifetime License available

SleekView table view for BlogVault Security

Scan and firewall data, locally tracked

BlogVault Security is built around an external service, but it leaves a meaningful local footprint. Scan results and configuration land in wp_options under keys prefixed with bvft_ and blogvault_. Firewall events, login monitoring, and IP blocks live in the plugin's own tables, typically wp_bvft_events and related child tables. The default admin embeds an iframe to the BlogVault dashboard, which is great for the hosted view but harder to slice locally.

SleekView reads the local entries and presents them as proper grids. Scan findings get columns for type, file, severity, and the first time they were seen. Firewall events expose IP, country, rule code, and action. Login monitoring rows show user, IP, result, and timestamp on the same grid you can filter and save.

The point is not to replace the BlogVault dashboard, which still owns the cloud scan and the offsite backups. The point is to give site owners a local, gridded view of what happened on this site, with saved filters they can reopen next week, inline notes for context the cloud dashboard cannot store, and a CSV export shaped the way an internal review actually needs.

Workflow

From BlogVault tables to a working local grid

1

Point at the local tables

Create a SleekView against wp_bvft_events for firewall data and the bvft_ entries in wp_options for scan summaries. SleekView detects each schema and offers fields as columns.
2

Promote useful columns

Surface IP, country, rule code, action, and URL for firewall events. Surface file, type, severity, and first-seen for scan findings. Add a local triage column for state that must survive scan refreshes.
3

Save review slices

Pin filters that recur: Blocked yesterday, Throttled by country, Open scan findings this week. Each captures columns, filter, and sort so reviewers reopen the same slice across audits.
4

Annotate and export

Tag rows, attach notes, and archive false positives inline. Export the active view as CSV for tickets, client reports, or incident handoffs. The cloud dashboard remains the source of truth for backups.

Sample columns

A typical BlogVault Security firewall view

One row per firewall event with IP, country, action, and rule code on the same row.
Source: wp_bvft_events (firewall) + wp_options (bvft_ prefixed scan and config keys)
When IP Country Rule Action URL
Today 09:14 198.51.100.7 RU sqli_admin Blocked /wp-admin/admin-ajax.php
Today 09:33 203.0.113.4 US rate_limit Throttled /wp-login.php
Today 09:52 192.0.2.40 BR bad_bot Blocked /xmlrpc.php
Today 10:18 203.0.113.9 DE geo_block Allowed /wp-json/wp/v2/posts

Comparison

Default BlogVault Security admin vs SleekView

Default BlogVault Security admin

  • The local admin is mostly an iframe to the BlogVault cloud dashboard, not a queryable view.
  • Local wp_bvft_events rows are not directly exposed as a filterable grid.
  • Scan summaries stored in wp_options are not browsable by file, type, or severity locally.
  • There is no inline annotation or triage state attached to local rows.
  • CSV exports come from the cloud dashboard rather than a column-scoped local grid.

SleekView

  • Reads wp_bvft_events as a real grid with IP, country, rule, action, and URL on every row.
  • Surfaces local scan summaries from wp_options as a per-finding view, not a settings card.
  • Filter by rule code, action, or country and save the view for weekly firewall reviews.
  • Inline annotate or tag rows so context lives next to the event instead of in a separate doc.
  • Local CSV exports respect the active filter and the columns currently visible.

Features

What SleekView gives you for BlogVault Security

Firewall as a grid

Treats wp_bvft_events as a first-class table. IP, country, rule code, action, and request path become filterable columns rather than a flat scrolling list inside an iframe.

Scan findings local

Pulls the scan summaries from the bvft_ options into a grid with file, type, severity, and first-seen columns. Saved views remember the filter so weekly malware reviews reopen unchanged.

Inline annotations

Tag a firewall event as reviewed, attach a note to a scan finding, or archive a false positive. Annotations stay local so internal context lives beside the row even if the cloud history rotates.

Audience

Who uses SleekView for BlogVault Security

Security teams

Triage firewall events from wp_bvft_events without bouncing into the cloud dashboard. Filter by rule code and IP range, annotate noise, and pin the views that recur every week.

Agency operators

Run the same firewall and scan review across many client sites by pinning a single saved view per network. Local annotations and triage state make the monthly client handoff a copy of one grid.

Site admins

Investigate a customer report by filtering firewall events on their IP. See the rule that fired, the action taken, and any prior context attached locally without waiting for cloud dashboard sync.

The bigger picture

Why local security data needs a real grid

Hybrid security tools like BlogVault leave their most actionable data in two places: a polished cloud dashboard and a quieter set of local tables and options. The cloud is great for cross-site rollups and long-term storage, but day-to-day questions live on each site. Which IP got blocked on this install in the last hour, which files were flagged in this scan, which login attempts ran into the rate limit on this domain.

The local rows in wp_bvft_events and the bvft_ option entries hold the answers; what is missing is a grid that exposes them with the right columns and lets a reviewer pin a saved view. Compliance reviews want repeatable evidence local to the site, not a screenshot of an iframe. Agencies want one shape they can replicate across clients without paying for a separate dashboard tier.

Treating BlogVault's local footprint as a grid closes that gap without competing with the cloud dashboard or the offsite backup pipeline that makes the plugin valuable in the first place.

Questions

Common questions about SleekView for BlogVault Security

No. BlogVault still owns the offsite backups, the cloud scans, and any cross-site rollups. SleekView only exposes the local wp_bvft_ tables and option entries as a grid for on-site investigation and weekly reviews.

 

Yes. Triggering a block writes through the plugin's own block API rather than touching wp_bvft_events directly. The cloud side receives the action through BlogVault's normal sync, keeping the centralized view consistent.

 

SleekView paginates server-side and uses the indexes on wp_bvft_events for IP and timestamp. Even on busy sites with months of events the grid stays responsive because the page is filtered against an index, not scanned in full.

 

Yes. SleekView keeps its own triage and note state for each finding key it sees in the bvft_ options. When BlogVault refreshes a scan the grid updates the underlying data while triage state and notes stay attached to the same row.

 

If BlogVault populates the country and ASN columns on wp_bvft_events, SleekView exposes them as filterable columns. Where the plugin leaves them blank, the grid simply shows blanks rather than inventing values.

 

Yes. Local CSV exports include the columns currently visible and respect the active filter and sort. Use it to attach a slice to a ticket, hand it to an incident review, or feed a SIEM that consumes periodic CSV.

 

Yes. SleekView respects the capability checks BlogVault uses for its admin pages, so only users with the right role can open the firewall or scan grids. Saved views can layer additional capability gates for sensitive slices.

 

No. Reading wp_bvft_events and the local options is cheap. The slow part of BlogVault is the cloud scan itself, which still runs on the BlogVault side; SleekView only renders what is already stored locally.

 

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