What's real successful for us is ingress/egress filtering; not blocking 
bunches of certain ports but rather defining which ports traffic can 
flow outward from, and assuming that your firewall denies all 
unsolicited inbound traffic by default.

for instance - I have 3 ip addresses accessing the internet. One machine 
can browse the web (cat. a - http/80, https/443). Another can access ftp 
sites (cat b - ftp/21). Another is just for mail, (cat c - smtp/25, 
pop/110). So 3 categories, a, b, c.

At the firewall the ALL out bound traffic from all internal address (our 
little netblock of 192.168.xxx.xxx) is first denied. Then category rule 
a comes next to allow out bound connections for ip 192.168.233.233 for 
http and https only. Another other machines needing only those default 
out bound connections go in the same group.

Then cat rule b is establed to allow machine 192.168.233.225 outbound on 
21. Any machines needing the same defaults go in this group also.

then cat rule c is established to allow for machines which only handle 
mail and can access only ports 25 and 110 outbound connections, and 
again all other machines needing these services also go in this group, 
which can also include some of the above mentioned ip address.

All unsolicited inbound is denied by default, and a dozen or so certain 
ports are always denied inbound, like ftp, ssh, stuff we don't use or is 
dangerous to the internal net.

works great. also makes it impossible for unknown ips to be setup on our 
network and expect to connect... makes for a very smooth fast and 
reliable connection also since bandwidth isn't being eaten up by unknown 
processes....




-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to