Question

  Asked: Jun 15 2005   5:00 PM GMT
  Asked by: AmyKucharik


Demilitarized zone using iptables?


Security management, Product/service procurement, Security products, Security, Management, Administration, Architecture/Design, Features/Functionality, Installation, Signature updating/Management, Network security, Firewalls, VPN, Intrusion management, Incident response, Forensics, Wireless

Hi,
I'm the Assistant Editor for SearchEnterpriseLinux.com. One of our users, "ruhi," posted the following question. Can you help?

"I have to plan and design a demilitarized zone using iptables. How can I do this?"

You can post your answer here on ITKE, or reply to mailto:editor@searchenterpriselinux.com?subject=iptables

Thanks!
Amy Kucharik
Assistant Editor,
SearchEnterpriseLinux.com

TechTarget

117 Kendrick Street, Suite 800
Needham, MA 02494

Office: 781-657-1451

Subscribe to Alerts! Get questions and answers delivered to your Inbox.


E-mail me updates on this question



   SUBSCRIBE

hidden modal window

Answer Wiki (Improve, edit or add to this answer)


 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0



You can certainly use iptables to build a basic "firewall" architecture. part of that structure would be DMZ area. another approach you could take is to use the iptables as server firewall, and block selected services.

You would need a routing functionality also , for which you could use any LINUX based routing daemon or a more mature router (cisco) ?

Dharminder Dargan
  • AddThis Social Bookmark Button

Browse more Questions and Answers on Security, CIO and Microsoft Windows.

Looking for relevant Security Whitepapers? Visit the SearchSecurity.com Research Library.


Discuss This Answer


You must be logged-in to discuss a question. Log-in/Register

sonyfreek  |   Jun 15 2005  9:08PM GMT

You can design your DMZ any way that you want it, but there are two generally practiced methods. The first is to have a firewall with three interfaces in it: Outside, Inside, and DMZ. The DMZ interface is not trusted by the internal network and all of your “expendable” servers and services should go there: ie the external DNS, Web Server, Mail Relay, IDS, etc. The internal network would be configured to allow port the email relay server through, but generally should not trust any connections from the DMZ into the internal network with that exception. Obviously, the external network shouldn’t be trusted at all and only necessary services should be allowed to access the Internet/outside from your internal hosts and DMZ services.

The second most popular DMZ setup is called “Barrier Reef.” With it, you configure two different firewalls (with different operating systems and firewall software) and install the DMZ between the two firewalls. Let’s call the one firewall the outside firewall and the other the inside firewall. The outside firewall has connections to the Internet and the DMZ. The Inside firewall has connections to the DMZ and the Internal network. In this case, the same rules are established as with a three interface firewall but you are “more protected” because if someone is capable of owning the one firewall, they may not have the expertise to crack the second one. Also, the ruleset on the second firewall should be more strict and selective of what it lets through.

Now, for the configuration of iptables… I suggest you use one of the front-ends to iptables to get you used to configuring rules. Later on, you may decide to take on the iptables ruleset directly if you are into that type of thing. I’ve used Shorewall before with a lot of success, but watch out with using a GUI on a production firewall. The easier it is for you to use, the easier it is for someone to hack it.

For setting up a three interface firewall, see <a href="http://www.shorewall.net/three-interface.htm." rel="nofollow">http://www.shorewall.net/three-interface.htm.</a>

SF

 

zottmann  |   Jun 16 2005  9:07AM GMT

Hi !!

Sonny gave an excelent explanation about how to set up a DMZ !!

As for a GUI frontend for iptables, I suggest you try Firewall Builder. It is really ease to use, and even has some wizards that helps you on building your initial set of rules.

Regards,
Carlos.

 

astronomer  |   Jun 16 2005  12:06PM GMT

Shortly after iptables came out, new riders published a book called: linux firewalls second edition. This book covers iptables in some depth and shows how to set up the standard architectures.
I have used this as a reference for three years now. It should have everything you need to know to set up the firewall section of your network.
If you have a specific question, let me know.
rt