From: Chris Brenton <cbrenton@chrisbrenton.org>
To: Sagara Wijetunga <sagaralists@yahoo.com>
Cc: netfilter <netfilter@lists.netfilter.org>
Subject: Re: Is this firewall good enough?
Date: Tue, 08 Jun 2004 08:38:47 -0400 [thread overview]
Message-ID: <1086698326.2008.31.camel@grendel> (raw)
In-Reply-To: <20040608091436.84113.qmail@web14712.mail.yahoo.com>
On Tue, 2004-06-08 at 05:14, Sagara Wijetunga wrote:
>
> 1. Does this effectively offer connections ONLY to the
> services I offer and nothing more than that?
Others have commented on your rules specifically, so I'll skip that
commentary. One thing I would like to point out however is that you are
exposing 11 services to Internet connectivity. That's 11 opportunities
for someone to find a way into the box.
> 2. Does the rule 2 create any security loophole?
#2 just lets in replies to outbound traffic. Its not so much a problem
as this:
17. /sbin/iptables -P OUTPUT ACCEPT
This rule reads "If you can find a way to exploit any one of the 11
exposed services, you can use any outbound transport to pull over your
rootkit".
> 3. This firewall allows passive as well as non-passive
> FTP connections. Is passive FTP connections a
> security threat?
Nope, because it will be handled via inspection in your RELATED rule.
> 4. Is this firewall good enough to protect the server?
> If no, could you kindly comment how could I improve
> further?
IMHO you have two problems:
1) Too many exposed services
2) You have configured the box to act like a client and a server
resulting in even more open conduits
Also keep in mind that iptables is a packet filter, not a proxy. This
means you are not seeing any protection to payload based attacks.
So in an ideal world you would want to break up these services across
multiple boxes. You would also want to limit them to server activity
only, and not permit them to generate random outbound sessions.
Now with all that said, it could be that you don't have the resources to
setup multiple boxes and you are stuck with this setup. If that's the
case, you are going to have to live with an elevated level of risk to
getting whacked.
Some other things you could do to mitigate this risk:
Setup an automatic patching system
Setup Tripwire or Aide to check system integrity
Setup another system to collect the logs off of this system
Setup Swatch or a similar tool to check these logs
Setup an IDS
HTH,
Chris
next prev parent reply other threads:[~2004-06-08 12:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 9:14 Is this firewall good enough? Sagara Wijetunga
2004-06-08 9:42 ` Feizhou
2004-06-08 9:57 ` Antony Stone
2004-06-08 15:03 ` Feizhou
2004-06-08 15:23 ` Antony Stone
2004-06-08 20:11 ` Feizhou
2004-06-09 9:48 ` Antony Stone
2004-06-09 10:03 ` Feizhou
2004-06-08 16:17 ` David Cannings
2004-06-08 20:14 ` Feizhou
2004-06-09 9:28 ` Jozsef Kadlecsik
2004-06-09 9:57 ` Feizhou
2004-06-09 11:05 ` Jozsef Kadlecsik
2004-06-09 13:18 ` Feizhou
2004-06-09 13:23 ` Feizhou
2004-06-09 8:36 ` Sagara Wijetunga
2004-06-08 9:44 ` Rob Sterenborg
2004-06-09 8:14 ` Sagara Wijetunga
2004-06-09 9:56 ` Rob Sterenborg
2004-06-09 15:12 ` Aleksandar Milivojevic
2004-06-09 15:15 ` Aleksandar Milivojevic
2004-06-11 14:24 ` Sagara Wijetunga
2004-06-08 9:55 ` Antony Stone
2004-06-08 12:38 ` Chris Brenton [this message]
2004-06-09 7:32 ` Sagara Wijetunga
2004-06-09 13:47 ` Chris Brenton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1086698326.2008.31.camel@grendel \
--to=cbrenton@chrisbrenton.org \
--cc=netfilter@lists.netfilter.org \
--cc=sagaralists@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.