SleekView for Defender
Read Defender's lockout, scan, and audit-log tables into a single workspace built for security operations. Combine cross-feature events into one filterable view your team can actually run on.
♾️ Lifetime License available
From multiple Defender screens to one workspace
Defender by WPMU DEV is a strong all-rounder: malware scans, firewall, comprehensive audit log, mask login URL, two-factor support, and security recommendations. Each capability comes with its own UI inside Defender, which is good for setup and configuration but rough for day-to-day operations once a portfolio includes multiple sites and multiple admins. Audit log lives in one screen, lockouts in another, scans in a third, and cross-feature questions require switching tabs.
SleekView reads Defender's wp_wpdef_* tables directly, including wp_wpdef_audit_log and the lockout tables, and renders them in a single workspace. Build columns for event type, user, IP, severity, and status. Save filters that span audit and lockout events together, like 'all activity for IP 45.61.x.x in the last 7 days' or 'high-severity events plus active blocks.'
The combination matters because Defender writes excellent telemetry; the gap is the operational surface that joins it. SleekView fills that gap without replacing any of Defender's enforcement, alerting, or scanning logic. Defender keeps doing what it does well; SleekView turns the resulting data into a workspace ops teams can actually run on.
Workflow
From scattered Defender screens to one ops workspace
Read the wpdef tables
Join the streams
Save runbook lenses
Export per audit
Sample columns
Audit log and lockouts together
wp_wpdef_audit_log
| Event | User | IP | Severity | Status | Date |
|---|---|---|---|---|---|
| Plugin updated | dennis | 84.12.x.x | Info | OK | 2026-04-24 |
| IP lockout | anon | 45.61.x.x | High | Blocked | 2026-04-24 |
| User created | marie | 84.12.x.x | Medium | Review | 2026-04-23 |
| File scan | system | — | Info | Clean | 2026-04-23 |
Comparison
Defender alone vs. Defender + SleekView
Default Defender screens
- Audit log and lockouts live behind separate menus
- Each Defender feature has its own filter set
- Hard to share a saved view with the whole team
- Limited cross-feature filtering
- Exports are per-screen rather than per-view
SleekView
- Reads wp_wpdef_* tables live
- Combine audit log and lockouts in one table
- Filter by severity, event, user, or IP
- Saved views for incident response
- Export filtered events for audits
Features
What SleekView gives you for Defender by WPMU DEV
Unified security view
Show high-severity audit events alongside active lockouts in one table. The picture sharpens immediately because cross-feature questions become one filter, not two screens.
Severity-first triage
Saved views by severity keep the team focused on what is actually urgent. Info-level scans hide so admins are not drowning in clean noise during an incident.
Audit exports
Send auditors a clean CSV of the exact events and window requested. Filtered exports honor the active selection, so nothing extra leaks into the report.
Audience
Defender deployments that benefit
Multi-site agencies
WPMU DEV-managed portfolios benefit from a single SleekView template applied across every site. One workspace pattern scales from one client to fifty without growing the playbook.
Internal security teams
When multiple admins share security duties, a shared saved view beats juggling separate dashboards. Everyone opens the same URL and sees the same triage queue.
Compliance-driven shops
Audit-ready exports of authentication events reduce review prep significantly. The DPO or auditor gets the slice they asked for, no more and no less.
The bigger picture
Telemetry is only useful if the workspace keeps up
Defender's value compounds with portfolio size. A single site with one admin barely needs a unified workspace; the default Defender UI works fine. By the time an agency or in-house team is running Defender across ten or fifty sites, the per-feature screen design starts to bite.
Audit, lockouts, and scans are each separately useful, but the questions that come up during an incident span features. 'Was this IP active before we blocked it?' requires audit plus lockouts. 'Did this user change anything before we noticed the malware?' requires audit plus scans.
SleekView treats the wpdef_* tables as one data layer and lets you build the cross-feature views the operational reality demands. None of Defender's protection logic changes; what changes is whether the team can answer questions during the eight minutes that matter, instead of remembering them on Monday morning when nobody can act.
Questions
Common questions about SleekView for Defender by WPMU DEV
No. Defender keeps detecting, scanning, blocking, and alerting exactly as configured. SleekView is a read view of the data Defender writes to its own tables. The two plugins are independent at runtime, which means installing SleekView never affects Defender's protection logic or its WPMU DEV cloud connectivity.
Yes. SleekView reads whatever Defender stores locally, free or Pro. The Pro plugin writes additional audit detail and richer scan results; those simply appear as additional rows or columns in your SleekView automatically without extra configuration on the SleekView side.
Unblock actions go through Defender's own UI by design, so the audit trail Defender maintains around enforcement stays clean and complete. SleekView lets you flag the row for follow-up, annotate it with context, or export the relevant entries to a ticket, but the actual unblock remains a Defender action.
Yes. Per-site scope is respected per blog. On a multisite install you can build a network-level view that joins audit and lockout events across blogs, which is useful when one security team monitors a whole network and needs a single triage queue rather than one per site.
No. Reads happen on demand only, and Defender's tables are already indexed for its own dashboards. SleekView reuses those indexes, runs no background jobs, and never touches the front-end request path. Visitor performance is identical with or without SleekView installed.
Yes. Each SleekView is gated by a capability you choose, so you can expose a triage view to a security role while keeping the broader audit log behind administrator capabilities. That matches the segregation most multi-admin teams already enforce in WordPress.
The corresponding rows simply stop being written. Existing rows in your SleekView remain visible (they are historical evidence), and the view keeps working for the features that are still enabled. SleekView never assumes which Defender features are active; it reads whatever is in the tables.
Indirectly. SleekView reads Defender's local tables, which are the same data that feeds the Hub for that site. The two views are independent, so the Hub's portfolio-wide reporting and SleekView's per-site or network-wide tables complement each other without duplicating workflow.
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.
Lifetime ♾️
Most popular
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
€749
Continue to checkout