Discussion Locked

Firewalls scrambling my brains

0 helpful
16 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Packet Filters? Bastion Host? Circuit Gateways? Application Gateways? Software vs Hardware solution! DMZ? Jeeze Louise!!, I am already a week late turning in my recomendation and the more I read the more I am confused. We are a small company and this will be my first ever Firewall installation/administration. We are setting up ColdFusion Pro Server 4.5 (as our web server) on top of IIS 4 with SP6a (SQL 7.0 also installed on same machine) all behind a NAT'd router that our ISP manages. We have a fractional T1 for our connection.

We will be hosting a web site that will require a Firewall more expensive than we can afford. I looked for facts on firewalls but what I end up with is "It dices, slices, its waterproof, it flies, it cures cancer! ... " PLEASE just some facts!
Can someone please help with suggestions on
*Products
*Placement(Router-FW-WWWRoot-Internal
Network or what?)
*How do I set it up?
*Things that will bite you later.
*Thing I do not know what to ask for.

Brian

16 replies

by bishopca

"We will be hosting a web site that will require a Firewall more expensive than we can afford"

Can you afford to lose the site to say vandals? Graffitti? Redirection?

I have been testing firewall from Zonealarm for the past couple of months. I am only using a 3 pcs on an ethernet, but I was impressed. It set itself up without my intervention and works well. The only problem is if it fails to initalize (this was due to my error)the machine MUST be restarted.

If you can afford to put up a site - protect it.

by gutridgesj

well then just go purchase Norton Personal Firewall 2001 2.5 for Windows/98/Me/NT/2000
or the norton internet security tools

those are cheap enough for you and easy to configure.

boom, done, move on

by gutridgesj

one more thing, a firewall will not protect you from people hacking your web site unless you restrict your website to specific ip addresses.

using a good security practices, keeping all the patches and fixes installed for the web software will dothat.

the firewall will just allow you to restrict all tcp/udp ports that you don't want hit. i assume you actually want people to connect to your web site

by sir_tuc

I don't think that a personal firewall
would have anywhere near enough "horse
power" for a company's frontline
defense.

by kevin m. hirahara

Part I of III

Hello,

There are 3 basic types of firewalls: Application Proxy, Stateful Inspection, and Packet Filtering (which is just a router with fancy filtering rules).

In the order of being the most secure, Application Proxy has always sat at the top of the heap with Packet Filtering at the bottom. There are system overhead and performance throughput issues that need to be dealt with when selecting one of the 3 types of firewalls. Application Proxy has enormous overhead - so to compensate, you?ll need to throw a higher-end system at it, in terms of hardware platform.

1.) Application Proxy ? A properly configured CyberGuard Firewall has NEVER been hacked and is used in abundance by the US military (and Citibank) as theirpreferred black box. App Proxies are the most expensive firewall because you need to procure adequate hardware to maintain adequate performance.

2.) Stateful Inspection ? Checkpoint Firewalls do maintain the largest market share to date in termsof a business installation base. Cisco PIX offers stateful connection oriented security as well and is gaining ground in terms of firewalling. The reason for Cisco?s increase in marketshare is that they are delivering Routers that can have the firewalling features enabled simply by inserting a key into the router. Stateful Inspection technology is considered to be the firewall of choice today. They are very simple to use, install, configure, and maintain while not compromising organizational security.

(continued on Part II)?

by kevin m. hirahara

Part II of III

(Continued from Part I)...

3.) Packet Filtering ? Ignore these. They aren?t considered ?Real? firewalls to security experts. Might as well put a Linux box in place. Never use an Open-Sourced O/S as a firewall O/S. Too many people have code to access and manipulate the kernels.

Checkpoint probably has the most varied of features of all the firewalls. They offer VPN connectivity (as do Cisco), High Availability options, Load Balancing, ISP Redundancy for both Inbound and Outbound activity, and is manipulating towards the IP version 6 (as is Cisco?s IOS).

The support base for Checkpoint is abundant ? you can locate Technical support (CCSA?s or CCSE?s) in every major US city. The lack of support is not an issue with Checkpoint nor Cisco PIX. The Application Proxy brands, you WILL have problems in terms of obtaining adequate Technical Support ? most times, you will be relying on the vendor (watch out, if that?s the case).

Checkpoint is higher in cost than Cisco but has many more features that enable it to operate in a web farm or high volume, internet interaction type of business organization. Cisco PIX is plenty adequate for a mid-sized business and is the most cost effective to implement.

4.) Personal Firewalls ? Never to be used as a firewall to protect a commercial environment. Might as well as leave the front door to your company unlocked at night.

I personally prefer Checkpoint in my organization. Checkpoint products offer the widest range of functionality, scalability, and technical support over any comparable firewall in a large enterprise organization.

Remember the saying, "No one ever gets fired for buying IBM"? This also rings true for Checkpoint products.

(continued on part III)...

by kevin m. hirahara

Part III of III

(continued from Part II)?

1.) As to Placement?

[Public internet]
|
[csu /dsu]
|
[internet router]
|
[FIREWALL] - [DMZ]
|
[internal lan]

The csu/dsu is used for a PRI or T1 connection to the Internet. If you are using xDSL, simply replace the csu/dsu and the internet router with your xDSL modem. The DMZ (?demilitarized zone?) is where you should be placing your webservers and any other resource that will be accessed by the public.

This means your firewall will require 3 nic cards, or network segments: Internal (aka, ?trusted?), Public (aka, ?untrusted?), DMZ (the ?demilitarized zone?).

2.) As to setting it up? This actually depends upon the Brand of firewall. Configs vary so widely that it?s like apples and oranges in terms of difficulty to simplicity.

3.) As to Things that will ?bite? you?

DNS is a requirement ? if your Firewall is not capable of DNS, you will need to configure a primary DNS on your internal network in order for InterNIC registration to point to your site. NAT (?Network Address Translation?) is used to ?hide? your internal address scheme from the public.

4.) As to Products?

CyberGuard is highend ? Application Proxy, Very Expensive to maintain. I have two in my organization.

Checkpoint is also considered highend but is Stateful Inspection Technology. Expensive, but its an EXCELLENT product with support that can be found everywhere.

Don?t even look at personal firewalls or packet filtering firewalls ? your job is on the line. The firewall you select will protect your company as well as your position.

I hope this information helps. If you have other questions, you may e-mail me directly and I can try to assist.

Good Luck to you in your quest for a firewall.

Regards,

Kevin.

by shanghai sam

If your still looking for info, please email me. You've asked a bit much to cover with a short answer.

mike_mds@yahoo.com

by sir_tuc

Has answered many questions through
personal email. Still an on going
event. Thanks a bunch!

by ve3yy

Well Brian, I'm not sure what you want to use as a firewall, but if it is generic information you want, here is some advice.
Look for a firewall that has proxies and can also handle NAT ( Static NAT for sure ). If you put your server on a DMZ off the firewall you can protect your servers. A firewall that can have 8 or more interfaces makes configuration easier AND increases the security. Put servers that respond to Internet connections on separate DMZs. Put two network interfaces in the servers and connect the servers to two DMZ connections. Include rules in your firewall that will allow the Internet interface to talk only to connections from the Internet and also put rules in the firewall so that the "internal DMZ" interface can communicate with your internal networks. Do not put any rule on the firewall that permits the systems on the DMZs to initiate any traffic to the Internet or the internal networks. If your servers are compromised in any way the most harm the hacker cando is trash the systems on that pair of DMZs. The firewall will prevent any of the systems on the DMZs from initiating any communication to any other network. Use proxies where you feel that the information contained with in the packets may contain bad data such as viruses or scripts. Use a good anti-virus system.
There are many ways to configure a firewall and the method I've described above is just one of them. You have to look at your corporate security policy, judge the potential risk, ask basic questions like "If someone trashes this server, will get fired?". Hope this helps.

This discussion is closed to new replies.