MalCare Pro splits responsibilities between its cloud scanner and the local site. On the WordPress side, wp_bv_fw_requests holds firewall request records with IP, rule, and outcome, wp_bv_lp_requests tracks login protection events, and wp_bv_ip_store caches the IP intelligence used by both. The plugin's dashboard summarises this clearly, but the local detail behind each summary is harder to pivot than it could be.

SleekView reads the three local tables directly and joins them into one grid keyed on IP. A firewall request shows alongside any matching login protection event, with the cached IP intelligence (country, threat level, last seen) inlined as columns. Filters and saved views work the same way they do for posts in WP Admin.

Note that MalCare's malware scanner runs as a cloud service. SleekView does not run scans or fetch results from MalCare's servers; it surfaces the local request and lockout data that already lives in your database. For the cloud scan results themselves, the MalCare dashboard remains the source.

MalCare Pro pushes most of the heavy lifting to its cloud service, which is the right architecture for malware scanning at scale. The trade-off is that the local data, the firewall requests and login protection events that live in your own database, can feel secondary even though it is what powers most day-to-day triage. A real grid over wp_bv_fw_requests, wp_bv_lp_requests, and wp_bv_ip_store turns those tables from a feed into a working timeline.

The same IP attacking your login page and your search endpoint is one row in the joined view rather than two rows in two screens. Country and threat level move from background fact to filterable column, which is what investigations need when the question is 'show me everything from this region in the last hour'. Saved views replace ad-hoc CSV exports for repeat reviews, and inline annotations turn the log from a record of what was blocked into a record of what your team did about it.

MalCare's cloud dashboard still handles the scanner side; the local grid simply makes the local side first class.