From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Do you block outbound ports?
Date: Sun, 21 Aug 2011 12:10:46 +0000 (UTC) [thread overview]
Message-ID: <loom.20110821T135349-730@post.gmane.org> (raw)
In-Reply-To: CAN0CFw2hfsq=Eo+Hwrn0nrs1yLu7_aKMWRhC9DdUc1_WwEszUw@mail.gmail.com
Grant <emailgrant <at> gmail.com> writes:
> Do you block outbound ports
> with a firewall or only inbound?
Logging outbound traffic, and then looking
at (analyzing) the outbound traffic may
be of interest to you. Two extremes
are wildly unpredictable: human imaginations
in a collective where outbound traffic policy
is constantly morphing; like a collection
of young computer scientist at your local
university. Like Alan alluded to, a basic
nightmare of intellectual argument as to
monitoring or blocking outbound traffic.
In the case where the services utilized
are more consistent in a pattern that is some
what consistent over time. For example a network
full of machines (literally machines for
physical process control) or servers offering limited
fixed services, then blocking outbound traffic
(that should not nor never exist) could make sense.
In a complex network, this may mean several different
firewalls with different policies on outbound
traffic.
The later network may be a candidate for
extensive monitoring, pattern detection and
profiling of outbound traffic; with subsequent
port blocking. If it's not used, block it, some
would say. Whether its is more work than of value,
can only be decided by the logs and the policy
requirements of that network's owner.
hth,
James
prev parent reply other threads:[~2011-08-21 12:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-20 17:38 [gentoo-user] Do you block outbound ports? Grant
2011-08-20 19:02 ` Alan McKinnon
2011-08-21 4:31 ` Pandu Poluan
2011-08-20 19:11 ` [gentoo-user] " Nikos Chantziaras
2011-08-20 22:41 ` [gentoo-user] " Paul Hartman
2011-08-21 12:10 ` James [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=loom.20110821T135349-730@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox