From: Saad Faruque <faruque@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: netfitler against Trojans and worms
Date: Tue, 6 Jul 2004 03:51:32 +0600 [thread overview]
Message-ID: <1d7da3f4040705145133d55add@mail.gmail.com> (raw)
In-Reply-To: <200407051622.00035.Antony@Soft-Solutions.co.uk>
I just thought if i was missing out some thing. i will give some more
thought into it. including all of your suggestions. or may be try out
things the way u suggested to figure out how it goes. wish me luck.
and thanks a lot for all ur time and help.
Regards,
Saad
On Mon, 5 Jul 2004 16:21:59 +0100, Antony Stone
<antony@soft-solutions.co.uk> wrote:
>
>
> On Monday 05 July 2004 3:10 pm, Gavin Hamill wrote:
>
> > On Monday 05 July 2004 14:59, Saad Faruque wrote:
> > > i did find couple of sites ex.
> > > (http://www.doshelp.com/trojanports.htm) which lists some ports. but i
> > > really am not sure if u simply block all these ports if it will effect
> > > my clients regular internet activity. any alternative suggestions are
> > > also welcome :)
> >
> > My suggestion would to stop fire-fighting and instead turn the problem on
> > its head.
> >
> > Change your default policy from ACCEPT to DROP, and put in rules so that
> > people are allowed to access port 80, 443, etc. and only the ports they
> > actually NEED access to.
>
> I agree completely with this. Standard security practice is to "block
> everything which is not expressly allowed", and to allow only that which is
> known to be needed.
>
> In a later posting you say you don't know what to allow - one approach which
> is very effective is to block everything, allow web, email and dns, then wait
> until your users say "I can't do X", and then decide whether they should be
> allowed to do X or not.
>
> If it isn't you who makes the decisions about what they should be allowed to
> do, then ask the person whose decision it is to give you a list of all the
> applications they're supposed to be able to access on the Internet.
>
> In another posting you also said that you are not able to ensure the security
> of the machines in the internal network. A good way to deal with that is to
> apply the security policy above, but then LOG all blocked packets, and
> summarise them by source IP address on a daily basis. Anyone whose machine
> generates enough blocked traffic that it looks like it's infected with
> something gets a DROP (or REJECT) rule in the firewall until they clean up
> their machine.
>
> You don't have to say much to justify this - you are insisting that they clean
> their machines so that they don't spread things to other machines on the
> network. You can stop them spreading it to the Internet, but you can't stop
> them spreading to the local LAN.
>
> Regards,
>
> Antony.
>
> --
> Behind the counter a boy with a shaven head stared vacantly into space,
> a dozen spikes of microsoft protruding from the socket behind his ear.
>
> - William Gibson, Neuromancer (1984)
>
> Please reply to the list;
> please don't CC me.
>
>
prev parent reply other threads:[~2004-07-05 21:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-05 13:59 netfitler against Trojans and worms Saad Faruque
2004-07-05 14:10 ` Gavin Hamill
2004-07-05 14:46 ` Saad Faruque
2004-07-05 14:59 ` Gavin Hamill
2004-07-05 15:21 ` Antony Stone
2004-07-05 21:51 ` Saad Faruque [this message]
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=1d7da3f4040705145133d55add@mail.gmail.com \
--to=faruque@gmail.com \
--cc=netfilter@lists.netfilter.org \
/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.