mellowd wrote:
It's very handy. You can have a single place to control all firewall polices for all sites very easily. A site simply becomes an address block to create rules for.
You can also have people VPN into a single core firewall, where you have rules to give access to any part of your network.
If you're working with a 3rd party and need an IPSec tunnel to them, you only need 1 tunnel from the core firewall, and all sites have access through that tunnel.
You can have a block of IP's which get NAT'd to servers/DMZ's at any part of your internal network. Need to move a server from site A to B? You can do that and just need to change the internal NAT address. Outside stays the same.
Yes you'll need a bigger pipe, but you're not paying for access from all your other sites. Is it a single point of failure? Not if you're running the firewall in an HA pair across 2 datacentres.
So yes, the advantages are plenty. I thoroughly recommend a core hosted firewall for whatever design I'm doing for our customers
cons, your managed firewall provider is unresponsive, every time you need to make a firewall change you have to call your provider, sit in some queue, get a tick opened, and wait a few days for the implementation. you can't control the security aspects of your firewall, unless of course your provider is running a multi context firewall and provides you with direct access to your context so you can manage it yourself.