Shield Security Pro keeps an unusually detailed schema for a WordPress security plugin: wp_shield_request_logs stores HTTP requests Shield evaluated, wp_shield_event_logs stores the security events it raised, and wp_shield_ip_rules stores the IP block and allow rules in effect. The plugin's screens cover each in turn, but the cross-table picture, the one operations teams actually need, lives behind the UI.

SleekView reads each Shield table as a first-class grid. Requests and events join cleanly on request ID where present, and both join to wp_shield_ip_rules on IP so a row carries the rule that did or did not apply. Filters and saved views capture the questions a team asks repeatedly, like failed-login attempts in the last hour or new IP rules created today.

Inline writes go through Shield's own functions where available, for example adding an entry to wp_shield_ip_rules or marking an event reviewed. Where Shield does not expose a public API, SleekView writes the row directly with conflict detection so concurrent admin changes do not silently overwrite each other.

Shield Security Pro records more local detail than most WordPress security plugins. Request logs and event logs sit side by side in your database, and that level of detail is exactly what triage needs when an incident spans bot traffic, brute force, and admin activity. The catch is that detail without a real grid is more burden than asset, because each table on its own only answers part of the question.

A bot signal makes more sense when the request that triggered it sits on the same row. A failed-login burst tells a clearer story when the IP rule that finally caught it shows next to the event. Treating wp_shield_request_logs, wp_shield_event_logs, and wp_shield_ip_rules as joined sources turns the detail into something an operations team can read at speed.

Saved views replace ad-hoc filters, so the next on-call admin reopens the same triage in one click. Inline writes mean the action and the evidence sit on the same row, and the audit log itself stays read-only by design. Shield captures the data faithfully; a real grid turns that data into a working incident response surface.