Skip to main content

When Bob met Alice...


Often an organization will add firewalls in an incremental fashion and end up with an administrative nightmare to manage. The firewalls are loosely arranged in a hierarchy or mesh. The answer is to connect all the firewalls to a choke as illustrated above.
The latter design ensures that no matter what the diameter of the organization, only two firewalls will be traversed. The interconnect between the firewalls, the choke, becomes a great location for a IDS/IPS. A logical hierarchy can be created using rule sets and administration is simplified as connection rulesets are limited to an ingress and egress component.
When Bob met Alice, there was a choke between them.

Comments

Popular posts from this blog

easywall - Web interface for easy use of the IPTables firewall on Linux systems written in Python3.

Firewalls are becoming increasingly important in today’s world. Hackers and automated scripts are constantly trying to invade your system and use it for Bitcoin mining, botnets or other things. To prevent these attacks, you can use a firewall on your system. IPTables is the strongest firewall in Linux because it can filter packets in the kernel before they reach the application. Using IPTables is not very easy for Linux beginners. We have created easywall - the simple IPTables web interface . The focus of the software is on easy installation and use. Access this neat software over on github: easywall

No Scrubs: The Architecture That Made Unmetered Mitigation Possible

When building a DDoS mitigation service it’s incredibly tempting to think that the solution is scrubbing centers or scrubbing servers. I, too, thought that was a good idea in the beginning, but experience has shown that there are serious pitfalls to this approach. Read the post of at Cloudflare's blog: N o Scrubs: The Architecture That Made Unmetered Mitigation Possible

Should You Buy A UniFi Dream Machine, USG, USG Pro, or Dream Machine Pro?