• Hi, I’m comparing Wordfence (WF) and NinjaFirewall (NF). I’ve been using both for quite a while, but I’d like to stick with just one of them for simplicity and to avoid potential conflicts. Overall I think Wordfence has the broader feature set, especially since the introduction of the new Application Firewall and Threat Defense Feed.

    However, NF offers a wide range of granular controls over its policies on its “Firewall Policies” page – including a lot of “scan” and “sanitise” settings for various HTTP variables, cookies, and other things. I wonder if Wordfence also provides the same functionality? If not, why not?

    NF also adds several “HTTP response headers” such as “X-Content-Type-Options”, “X-Frame-Options”, “X-XSS-Protection”, etc. Does WF add these? Are they recommended?

    I guess I’m just wondering if I’m going to miss out on any additional layers of protection if I were to remove NF and therefore not have these scans and settings that are available on NF’s policies page.

  • The topic ‘Wordfence vs NinjaFirewall’ is closed to new replies.