Floodspark Counterespionage Firewall (CEF) helps you block reconnaissance or otherwise illegitimate traffic. CEF is like a web application firewall (WAF) but protects against intelligence gathering. CEF focuses on pre-attack protection and is designed to complement security plugins such as Wordfence or Sucuri.
So far CEF can:
* Fake out WPScan and bots by hiding your real usernames, instead supplying them with fake ones they will never be able to log in with.
* Defeat WPScan’s aggressive plugin and theme scans, also causing the scanner to terminate.
…as well as detect and block:
* Tor browser, with minor delay
* Chrome Incognito, with minor delay, over HTTPS
* Firefox Private Browsing, with minor delay
* Chrome-Selenium in its default configuration, with minor delay
* cURL in its default configuration
* Wget in its default configuration
* HTTP methods other than GET, POST, and HEAD
* Proxy probing
How does this work?
So! A hacker’s usual approach for hacking into WordPress sites includes using a tool like WPScan to find out usernames as well as which plugins and themes are installed. They’ll try to guess passwords for the user account(s) and also check vulnerability/exploit databases for any known vulnerabilities in any of the installed plugins or themes, and then try to hack into the site through those.
But! We’re aiming to disrupt that information gathering step of the attack. So when WPScan scans for usernames, we give out fake ones that don’t exist. So all the password guessing attempts will be in vain. When WPScan scans for any of 88.5k plugins that might be installed, we respond that every one of them is installed. Same with themes–when WPScan scans for 400 themes, we assert that they too are all installed.
So the attacker then has so much data they don’t know what to trust. And they’ll launch attacks against plugins and themes that don’t exist, so the exploits will never work.
PS, WPScan is a legit tool that we love and just use as an example.
Endurance Cache / Endurance Page Cache (perhaps installed by your hosting provider) will likely cause issues when it caches blocked pages. Setting this to “Off (Level 0)” is recommended. This is found under Settings > General > Endurance Cache in you admin dashboard (see screenshot #6). We are looking into a workaround.
Cyber Intent Blog
The Floodspark Cyber Intent Blog uses this plugin and is all about just that, cyber intent. Here we will cover the art and science of it and the developments in the Counterespionage Firewall (CEF) portfolio (CEF for WordPress and CEF Full) that turn these ideas into reality.
Stay up to date
Stay up to date with developments in the Floodspark portfolio: http://floodspark.com/uptodate.html
Feedback is greatly appreciated as we continue to shape Floodspark. Email us anytime – email@example.com.
How can I test CEF’s protection?
Use the Docker version of WPScan and the commands below. When prompted whether to update the database, you shouldn’t need to.
To verify that CEF deceives WPScan’s username scan, issue the following command:
docker run -it –rm wpscanteam/wpscan –url http://[yourbloghere.com] –enumerate u
To verify that CEF deceives WPScan’s plugin scan, issue the following command:
docker run -it –rm wpscanteam/wpscan –url http://[yourbloghere.com] –plugins-detection aggressive
To verify that CEF deceives WPScan’s theme scan, issue the following command:
docker run -it –rm wpscanteam/wpscan –url http://[yourbloghere.com] –enumerate t
Does CEF replace a Web Application Firewall (WAF)?
No. CEF and was specifically designed to leave protection against active web attacks to WAFs, which do it best.
Does CEF replace a host firewall?
No. CEF specializes in web-type intelligence and leaves the protection of other services to the host firewall.
Should I keep my WAF and host firewall?
Why would I use CEF?
CEF helps you earlier in the cyber-attack chain, during the Reconnaissance stage, to disrupt malicious research efforts. Remember, attacks do not necessarily correlate with the research origin(s).
What is an Intent Indicator?
An Intent Indicator is a trait derived from cyber threat intelligence that with high confidence indicates malicious intent. You do not need to activate every Intent Indicator powering CEF if for some reason one or more break your business traffic. E.g. A bank may want to block visitors using Tor to reduce fraud, while an online newspaper may recognize that readers and journalists have an interest in using Tor to avoid censorship and retribution.
How is an Intent Indicator different than an Indicator of Compromise (IoC)?
BLUF: An Intent Indicator is earlier than an IoC. You can see why this is beneficial.
An IOC indicates that a breach already took place, allowing you only to respond after the fact. Intent Indicators are the attacker’s traits, or Tactics, Techniques, and Procedures (TTPs), observable during the recon phase–traits, that with high confidence, would not belong to legitimate visitor traffic and behavior.
No hi ha ressenyes per a aquesta extensió.
Col·laboradors i desenvolupadors
"Counterespionage Firewall" és programari de codi obert. La següent gent ha contribuït en aquesta extensió.Contribuïdors
Interessats en el desenvolupament?
Registre de canvis
- Bug fix: async checks now also work for sites not located in the root folder
- CEF now disrupts hacker attempts at plugin and theme gathering/harvesting/enumeration
- CEF now disrupts hacker attempts at username gathering/harvesting/enumeration
- Fakes most current version of PHP
- Permitted HTTP methods safelisting
- Block proxy probes
- Blocked message appears for bad visitors
- General fixes
- Added Wget detection
- Commented out debugging/localhost settings
- Initial public release