2 ms·

So you're doing an onion firewall setup. How is this more useful than pfsense+cloudflare?

blackmirrorfw 4y ago
Hi downrightmike, We don't use pfsense, so we cannot comment on that. Blackmirror Firewall is designed to be used for IIS and other Windows based servers that connects to Cloudflares Edge, using their API to block at their perimeter. FreeBSD, linux, ubuntu and the like have great possible solutions already (apache reverse proxies, haproxy, fail2ban, etc), and these are great strategies in a layered approach to cover all possible surface attack vectors. We block both IPs and ASNs (ASNs can be disabled but both are on by default) With our software platform, you don't need to know how to use FreeBSD/Linux, etc with complex setups. We just need a custom Cloudflare API token and that's it, which blocks malicious IPS/ASNs across all domains/sub-domains account-wide. So in terms of usefulness, it's a much faster deployment, and more so for people that are being attacked as we speak because it can be deployed in 5-10 minutes for your average user to mitigate/stop the attacks quickly. In terms of features, perhaps it does the same thing as pfsense, we're not exactly sure. Usefulness comes from the fact that with the combination of Cloudflare Tunnels and Blackmirror, they can be leveraged to protect Windows-based HOSTS/VMs which Windows doesn't have a great solution that we know of. Cloudflare rate-limiter can be by-passed and WAF rules etc, via spoofing etc. Not sure how pfsense or of their limitations work but it likely also does what we do Also, when it comes to Layer-7 application attacks for instance, db instances can be easily consumed. There are just so many different techniques and strategies that are more beneficial for the black hats than there are for white hats. Our methodology is to block at the edge, because you can't get hurt if they can't even get in! You can read through the FAQ on our page which should give you a better understanding.

Hi downrightmike, We don't use pfsense, so we cannot comment on that. Blackmirror Firewall is designed to be used for IIS and other Windows based servers that connects to Cloudflares Edge, using their API to block at their perimeter. FreeBSD, linux, ubuntu and the like have great possible solutions already (apache reverse proxies, haproxy, fail2ban, etc), and these are great strategies in a layered approach to cover all possible surface attack vectors. We block both IPs and ASNs (ASNs can be disabled but both are on by default) With our software platform, you don't need to know how to use FreeBSD/Linux, etc with complex setups. We just need a custom Cloudflare API token and that's it, which blocks malicious IPS/ASNs across all domains/sub-domains account-wide. So in terms of usefulness, it's a much faster deployment, and more so for people that are being attacked as we speak because it can be deployed in 5-10 minutes for your average user to mitigate/stop the attacks quickly. In terms of features, perhaps it does the same thing as pfsense, we're not exactly sure. Usefulness comes from the fact that with the combination of Cloudflare Tunnels and Blackmirror, they can be leveraged to protect Windows-based HOSTS/VMs which Windows doesn't have a great solution that we know of. Cloudflare rate-limiter can be by-passed and WAF rules etc, via spoofing etc. Not sure how pfsense or of their limitations work but it likely also does what we do Also, when it comes to Layer-7 application attacks for instance, db instances can be easily consumed. There are just so many different techniques and strategies that are more beneficial for the black hats than there are for white hats. Our methodology is to block at the edge, because you can't get hurt if they can't even get in! You can read through the FAQ on our page which should give you a better understanding.