NinjaFirewall Pro extends the free edition with additional WAF policies, an extended event log, and an IP access list that supports allow, deny, and time-bound entries. The event log records each decision (rule, action, IP, URI, method, stamp), and the access list lives in the plugin's own table.

The default admin presents the event log and the IP access list on separate screens. Triaging a brute force campaign therefore means flipping between the log to find the offending IP and the access list to deny it, with no shared filter set across the two surfaces.

SleekView reads both as paired sources. Each event row carries rule, action, IP, URI, method, and timestamp. The access list shows the same IPs with type (allow, deny, temp), reason, expiry, and last-hit columns. Saved views like Repeat offenders not yet denied join the two so triage becomes a single workspace. NinjaFirewall Pro still owns the rules and the engine; SleekView only adds the queryable surface.

NinjaFirewall Pro earns its keep by giving operators an extended event log and an IP access list with allow, deny, and temporary entries. The two surfaces together are the working set of a security review, and the default admin keeps them on separate screens. Triaging an active brute force campaign therefore means flipping between the log to find the offending IP and the access list to deny it.

SleekView joins both inside WordPress and renders them as one workspace. The firewall keeps owning the rules, the engine, and the access-list semantics. The team gets a triage surface with access-list context on every row, saved views for not-yet-denied repeat offenders, role scoping, and CSV exports that honour the active filter set, so the value of Pro's richer logging finally matches the work it makes possible.