In reply to Keith Davis.

The "falcon engine" is a solution to a problem that shouldn't exist if security was done correctly. That is, if security was placed here as it should be for optimal performance and effectiveness:

Attacker => HTTP server => PHP => **Security** => WordPress => Plugins

There would be no need to cobble together a separate caching solution and introduce yet another break point as wordfence has done.

But since security is placed after wordpress and after plugins, coming late to the party as it were, then they are left scrambling to fix a problem that they themselves created.

The only security/firewall that I'm aware of that does it correctly and blows all the current security plugins out of the water is ninja firewall. Here are benchmark comparisons with the 5 most popular security plugins showing the difference:
http://nintechnet.com/wordpress-brute-force-detection-plugins-benchmarks.html

ps I am in no way related to ninja, its creators, etc. just a wordpress user who is more and more surprised every day that no one makes mention of this critical difference in how security is done and how it should be done.